The latest development version of this page may be more current than this released 2.7.5 version.

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.

Direct dependencies

ARCH_HAS_TRUSTED_EXECUTION

(Includes any dependencies from ifs and menus.)

Defaults

No defaults. Implicitly defaults to n.

Kconfig definition

At arch/Kconfig:206

Included via Kconfig:8 → Kconfig.zephyr:39

Menu path: (Top) → General Architecture Options

config TRUSTED_EXECUTION_SECURE
    bool "Trusted Execution: Secure firmware image"
    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.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)