On Tue, Sep 06, 2016 at 03:54:31PM -0500, Andrew F. Davis wrote:
On 09/02/2016 12:40 AM, Daniel Allred wrote:
If the ending portion of the DRAM is reserved for secure world use, then u-boot cannot use this memory for its relocation purposes. To prevent issues, we mark this memory as PRAM and this prevents it from being used by u-boot at all.
Signed-off-by: Daniel Allred d-allred@ti.com
include/configs/ti_omap5_common.h | 8 ++++++++ 1 file changed, 8 insertions(+)
diff --git a/include/configs/ti_omap5_common.h b/include/configs/ti_omap5_common.h index e42c88e..70fdc6e 100644 --- a/include/configs/ti_omap5_common.h +++ b/include/configs/ti_omap5_common.h @@ -146,6 +146,14 @@ */ #define TI_OMAP5_SECURE_BOOT_RESV_SRAM_SZ 0x1000 #define CONFIG_SPL_TEXT_BASE 0x40301350 +/* If no specific start address is specified then the secure EMIF
- region will be placed at the end of the DDR space. In order to prevent
- the main u-boot relocation from clobbering that memory and causing a
- firewall violation, we tell u-boot that memory is protected RAM (PRAM)
- */
+#if (CONFIG_TI_SECURE_EMIF_REGION_START == 0)
What about if we set the start address manually, what prevents u-boot from over-writing that memory?
I think that's another reason this needs to be made to use the existing pram mechanism as we make sure that if pram isn't set in the environment we set it to the default of CONFIG_PRAM.