• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 470 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.

strange ipnc 2.6 for dm368 boot fail with uboot nand read error

Wonder Won
Intellectual 995 points

Hi, everyone,

      I encounter a strange uboot nand operation fail.  I use nand erease, nand write command to flash kernel and cramfs image, everything is ok, no any error message. Then I boot the system, uboot can read kernel and cramfs image, mount cramfs, run application with many error message. If I reflash system, the problem is similar, just get different error message when run in application in rootfs. If I refalsh and mount cramfs rootfs in a different  address range in nand or replace the nand chip with other ipnc368 machine, the problem disappeared, system can boot and run normal.

     So, It seems nand flash damage just in some address range. But, Why uboot nand write command can't report error, is there no ecc generate and read back verify?  And when uboot boot and nand command read the cramfs image, no error report also(uboot can't find camfs error, linux find error untill run application in cramfs), is there no ecc check?

     How to fix this issue?

  • 0
    Intellectual 995 points

    nobody kown this issue? I have found serveral machines with this issue in 100 machines after long time user filed deploy

  • 0
    Prodigy 170 points

    Dear Sir,

    Can you tell us which sensor version that you use? In addition, please provide the boot commnads to us.

    Of course, you can burn the binary files with the following boot commands and then try it again. Thanks.

    Boot commands for DM368 Ver2.6:

    set ipaddr 10.2.1.5;set serverip 10.2.1.218;set ethaddr 00:0C:0C:A0:FF:FA;saveenv;reset
    tftpboot 0x80700000 uImage_ipnc_dm368_2.6.0;tftpboot 0x82000000 cramfsImage_ipnc_dm368_2.6.0

    nand erase 0x500000 0x1000000;nand write 0x80700000 0x500000 0x200000;nand write 0x82000000 0x700000 0xe00000

    setenv bootcmd 'nand read 0x82000000 0x700000 0x0E00000;nboot 0x80700000 0 0x500000;bootm 0x80700000'

    setenv bootargs 'mem=48M console=ttyS1,115200n8 root=/dev/mtdblock3 rootfstype=cramfs ip=192.168.1.101:192.168.1.100:192.168.1.1:255.255.255.0:::off eth=00:0C:0C:A0:08:25';saveenv;reset

    Best Regards,

    Appro Support Team

  • 0
    Intellectual 995 points

    Hi, appro support team,

         My sensor is mt9p031, the boot command is

               setenv bootcmd 'nboot 0x80700000 0 0x500000;nand read 0x82000000 0x700000 0xE00000;bootm 0x80700000'

               setenv bootargs console=ttyS1,115200n8 root=/dev/ram0 rw initrd=0x82000000,14M ip=off eth=$(ethaddr) mem=46M

         But, I think the issue is irelation with image sensor or boot command. Because

    Wonder Won said:
    If I refalsh and mount cramfs rootfs in a different  address range in nand or replace the nand chip with other ipnc368 machine, the problem disappeared, system can boot and run normal.

  • 0 in reply to Wonder Won
    Genius 3475 points

    Can you check bad blocks in uboot with 'nand bad', then 'nand scrub' over that range if necessary.

    Regards.