• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 642 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Linux/DM3730: DM3730

Arunkumar
Intellectual 330 points
Part Number: DM3730

Tool/software: Linux

Hi Everyone,

What this line means while booting DM3730 -> At line 3011 of func nand_scan_tail in file nand_base.c ?

can anyone say what is the problem while it shows following error during nand whole chip erase?

NAND erase.chip: device 0 whole chip
Skipping bad block at 0x00000000
Skipping bad block at 0x00010000
Skipping bad block at 0x00020000
Skipping bad block at 0x00030000
Skipping bad block at 0x00040000
Skipping bad block at 0x00060000
Skipping bad block at 0x00070000
Skipping bad block at 0x00080000
Skipping bad block at 0x00090000
Skipping bad block at 0x10000000
Skipping bad block at 0x10010000
Skipping bad block at 0x10020000
Skipping bad block at 0x10030000
Skipping bad block at 0x10040000
Skipping bad block at 0x10060000
Skipping bad block at 0x10070000
Skipping bad block at 0x10080000
Skipping bad block at 0x10090000
Skipping bad block at 0x20000000
Skipping bad block at 0x20010000
Skipping bad block at 0x20020000
Skipping bad block at 0x20030000
Skipping bad block at 0x20040000
Skipping bad block at 0x20060000
Skipping bad block at 0x20070000
Skipping bad block at 0x20080000
Skipping bad block at 0x20090000
Skipping bad block at 0x30000000
Skipping bad block at 0x30010000
Skipping bad block at 0x30020000
Skipping bad block at 0x30030000
Skipping bad block at 0x30040000
Skipping bad block at 0x30060000
Skipping bad block at 0x30070000
Skipping bad block at 0x30080000
Skipping bad block at 0x30090000
Erasing at 0x3fff0000 -- 100% complete.
Ok

Thanks & Regards,

M.Arun kumar

  • 0
    TI__Guru 65405 points
    Hi M.Arun,

    The NAND blocks are checked during erasing procedure. If a block is bad it is marked as bad and its address is printed and written in the flash based bad block table. The information of bad blocks prevents bad blocks usage and the NAND memory continue to work properly.
    If the number of bad blocks is not very high you should not worry and continue to use that device.

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    Intellectual 330 points
    Hi Tsvetolin,

    Whether the controller determines these bad block using CRC??

    I am trying to write UBOOT in NAND anf boot from it.
    But while writing it is show same Bad block at some address.
    and not booting from NAND.

    Can you suggest any thing to overcome this problem?

    Thanks,
    Arun
  • 0 in reply to Arunkumar
    TI__Guru 65405 points

    Arun,

    " ...not booting from NAND... " - This seems not good. The problem with NAND is more serious then I suspect after the first post.
    I suggest you to erase the NAND several times and compare the list of bad blocks after each erase. If the addresses are the same after each erase you could try to force marking them. If the bad blocks are increased after each next erase the NAND seems not be usable more.
    You can find description of some useful commands about NAND diagnostic at the link below:
    processors.wiki.ti.com/.../AM35x-OMAP35x-PSP_04.02.00.07_UserGuide
    Also by making use of some error correction coding (ECC) techniques using nandecc command it is possible to workaround the problem (but it is not guaranteed).

    BR
    Tsvetolin Shulev

  • 0 in reply to Cvetolin Shulev-XID
    Intellectual 330 points
    Hi Tsvetolin,

    I am getting the same bad blocks as above after erase the nand chip several times.

    Is there any problem in configuration NAND flash, that can made some bad blocks??

    Please post your suggestions.

    Thanks ,
    Arun.
  • 0 in reply to Arunkumar
    TI__Guru 65405 points
    Arun,

    I suggest you to try to force mark bad blocks as it is described in the link in my previous post:
    OMAP3_EVM # nand markbad <offset>
    If this not solving the issue seems the NAND flash chip is not usable anymore.

    BR
    Tsvetolin Shulev