Re: kernel boot stuck at udbg_putc_cpm()

2010-07-12 Thread Shawn Jin
For some reason. This email was rejected. Resending... On Sun, Jul 11, 2010 at 11:26 PM, Shawn Jin wrote: > You're probably getting to the point where udbg is disabled because the > real serial driver is trying to take over -- and something's going > wrong with the real serial port driver.  Check

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-11 Thread Shawn Jin
> You're probably getting to the point where udbg is disabled because the > real serial driver is trying to take over -- and something's going > wrong with the real serial port driver.  Check to make sure the brg > config is correct (both the input clock and the baud rate you're trying > to switch

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-09 Thread Scott Wood
On Fri, 9 Jul 2010 00:35:43 -0700 Shawn Jin wrote: > I changed my toolchain and rebuilt the kernel image. This time all the > messages below magically displayed on the serial port. :-D Are all > these the early debugging messages? Yes, it's an alternate output for the regular console (there are

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-09 Thread Shawn Jin
I changed my toolchain and rebuilt the kernel image. This time all the messages below magically displayed on the serial port. :-D Are all these the early debugging messages? > Here is the kernel log buf dump. Anything suspicious? > > <6>Using My MPC870 machine description > <5>Linux version 2.6.33

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-07 Thread Scott Wood
On Tue, 6 Jul 2010 17:17:16 -0700 Shawn Jin wrote: > >> That was it. The value @0xfa203bf8 is 0x2001. The kernel > >> certainly moved forward till it stuck at the new place > >> cpm_uart_initbd() as shown below. > > > > Do you get any output from the serial port?  I'd have expected > > someth

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-06 Thread Shawn Jin
>> That was it. The value @0xfa203bf8 is 0x2001. The kernel certainly >> moved forward till it stuck at the new place cpm_uart_initbd() as >> shown below. > > Do you get any output from the serial port?  I'd have expected > something by the time you get to cpm_uart_initbd() -- in fact, the > ea

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-06 Thread Scott Wood
On Tue, 6 Jul 2010 16:08:26 -0700 Shawn Jin wrote: > On Tue, Jul 6, 2010 at 1:21 PM, Scott Wood > wrote: > > Hmm... try 0xfa203bf8 (assuming your muram/data node has reg = <0 > > 0x1c00>). It looks like commit > > 0x1c00>c2dd3529f35de9e2f51eba9bbf9969f5dc8382d4 > > changed the bootwrapper's cpm-

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-06 Thread Shawn Jin
On Tue, Jul 6, 2010 at 1:21 PM, Scott Wood wrote: > Hmm... try 0xfa203bf8 (assuming your muram/data node has reg = <0 > 0x1c00>). It looks like commit c2dd3529f35de9e2f51eba9bbf9969f5dc8382d4 > changed the bootwrapper's cpm-serial driver to allocate from the end of > MURAM instead of the beginning

Re: kernel boot stuck at udbg_putc_cpm()

2010-07-06 Thread Scott Wood
On Mon, 5 Jul 2010 00:23:45 -0700 Shawn Jin wrote: > Hi, > > I'm debugging the kernel (2.6.33.5) ported for a MPC870 board. The > changes are mostly based on the board adder875. The first thing I want > to test is the serial port. So I enabled CONFIG_PPC_EARLY_DEBUG and > CONFIG_PPC_EARLY_DEBUG_

kernel boot stuck at udbg_putc_cpm()

2010-07-05 Thread Shawn Jin
Hi, I'm debugging the kernel (2.6.33.5) ported for a MPC870 board. The changes are mostly based on the board adder875. The first thing I want to test is the serial port. So I enabled CONFIG_PPC_EARLY_DEBUG and CONFIG_PPC_EARLY_DEBUG_CPM, and changed CONFIG_PPC_EARLY_DEBUG_CPM_ADDR to 0xfa202008. M