DM368 IPNC_MT5 4.0 boot problem

Hi,

Can u set the environment variable 'verify' as given below and try booting again.

setenv verify no

Thank you Akshita. It works!!!

But i am faced with new problem.

tftp boot doesn't work. I just download same image via network.

only differences is bootcmd and verify argue.

even I eliminate verify argue because it works before without the verify argue, but it doesn't work.

could you please give some advice?

Thank you.

Jay.

DM368 IPNC :>pri

bootdelay=4

baudrate=115200

bootfile="uImage"

setboot=setenv bootargs $(bootargs)

verify=no

serverip=192.168.1.210

ipaddr=192.168.1.208

ethaddr=00:01:02:03:04:05

netmask=255.255.255.0

gatewayip=192.168.1.1

network=192.168.1.0

dnsip=128.126.63.1

nfshost=192.168.1.210

rootpath=/opt/dm36x_ipnc4/Source/ipnc_rdk/target/filesys

bootargs=mem=48M console=ttyS1,115200n8 noinitrd ip=dhcp rw ubi.mtd=3,2048 rootfstype=ubifs root=ubi0:rootfs cmemk.phys_start=0x83000000 cmemk.phys_end=0x88000000 cmemk.phys_start_1=0x00001000 cmemk.phys_end_1=0x00008000 cmemk.pools_1=1x28672 cmemk.allowOverlap=1 cmemk.useHeapIfPoolUnavailable=1 lpj=1077248 nohz=off highres=off eth=$(ethaddr)

bootcmd=tftpboot 0x80700000 uImage_ipnc_dm368_nand; bootm 0x80700000

stdin=serial

stdout=serial

stderr=serial

ver=U-Boot 1.3.4 (Jun  9 2012 - 17:24:47) DM368-IPNC-4.0.0

Environment size: 838/131068 bytes

DM368 IPNC :>boot

TFTP from server 192.168.1.210; our IP address is 192.168.1.208

Filename 'uImage_ipnc_dm368_nand'.

Load address: 0x80700000

Loading: #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         #################################################################

         ######################

done

Bytes transferred = 3440032 (347da0 hex)

## Booting kernel from Legacy Image at 80700000 ...

   Image Name:   Linux-2.6.37_IPNC_DM365_4.0.0

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    3439968 Bytes =  3.3 MB

   Load Address: 80008000

   Entry Point:  80008000

   Loading Kernel Image ... OK

OK

Starting kernel ...

Hi,

Since the bootm command has been optimised for boot time optimisation, directing booting using tftp wouldn't work. Use the following command to flash the uImage to nand and then try booting. Change the boot command to the following.

tftpboot 0x82000000 uImage_ipnc_DM368;nand erase 0x500000 0x400000;nand write 0x82000000 0x500000 0x400000

setenv bootcmd 'nboot 0x80700000 0 0x500000; bootm 0x80700000'

I'm really appriciate your answer.

but as I mentioned from first post, I boot the kernel with tftp before nand boot.

I don't know why it doesn't work now. also recompile the uImage for nfs, and boot from tftp doesn't proceed.

User Guide for IPNC 4.0 reffered these things.

because why i'm still trying. I may miss something.T.T

im not sure how the kernel booted without flashing uImage to the nand in your case.  If you follow the IPNC 4.0 User Guide on how to flash the uImage before booting, it should work.