- Last edited 6 days ago ago
Changes notification – v4.1.0
1 Article purpose
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
This article provides some details for the main changes between STM32 MPU ecosystem release v4.0.0 and new STM32 MPU ecosystem release v4.1.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
3.1 Yocto build environment for Distribution Package
3.2 Hardware configuration
Check the device tree files for the STMP32 MPU board:
Linux® kernel: between Linux kernel v5.15-stm32mp-r2 (v5.15.67) and previous Linux kernel v5.15-stm32mp-r1 (v5.15.24)
- IIO consumer binding and channels configuration update. Links and examples updated in ADC device tree configuration example
U-Boot: between U-Boot v2021.10-stm32mp-r2 and previous U-Boot v2021.10-stm32mp-r1
OP-TEE: between OP-TEE 3.16.0-stm32mp-r2 and previous OP-TEE 3.16.0-stm32mp-r1
TF-A: between TF-A v2.6-stm32mp-r2 and previous TF-A v2.6-stm32mp-r1
- Chain of Trust (COT) binding update. Links updated in TF-A_BL2_Chain of trust implementation
3.3 System configuration
- FIP only has been supported since the STM32 MPU ecosystem release v4.0.0 . NoFIP is no more supported.
3.4 Boot stages
3.6 User space and applications