imx233: fix app.lds to properly support INIT_ATTR

Original fix by Marcin: it had a problem because crt0 on imx233 is more
complicated than many targets: since we use virtual memory, we first disable
the MMU, then move the entire image (including init and itext stuff), then
setup a temporary stack to setup the MMU. Only when the MMU is enabled, can
we move the init and itext stuff to its right location and finally boot.
This requires some trickery because:
- the initial move copies everything, including init and itext
- the stack overlaps with init and itext to reclaim space
- the temporary stack cannot be the same as the main stack to avoid trashing
  the init and itext code, also it needs to be a physical address

Change-Id: Ibaf331c7d90b61f99225d93c9e621eb0f3f8f2dc

1 files changed, 6 insertions, 3 deletions

diff --git a/firmware/target/arm/imx233/crt0.S b/firmware/target/arm/imx233/crt0.S
index 0a71da5d08..5e1720c7c9 100644
--- a/firmware/target/arm/imx233/crt0.S
+++ b/firmware/target/arm/imx233/crt0.S
@@ -56,9 +56,12 @@ start:
     bic     r0, r1
     mcr     p15, 0, r0, c1, c0, 0
 
-    /* To call the C code we need a stack, since the stack is in virtual memory
-     * use the stack's physical address */
-    ldr     sp, =stackend_phys
+    /* To call the C code we need a stack, since the loader's stack might be
+     * in virtual memory, we need a physical address for the stack. Furthermore,
+     * we cannot use the main firmware stack yet because it overlaps with the
+     * init code which will be moved later. We rely on the linker to provide
+     * a safe, temporary stack */
+    ldr     sp, =crt0_tmpstack_phys
 
     /* Enable MMU */
     bl      memory_init