CONFIG_INIT_ARCH_HW_AT_BOOT¶

Initialize internal architecture state at boot

Type: bool

Help¶

The image will be booted directly by an unknown image which might not
leave the system in a clean state, so it is necessary to perform
architecture specific hardware initialization.

Help¶

This option instructs Zephyr to force the initialization
of the internal architectural state (for example ARCH-level
HW registers and system control blocks) during boot to
the reset values as specified by the corresponding
architecture manual. The option is useful when the Zephyr
firmware image is chain-loaded, for example, by a debugger
or a bootloader, and we need to guarantee that the internal
states of the architecture core blocks are restored to the
reset values (as specified by the architecture).

Note: the functionality is architecture-specific. For the
implementation details refer to each architecture where
this feature is supported.

Defaults¶

n if SPM
y

Symbols that imply this symbol¶

Kconfig definitions¶

At <nRF>/modules/Kconfig.mcuboot:21

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:31 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:55 → <nRF>/modules/Kconfig:7

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect

config INIT_ARCH_HW_AT_BOOT
    bool
    default n if SPM
    default y
    help
      The image will be booted directly by an unknown image which might not
      leave the system in a clean state, so it is necessary to perform
      architecture specific hardware initialization.

At <Zephyr>/arch/Kconfig:443

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:37

Menu path: (Top) → General Architecture Options

config INIT_ARCH_HW_AT_BOOT
    bool "Initialize internal architecture state at boot"
    depends on ARCH_SUPPORTS_ARCH_HW_INIT
    help
      This option instructs Zephyr to force the initialization
      of the internal architectural state (for example ARCH-level
      HW registers and system control blocks) during boot to
      the reset values as specified by the corresponding
      architecture manual. The option is useful when the Zephyr
      firmware image is chain-loaded, for example, by a debugger
      or a bootloader, and we need to guarantee that the internal
      states of the architecture core blocks are restored to the
      reset values (as specified by the architecture).

      Note: the functionality is architecture-specific. For the
      implementation details refer to each architecture where
      this feature is supported.

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