This article shows the mapping used in STM32 MPU Embedded Software distribution for ST boards, that can be used as starting point for other boards.
1. Supported Flash memory technologies[edit | edit source]
STM32MP1 series and STM32MP2 series support the different types of Flash memory. The bullets below show which interfaces are supported on STMicroelectronics boards:
- SD card on the SDMMC interface
- used on STM32MP13 DISCO board
- used on STM32MP15 EVAL board
- used on STM32MP15 DISCO board
- used on STM32MP25 EVAL board
- used on STM32MP25 DISCO board
- e•MMC on the SDMMC interface
- used on STM32MP15 EVAL board
- used on STM32MP25 EVAL board
- used on STM32MP25 DISCO board
- NAND Flash memory on the FMC interface
- used on STM32MP15 EVAL board only.
- Serial NOR Flash memory on the Dual QSPI/OCTOSPI interface
- used on STM32MP15 EVAL board
- used on STM32MP25 EVAL board
- Serial NAND Flash memory on the Dual QSPI/OCTOSPI interface
- not present on ST boards
- HyperFlash memory on the OCTOSPI interface
- not present on ST boards
The next section lists all partitions used on STM32MPU boards (size, name, and content), and the following sections show how they are mapped on the different types of Flash memory.
2. Flash partitions[edit | edit source]
2.1. STMP32MP1 and STM32MP2 boards in A35-TD flavor 
[edit | edit source]
The tables below list the partitions defined for STMP32MP1 and STM32MP2 boards in A35-TD flavor and gives typical sizes with OpenSTLinux, that can be tuned, depending on the targeted application needs.
| Size | Component | Comment |
|---|---|---|
| Remaining area | userfs | The user file system contains user data and examples |
| 768 Mbytes | rootfs | Linux root file system contains all user space binaries (executable, libraries, and so on), and kernel modules |
| 16 Mbytes | vendorfs | This partition is preferred to the rootfs for third-party proprietary binaries, and ensures that they are not contaminated by any open source licence, such as GPL v3 |
| 64 Mbytes | bootfs or boot (NAND) |
The boot file system contains:
|
| 2 * 256 Kbytes (*) | u-boot-env or uboot_config / uboot_config_r (NAND) |
This partition is used to store the U-Boot environment. uboot_config_r is used for redundancy management with uboot_config, in NAND Flash. |
| (2 *) 4 Mbytes | fip | The TF-A firmware image package (FIP) is a binary file that encapsulates several binaries, and their certificates (optionally, for authentication), that will be loaded by TF-A BL2. OpenSTLinux FIP contains:
There are two partitions, fip-a and fip-b, when A/B (seamless) FIP firmware update is activated in TF-A BL2. |
| 256 Kbytes to 512 Kbytes (*) | metadata | Metadata are used by TF-A BL2 to localize the FIP version to use, when the FIP is subject to firmware update.
Notes:
|
| 2 * 256 Kbytes to 512 Kbytes (*) | fsbla | The first stage boot loader is Arm Trusted Firmware (TF-A). At least two copies are embedded (fsbla1, fsbla2). Notes:
|
(*): The partition size depends on the Flash technology, to be aligned to the block erase size of the Flash memory present on the board: NOR (256 Kbytes) / NAND (512 Kbytes).
 Information
