Do not define CONFIG_TRUSTED_EXECUTION_SECURE for bare-metal

Defining CONFIG_TRUSTED_EXECUTION_SECURE measn device execute in secure mode on zephyr side The driver especially flash_reva.c implemented by this way, so do not define it for bare-metal side Signed-off-by: Sadik Ozer <[email protected]>
analogdevicesinc · Sep 20, 2024 · b308c40 · b308c40
1 parent 53fc098
commit b308c40
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/Libraries/CMSIS/Device/Maxim/GCC/gcc.mk b/Libraries/CMSIS/Device/Maxim/GCC/gcc.mk
@@ -300,8 +300,8 @@ PROJ_AFLAGS += -DIS_SECURE_ENVIRONMENT=1
 PROJ_CFLAGS += -DIS_SECURE_ENVIRONMENT=1
 else
 # Align with Zephyr flags.
-PROJ_AFLAGS += -DCONFIG_TRUSTED_EXECUTION_SECURE=0
-PROJ_CFLAGS += -DCONFIG_TRUSTED_EXECUTION_SECURE=0
+# Do not define CONFIG_TRUSTED_EXECUTION_SECURE
+# not defining means 0
 
 # Leaving these to support initial development.
 PROJ_AFLAGS += -DIS_SECURE_ENVIRONMENT=0