From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND flash - bad blocks
Date: Tue, 15 Jan 2013 11:33:20 -0600 [thread overview]
Message-ID: <1358271200.7463.0@snotra> (raw)
In-Reply-To: <008001cdf310$c2002c70$2901a8c0@dpn> (from dpn@switchfin.org on Tue Jan 15 05:09:16 2013)
On 01/15/2013 05:09:16 AM, Dimitar Penev wrote:
> Hi Scott,
>
> I have tried to do some more tests on the board with the NAND chip I
> have scrub-ed
>
> -I have done 'nand erase.chip clean'
Don't specify "clean". That will cause jffs2 cleanmarkers to be
written. Not all NAND chips can handle partial programming, and in any
case it's an unnecessary variable for figuring out the bad block
situation.
> and tried to probe different nand regions
> (I have 128MB RAM and 1GB NAND and I am not sure how I could dump the
> whole NAND at once)
> It seems the whole NAND is 0xFF
Including OOB?
> So I tend to think that nand scrub did a good think for me.
No, it didn't. You are ignoring the problem.
-Scott
prev parent reply other threads:[~2013-01-15 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 7:56 [U-Boot] NAND flash - bad blocks Dimitar Penev
2013-01-10 19:19 ` Scott Wood
2013-01-11 8:46 ` Dimitar Penev
2013-01-11 20:21 ` Scott Wood
2013-01-15 11:09 ` Dimitar Penev
2013-01-15 17:33 ` Scott Wood [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=1358271200.7463.0@snotra \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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