• State Answer Suggested
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 423 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.

IPNC DM36x SD CARD Boot issue

Justin_Liu
Intellectual 260 points

Dear all:

On SD CARD Boot mode, I erase nand flash and burn images to IPNC DM368 v5.1.0.

At the first boot I can mount filesystem, and runs well. But when I power off and boot again, it will error and show below logs.

Anyone can shed a light, and help to solve this issue?

Thanks.

===========================================================================

[    4.347894] UBI error: ubi_io_read: error -74 (ECC error) while reading 126976 bytes from PEB 3:4096, read 126976 bytes

[    4.383155] UBI error: ubi_io_read: error -74 (ECC error) while reading 126976 bytes from PEB 4:4096, read 126976 bytes

[    4.395413] UBIFS: recovery needed

[    4.400381] UBI error: ubi_io_read: error -74 (ECC error) while reading 11 bytes from PEB 9:6144, read 11 bytes

[    4.430841] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)

[    4.437909] Please append a correct "root=" boot option; here are the available partitions:

[    4.446505] 1f00            3072 mtdblock0  (driver?)

[    4.451701] 1f01            2048 mtdblock1  (driver?)

[    4.456785] 1f02            4096 mtdblock2  (driver?)

[    4.461972] 1f03           40960 mtdblock3  (driver?)

[    4.467053] 1f04            8192 mtdblock4  (driver?)

[    4.472212] 1f05           40960 mtdblock5  (driver?)

[    4.477293] 1f06           31744 mtdblock6  (driver?)

[    4.482436] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

[    4.490755] Backtrace:

[    4.493221] Function entered at [<c002e518>] from [<c02f4524>]

[    4.499058]  r7:00008000 r6:c2813000 r5:c0024660 r4:c0392be0

[    4.504815] Function entered at [<c02f450c>] from [<c02f4590>]

[    4.510703] Function entered at [<c02f4528>] from [<c0008f8c>]

[    4.516544]  r3:00000000 r2:00000000 r1:c2825f78 r0:c0316455

[    4.522291] Function entered at [<c0008d28>] from [<c00090e4>]

[    4.528128] Function entered at [<c0009050>] from [<c00084b4>]

[    4.534011]  r5:c0023dfc r4:c03923f8

[    4.537616] Function entered at [<c00083a4>] from [<c00433cc>]

[    4.543491]  r5:c00083a4 r4:00000000

===========================================================================

 Below is the entire log file:

8255.IPNC5.1.0 DM36X log.docx

===========================================================================

bootcmd

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

bootargs   dhcp   quiet

setenv 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 nohz=off highres=off clocksource=acpi_pm lpj=1077248 eth=$(ethaddr)'

===========================================================================

 

 

 

 

Best Regards,

Justin

  • 0
    TI__Genius 11000 points

    Hello,

    Please run "nand scrub" at u-boot prompt and try reburning the binaries via CCS and check if this issue persists

    PLease let us know the results

    Regards,

    Raghu

  • 0 in reply to Raghu Kudva
    Intellectual 260 points

    Dear Raghu:

     

    As what you said, I run "nand scrub" in the begin and burn binaries to NAND FLASH.

    After that, I setup bootcmd and bootargs, then boot.

     

    Below are the results between I using TFTP and SD CARD.

    ---------------------------------------------------------------------------------------

    TFTP:

    It can mount filesystem no matter how I reset or restart the power.

     

    SD CARD:

    It can only mount the filesystem at the first time.

    ---------------------------------------------------------------------------------------

     

    conclusion:

    It seems the SD CARD “install” script does not set correct ECC.

    Any comments?

     

     

     

    Best Regards,

    Justin

     

  • 0 in reply to Justin_Liu
    Intellectual 260 points

    Dear Raghu:

     

    To disable ECC, now I can use SD CARD burn images and boot from NAND FLASH.

     

    I modify ecc_mode from NAND_ECC_HW to NAND_ECC_NONE, and rebuild all the images to make a SD CARD.

    After I use SD CARD to burn images to IPNC, and now it can boot well now.

     

    Default board-dm368-ipnc.c

    131 static struct davinci_nand_pdata davinci_nand_data = {

    132         .parts                  = davinci_nand_partitions,

    133         .nr_parts               = ARRAY_SIZE(davinci_nand_partitions),

    134         .ecc_mode               = NAND_ECC_HW,   // change ECC_HW to NONE

    135         .options                = NAND_USE_FLASH_BBT,

    136         .ecc_bits               = 4,

    137 };

     

    board-dm368-ipnc.c

    131 static struct davinci_nand_pdata davinci_nand_data = {

    132         .parts                  = davinci_nand_partitions,

    133         .nr_parts               = ARRAY_SIZE(davinci_nand_partitions),

    134         .ecc_mode               = NAND_ECC_NONE,

    135         .options                = NAND_USE_FLASH_BBT,

    136         .ecc_bits               = 4,

    137 };

     

     

    --

    Best Regards,

    Justin

  • 0 in reply to Justin_Liu
    Intellectual 260 points

    Dear Raghu:

     

    Do you have any solution for this issue?

    or any comments?

     

     

    Best Regards,

    Justin

  • 0 in reply to Justin_Liu
    Intellectual 260 points

    Hi Raghu:

     

    Do you have any solution for this issue (ECC error)?

     

     

     

    Regards,

    Justin