From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] *** Warning - bad CRC, using default environment
Date: Thu, 20 May 2010 15:04:42 +0200 [thread overview]
Message-ID: <m2tyq267x1.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4BF4F3DF.7000507@ge.com> (Nick Thompson's message of "Thu, 20 May 2010 09:33:35 +0100")
Hi Nick,
> Yes, indeed! The warning was trying to let you know that your work flow is
> wrong. Flash can be eased in sectors. The env should be in a sector(s) on
> it's own. There is no need to erase that sector(s) to re-flash U-Boot.
>
> Erase only U-Boot before re-flashing U-Boot. This will keep all you env
> data (which is valuable) intact and the warning will not reappear. If it
> does reappear you've done /something/ wrong and the warning will catch
> that for you again.
Just for completeness, let me mention that we have configurations where
the environment is embedded into the U-Boot image, so there you have to
erase the env in flash to reprogram U-Boot. Furtunately one usually
updates U-Boot out of a running copy of it, so after the reflash a
"saveenv" solves this specific problem nicely ;)
Cheers
Detlev
--
Narren sind alle, die es scheinen, und die Haelfte derer, die es nicht
scheinen .. Jedoch ist der groesste Narr, wer es nicht zu sein glaubt
und alle andern dafuer erklaert.
--- Baltasar Gracian
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
prev parent reply other threads:[~2010-05-20 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 7:11 [U-Boot] *** Warning - bad CRC, using default environment anup behare
2010-05-18 7:55 ` Stefan Roese
2010-05-18 9:12 ` anup behare
2010-05-18 9:23 ` Stefan Roese
2010-05-18 9:28 ` anup behare
2010-05-19 15:24 ` Nick Thompson
2010-05-20 3:43 ` anup behare
2010-05-20 8:33 ` Nick Thompson
2010-05-20 13:04 ` Detlev Zundel [this message]
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=m2tyq267x1.fsf@ohwell.denx.de \
--to=dzu@denx.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