:orphan:

.. title:: CONFIG_TFM_MCUBOOT_PATH_LOCAL

.. kconfig:: CONFIG_TFM_MCUBOOT_PATH_LOCAL

CONFIG_TFM_MCUBOOT_PATH_LOCAL
#############################

*TF-M to use Zephyr's MCUboot*

Type: ``bool``

Help
====

.. code-block:: none

    TF-M builds with BL2 will use the Zephyr's MCUboot version,
    which is present in the MCUboot module.

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

\ :ref:`<choice TFM_MCUBOOT_PATH: Path to MCUboot or DOWNLOAD to fetch automatically> <choice_33>`

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

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



At ``<External Modules>/trusted-firmware-m/Kconfig.tfm:171``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:33`` → ``<External Modules>/Kconfig:74`` → ``<External Modules>/trusted-firmware-m/Kconfig:7``

Menu path: (Top) → Modules → Build with TF-M as the Secure Execution Environment → Add MCUboot to TFM → Path to MCUboot or DOWNLOAD to fetch automatically

.. code-block:: kconfig

    config TFM_MCUBOOT_PATH_LOCAL
    	bool "TF-M to use Zephyr's MCUboot"
    	depends on <choice TFM_MCUBOOT_PATH>
    	help
    	  TF-M builds with BL2 will use the Zephyr's MCUboot version,
    	  which is present in the MCUboot module.

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