From: Grant Likely <glikely@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] My first embedded project
Date: Sat, 12 Feb 2005 01:14:33 -0700 [thread overview]
Message-ID: <528646bc050212001475fc6c92@mail.gmail.com> (raw)
In-Reply-To: <200502111457.39393.roger.larsson@norran.net>
On Fri, 11 Feb 2005 14:57:39 +0100, Roger Larsson
<roger.larsson@norran.net> wrote:
>
> Shouldn't it be possible to do this in two stages.
> 1) Have environment variables in flash/EEPROM so you can mount the CF disk
> 2) Run an autoscript(?) from that disk to change the variables (do not save)
> 3) Boot
>
Would it be safe to assume that you're using a VIIPro w/ a SystemACE
boot device? If so, is it also safe to assume that you want to do
this because your don't have a FLASH device? Are you booting off of
BRAM that is loaded as part of the FPGA image?
If all of the above is true, another way to go about it is to use a
two stage boot loader system. Create a very small boot loader that
lives in BRAM who's sole purpose in life is to load a more feature
rich bootloader off of the CF card from a predefined filename. The
second stage boot loader can then also read boot parameters from CF
and provide a boot console.
If you wish to use u-boot, you could get a simple 1st stage to load
u-boot and it's environment image from CF into SDRAM. u-boot then
becomes your second stage.
Wolfgang, regardless of the fact that the FAQ says that u-boot must
run out of FLASH, in this scenario it will be running out of SDRAM.
Now, from what I know, I cannot see this being a problem because with
the VIIPro+SystemACE there is no SDRAM initialization that the
bootloader is responsible for. Plus there is absolutely no FLASH
device available anyway. Do you see this as a problem? If so, what
are the likely issues that Roger may see?
Note; BRAM may be expensive so it is desirable to keep it as small as
possible; especially considering that the SystemACE loads the VIIPro
via JTAG. Big Image=Slow Boot. I would make the first stage loader
as dumb as possible.
At the risk of peeing in this particular pool; if there is still a
problem with running out of SDRAM then you may want to consider
RedBoot as your second stage. Word of warning though; RedBoot/eCos
has a steep learning curve associated with it.
Cheers,
g.
> /RogerL
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
next prev parent reply other threads:[~2005-02-12 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 22:51 [U-Boot-Users] My first embedded project Benjamin D Boicourt
2005-02-10 23:11 ` Wolfgang Denk
2005-02-11 13:57 ` Roger Larsson
2005-02-11 17:21 ` Wolfgang Denk
2005-02-12 8:14 ` Grant Likely [this message]
2005-02-12 20:15 ` Wolfgang Denk
2005-02-12 20:24 ` Grant Likely
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=528646bc050212001475fc6c92@mail.gmail.com \
--to=glikely@gmail.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