|
|
|
|
|
|
Some memory chips have broken bytes at pages
Controller can not use this bytes to store data
So it skip this bytes
Flash-Extractor expects that data is sequential
So we must cut unused bytes
And fill free space at end of page with ff to keep same page size
Hardware bad bytes
Some memory chips is tested at factory
List of bad bytes positions gen be read from chip with special command
NAND_Reader read this positions and store them in 01_01.dump.bb file
Then we can use "Cut bad bytes" step in mix editor to remove bad bytes
Software bad bytes
Some controllers test memory chips by its own method
They form list of bad bytes and store it somewhere in memory
We do not know where they store it
And can not use it to remove bad bytes
So, before use Flash Extractor,
we need find positions of bad bytes and remove them
|
|
|
|
|
|
|
|
|
|
