From: Thomas Gleixner <tglx@linutronix.de>
To: Shen Aaron-r62966 <Aaron.Shen@motorola.com>,
"'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: How to verify the ECC code for NAND Flash do work
Date: Tue, 09 Mar 2004 08:41:30 +0100 [thread overview]
Message-ID: <200403090841.30564.tglx@linutronix.de> (raw)
In-Reply-To: <01139FC052A0D411900B00508B9535FC102796CD@ZCH07EXM04.corp.mot.com>
On Tuesday 09 March 2004 06:47, Shen Aaron-r62966 wrote:
> Hello all,
>
> I have modified the ECC part of code in my Linux system, but I don't know
> how to confirm that it does work.
Why did you modify the code ? It is stable and tested.
> One way I'm thinking of is to get a NAND
> Flash with bad block somewhere inside it.
The bad block is not related to ECC. Bad blocks are skipped. They aren't read,
writted, erased.
>1. A suitable probram to create a period of bad block
> inside a normal NAND Flash is needed.
You have to set the bad block marker. This can be done from userspace. Have a
look at utils/nandwrite.c
> What's the result if the ECC part fails?
The raw data on flash are returned to the caller with an errorcode. If ECC
fails completely then the data will be lost in the most cases.
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2004-03-09 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 5:47 How to verify the ECC code for NAND Flash do work Shen Aaron-r62966
2004-03-09 7:41 ` Thomas Gleixner [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=200403090841.30564.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=Aaron.Shen@motorola.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox