From: Dennis Borgmann <dennis.borgmann@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [u-boot]automatic reset of variables to defaults
Date: Thu, 17 Nov 2011 16:46:32 +0100 [thread overview]
Message-ID: <4EC52C58.8030308@googlemail.com> (raw)
Hello u-boot users list,
I am experiencing a problem concerning variables being set and later
getting lost.
In order to boot a Linux on a quite small plattform (Eddy CPU:
http://sysbas.en.ec21.com/Embedded_CPU_Module--1904028_1904479.html ), I
have to reset the variable "OS_SDRAM" from its initial value of
"0x20000000" to "0x21000000". If I don't do so, the bootloader reports
problems extracting my kernel. This must be due to my kernel being
bigger than expected by u-boot.
These are the steps, that I take:
[code]
setenv OS_SDRAM 0x21000000
saveenv
reset
[/code]
Anyway, this way, it works fine.
Sometimes, the bootloader looses this configuration and resets its
variable "OS_SDRAM" back to its default value. Once, the bootloader has
reset this value, it cannot boot anymore(well, of course not, since I
had to manually alter this value in order to make it boot my linux).
Annoyingly, I cannot surely reproduce this error. I tried rebooting it
over 3 days in 2-minute-steps and the error won't occur. In addition, I
tried giving random input to the console of u-boot for 3 days (again in
2-minute-steps) and still the error won't come up.
Two questions:
1. What else might be the cause of this?
2. How could I prevent u-boot from resetting to its default value?
I'd be happy for any kind of help.
Best regards,
Dennis
next reply other threads:[~2011-11-17 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 15:46 Dennis Borgmann [this message]
2011-11-17 18:26 ` [U-Boot] [u-boot]automatic reset of variables to defaults Jerry Van Baren
2011-11-18 8:36 ` Dennis Borgmann
-- strict thread matches above, loose matches on Subject: below --
2011-11-17 15:44 Dennis Borgmann
2011-11-17 18:17 ` Wolfgang Denk
2011-11-17 18:26 ` Marek Vasut
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=4EC52C58.8030308@googlemail.com \
--to=dennis.borgmann@googlemail.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