ARM memory layout

Daniel Krüger daniel.krueger at
Thu Jun 16 03:11:10 PDT 2016


during the porting of barebox to a new i.MX35 board I stumbled over some 
crazy things with the memory layout. The comments in file 
arch/arm/cpu/entry.c seem to be wrong or at least misleading.

We configured barebox as non-relocatable image. So I think the 
configured TEXT_BASE is very important.

I use the following configuration with 128 MB RAM:

The stack is configured very large in this project, because of other reason.

I get the following memory layout:
     0x87ffffff top of RAM
      |           free-space (see arm_mem_stack() in
      |                       arch/arm/include/asm/barebox-arm.h)
     0x87ff0000 start of 64 kB free-space (vector table)
     0x87feffff top of stack
     0x87ef0000 start of 1 MB reserved stack space
      |         16 kB early translation table
     0x87eec000 early TTB (translation table base)
     0x87eebfff malloc end
      |          13 MB malloc space
     0x871ec000 malloc start
      |         some small free space
      |         barebox binary
     0x87000000 TEXT_BASE

This does not comply to the comment in the above mentioned source file. 
There the malloc space and the vector table are missing.

I would expect some check in the source code, when TEXT_BASE is too high 
or barebox binary is too large, so they collide with malloc space or 
stack. By reverse engineering the detailed memory layout above, I 
discovered that in another project the TEXT_BASE falls within the malloc 

How does is run on other ARM boards? Are they all running with 

Best regards,


SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund

Telefon : +49 (0) 3765 38600-0
Fax     : +49 (0) 3765 38600-4100
Email   : daniel.krueger at
Website :

Managing Directors  :
   Dipl.-Phys. Siegmar Schmidt, Dipl. Ing. (FH) Armin von Collrepp
Commercial registry : Amtsgericht Chemnitz, HRB 28082
USt.-Id Nr.         : DE150534010

More information about the barebox mailing list