From: Peter Barada <peter.barada@logicpd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND flash question
Date: Thu, 19 Sep 2013 16:25:32 -0400 [thread overview]
Message-ID: <523B5DBC.7080103@logicpd.com> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C639AD07CE@ex-mb1.corp.adtran.com>
On 09/19/2013 04:04 PM, ANDY KENNEDY wrote:
> All,
>
> We have a design that has NAND as a secondary device (not the boot
> device). The last four pages of the NAND flash are reported as bad.
> Should this be true for all NAND flash devices we have?
>
>
No, I wouldn't think so. Manufacturers qualify their parts and mark bad
blocks found during qualification testing. Most data sheets indicate
that the number of bad blocks marked bad during manufacturer is below a
set percentage(if above thent he part is rejected). Some parts that are
meant to be used during boot (such as NAND meant for OMAP parts) will
have certain blocks that are guaranteed good (i.e. the boot blocks).
Past that bad blocks could be anywhere in a particular device.
--
Peter Barada
peter.barada at logicpd.com
next prev parent reply other threads:[~2013-09-19 20:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 20:04 [U-Boot] NAND flash question ANDY KENNEDY
2013-09-19 20:25 ` Peter Barada [this message]
2013-09-20 15:27 ` ANDY KENNEDY
2013-09-23 17:02 ` Peter Barada
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=523B5DBC.7080103@logicpd.com \
--to=peter.barada@logicpd.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