Lines Matching refs:M
3 TF-M Build System
6 When building a valid ``_ns`` board target, TF-M will be built in the
8 of TF-M's build system is required in most cases, and the following will
9 build a TF-M and Zephyr image pair, and run it in qemu with no additional
20 Images Created by the TF-M Build
23 The TF-M build system creates the following executable files:
25 * tfm_s - TF-M secure firmware
26 * tfm_ns - TF-M non-secure app (only used by regression tests).
27 * bl2 - TF-M MCUboot, if enabled
31 The TF-M build system also creates signed variants of tfm_s and tfm_ns, and a
40 The TF-M non-secure app is discarded in favor of Zephyr non-secure app except
41 when running the TF-M regression test suite.
59 When :kconfig:option:`CONFIG_TFM_BL2` is set to ``y``, TF-M uses a secure bootloader
101 When building a Zephyr application with TF-M it might be necessary to control
102 the CMake arguments passed to the TF-M build.
104 Zephyr TF-M build offers several Kconfig options for controlling the build, but
105 doesn't cover every CMake argument supported by the TF-M build system.
108 to pass custom CMake arguments to the TF-M build system.
110 To pass the CMake argument ``-DFOO=bar`` to the TF-M build system, place the
126 passed to the TF-M build system.
144 Use the ``tfm_ram_report`` to get the RAM report for TF-M secure firmware (tfm_s).
152 Use the ``tfm_rom_report`` to get the ROM report for TF-M secure firmware (tfm_s).
160 Use the ``bl2_ram_report`` to get the RAM report for TF-M MCUboot, if enabled.
168 Use the ``bl2_rom_report`` to get the ROM report for TF-M MCUboot, if enabled.