From: Wolfgang Wegner <wolfgang@leila.ping.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] environment in NAND
Date: Tue, 6 Sep 2011 16:22:42 +0200 [thread overview]
Message-ID: <20110906142242.GE21272@leila.ping.de> (raw)
In-Reply-To: <CAACX+R38SwZeo199cugVRfMQn8VMNALaUN3hjSJPmDtWzAUzwQ@mail.gmail.com>
Hi Arno,
On Tue, Sep 06, 2011 at 04:16:59PM +0200, Arno Steffen wrote:
> NAND is sufferered from Bad blocks and bit errors. Thats why usually
> exists a bad block handling and an ECC. Am I wrong, that I miss both
> on uboot for it's environment?
U-Boot 2010.06 already has bad block handling in the way that it
skips bad blocks during read and write. At least this is how I understand
the code in common/env_nand.c (writeenv(), readenv()).
However, it seems to me that some boards might run into problems
in case there really are bad blocks because there is no extra
space reserved to compensate for them in case of bad blocks.
But this is just a configuration issue.
(Just stumbled over this for openrd, my image needs 3 blocks of
0x20000 size each, env starts at 0x60000 and has size 0x20000 -
this looks fatal to me in case of a bad block within the first
4 blocks, or am I overlooking something here?)
Regards,
Wolfgang
next prev parent reply other threads:[~2011-09-06 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 14:16 [U-Boot] environment in NAND Arno Steffen
2011-09-06 14:22 ` Wolfgang Wegner [this message]
2011-09-06 14:23 ` Marek Vasut
2011-09-07 6:20 ` Arno Steffen
2011-09-07 7:02 ` Wolfgang Wegner
2011-09-07 9:34 ` Arno Steffen
2011-09-07 9:35 ` Wolfgang Wegner
2011-09-07 10:20 ` Arno Steffen
2011-09-07 11:07 ` Wolfgang Wegner
2011-09-15 22:34 ` 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=20110906142242.GE21272@leila.ping.de \
--to=wolfgang@leila.ping.de \
--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