From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nand dump and nand bad block disagree
Date: Tue, 28 Feb 2012 17:40:47 -0600 [thread overview]
Message-ID: <4F4D65FF.4070700@freescale.com> (raw)
In-Reply-To: <CAGGh5h0j-UG8kr6CRJsqbPPWwws==KLS7JBR6Kv=wogCT0Kfgw@mail.gmail.com>
On 02/28/2012 08:34 AM, jean-philippe francois wrote:
> Hi,
>
> I have an omap3 based board with a micron 4Gbit large page nand attached.
> when using software ecc, everything is fine.
>
> When using hardware ecc, ecc is ok (ie u-boot and ROM bootloader agree),
> but bad block detection is broken.
>
> Here is an OOB dump
> OOB:
> ff 44 bb 1e ba 45 87 f7
> f7 88 38 c7 d2 ff ff ff
> ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff
>
> According to the code in drivers/mtd/nand_base.c, bad block checking
> is done by reading OOB data at a particular position. For large page,
> this is at NAND_LARGE_BADBLOCK_POS which is zero.
>
> In the above OOB data, oob[0] is 0xff, so there is no reason
> for this block to be considered as bad. How can I sort this ?
Is this a 16-bit NAND? If so, the first two bytes have to be 0xffff,
unless the controller driver defines the bad block pattern differently.
Also please mention which version of U-Boot you're using. Top of tree
currently has broken nand dump (fixed with the latest nand pull request).
-Scott
next prev parent reply other threads:[~2012-02-28 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 14:34 [U-Boot] Nand dump and nand bad block disagree jean-philippe francois
2012-02-28 23:40 ` Scott Wood [this message]
2012-02-29 9:02 ` jean-philippe francois
2012-02-29 19:06 ` Mike Frysinger
2012-02-29 19:09 ` Scott Wood
2012-02-29 22:34 ` Mike Frysinger
2012-02-29 22:37 ` Scott Wood
2012-02-29 22:54 ` Mike Frysinger
2012-02-29 23:14 ` Scott Wood
2012-02-29 19:11 ` Scott Wood
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=4F4D65FF.4070700@freescale.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.