From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [u-boot] CRC / ECC protection of environment
Date: Wed, 21 Sep 2011 13:40:42 -0500 [thread overview]
Message-ID: <4E7A2FAA.7010802@freescale.com> (raw)
In-Reply-To: <CAACX+R20U5uHXQyLHxRKAE+CfUJ3pLXYajmsHxqy=BLvs4uM0Q@mail.gmail.com>
On 09/21/2011 04:59 AM, Arno Steffen wrote:
> Thank you for clarification. Although I am estonished, that after some
> time of running 2 devices come up with CRC errors (with just read
> access to environment!!).
> Unfortunatly I don't know a way just to change 1 bit in flash without
> changing the OOB data to simulate a toogling bit.
http://patchwork.ozlabs.org/patch/114262/ provides the ability to do a
raw write. Copy out the good data (including OOB), erase the block,
flip a bit in the RAM copy, and raw-write it all back at once.
What board and nand driver are you using?
-Scott
next prev parent reply other threads:[~2011-09-21 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 10:05 [U-Boot] [u-boot] CRC / ECC protection of environment Arno Steffen
2011-09-20 11:26 ` Wolfgang Denk
2011-09-21 9:59 ` Arno Steffen
2011-09-21 18:40 ` Scott Wood [this message]
2011-09-22 10:20 ` Arno Steffen
2011-09-22 13:54 ` Wolfgang Denk
2011-09-23 13:06 ` Arno Steffen
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=4E7A2FAA.7010802@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox