Quote:
Originally Posted by hawhill
Note that the MMC is not - however, I wouldn't go as far as recommending to desolder the eMMC chip and replace it by another. At least if you never did SMD soldering before.
|
That would be a challange, to re-work the board.
I do have a Kindle-3, it is open, it is lying next to the photo stand...
But I haven't had the time (yet) to photograph the MMC part and locate its datasheet. I expect it will turn out to be a Hynix part, and Hynix is real good about publishing their datasheets.
In the datasheet we should be able to learn where (if) they put the erase-block(s) that serve as the bad block table, the details for unlocking it and updating it.
The erase-blocks used for the internal bad block table are usually on their own dedicated lock chain.
And sometimes the read/erase/re-program commands are different.
Since it appears that we only have to deal with one or two blocks, it should be practical to do this "by hand" (well, with general purpose commands).
Once that bad block which the driver keeps running into is gone, the driver might just return to 'operation as normal'.
Although I also agree that the driver could probably benefit from a touch of re-writing.
At the moment, I have lost interest in this subject.
Maybe when my own K3 starts to wear-out...