Lines Matching +full:ext +full:- +full:address +full:- +full:match

1 Trusted Firmware-M Integration
4 The Trusted Firmware-M (TF-M) section contains information about the
5 integration between TF-M and Zephyr RTOS. Use this information to help
6 understand how to integrate TF-M with Zephyr for Cortex-M platforms and make
7 use of its secure run-time services in Zephyr applications.
12 TF-M will be built for the secure processing environment along with Zephyr if
16 and all config flags required for TF-M should be set in a board variant with
22 `modules/trusted-firmware-m/Kconfig.tfm <https://github.com/zephyrproject-rtos/zephyr/blob/main/mod…
23 to the board name that TF-M expects for this target, so that it knows which
29 The ``mps2/an521/cpu0`` board target is a dual-core Arm Cortex-M33 evaluation board that generates
34 non-secure image, linked with TF-M as an external project, and optionally the
43 the required space for TF-M and the secure bootloader:
47     reserved-memory {
48 		#address-cells = <1>;
49 		#size-cells = <1>;
52 		/* The memory regions defined below must match what the TF-M
53 		 * project has defined for that board - a single image boot is
55 …* https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/ext/target/mps2/an521/…
67 This reserves 1 MB of code memory and 1 MB of RAM for secure boot and TF-M,
68 such that our non-secure Zephyr application code will start at 0x10000, with
72 This matches the flash memory layout we see in ``flash_layout.h`` in TF-M:
76     * 0x0000_0000 BL2 - MCUBoot (0.5 MB)
78     * 0x0010_0000 Non-secure image primary slot (0.5 MB)
80     * 0x0020_0000 Non-secure image secondary slot (0.5 MB)
87 ``mps2/an521`` will be passed in to Tf-M as the board target, specified via