Secure firmwares must be loaded if SOC is secure,
currently rproc framework chooses non-secure firmware always.

So adding support to load secure firmware, when SOC is secure

Signed-off-by: Manorit Chawdhry <m-chawd...@ti.com>
Signed-off-by: Udit Kumar <u-kum...@ti.com>
---
 include/env/ti/k3_rproc.env  | 6 +++++-
 include/env/ti/ti_common.env | 1 +
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/include/env/ti/k3_rproc.env b/include/env/ti/k3_rproc.env
index 87d9d76eba..d4f0f1708c 100644
--- a/include/env/ti/k3_rproc.env
+++ b/include/env/ti/k3_rproc.env
@@ -13,11 +13,15 @@ rproc_load_and_boot_one=
 boot_rprocs_mmc=
        env set rproc_id;
        env set rproc_fw;
+       env set secure_suffix;
+       if test ${secure_rprocs} -eq 1; then
+               env set secure_suffix -sec;
+       fi;
        for i in ${rproc_fw_binaries} ; do
                if test -z "${rproc_id}" ; then
                        env set rproc_id $i;
                else
-                       env set rproc_fw $i;
+                       env set rproc_fw $i${secure_suffix};
                        run rproc_load_and_boot_one;
                        env set rproc_id;
                        env set rproc_fw;
diff --git a/include/env/ti/ti_common.env b/include/env/ti/ti_common.env
index 02b410c3ad..c5c3642177 100644
--- a/include/env/ti/ti_common.env
+++ b/include/env/ti/ti_common.env
@@ -12,6 +12,7 @@ bootm_size=0x10000000
 boot_fdt=try
 
 boot_fit=0
+secure_rprocs=0
 addr_fit=0x90000000
 name_fit=fitImage
 update_to_fit=setenv loadaddr ${addr_fit}; setenv bootfile ${name_fit}
-- 
2.34.1

Reply via email to