:orphan:

.. title:: CONFIG_INIT_ARCH_HW_AT_BOOT

.. kconfig:: CONFIG_INIT_ARCH_HW_AT_BOOT

CONFIG_INIT_ARCH_HW_AT_BOOT
###########################

*Initialize internal architecture state at boot*

Type: ``bool``

Help
====

.. code-block:: none

    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
===================

\ :kconfig:`ARCH_SUPPORTS_ARCH_HW_INIT <CONFIG_ARCH_SUPPORTS_ARCH_HW_INIT>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Symbols that imply this symbol
==============================

- \ :kconfig:`BUILD_WITH_TFM <CONFIG_BUILD_WITH_TFM>`
- \ :kconfig:`BOOTLOADER_MCUBOOT <CONFIG_BOOTLOADER_MCUBOOT>`

Kconfig definition
==================



At ``<Zephyr Architecture>/Kconfig:443``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:39``

Menu path: (Top) → General Architecture Options

.. code-block:: kconfig

    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.)*