- Last edited 3 weeks ago ago
Changes notification – v5.0.0
Contents
1 Article purpose[edit]
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]
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]
3.1 Yocto build environment for Distribution Package[edit]
- For the process to enable secure boot from Distribution package updated, refer to dedicated wiki page.
3.2 Hardware configuration[edit]
Check the device tree files for the STMP32 MPU board for more details:
Linux® kernel: between Linux kernel v6.1-stm32mp-r1 (v6.1.28) and previous Linux kernel v5.15-stm32mp-r2 (v5.15.67)
- arm_wdt node enabled for watchdog
- New etzpc node section
U-Boot: between U-Boot v2022.10-stm32mp-r1 and previous U-Boot v2021.10-stm32mp-r2
- Alignment with Linux® kernel device tree
OP-TEE: between OP-TEE 3.19.0-stm32mp-r1 and previous OP-TEE 3.16.0-stm32mp-r2
- Alignment with Linux® kernel device tree
TF-A: between TF-A v2.8-stm32mp-r1 and previous TF-A v2.6-stm32mp-r2
- Alignment with Linux® kernel device tree
- BL2 always runs at 650MHz (PLL1 configuration removed from DT)
- Move compatible field to secure RCC from SoC DT to board DT
- Shared memory with OP-TEE removed
- For STM32MP15x lines
- RCC configuration updated to follow new bindings
3.3 System configuration[edit]
- None
3.4 Boot stages[edit]
- This ecosystem release v5.0.0
does not support anymore the TF-A SP-MIN as secure monitor.
OP-TEE is only the supported BL32 and you must migrate the STM32MP15x linesprojects to be able to use it.
- The MTD partitions are defined in U-Boot device tree and are no more defined in U-Boot defconfig.
3.5 Security[edit]
- New implementation of a secure watchdog
- New device-tree RNG configuration
- Use of a watchdog framework
- IWDG early-interrupt fixing
3.6 User space and applications[edit]
- None