• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 427 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.

NAND bad block with uboot, url, file system

Tao_SV
Intellectual 300 points

Hi,

NAND flash will have bad blocks. I want to know how the BBT handle it with the interaction with uboot, url, file system. 

URL, and uboot seems to be stored at specific locations. If these locations have bad blocks, will it still work? if not, how to solve it?

thanks in advance.

Tao

 

  • 0
    TI__Mastermind 37340 points

    Tao,

    The RBL expects UBL at a certain location, normally the beginning of flash; this is where it starts looking for it, but if it does not find it there it keeps searching the next few blocks (5 I believe); therefore if you have a bad block, it should be able to recover.... UBL programs location where u-boot can be found, hence u-boot can be moved around. 

  • 0 in reply to Juan Gonzales
    Intellectual 300 points

    I look at the document of NAND boot. Yes, the RBL search for Page 0 of Block i for magic number, if does not find it, go to search for Page 0 of Block i+1.

    But it does not solve my problem directly. Let me make it more clear in an example. Assume Block 1 and Block 2 are bad, and UBL is within a block size. Does it need to write UBL multiple times in different Blocks, like Block 1, 2, 3, 4, 5, etc?

    And the UBL also find U-boot at specific pre-determined locations, if the flash in that location is corrupted, how UBL load U-boot?

    thanks a lot.

    Tao