Quote:
Originally Posted by geekmaster
From what I have seen in the mmc read and write functions in the u-boot source code, they do not do effective write wear-leveling. It is possible that the mmc was worn out by too many repeated writes to a limited area. One way this can occur is by mounting a swap file on the MMC. It should be possible to map out the bad areas, but some blocks may still be near end-of-life. FAT partitions support bad block mapping, so you can map out defective areas that way.
|
We
__should__ be able to re-map the bad erase block(s) for good erase block(s) at the device level.
These high capacity flash-cell base devices are "over built" with spares just because flash-cell building is sort of 'iffy' technology.
The internal device controller often can do the mapping transparent to the user, but this device looks like it will need a bit of manual help with the chore.
__AND__ I don't (yet) know if the mmc tools required are installed on this model kindle - we may have to compile them for the O.P.