From: Grant Erickson <gerickson@nuovations.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot 2010.12 Cannot Successfully Save Variables with Redundant NAND Environment
Date: Sun, 06 Feb 2011 12:41:02 -0800 [thread overview]
Message-ID: <C974475E.23E4D%gerickson@nuovations.com> (raw)
I recently updated my TI AM37x EVM from U-Boot 2010.09 to 2010.12 and
noticed that, in doing so, saveenv / env save no longer seems to work. The
following example demonstrates:
=> version
U-Boot 2010.12 (Feb 04 2011 - 16:12:51)
=> env print foo
## Error: "foo" not defined
=> env set foo bar
=> env save
Saving Environment to NAND...
Erasing redundant NAND...
Erasing at 0x3a0000 -- 100% complete.
Writing to redundant NAND... done
=> env print foo
foo=bar
=> reset
resetting ...
...
Hit any key to stop autoboot: 0
=> env print foo
## Error: "foo" not defined
However, I can successfully read and write NAND, for example, updating
u-boot.
Anyone else noticed this on OMAP-based boards? With NAND? With NOR?
Running a few more experiments, I find that I can entirely whack the
environment, set a variable once thereafter, but never again:
=> printenv resetenv
resetenv=nand erase 0x340000 0x1000 && nand erase 0x3a0000 0x1000
=> run resetenv
NAND erase: device 0 offset 0x340000, size 0x1000
Erasing at 0x340000 -- 100% complete.
OK
NAND erase: device 0 offset 0x3a0000, size 0x1000
Erasing at 0x3a0000 -- 100% complete.
OK
=> reset
resetting ...
...
*** Warning - bad CRC, using default environment
...
Hit any key to stop autoboot: 0
=> saveenv
Saving Environment to NAND...
Erasing redundant NAND...
Erasing at 0x3a0000 -- 100% complete.
Writing to redundant NAND... done
=> setenv foo bar
=> printenv foo
foo=bar
=> saveenv
Saving Environment to NAND...
Erasing NAND...
Erasing at 0x340000 -- 100% complete.
Writing to NAND... done
=> printenv foo
foo=bar
=> reset
resetting ...
...
Hit any key to stop autoboot: 0
=> printenv foo
foo=bar
=> env delete foo
Not implemented yet
=> setenv foo
=> printenv foo
## Error: "foo" not defined
=> saveenv
Saving Environment to NAND...
Erasing redundant NAND...
Erasing at 0x3a0000 -- 100% complete.
Writing to redundant NAND... done
=> printenv foo
## Error: "foo" not defined
=> reset
resetting ...
...
Hit any key to stop autoboot: 0
=> printenv foo
foo=bar
--
Principal
Nuovations
998 Alpine Terrace Suite 3
Sunnyvale, CA 94086-2469
US
T +1-408-749-0495
F +1-205-449-0495
M +1-408-489-5710
gerickson at nuovations.com
http://www.nuovations.com/
Best,
Grant
next reply other threads:[~2011-02-06 20:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 20:41 Grant Erickson [this message]
2011-02-06 21:19 ` [U-Boot] U-Boot 2010.12 Cannot Successfully Save Variables with Redundant NAND Environment Wolfgang Denk
2011-02-06 21:33 ` Grant Erickson
2011-02-07 10:28 ` Alexander Holler
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=C974475E.23E4D%gerickson@nuovations.com \
--to=gerickson@nuovations.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