Changes notification

Applicable for

STM32MP13x lines, STM32MP15x lines, STM32MP25x lines

1. Article purpose[edit | 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 | edit source]

This article provides some details for the main changes between STM32 MPU ecosystem release v5.0.0 and new STM32 MPU ecosystem release v5.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[edit | edit source]

3.1. Yocto build environment for Distribution Package[edit | edit source]

None

3.2. Hardware configuration[edit | edit source]

Check the device tree files for the STMP32 MPU board:

Linux^® kernel: between Linux kernel v6.1-stm32mp-r2 (v6.1.82) and previous Linux kernel v6.1-stm32mp-r1 (v6.1.28)

None

U-Boot: between U-Boot v2022.10-stm32mp-r2 and previous U-Boot v2022.10-stm32mp-r1

None

OP-TEE: between OP-TEE 3.19.0-stm32mp-r2 and previous OP-TEE 3.19.0-stm32mp-r1

None

TF-A: between TF-A v2.8-stm32mp-r2 and previous TF-A v2.8-stm32mp-r1

None

Information

This is possible with git diff command to get delta between two branches in the same repository.
Example with STLINUX GitHub repository and for all STM32MP1 device tree files:

git diff v5.10-stm32mp-r2 v5.15-stm32mp-r1 -- arch/arm/boot/dts/stm32mp1*

3.3. System configuration[edit | edit source]

FIP only has been supported since the STM32 MPU ecosystem release v5.0.0 . NoFIP is no more supported.

3.4. Boot stages[edit | edit source]

None

3.5. Security[edit | edit source]

New ST_OPTEE_PROFILE is set on Yocto MACHINE to select OP-TEE configuration:
- system_services
- secure_and_system_services

3.6. User space and applications[edit | edit source]

None