From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] CONFIG_ENV_ADDR incorrect in MPC8313ERDB.h
Date: Tue, 16 Dec 2008 15:58:00 +0100 [thread overview]
Message-ID: <4947C1F8.5090108@aimvalley.nl> (raw)
I built the latest u-boot for MPC8313E-RDB, flashed it, and ran into trouble
after saving my environment to flash.
I'm using git://git.denx.de/u-boot-nand-flash.git (I believe the "problem" is in
other gits as well).
I'm booting from NOR flash ('make MPC8313ERDB_33_config')
The problem is CONFIG_ENV_ADDR in MPC8313ERDB.h, it says:
#define CONFIG_SYS_MONITOR_BASE TEXT_BASE /* start of monitor */
#define CONFIG_SYS_MONITOR_LEN (256 * 1024) /* Reserve 256 kB for Mon */
#define CONFIG_ENV_ADDR (CONFIG_SYS_MONITOR_BASE + CONFIG_SYS_MONITOR_LEN)
I'm not sure what 'monitor' is, but the above makes CONFIG_ENV_ADDR = 0xfe040000.
This is incorrect since the resulting u-boot.bin is (in my case) 265356=0x40c8c bytes.
So the saveenv overwrites u-boot itself (in my case the av_ variable, causing
(k)malloc to crash every next reboot).
Although it is only a customization, setting the default CONFIG_ENV_ADDR to a correct
value would save 8313E-RDB u-boot users like me the trouble finding this.
"#define CONFIG_ENV_ADDR 0xfe080000" works fine for me.
reply other threads:[~2008-12-16 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4947C1F8.5090108@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--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