Hi Andrew
On 18/05/23 22:09, Andrew Davis wrote:
On 5/18/23 9:27 AM, Neha Malcom Francis wrote:
From: Kamlesh Gurudasani <kaml...@ti.com>
AM64x family of SoCs by default will have some level of security
enforcement checking. Enable CONFIG_TI_SECURE_DEVICE by default so all
levels of secure SoCs will boot with binman.
Signed-off-by: Kamlesh Gurudasani <kaml...@ti.com>
Signed-off-by: Neha Francis <n-fran...@ti.com>
Signed-off-by: Neha Malcom Francis <n-fran...@ti.com>
(apologies for the incorrect tags)
---
This fix is independent of the binman changes and should go
in first anyway to keep bisectability.
Andrew
This fix breaks KIG flow though, which is why it was decided to be put
in along with the binman series.
configs/am64x_evm_a53_defconfig | 1 +
configs/am64x_evm_r5_defconfig | 1 +
2 files changed, 2 insertions(+)
diff --git a/configs/am64x_evm_a53_defconfig
b/configs/am64x_evm_a53_defconfig
index 4589624e96..09037ecd0f 100644
--- a/configs/am64x_evm_a53_defconfig
+++ b/configs/am64x_evm_a53_defconfig
@@ -1,6 +1,7 @@
CONFIG_ARM=y
CONFIG_SKIP_LOWLEVEL_INIT=y
CONFIG_ARCH_K3=y
+CONFIG_TI_SECURE_DEVICE=y
CONFIG_SYS_MALLOC_LEN=0x2000000
CONFIG_SYS_MALLOC_F_LEN=0x8000
CONFIG_SPL_GPIO=y
diff --git a/configs/am64x_evm_r5_defconfig
b/configs/am64x_evm_r5_defconfig
index 023ee638a0..d824298773 100644
--- a/configs/am64x_evm_r5_defconfig
+++ b/configs/am64x_evm_r5_defconfig
@@ -1,5 +1,6 @@
CONFIG_ARM=y
CONFIG_ARCH_K3=y
+CONFIG_TI_SECURE_DEVICE=y
CONFIG_SYS_MALLOC_LEN=0x2000000
CONFIG_SYS_MALLOC_F_LEN=0x80000
CONFIG_SPL_GPIO=y
--
Thanking You
Neha Malcom Francis
