Hello, TI Experts,
Our customer sent us a question about NAND-boot with DM365 Linux-SDK .
Question:
UBL(ver1.65) can extract u-boot properly, even if bad-block is detected during u-boot image writing by like below command in the wiki.
http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility#Serial_Flasher_Usage
> sfh_<DEVICENAME>.exe -nandflash <UBL binary file> <binary application file>
Is this understanding correct?
Detail:
We also found the instruction in the DVSDK document like below.
TMS320DM365_Software_Developers_Guide.pdf (page21)
c:\> sfh_DM36x.exe -nandflash UBL_DM36x_NAND.bin u-boot-dm365-evm.bin
So, we think like below;
- During u-boot-dm365-evm.bin writing by sfh_DM36x.exe, sfh_DM36x.exe skip the bad-block & operate proper writing to next block, even if bad-block is detected.
- UBL can extract u-boot to DRAM properly to skip the bad-block & operate proper reading from next block, even if bad-block is detected.
Is this understanding correct?
Best regards,
