3.4. Managing OneNAND
The u-boot has been updated to include bad block management for OneNAND.
These updates also impacted behavior of existing OneNAND commands. This
section describes the new and modified commands added for the purpose.
3.4.1. Marking a bad block
To forcefully mark a block as bad:
For example, to mark block 32 (assuming erase block size of 128Kbytes) as bad
block - offset = blocknum * 128 * 1024:
3.4.2. Erasing OneNAND
To erase OneNAND blocks in the address range:
This commands skips bad blocks (both factory or user marked) encountered
within the specified range.
For example, to erase blocks 32 through 34:
22
OMAP3EVM# onenand markbad <offset>
OMAP3EVM# onenand markbad 0x400000
OMAP3EVM# onenand erase <stoffaddr> <endoffaddr>
or
OMAP3EVM# onenand erase block <stblknum-endblknum>
Note
The behavior of this command was modified.
Important
If the erase operation fails, the block is marked bad and the command aborts.
To continue erase operation, the command needs to be re-executed for the
remaining blocks in the range.
Platform Support Products
U-Boot
Managing OneNAND
Version 02.01.01.08