MX35LF1GE4AB-Macronix

MX35LF1GE4AB
MX35LF2GE4AB
11. SOFTWARE ALGORITHM
11-1. Invalid Blocks (Bad Blocks)
The bad blocks are included in the device while it gets shipped. During the time of using the device, the
additional bad blocks might be increasing; therefore, it is necessary to check the bad block marks and avoid
using the bad blocks. Furthermore, please read out the bad block information before any erase operation
since the bad block marks may be cleared by any erase operation.
Figure 22. Bad Blocks
Bad Block
Bad Block
While the device is shipped, the value of all data bytes of the good blocks are FFh. The 1 st byte of the
1 st and 2 nd page in the spare area for bad block will be 00h. The erase operation at the bad blocks is not
recommended.
After the device is installed in the system, the bad block checking is recommended. "Figure 23. Bad Block
Test Flow" shows the brief test flow by the system software managing the bad blocks while the bad blocks
were found. When a block gets damaged, it should not be used any more.
Due to the blocks are isolated from bit-line by the selected gate, the performance of good blocks will not be
impacted by bad ones.
Table 10. Valid Blocks
Density Min. Typ. Max. Unit Remark
Valid (Good)
Block Number
1Gb 1004 1024 Block
2Gb 2008 2048 Block
Block 0 is guaranteed to be good
(with ECC).
P/N: PM2128 REV. 1.5, June 07, 2017
36