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.

NAND bad blocks on dm368

After using the u-boot of dvsdk 4.02 almost all of my nand blocks were marked as bad!

This happened to 3 different boards (1 dm365 EVM, costume dm365 board and another costume dm368 board).

I had to use the "nand scrub" command to erase the bad blocks, but it also deletes all of the real factory bad blocks.

Is there any way to scan the NAND for real bad blocks after running "nand scrub"?

  • hello Friend,

    I did not use the same device exactly but I can guess that the uboot code is the same.

    See this post:

    http://e2e.ti.com/support/embedded/linux/f/354/t/128587.aspx

     

    Brandy

  • Thanks Brandy, but the problem is "nand erase" doesn't erase the bad blocks so it doesn't fix anything, and "nand scrub" erases all bad blocks - even the ones that are really bad and were marked that way from the factory... So I need a way to detect the blocks that are really bad (and not just falsely marked as bad). 

  • Sorry, I should have given you more info.  The problem for us was an unnecessary check in Uboot for the spare data to contain a certain value.  We changed UBoot to write those values into the spare memory.  Or just as a test, change uboot to not make those as bad blocks to see what happens.  Then, if I remember there are only a few lines regarding bad blocks so it should be easy to find and once the spare data problem was solved, the erase would work.

    Anyhow, it was just a thought.  Good luck then!

    Brandy