- Last edited 4 months ago ago
1 Article purpose
The article aims to help to rebase an STM32 MPU project on a new ecosystem release by focusing on main changes impacts.
2 Scope of this article
This article provides some details for main changes between STM32 MPU ecosystem release v4.0.0 and new STM32 MPU ecosystem release v4.1.0 to help for migrating your project.
All Informations 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 device tree files for 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 since STM32 MPU ecosystem release v4.0.0 . NoFIP is no more supported
3.4 Boot stages
3.6 User space and applications