I am not expert but can someone post more details about bad block on ps3?
how recognize and manage badblock?
In xbox360 there's documentation about.
I found this basic information:
http://www.eetasia.com/ARTICLES/2004...9_MEM_AN06.PDF
http://139.138.48.19/pdf/NAND/Toshib...nGuide.pdf.pdf
http://wiki.laptop.org/go/NAND_Flash_Bad_Block_Table
and naturally samsung ps3 nand datasheet
http://www.trisaster.de/file/sony/ps...K9F1G08U0A.pdf
for example I don't know is this apply also at ps3 nand:
The standard factory location for the bad block byte is byte 517 (the 518th byte) of a NAND
page. If this byte is FFh, the block is good, otherwise, the block is bad (typically indicated by 00h).
This format for marking bad blocks is from SmartMedia card (NAND flash in a removable card
package) and was standardized by the SSFDC Forum (Solid State Floppy Disk Card – the former
name of SmartMedia). If additional bad blocks form during use, the block is marked bad.
Generally, this is possible even if the block that you are marking is considered bad. To distinguish
between factory marked bad blocks and blocks that go bad during use, two flag values are defined
in the SmartMedia format: 00h (for initial factory marked bad blocks) and F0h (for blocks that go
bad during system use).
An alternative approach to the “in block” method of keeping track of bad blocks is to maintain
a bad block table. However, where to you store a bad block table since blocks could be bad? For
NAND TSOP devices only, the first block of the NAND flash (block 0) is guaranteed to be good.
Thus, block 0 could be used to hold a bad block table if desired. However, at power up, many
systems simply scan the first page of each block to determine whether they are good or bad and
build a bad block table in RAM.
|
maybe is also important distinguish from "native" badblock and "during lifetime" badblock