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 flash bad blocks on DM365

Hello,
I'm starting to use DM365, there two questions about nand flash bad blocks as below need your help, Thanks.
a. UBL is small and loads u-boot to RAM from flash for running, but what's the solution to deal with nand flash bad blocks when loading u-boot in UBL, and loading kernel in u-boot? I checked the UBL source that it will use NAND_Copy() function to search the magic of u-boot, then load u-boot(includes many blocks) to RAM, but it seems don't take valid action when some blocks have loaded to RAM and one bad block exist, i think UBL needs skip the bad block and load the next block. Could you help taking a check?
b. Could you provide some method to deal with the nand flash bad blocks?

Thanks.
Best Regards
Sharp

  • Hi Sharp,

    Did you ever receive an answer to your bad block query? I am also intrigued as to what happens when UBL loads u-boot form flash into RAM!

    Sincerely,
    NickA

  • Hi NickAllen,

    I have not received any answer about this query.

    The detail issue i found is that RBL can't load UBL under  NAND Boot Mode when nand flash bad block exists between UBL margic descriptor and UBL for mass production. It seems  be caused  by the block number where the ubl is present defiend in  margic descriptor is absolute value from block 0, so RBL can't load UBL starting from the block number. Please help check this issue and give your advice. Thanks very much.