From: Frans Meulenbroeks <fransmeulenbroeks@yahoo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND bad environment block handling
Date: Sun, 11 Jan 2009 06:35:08 -0800 (PST) [thread overview]
Message-ID: <817622.67175.qm@web33604.mail.mud.yahoo.com> (raw)
In-Reply-To: <20090111132843.86CE0832E425@gemini.denx.de>
>
> That's a pretty risky setup because it is based on
> an incorrect
> assumption - on NAND, block become not only bad when being
> erased or
> written to, but also after a certain number of read
> operations is
> exceeded. Yes, there is a maximum number of reads per
> block on NAND!
> People like to ignore that... See for example the Micron
> Technical
> Note "Design and Use Considerations for NAND
> Flash Memory",
> http://download.micron.com/pdf/technotes/nand/tn2917.pdf
Thanks for the link. I was not aware of read degradation. That is what most manufacturers do not tell you.
>
> Time to look into UBI, me thinks.
For u-boot env settings??
My problem that the designated env blocks can be bad or become bad during the lifetime of the device. Not desirable especially not for expensive devices.
Frans.
next prev parent reply other threads:[~2009-01-11 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 15:19 [U-Boot] NAND bad environment block handling Frans Meulenbroeks
2009-01-08 16:06 ` Cote, Sylvain
2009-01-09 7:25 ` Frans Meulenbroeks
2009-01-08 19:57 ` Scott Wood
2009-01-09 7:21 ` Marcel Ziswiler
2009-01-09 21:23 ` Wolfgang Denk
2009-01-11 11:10 ` Schlaegl Manfred jun.
2009-01-11 13:26 ` Frans Meulenbroeks
2009-01-11 20:20 ` Schlaegl Manfred jun.
2009-01-11 13:28 ` Wolfgang Denk
2009-01-11 14:35 ` Frans Meulenbroeks [this message]
2009-01-11 21:56 ` Wolfgang Denk
2009-01-11 20:30 ` Schlaegl Manfred jun.
[not found] <mailman.2543.1231435349.2783.u-boot@lists.denx.de>
2009-01-08 18:27 ` Derek Ou
[not found] <mailman.2551.1231706115.2783.u-boot@lists.denx.de>
2009-01-13 14:55 ` David.Kondrad at onqlegrand.com
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=817622.67175.qm@web33604.mail.mud.yahoo.com \
--to=fransmeulenbroeks@yahoo.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