From: NZG <ngustavson@emacinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 5282 u-boot shadowing
Date: Tue, 15 Mar 2005 11:50:34 -0600 [thread overview]
Message-ID: <200503151150.34533.ngustavson@emacinc.com> (raw)
I'm working on getting u-boot up and running, pre-loader less, for the 5282.
I've run into a few issues with the way things are currently done and I wanted
to run some alternatives past the list to make sure I'm not violating any
u-boot standards.
1. The m68k code currently copies it's flash to DRAM at it's final location,
then jumps to DRAM.
To do it this way, the DRAM cannot be located at 0, as initializing the RAM
there will shadow the Flash before the code has been copied.
Therefore the RAM can either be
1. moved to another location - I have implemented a version that does this,
and it starts up ok, but the RAM winds up being at location 0xff000000,
rather than 0. Is this going to work? Or am I violating some important
standard?
2. Copied before the address of the RAM is set, then just drop the RAM
directly on top of it. I haven't tried this yet, but it may be a better
solution as I'm getting the feeling that u-boot is expecting RAM at 0.
Is this correct?
thx,
NZG.
next reply other threads:[~2005-03-15 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 17:50 NZG [this message]
2005-03-15 18:33 ` [U-Boot-Users] 5282 u-boot shadowing Zachary Landau
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=200503151150.34533.ngustavson@emacinc.com \
--to=ngustavson@emacinc.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