From: Steven Zedeck <saz@proliphix.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBOOT relocation question on Atmel arm926ejs
Date: Tue, 21 Apr 2009 13:19:52 -0700 (PDT) [thread overview]
Message-ID: <23164136.post@talk.nabble.com> (raw)
Hi,
I am having a hard time understanding how the uboot relocation from flash to
RAM happens. I'm trying to follow the code flow. I "think" I understand it,
but wanted to run it by you experts to confirm.
The flow starts in cpu/arm926ejs/start.s. In the reset function, after
cpu_init_crit, u_boot is relocated to RAM. At the end of the reset function,
we jump to start_armboot which is in lib_arm/board.c. At this point, we are
already executing out or RAM. Do I have it correct?
The reason I'm confused is that in start_armboot we call several functions
via an init_sequence table with functions with names that end in "_f"
(meaning in flash).
Am I missing something?
Thanks in advance,
Steve
--
View this message in context: http://www.nabble.com/UBOOT-relocation-question-on-Atmel-arm926ejs-tp23164136p23164136.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
reply other threads:[~2009-04-21 20:19 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=23164136.post@talk.nabble.com \
--to=saz@proliphix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.