From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Mon, 29 Oct 2012 11:13:06 -0700 Subject: [U-Boot] Current u-boot memory mapping In-Reply-To: <20121027111700.GB30536@crg> References: <20121027111700.GB30536@crg> Message-ID: <20121029181306.GE15691@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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: