This is the documentation for the latest (master) development branch of Zephyr. If you are looking for the documentation of previous releases, use the drop-down menu on the left and select the desired version.
CONFIG_ARM_NSC_REGION_BASE_ADDRESS

ARM Non-Secure Callable Region base address

Type: hex

Help

Start address of Non-Secure Callable section.

Notes: - The default value (i.e. when the user does not configure the option explicitly) instructs the linker script to place the Non-Secure Callable section, automatically, inside the .text area. - Certain requirements/restrictions may apply regarding the size and the alignment of the starting address for a Non-Secure Callable section, depending on the available security attribution unit (SAU or IDAU) for a given SOC.

Direct dependencies

ARM_FIRMWARE_HAS_SECURE_ENTRY_FUNCS && (ARM_SECURE_FIRMWARE || ARM_NONSECURE_FIRMWARE) && ARM_TRUSTZONE_M && CPU_CORTEX_M && !ARM64 && ARM

(Includes any dependencies from ifs and menus.)

Default

  • 0

Kconfig definition

At arch/arm/core/aarch32/cortex_m/tz/Kconfig:40

Included via Kconfig:8Kconfig.zephyr:29arch/Kconfig:12arch/arm/Kconfig:42arch/arm/core/aarch32/Kconfig:236arch/arm/core/aarch32/cortex_m/Kconfig:301

Menu path: (Top) → ARM Options → ARM TrustZone-M support → ARM TrustZone-M Options → Secure Firmware has Secure Entry functions

config ARM_NSC_REGION_BASE_ADDRESS
    hex "ARM Non-Secure Callable Region base address"
    default 0
    depends on ARM_FIRMWARE_HAS_SECURE_ENTRY_FUNCS && (ARM_SECURE_FIRMWARE || ARM_NONSECURE_FIRMWARE) && ARM_TRUSTZONE_M && CPU_CORTEX_M && !ARM64 && ARM
    help
      Start address of Non-Secure Callable section.

      Notes:
      - The default value (i.e. when the user does not configure
      the option explicitly) instructs the linker script to
      place the Non-Secure Callable section, automatically,
      inside the .text area.
      - Certain requirements/restrictions may apply regarding
      the size and the alignment of the starting address for
      a Non-Secure Callable section, depending on the available
      security attribution unit (SAU or IDAU) for a given SOC.

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