1. Article purpose[edit source]
The article aims to help rebase an STM32 MPU project on a new ecosystem release by focusing on the impacts of the main changes.
2. Scope of this article[edit source]
This article provides some details for the main changes between STM32 MPU ecosystem release v4.1.0 and new STM32 MPU ecosystem release v5.0.0 . The aim is to help migrate your project.
All Information about the features delivered in the new release is also available in the OpenSTLinux release note.
3. Impacted domains[edit source]
3.1. Yocto build environment for Distribution Package[edit source]
- None
3.2. Hardware configuration[edit source]
Check the device tree files for the STMP32 MPU board:
Linux® kernel: between Linux kernel v6.1-stm32mp-r1 (v6.1.28) and previous Linux kernel v5.15-stm32mp-r2 (v5.15.67)
U-Boot: between U-Boot v2022.10-stm32mp-r1 and previous U-Boot v2021.10-stm32mp-r2
- None except alignement with Linux® kernel device tree
OP-TEE: between OP-TEE 3.19.0-stm32mp-r1 and previous OP-TEE 3.16.0-stm32mp-r2
- New SCMI thread provisioning
- Reworked OCALL to OCALL2
- Move SCMI mailbox to Linux/U-Boot memory
- Full clock tree is applied in OP-TEE to allow clock tree update over FOTA
- Support bit offset for NVMEM
- Disable external device-tree support
- Low-power fixes
- For STM32MP15x lines :
- OP-TEE build in DDR (pager OFF) : Some services are now default disabled
TF-A: between TF-A v2.8-stm32mp-r1 and previous TF-A v2.6-stm32mp-r2
- Remove BL32 (SP_MIN) configuration
- BL2 always runs at 650MHz (PLL1 configuration removed from DT)
- STM32MP15x lines RCC configuration updated to follow new bindings
- Move compatible to secure RCC from SoC DT to board DT
- Shared memory with OP-TEE removed
3.3. System configuration[edit source]
3.4. Boot stages[edit source]
- ecosystem release v5.0.0 no more supports the TF-A SP-MIN as secure monitor.
OP-TEE is only the supported BL32 and you must migrate the STM32MP15x lines projects to use it - The MTD partitions are defined in U-Boot device tree and no more in U-Boot defconfig
3.5. Security[edit source]
- New implementation of a secure watchdog
- New device-tree RNG configuration
- Use of watchdog framework
- Fix IWDG early-interrupt
3.6. User space and applications[edit source]
- None
4. References[edit source]