Re: debugging using bdi2000, unable to proceed.

In message [ref] you wrote:

Wolfgang Denk wrote:

quoted

in message [off-list ref] you wrote:

quoted

Could you give me a hand to help me figure out this issue on ebony?

I've read your story before, but I cannot help.

quoted

If I use "bootp" or "tftp" to load kernel image(linuxppc_2_4_devel from
BK) at address 0x01000000 and then issue "bootm", everything works fine.
I have also programmed the image into flash at 0xffe00000, but each time
when I issue "bootm 0xffe00000", it will get stuck at when trying to
mount NFS.

Technically there is absolutely no difference between both cases:  in
either  case  U-Boot  will  copy  and  uncompress  the  kernel to RAM
starting at physical adress 0x0000, and start it there.  I  have  not
the slightest idea whaty could cause a behaviour as described by you,
nor have I ever seen anything like that before.

Well, there _is_ one obvious difference: when you use "tftp" to  load
kernel  then  U-Boot  will  perform the initialization of the network
interface. You can perform a simple test for this:

Do a dummy TFTP download, and then try  to  "bootm"  the  image  from
flash. I bet it'll work.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
In C we had to code our own bugs, in C++ we can inherit them.

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