-
CONFIG_TRUSTED_EXECUTION_SECURE¶
Trusted Execution: Secure firmware image
Type: bool
Help¶
Select this option to enable building a Secure firmware image for a platform that supports Trusted Execution. A Secure firmware image will execute in Secure state. It may allow the CPU to execute in Non-Secure (Normal) state. Therefore, a Secure firmware image shall be able to configure security attributions of CPU resources (memory areas, peripherals, interrupts, etc.) as well as to handle faults, related to security violations. It may optionally allow certain functions to be called from the Non-Secure (Normal) domain.
Defaults¶
No defaults. Implicitly defaults to n.
Kconfig definition¶
At arch/Kconfig:124
Included via Kconfig:10 → Kconfig.zephyr:29
Menu path: (top menu) → General Architecture Options
config TRUSTED_EXECUTION_SECURE
bool
prompt "Trusted Execution: Secure firmware image" if ARCH_HAS_TRUSTED_EXECUTION
depends on ARCH_HAS_TRUSTED_EXECUTION
help
Select this option to enable building a Secure firmware
image for a platform that supports Trusted Execution. A
Secure firmware image will execute in Secure state. It may
allow the CPU to execute in Non-Secure (Normal) state.
Therefore, a Secure firmware image shall be able to
configure security attributions of CPU resources (memory
areas, peripherals, interrupts, etc.) as well as to handle
faults, related to security violations. It may optionally
allow certain functions to be called from the Non-Secure
(Normal) domain.
(Definitions include propagated dependencies, including from if’s and menus.)