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.

SK-AM62A-LP: Uniflash does not use Bad Block Management. Can AM62A be bricked?

Part Number: SK-AM62A-LP
Other Parts Discussed in Thread: UNIFLASH, SYSCONFIG

Hello TI.

We recently started to work with SK AM62A-LP. One of the activities we are focused on is usage of OSPI Nand Flash (W35N01JWTBAG) mounted in system. We want to understand how the driver used in the SDK handles Bad Block.

We noticed that Uniflash example ("sbl_uart_uniflash_stage2"), which is responsible to write binanies to OSPI appears to have no BBM verification. The only configuration related with BBM  in SysConfig is

And results deactivated

/* FLASH Object - initialized during Flash_open() */
Flash_NandOspiObject gFlashObject_W35N01JWTBAG =
.badBlockCheck = FALSE,

Maybe I am wrong, but I don't see any API to operate with Advanced Features with that OSPI mounted in Starter Kit in any example, and most importat in, in Uniflash firmware.

As it is known, NAND flashes can have issues in sectors during operations, thus, it is quite likely that any block will fail, and must be managed by SW that operates with device (Uniflash). As I assume Uniflash is not doing so, then it is possible that firmware downloaded after many cycles is corrupted, briking the board when is booted from OSPI.

Can this be possible? How TI manage this sitation with OSPI nand flash using the current SDK?