NAND OOB data.

Atlant Schmidt aschmidt at dekaresearch.com
Mon Jun 20 07:13:45 EDT 2011


Andy:

  If you don't have the old bad block information saved
  away somewhere (a bad block table, a scrap of paper,
  etc.), then you *CAN'T* completely recover from this
  situation; the original bad block data for that chip
  is probably irretrievably lost.*

  You can mark all the blocks as "good", of course, and
  then exercise the chip a bit, marking bad blocks as you
  go. You'll probably never achieve the same depth of
  testing that the factory was able to achieve using
  voltage, temperature, and timing margining, of course,
  but the results may be "good enough".

                          Atlant


* A few chip designs apparently blow fuses for the
  factory bad sectors and these blown fuses prevent
  you from ever writing the OOB bits to the state
  that would indicate a good block. For chips of
  these designs, you can fully recover the factory
  bad block data.


-----Original Message-----
From: linux-mtd-bounces at lists.infradead.org [mailto:linux-mtd-bounces at lists.infradead.org] On Behalf Of ANDY KENNEDY
Sent: Friday, June 17, 2011 18:09
To: linux-mtd at lists.infradead.org
Subject: NAND OOB data.

I have overwritten my OOB data, to the point where all blocks are seen
as bad.  What do I do to recover from this?

Thanks,
Andy

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.



More information about the linux-mtd mailing list