MVL 5.0 uImage hangs while booting (DM6446 DVEVM)

I use the same U-boot version ，but I can boot MVL5.0.however，my issue is the new kernel can not ping my server.Do you also boot via TFTP？

I just tried this on my DM6446 EVM; I was using the pre-built uImage-dm6446 file included in the dvsdk_2_00_00_22/PSP_02_00_00_140/bin/dm6446 directory.  I was able to boot fine via TFTP and was also able to ping my host from my EVM (log below)

-----

MontaVista(R) Linux(R) Professional Edition 5.0.0 (0801921)

156.117.95.149 login: root
Last login: Thu Jan  1 00:00:54 1970 on console
Linux 156.117.95.149 2.6.18_pro500-davinci_evm-arm_v5t_le #1 PREEMPT Wed May 20 01:14:17 IST 2009 armv5tejl GNU/Linux

Welcome to MontaVista(R) Linux(R) Professional Edition 5.0.0 (0801921).

root@156.117.95.149:~# ping 156.117.95.15
PING 156.117.95.15 (156.117.95.15) 56(84) bytes of data.
64 bytes from 156.117.95.15: icmp_seq=1 ttl=64 time=0.951 ms
64 bytes from 156.117.95.15: icmp_seq=2 ttl=64 time=0.614 ms
64 bytes from 156.117.95.15: icmp_seq=3 ttl=64 time=0.602 ms
64 bytes from 156.117.95.15: icmp_seq=4 ttl=64 time=0.630 ms
64 bytes from 156.117.95.15: icmp_seq=5 ttl=64 time=0.584 ms
64 bytes from 156.117.95.15: icmp_seq=6 ttl=64 time=0.686 ms
64 bytes from 156.117.95.15: icmp_seq=7 ttl=64 time=0.663 ms
64 bytes from 156.117.95.15: icmp_seq=8 ttl=64 time=0.677 ms
64 bytes from 156.117.95.15: icmp_seq=9 ttl=64 time=0.512 ms
64 bytes from 156.117.95.15: icmp_seq=10 ttl=64 time=0.449 ms
64 bytes from 156.117.95.15: icmp_seq=11 ttl=64 time=0.662 ms
64 bytes from 156.117.95.15: icmp_seq=12 ttl=64 time=0.672 ms
64 bytes from 156.117.95.15: icmp_seq=13 ttl=64 time=0.682 ms
64 bytes from 156.117.95.15: icmp_seq=14 ttl=64 time=0.614 ms
64 bytes from 156.117.95.15: icmp_seq=15 ttl=64 time=0.655 ms
64 bytes from 156.117.95.15: icmp_seq=16 ttl=64 time=0.668 ms
64 bytes from 156.117.95.15: icmp_seq=17 ttl=64 time=0.561 ms
64 bytes from 156.117.95.15: icmp_seq=18 ttl=64 time=0.559 ms
64 bytes from 156.117.95.15: icmp_seq=19 ttl=64 time=0.546 ms
64 bytes from 156.117.95.15: icmp_seq=20 ttl=64 time=0.659 ms
64 bytes from 156.117.95.15: icmp_seq=21 ttl=64 time=0.723 ms
64 bytes from 156.117.95.15: icmp_seq=22 ttl=64 time=0.445 ms
64 bytes from 156.117.95.15: icmp_seq=23 ttl=64 time=0.500 ms
64 bytes from 156.117.95.15: icmp_seq=24 ttl=64 time=0.593 ms
64 bytes from 156.117.95.15: icmp_seq=25 ttl=64 time=0.497 ms
64 bytes from 156.117.95.15: icmp_seq=26 ttl=64 time=0.516 ms
64 bytes from 156.117.95.15: icmp_seq=27 ttl=64 time=0.599 ms
64 bytes from 156.117.95.15: icmp_seq=28 ttl=64 time=0.621 ms
64 bytes from 156.117.95.15: icmp_seq=29 ttl=64 time=0.589 ms
64 bytes from 156.117.95.15: icmp_seq=30 ttl=64 time=0.497 ms
64 bytes from 156.117.95.15: icmp_seq=31 ttl=64 time=0.666 ms
64 bytes from 156.117.95.15: icmp_seq=32 ttl=64 time=0.558 ms
64 bytes from 156.117.95.15: icmp_seq=33 ttl=64 time=0.634 ms
64 bytes from 156.117.95.15: icmp_seq=34 ttl=64 time=0.538 ms
64 bytes from 156.117.95.15: icmp_seq=35 ttl=64 time=0.651 ms
64 bytes from 156.117.95.15: icmp_seq=36 ttl=64 time=0.594 ms
64 bytes from 156.117.95.15: icmp_seq=37 ttl=64 time=0.665 ms

--- 156.117.95.15 ping statistics ---
37 packets transmitted, 37 received, 0% packet loss, time 35992ms
rtt min/avg/max/mdev = 0.445/0.608/0.951/0.096 ms
root@156.117.95.149:~#

Thank you for the reply.

I guess that the silence after "........done, booting the kernel." most likely can be caused by execution of wrong instructions. Something could be wrong with entry point or other memory access issues, or the image could have been corrupted somehow during or after uncompressing. What can I do to check these things? Do you have other ideas?

I have seen similar situations happen in the past when loading incompatible kernel or when kernel gets corrupt somehow.  Normally this is resolved by using a known good kernel such as the pre-built one included in the dvsdk (see PSP directory).

Yes, I'm trying to boot the original uImage-dm6446 from dvsdk_2_00_00_22/PSP_02_00_00_140/bin/dm6446, it should be ok. And the MVL 4 kernel from LSP 1.20 PSP_01_20_00_014/bin/dm6446/uImage-dm6446) boots well!

I wonder what have changed in the boot process since MVL 4.

perhaps u-boot?  Try upgrading to u-boot 1.2.0 (that is what I am using).  Also, if you could post a log of your u-boot environment variables, that may help pin-point the issue.

Exactly!

Thank you, Juan!

I am using u-boot version 1.3.4 with Montavista 5.0.24 and I have the same issue. It seems that the uImage when it gets unzipped and felocate to RAM has the first 4 bytes as 60 00 00 00, not sure what it is. I  am wondering if you have resolved this issue and how. Thanks Regards Claudio Spinelli

I simply updated u-boot to 1.2 and the problem gone, so I did not dig deeply in these things.