CONFIG_NRF_SECURE_APPROTECT_USER_HANDLING¶

Allow user handling

Type: bool

Help¶

When this option is selected, the SystemInit() function does not
touch the secure APPROTECT mechanism, allowing the user code to
handle it at later stages, for example, to implement authenticated
debug.

Help¶

When this option is selected, the SystemInit() function does not
touch the secure APPROTECT mechanism, allowing the user code to
handle it at later stages, for example, to implement authenticated
debug.

Direct dependencies¶

(!SOC_SERIES_NRF52X && <choice NRF_SECURE_APPROTECT_HANDLING: Secure APPROTECT handling>) || (!SOC_SERIES_NRF52X && <choice NRF_SECURE_APPROTECT_HANDLING: Secure APPROTECT handling>)

(Includes any dependencies from ifs and menus.)

Kconfig definitions¶

At <Zephyr SoC>/arm/nordic_nrf/Kconfig:111

Included via Kconfig:8 → Kconfig.zephyr:38 → <Zephyr SoC>/Kconfig:15 → <BuildDir>/kconfig/Kconfig.soc.arch:2

Menu path: (Top) → Hardware Configuration → Secure APPROTECT handling

config NRF_SECURE_APPROTECT_USER_HANDLING
    bool "Allow user handling"
    depends on !SOC_SERIES_NRF52X && <choice NRF_SECURE_APPROTECT_HANDLING>
    help
      When this option is selected, the SystemInit() function does not
      touch the secure APPROTECT mechanism, allowing the user code to
      handle it at later stages, for example, to implement authenticated
      debug.

At <Zephyr SoC>/arm/nordic_nrf/Kconfig:111

Included via Kconfig:8 → Kconfig.zephyr:38 → <Zephyr SoC>/Kconfig:18

Menu path: (Top) → Hardware Configuration → Secure APPROTECT handling

config NRF_SECURE_APPROTECT_USER_HANDLING
    bool "Allow user handling"
    depends on !SOC_SERIES_NRF52X && <choice NRF_SECURE_APPROTECT_HANDLING>
    help
      When this option is selected, the SystemInit() function does not
      touch the secure APPROTECT mechanism, allowing the user code to
      handle it at later stages, for example, to implement authenticated
      debug.

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