From: Shamile Khan <shamile@edgewater.ca>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] environment not being used
Date: 03 Feb 2004 19:47:40 -0500 [thread overview]
Message-ID: <1075855660.7664.95.camel@localhost.localdomain> (raw)
In-Reply-To: <20040131171252.96147C112A@atlas.denx.de>
Hi,
Just as a follow up, I conclude that U-boot treats flash reads exactly
as sdram reads i.e. 32-bit accesses. So its not just about the
environment variables. Most of the flash-based U-boot functionality
wouldn't work for us unless we modify all the commands that have access
to flash e.g md, imiinfo, bootm etc. A hardware fix (an 8-bit bus to our
byte-mode flash chip) seems like the right way to go.
Shamile
On Sat, 2004-01-31 at 12:12, Wolfgang Denk wrote:
> In message <1075423717.18221.233.camel@localhost.localdomain> you wrote:
> >
> > To get around this, we have a small program which is stored in FPGA
> > bitstream and runs in FPGA on-chip memory (called BRAM). This program
> > copies u-boot binary image from flash to sdram and jumps to it. This
> > allows U-boot to run. However the problem is that the environment
> > variables saved in flash are not being used even though U-boot has been
> > configured with the CFG_ENV_IS_IN_FLASH option turned on.
> > CFG_FLASH_BASE has been set to the flash base address of u-boot and when
> > I use saveenv the environment is saved at the proper offset
> > CFG_ENV_OFFSET. The only thing thats a bit different for my U-boot
> > configuration is that CFG_MONITOR_BASE is set to the sdram base address
> > where U-boot starts executing from instead of being set to
> > CFG_FLASH_BASE.
>
> Normally U-Boot attempts to read the environment when starting from
> the same position in memory where it will save it to when you issue a
> "saveenv" command. You will have to modify U-Boot such that the
> initialization reads from the "fixed" copy in RAM, while "saveenv"
> saves to the address in flash, performing the 16-bit-expansion needed
> for your setup. It seems obvious that a plain copy as usuall cannot
> work on your system.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> See us @ Embedded World, Nuremberg, Feb 17 - 19, Hall 12.0 Booth 440
> Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
> Drun'? 'm not drun'! You woudn' dare call m' drun' if I was sober!
> - Terry Pratchett, _Men at Arms_
>
next prev parent reply other threads:[~2004-02-04 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-30 0:48 [U-Boot-Users] environment not being used Shamile Khan
2004-01-31 17:12 ` Wolfgang Denk
2004-02-04 0:47 ` Shamile Khan [this message]
2004-02-04 20:30 ` Wolfgang Denk
2004-02-04 23:15 ` Shamile Khan
2004-02-04 23:34 ` Wolfgang Denk
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=1075855660.7664.95.camel@localhost.localdomain \
--to=shamile@edgewater.ca \
--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