• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 312 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Dm365 startup failed !

Jingwei Song
Prodigy 105 points

I find one thing interesting but depressed. Could you help me to analysis it ?

I use the cmd setenv in u-boot like below :

setenv bootargs 'mem=70M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=192.168.1.228:192.168.1.3:192.168.1.1:255.255.255.0::eth0:off eth=00:40:01:2B:64:60 video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=1 davinci_enc_mngr.ch0_mode=pal'

then bootm dm365, it startuped. Next, I reboot dm365, A strange thing happened. Dm365 couldnot startup and error comes.

IP-Config: Complete:
device=eth0, addr=192.168.1.228, mask=255.255.255.0, gw=192.168.1.1,
host=192.168.1.228, domain=, nis-domain=(none),
bootserver=192.168.1.3, rootserver=192.168.1.3, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.3
PHY: 1:01 - Link is Up - 100/Full
Looking up port of RPC 100005/1 on 192.168.1.3
Root-NFS: Server returned error -13 while mounting /tftpboot/192.168.1.228
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "mtdblock3" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c002d5f4>] (dump_backtrace+0x0/0x114) from [<c0306298>] (dump_stack+0x18/0x1c)
r7:00008000 r6:c3012000 r5:c0025808 r4:c04333d0
[<c0306280>] (dump_stack+0x0/0x1c) from [<c03062f0>] (panic+0x54/0x12c)
[<c030629c>] (panic+0x0/0x12c) from [<c0008fbc>] (mount_block_root+0x1e0/0x220)
r3:00000001 r2:c3027e98 r1:c3027f60 r0:c039c256
[<c0008ddc>] (mount_block_root+0x0/0x220) from [<c00090c0>] (mount_root+0xc4/0xfc)
r8:00000000 r7:00000000 r6:00000000 r5:00000000 r4:00200000
[<c0008ffc>] (mount_root+0x0/0xfc) from [<c0009268>] (prepare_namespace+0x170/0x1c8)
r5:c0025808 r4:c0432ee0
[<c00090f8>] (prepare_namespace+0x0/0x1c8) from [<c00084bc>] (kernel_init+0xe4/0x118)
r5:00000000 r4:c0432ca0
[<c00083d8>] (kernel_init+0x0/0x118) from [<c0042170>] (do_exit+0x0/0x668)
r5:00000000 r4:00000000


You can check more info in the log.

7271.Edit1.TXT

  • 0
    Guru 31670 points

    Song,

    There is no NAND device detected in after the reboot. Are you sure that you are running the same kernel image again?

    If you see the first log, you can see the NAND device getting detected, which is absent when you reboot. Just double check what is the configuration of the second 

    NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)

    2 NAND chips detected

    Another difference I found is that, you not reading the kernel image from NAND as you are running bootm command directly, where as in second boot your are running "boot" command which will execute "nboot 0x80700000 0 0x400000; bootm"

    Just double check all these points