[U-Boot] [PATCH] configs: ti_armv7_keystone2: make SYS_TEXT_BASE configurable at build time
U-boot for general purpose KS2 devices is loaded to the beginning of the internal memory (0x0c000000). Secure devices uses this memory and CONFIG_SYS_TEXT_BASE has to be different for those devices.
This commit make this configurable at build time by giving CONFIG_SYS_TEXT_BASE as a command line definition to make command.
Signed-off-by: Vitaly Andrianov vitalya@ti.com --- include/configs/ti_armv7_keystone2.h | 2 ++ 1 file changed, 2 insertions(+)
diff --git a/include/configs/ti_armv7_keystone2.h b/include/configs/ti_armv7_keystone2.h index a7206f4..76b901bf 100644 --- a/include/configs/ti_armv7_keystone2.h +++ b/include/configs/ti_armv7_keystone2.h @@ -20,7 +20,9 @@ /* SoC Configuration */ #define CONFIG_ARCH_CPU_INIT #define CONFIG_SYS_ARCH_TIMER +#ifndef CONFIG_SYS_TEXT_BASE #define CONFIG_SYS_TEXT_BASE 0x0c000000 +#endif #define CONFIG_SPL_TARGET "u-boot-spi.gph" #define CONFIG_SYS_DCACHE_OFF
On Mon, Mar 28, 2016 at 03:15:59PM -0400, Vitaly Andrianov wrote:
U-boot for general purpose KS2 devices is loaded to the beginning of the internal memory (0x0c000000). Secure devices uses this memory and CONFIG_SYS_TEXT_BASE has to be different for those devices.
This commit make this configurable at build time by giving CONFIG_SYS_TEXT_BASE as a command line definition to make command.
I'm interested in getting secure device support going, but it seems like we should need more than that, ie something to keep the chain of trust going. I also don't like that we're just overriding this in the command line, especially as I expect we'll need other changes too once this gets moving forward. Thanks!
On 03/28/2016 03:32 PM, Tom Rini wrote:
On Mon, Mar 28, 2016 at 03:15:59PM -0400, Vitaly Andrianov wrote:
U-boot for general purpose KS2 devices is loaded to the beginning of the internal memory (0x0c000000). Secure devices uses this memory and CONFIG_SYS_TEXT_BASE has to be different for those devices.
This commit make this configurable at build time by giving CONFIG_SYS_TEXT_BASE as a command line definition to make command.
I'm interested in getting secure device support going, but it seems like we should need more than that, ie something to keep the chain of trust going. I also don't like that we're just overriding this in the command line, especially as I expect we'll need other changes too once this gets moving forward. Thanks!
Tom,
I reworked boot-monitor for KS2 secure devices and CONFIG_SYS_TEXT_BASE is only change required to support KS2 secure devices.
Thanks, Vitaly
On Mon, Mar 28, 2016 at 03:15:59PM -0400, Vitaly Andrianov wrote:
U-boot for general purpose KS2 devices is loaded to the beginning of the internal memory (0x0c000000). Secure devices uses this memory and CONFIG_SYS_TEXT_BASE has to be different for those devices.
This commit make this configurable at build time by giving CONFIG_SYS_TEXT_BASE as a command line definition to make command.
Signed-off-by: Vitaly Andrianov vitalya@ti.com
Applied to u-boot/master, thanks!
participants (2)
-
Tom Rini -
Vitaly Andrianov