u-boot cannot leads kernel on OMAP35X EVM platform

It appears that you are using  a really old version of the u-boot and kernel.

Can you tell which board are you using? and its version?

Thanks for your suggestion, the version of kernel is uImage-0.9.7-orig , the version of u_boot is U-Boot 1.1.4,  they are come from OMAP35X_SDK_0.9.7,  which is CD-ROMS contains.  The board is OMAP35Xtm--EVM and version is TMDXEVM3503 03503-EVM.

Did you make any changes to the kernel?

For test, can you try booting the pre-built uImage shipped in the CD? OR can you confirm if you are already doing so?

Yes, I use the pre_built uImage shipped in the CD and not change it, but the result is the same.

Hi Jiang,

Can you please provide the environment variables configured in u-boot? issue "printenv" command from u-boot prompt.

Thanks,

Vaibhav

The environment i set is:

setenv get_kernel      run nand_kernel

setenv get_initrd      run nand_initrd

setenv nand_kernel     nand read 0x80000000 280000 200000

setenv nand_initrd     nand read 0x81600000 780000 1000000

setenv tftp_kernel     tftpboot 0x80000000 uImage

setenv tftp_initrd     tftpboot 0x81600000 ramdisk.gz

setenv bootargs_rd     mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960

setenv addip           setenv bootargs \$(bootargs) ip=\$(ipaddr):\$(serverip):\$(gatewayip):\$(netmask):\$(hostname):eth0:on

setenv boot_rd         run get_kernel\; run get_initrd\; setenv bootargs \$(bootargs_rd)\; run addip\; bootm 0x80000000

setenv bootcmd         run boot_rd

setenv bootdelay       20

setenv bootkernel

setenv bootkernel_1

Thanks!!!

Hi Jiang,

I could see you do not have network related environment variables, like "ethaddr", "ipaddr", "netmask", etc... And alos apart from this can you try giving "bootargs" directly, without parsing recursively (as done above). I just extracted it below from your environment variables above -

setenv bootargs       'mem=128M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,40M ramdisk_size=40960 ip=dhcp'

setenv bootcmd       run get_kernel\; run get_initrd\;bootm 0x80000000

The point I am trying to make here is, we have seen this kind of behavior if you fail to specify "MEM=" in your bootargs. I am just trying to minimize variables.

Thanks,

Vaibhav

Thanks Vaibhav, I have solved the problem!