|
| Some boards can be equipped with multiple Flash devices, like the STM32MP15 EVAL board, where all of the Flash devices can be programmed with STM32CubeProgrammer. However, caution must be taken for the serial NOR/NAND and SLC NAND because a static bootable MTD partitioning is defined in U-Boot default config (see MTD configuration for details), with the consequence that up to 6 Mbytes of space is lost at the beginning of each such device, even those which are not bootable. |
2.2. STM32MP2 boards in M33-TD flavor [edit | edit source]
The tables below list the partitions defined for STM32MP2 boards in M33-TD flavor and gives typical sizes with OpenSTLinux, that can be tuned, depending on the targeted application needs.
| Size | Component | Comment |
|---|---|---|
| Remaining area | userfs | The user file system contains user data and examples |
| 768 Mbytes | rootfs | Linux root file system contains all user space binaries (executable, libraries, and so on), and kernel modules |
| 16 Mbytes | vendorfs | This partition is preferred to the rootfs for third-party proprietary binaries, and ensures that they are not contaminated by any open source licence, such as GPL v3 |
| 64 Mbytes | bootfs or boot (NAND) |
The boot file system contains:
|
| 2 * 256 Kbytes (*) | u-boot-env or uboot_config / uboot_config_r (NAND) |
This partition is used to store the U-Boot environment. uboot_config_r is used for redundancy management with uboot_config, in NAND Flash. |
| (2 *) 4 Mbytes | fip | The TF-A firmware image package (FIP) is a binary file that encapsulates several binaries, and their certificates (optionally, for authentication), that will be loaded by TF-A BL2. OpenSTLinux FIP contains:
There are two partitions, fip-a and fip-b, when A/B (seamless) FIP firmware update is activated in TF-A BL2. |
| 256 Kbytes to 512 Kbytes (*) | metadata | Metadata are used by TF-A BL2 to localize the FIP version to use, when the FIP is subject to firmware update.
Notes:
|
| 2 * 256 Kbytes to 512 Kbytes (*) | fsbla | The first stage boot loader is Arm Trusted Firmware (TF-A). At least two copies are embedded (fsbla1, fsbla2). Notes:
|
| 2 * 9 Mbytes | m33fw | The Cortex-M33 firmware (including secure and non-secure) required to start the Fw-ST-M exosystem. At least two copies are embedded (m33fw-a, m33fw-b) to allow update firmware management. The content of the partition is linked to the MCUboot packaging and includes;
|
| 2 * 256 Kbytes to 512 Kbytes (*) | m33ddr | The DDR firmware required to manage the DDR training. At least two copies are embedded (m33ddr-a, m33ddr-b). |
| 2 * 256 Kbytes to 512 Kbytes (*) | fsblm | The first stage boot loader is (MCUboot). At least two copies are embedded (fsblm1, fsblm2). Notes:
|
(*): The partition size depends on the Flash technology, to be aligned to the block erase size of the Flash memory present on the board: NOR (256 Kbytes) / NAND (512 Kbytes).
| Information
|
| Some boards can be equipped with multiple Flash devices, like the STM32MP15 EVAL board, where all of the Flash devices can be programmed with STM32CubeProgrammer. However, caution must be taken for the serial NOR/NAND and SLC NAND because a static bootable MTD partitioning is defined in U-Boot default config (see MTD configuration for details), with the consequence that up to 6 Mbytes of space is lost at the beginning of each such device, even those which are not bootable. |
3. STMP32MP1 and STM32MP2 boards in A35-TD flavor [edit | edit source]
3.1. SD card memory mapping[edit | edit source]
The SD card has to be partitioned with GPT format in order to be recognized by the STM32MP1 and STM32MP2 ROM code. The easiest way to achieve this is to use STM32CubeProgrammer.
The ROM code looks for the GPT entries whose name begins with "fsbl": fsbl1 and fsbl2 for example.
Note: The SD card can be unplugged from the board and inserted into a Linux host computer for direct partitioning with Linux utilities and access to the bootfs, rootfs and userfs partitions. The file system is Linux EXT4.
3.2. e•MMC memory mapping[edit | edit source]
The e•MMC embeds four physical partitions:
- Boot area partition 1: one copy of the FSBL
- Boot area partition 2: one copy of the FSBL
- User data area: formatted with GPT partitioning and used to store all remaining partitions
- Replay Protected Memory Block (RPMB): not shown in the figure below, since not involved in the current boot chain.
STM32CubeProgrammer has to be used to prepare the e•MMC with the layout shown below, and to populate each partition.
| Information
|
| The boot area partition used by the e•MMC boot sequence is selected via the EXT_CSD[179] register in the e•MMC. The STM32CubeProgrammer execution is concluded with the selection of the last written partition from the flashlayout file, typically partition 2. The other copy is never used as long as the user does not explicitly change the e•MMC EXT_CSD[179] register to select it. |
3.3. NOR memory mapping[edit | edit source]
As NOR Flash memory is expensive, its size is usually limited to the minimum needed to store only the bootloaders. The system files (bootfs, rootfs and userfs) are usually stored in another Flash memory, such as the SD card in OpenSTLinux distribution.
STM32CubeProgrammer must be used to prepare the NOR Flash and the SD card with the layout shown below, and to populate each partition.
It is possible to use an e•MMC card or NAND as second-level Flash memory, rather than an SD card. This requires the following aspects to be changed:
- The Flash memory layout, using STM32CubeProgrammer in order to write the rootfs and userfs to the targeted Flash memory
- The Linux kernel parameters, using U-Boot, in order to indicate where the rootfs and userfs have to be mounted.
3.4. NAND memory mapping[edit | edit source]
STM32CubeProgrammer has to be used to prepare the NAND Flash memory with the layout shown below, and to populate each partition.
4. STM32MP2 boards in M33-TD flavor [edit | edit source]
Using STM32MP2 series in M33-TD flavor , the memory mapping depends on the STM32_MPU_ROM_code_overview#Boot_device_selection_on_STM32MP2_seriessupported boot device configuration:
- Dual boot storage device: Each Arm® Cortex® core uses its own an dedicated storage.
- Single boot storage device: All the boot images are stored in a single storage which remains used by the Arm® Cortex®-A (secondary boot core).
4.1. SD card memory mapping[edit | edit source]
4.1.1. Dual boot storage (Used a dedicated storage by Arm® Cortex®-A)[edit | edit source]
The SD card is used as dedicated storage device for the OpenSTLinux. It only embeds the Arm® Cortex®-A images, same as the A35-TD flavor .
In that case, another device is required for the Arm® Cortex®-M images.
4.1.2. Single boot storage[edit | edit source]
The SD card is used as boot storage for both Arm® Cortex®-A and Arm® Cortex®-M images. It embeds the boot images for both core and the filesystem for OpenSTLinux ecosystem.
4.2. e•MMC memory mapping[edit | edit source]
4.2.1. Dual boot storage (Used as dedicated storage by Arm® Cortex®-A)[edit | edit source]
The e•MMC is used as dedicated storage device for the OpenSTLinu. It only embeds the Arm® Cortex®-A images. It uses the same partitions as defined in the A35-TD flavor .
In that case, another device is required for the Arm® Cortex®-M images.
4.2.2. Single boot storage[edit | edit source]
The e•MMC is used as boot storage for both Arm® Cortex®-A and Arm® Cortex®-M images. It embeds the boot images for both core and the filesystem for OpenSTLinux ecosystem.
Due to boot partitions in e•MMC, the FSBL-M will be located in that partitions as they are used by the ROM code as primary image to boot the ARM Cortex-M33.
4.3. NOR memory mapping[edit | edit source]
NOR device is recommended as boot device using M33-TD flavor .
When using the NOR device in a dual boot storage mode, the NOR device remains allocated to the Arm® Cortex®-M and allow the Protected Storage service to be enabled.
4.3.1. Dual boot storage (Used as dedicated storage by Arm® Cortex®-M)[edit | edit source]
The NOR is used as dedicated storage device for the FwST-M. It only embeds the Arm® Cortex®-M images and the associated partitions. A second device must be used for the other Arm® Cortex®-A images.
4.3.2. Single boot storage[edit | edit source]
As NOR Flash memory is expensive, its size is usually limited to the minimum needed to store only the bootloaders. The system files (bootfs, rootfs and userfs) are usually stored in another Flash memory, such as the SD card in OpenSTLinux distribution.
STM32CubeProgrammer must be used to prepare the NOR Flash and the SD card with the layout shown below, and to populate each partition.
4.4. NAND memory mapping[edit | edit source]
|
Coming soon |
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere. 
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.