From: Alessandro Rubini <rubini-list@gnudd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] help in understand the address of standalone applications, ARM MCU
Date: Sun, 11 May 2008 22:22:39 +0200 [thread overview]
Message-ID: <20080511202239.GA11099@mail.gnudd.com> (raw)
In-Reply-To: <200805112051.43401.casainho@gmail.com>
> Hmm... So I must know detailed memory map, and that depends on U-Boot usage,
> right? - the board manual just tells the principle and the end addresses of
> the SDRAM... - maybe the information I am looking for is in the sources of
> U-Boot...
Most likely u-boot is running at 0x23f0.0000. Usually the initial
bytes are used for special purposes (I don't remember the details but
irq vectors might be located there), so anything in-between should
work. Try 0x2010.0000 (1M within the RAM area) or whatever.
In short: yes, it depends on the detailed memory map.
A good choice, if you don't want to know the details, is the address
where you load the kernel image (it's on the manual, or default boot
command). Note: not the flash address, but the load address in the
range 2000.0000-2400.0000; it usually is 32k in the ram, but whatever
it is, that is a safe address. 0 and 0xc000.0000 are definitely not good.
> If I find the right address and use it on the -Ttext link time and
> on the tftp load and go command, my original program should work?
Yes.
Hope this helps
/alessandro
next prev parent reply other threads:[~2008-05-11 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 16:36 [U-Boot-Users] help in understand the address of standalone applications, ARM MCU J.P. Casainho
2008-05-11 18:31 ` Wolfgang Denk
2008-05-11 19:51 ` J.P. Casainho
2008-05-11 20:22 ` Alessandro Rubini [this message]
2008-05-11 20:36 ` Wolfgang Denk
2008-05-11 20:40 ` [U-Boot-Users] help in understand the address of standaloneapplications, " Ulf Samuelsson
2008-05-12 0:01 ` J.P. Casainho
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=20080511202239.GA11099@mail.gnudd.com \
--to=rubini-list@gnudd.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