From mboxrd@z Thu Jan 1 00:00:00 1970 From: RgC Date: Sat, 27 Oct 2012 20:17:00 +0900 Subject: [U-Boot] Current u-boot memory mapping Message-ID: <20121027111700.GB30536@crg> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi All, Last week I got a weird problem on an ARM platfrom. It is using an old version of u-boot because of our design/implementation cycle, but let's not talk about upgrading the u-boot version that I use please. My understanding of the u-boot memory mapping is in question :-) I've dealt with the early versions (v1.x.x) on PowerPC and ARM. I'm now dealing with newer u-boot versions but mostly on the PowerPC arch. So I'm not sure if everything I know applies to the ARM arch. In the PowerPC arch, after relocation the actual memory mapping follows the "Memory Management" section in the u-boot README. Bottom of RAM for exception handlers, then free space until we reach near the top of RAM. This is populated by the stack, global data, malloc-area, and the u-boot code. My understanding is that this design was never altered and was implemented across all platforms. 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? 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. All the best, RgC -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 487 bytes Desc: not available URL: