:orphan:

.. title:: CONFIG_ARM_NONSECURE_FIRMWARE

.. kconfig:: CONFIG_ARM_NONSECURE_FIRMWARE

CONFIG_ARM_NONSECURE_FIRMWARE
#############################

*(No prompt -- not directly user assignable.)*

Type: ``bool``

Help
====

.. code-block:: none

    This option indicates that we are building a Zephyr image that
    is intended to execute in Non-Secure state. Execution of this
    image is triggered by Secure firmware that executes in Secure
    state. The option is only applicable to ARMv8-M MCUs that
    implement the Security Extension.

    This option enables Zephyr to include code that executes in
    Non-Secure state only, as well as to exclude code that is
    designed to execute only in Secure state.

    Code executing in Non-Secure state has no access to Secure
    resources of the Cortex-M MCU, and, therefore, it shall avoid
    accessing them.

Direct dependencies
===================

!\ :kconfig:`ARM_SECURE_FIRMWARE <CONFIG_ARM_SECURE_FIRMWARE>` && \ :kconfig:`ARMV8_M_SE <CONFIG_ARMV8_M_SE>` && \ :kconfig:`ARM <CONFIG_ARM>`

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

Default
=======

- y if \ :kconfig:`TRUSTED_EXECUTION_NONSECURE <CONFIG_TRUSTED_EXECUTION_NONSECURE>`

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



At ``<Zephyr Architecture>/arm/core/aarch32/Kconfig:201``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:39`` → ``<Zephyr Architecture>/Kconfig:12`` → ``<Zephyr Architecture>/arm/Kconfig:57``

Menu path: (Top) → ARM Options

.. code-block:: kconfig

    config ARM_NONSECURE_FIRMWARE
    	bool
    	default y if TRUSTED_EXECUTION_NONSECURE
    	depends on !ARM_SECURE_FIRMWARE && ARMV8_M_SE && ARM
    	help
    	  This option indicates that we are building a Zephyr image that
    	  is intended to execute in Non-Secure state. Execution of this
    	  image is triggered by Secure firmware that executes in Secure
    	  state. The option is only applicable to ARMv8-M MCUs that
    	  implement the Security Extension.
	  
    	  This option enables Zephyr to include code that executes in
    	  Non-Secure state only, as well as to exclude code that is
    	  designed to execute only in Secure state.
	  
    	  Code executing in Non-Secure state has no access to Secure
    	  resources of the Cortex-M MCU, and, therefore, it shall avoid
    	  accessing them.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*