From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Current u-boot memory mapping
Date: Mon, 29 Oct 2012 11:13:06 -0700 [thread overview]
Message-ID: <20121029181306.GE15691@bill-the-cat> (raw)
In-Reply-To: <20121027111700.GB30536@crg>
On Sat, Oct 27, 2012 at 08:17:00PM +0900, RgC wrote:
[snip]
> My understanding is that after relocation no area between the bottom
> and the top of RAM is reserved. We can use it freely. Is this correct?
Basically, yes. You can use 'bdinfo' to see what / where things are
being used at run-time.
> If writing to the the "free area" in RAM results in crashing u-boot
> then there is problem in the relocation procedure or a possible linker
> script problem.
Well, it depends on how you trigger that crash. If you're writing near
where U-Boot is running you can overwrite yourself pretty easily. If
you aren't, then are you sure you've configured your memory controller
correctly?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20121029/d16a5600/attachment.pgp>
next prev parent reply other threads:[~2012-10-29 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 11:17 [U-Boot] Current u-boot memory mapping RgC
2012-10-29 18:13 ` Tom Rini [this message]
2012-10-31 21:49 ` RgC
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=20121029181306.GE15691@bill-the-cat \
--to=trini@ti.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