Re: linux booting

Hi,

in message <002301c24b03$038024f0$fc4bb73d@leeyang> you wrote:

quoted

quoted

I have a BDI2000,but I think I should debug the bootm
part of ppcboot,however someone says it is quite
difficult to do so( at least for me).

Well, it's not _that_ difficult. Try it out, so you get used to is ;-)

I wish it is not that hard,however I can not debug the kernel or
ppcboot according the  brief introduction in BDI manual.:(

There are some more hints at
http://www.denx.de/doc/TQM8xxL/debugging.html

I want to watch r3,r4,r5,r6,r7 register when ppcboot transferring
to kernel.Could you tell me how to get that? thanks a lot!

Start PPCBoot, setup bootargs etc., load  the  kernel  image.  Before
finally typing the "bootm" command set a (hardware) breakpoint at the
kernel entry point (= physical address 0x0000).

When hitting the breakpoint, print the registers...

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
You don't have to worry about me. I might have been born yesterday...
but I stayed up all night.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

hi,WD

There are some more hints at
http://www.denx.de/doc/TQM8xxL/debugging.html

I have read it before,but only for module or application,
not for kernel and ppcboot,someone told me because of
ppcboot's relocation,so it is difficult in some externd.
Anyway it helps some:)

quoted

I want to watch r3,r4,r5,r6,r7 register when ppcboot transferring
to kernel.Could you tell me how to get that? thanks a lot!

Start PPCBoot, setup bootargs etc., load  the  kernel  image.  Before
finally typing the "bootm" command set a (hardware) breakpoint at the
kernel entry point (= physical address 0x0000).

When hitting the breakpoint, print the registers...

Yes,it works:),and I can check thoes regs when entering kernel.
and I am sure ppcboot handle correct value to kernel now.

the kernel can boot and I can see some in the console now.
I replaced the ppcboot.h in the 1.1.6 with one in old version
so I think it is still bdinfo problem.

However,new ones come:
kernel can not find init in the ramdisk!
the initrd had been tested in the old kernel and can mount fs
and entering system.so a little strange:(

the only reason I am wondering is the compiler!
the file in the initrd were compiled with HHL1.2 ppc compiler.
and the kernel was created with eldk.
Is that make sense?

leeyang


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/