[Yaffs-archive] Re: Restore the bad block flag in OOB of NA…

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Charles Manning
Date:  
To: Paul, linux-mtd, yaffs list
Subject: [Yaffs-archive] Re: Restore the bad block flag in OOB of NAND flash
On Friday 18 April 2003 05:21, Paul wrote:
> Dear All,
>
>     How can I restore the 0xFF in the OOB[5]?   i understood the oob[5] is
>  the bad block indicator. The YAFFS set accidentally the byte to 0x00 . I
>  want to use JFFS2 but the eraseall command said they are invalid block. I
> am
>  sure that the block is health . So, I want to force set the oob[5] to
> oxFF, pls. how can i do? Thank you.

>
> Paul


Generally this is a bad idea to erase bad blocks since destroying factory
marked bad blocks can cause problems through the entire chip (not just the
bad block). eg. Some blocks are marked because a write to the block could
disturb data in another block.

More recent chips seem to have some hardware "fuse" blown to prevent bad
blocks from being erased.

One way to achieve what you want is to hack mkyaffs. mkyaffs erases the
blocks in the partition, but first checks for bad block markers. If you
comment out the check then it will erase the block regardless. This will set
all the bits in the block to 1 (including the bad block marker).

BTW: I am curious as to how YAFFS managed to mark your block bad.

-- Charles



---------------------------------------------------------------------------------------
This mailing list is hosted by Toby Churchill open software (www.toby-churchill.org).
If mailing list membership is no longer wanted you can remove yourself from the list by
sending an email to with the text "unsubscribe"
(without the quotes) as the subject.