This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

problem DM365, the kernel can not be started

Today, I want to establish a system of TFTP/NFS using minicom, I have successed to dans download the kernel uImage to the NAND. But when I try to lance the kernel, the carte reboot, I don't know why?

My command

tftp 0x80700000 uImage (No problem)

nand erase 0x400000 0x250000 (No problem)

nand write 0x80700000 0x400000 0x250000(No problem)

uboot 0X80700000 0 0x400000(no problem)

Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
   Image Name:   Linux-2.6.32-rc2-davinci1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1446728 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000

bootm

## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.32-rc2-davinci1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1446728 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...                            <---------------------------------The process stop at this line and reboot

Jumping to entry point at 0x81080000.

 LSP 2.10 BETA RELEASE
 VERSION: 2.10.008.02

U-Boot 1.3.4 (Mar  2 2009 - 11:50:39)

I2C:   ready
DRAM:  128 MB
NAND:  NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB)
Bad block table found at page 524224, version 0x01
Bad block table found at page 524160, version 0x01
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8)
Bad block table found at page 524224, version 0x01
Bad block table found at page 524160, version 0x01
2048 MiB
In:    serial
Out:   serial
Err:   serial
Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot:  0

My enviroment variable is this

bootdelay=4
baudrate=115200
ethaddr=00:0e:99:02:cd:cc
ipaddrdhcp
ipaddr=192.168.1.199
rootfstype=jffs2
bootfile=uImage
filesize=204FB0
fileaddr=80700000
netmask=255.255.255.0
ipaddr=192.168.2.199
bootcmd=nboot 0x80700000 0 0x400000; bootm
serverip=192.168.2.30
nfshost=192.168.2.30
rsetenv=rootpath
rootpath=/home/chemi/workdir/filesys
bootargs=mem=60M console=ttyS0,11520n8 nfsroot=192.168.2.30:/home/chemi/woe
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 1.3.4 (Mar  2 2009 - 11:50:39)

The ip of PC is 192.168.2.30, the ip of EMV is 192.168.2.199

I try to use an entire day to solve this problem, but failed, who can help me, in this tag, you can also find my file of uImge, thank you very much.

 

  • Hi Chen,

        Have you got your problem solved?  How did you solve this issue?  I also find my customed board rebooted automatically after the uboot posting "starting kernel".  Is there any problem with the watchdog?  Could you help me?

    Naroah

    Nov/11/2013