All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul Wong" <paul.wong@digitalview.com>
To: <manningc2@actrix.gen.nz>, <linux-mtd@lists.infradead.org>,
	"yaffs list" <yaffs@toby-churchill.org>
Subject: Re: Restore the bad block flag in OOB of  NAND flash
Date: Fri, 18 Apr 2003 11:44:27 +0800	[thread overview]
Message-ID: <001401c3055c$dc8ec4e0$6c00a8c0@home> (raw)
In-Reply-To: 20030417204847.5409515144@desire.actrix.co.nz

Thanks  for suggestion. I will try it.

I am using the Samsung 16MB NAND flash . and separate 3 partitions.
/dev/mtd0 is used for kernel img; /dev/mtd1 for general file drive (YAFFS);
/dev/mtd2 for initrd.img. The yaffs driver is compiled by module. and set
"mount -t yaffs /dev/block1 /mnt/flash" in rcS (setup script). No format the
partition in the first mounting.
The drive is not always to use, it is just saved the config. file. So, I
dont clearly know why the yaffs is corrupt. I check the disk space by "du"
command. It said 100% used . And cannot remove any file in this /mnt/flash.
therefore , i think it is corrupted.

Any ideal??

Thank a lot.

Paul

----- Original Message -----
From: "Charles Manning" <manningc2@actrix.gen.nz>
To: "Paul" <paul@maypaul.com>; <linux-mtd@lists.infradead.org>; "yaffs list"
<yaffs@toby-churchill.org>
Sent: Friday, April 18, 2003 4:49 AM
Subject: 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 yaffs-request@toby-churchill.org with the text
"unsubscribe"
> (without the quotes) as the subject.
>
>

      parent reply	other threads:[~2003-04-18  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 17:21 Restore the bad block flag in OOB of NAND flash Paul
2003-04-17 19:14 ` Thomas Gleixner
2003-04-17 20:49 ` Charles Manning
2003-04-17 22:20   ` Thomas Gleixner
2003-04-18  3:44   ` Paul Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001401c3055c$dc8ec4e0$6c00a8c0@home' \
    --to=paul.wong@digitalview.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=yaffs@toby-churchill.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.