From: Bernhard Priewasser <priewasser@gmail.com>
To: MTD mailing list <linux-mtd@lists.infradead.org>
Subject: NOR "bad blocks"
Date: Thu, 27 Oct 2005 10:04:03 +0200 [thread overview]
Message-ID: <436089F3.806@gmail.com> (raw)
Hi all,
just a thought...
Same as NAND, NOR flashes mostly have an endurance of guaranted 100K
program/erase cycles.
If a block reaches this (theoretical) value, it should be recognized as
bad block if erase fails; e.g. not conaining only 0xFF after erase on
NAND. (I don't know if the "100K" erase cycle boundary is mostly
responsible for this)
But obviously a block can wear out on NOR too after the max. number of
erase cycles. (How) can this be recognized, handled?
--
Bernhard
next reply other threads:[~2005-10-27 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 8:04 Bernhard Priewasser [this message]
2005-10-27 8:21 ` NOR "bad blocks" Jörn Engel
2005-10-27 8:31 ` Bernhard Priewasser
2005-10-27 8:49 ` Jörn Engel
2005-10-27 9:09 ` Bernhard Priewasser
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=436089F3.806@gmail.com \
--to=priewasser@gmail.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