:orphan: .. title:: INIT_ARCH_HW_AT_BOOT .. option:: CONFIG_INIT_ARCH_HW_AT_BOOT *Initialize internal architecture state at boot* Type: ``bool`` 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. Direct dependencies =================== \ :option:`ARCH_SUPPORTS_ARCH_HW_INIT ` *(Includes any dependencies from ifs and menus.)* Defaults ======== No defaults. Implicitly defaults to ``n``. Symbols that imply this symbol ============================== - \ :option:`BUILD_WITH_TFM ` - \ :option:`BOOTLOADER_MCUBOOT ` Kconfig definition ================== .. highlight:: kconfig At ``arch/Kconfig:403`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:29`` Menu path: (Top) → General Architecture Options .. parsed-literal:: config INIT_ARCH_HW_AT_BOOT bool "Initialize internal architecture state at boot" depends on \ :option:`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.)*