Changes notification

Applicable for

STM32MP13x lines, STM32MP15x lines, STM32MP21x lines, STM32MP23x 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.1.0 and new STM32 MPU ecosystem release v6.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.

Important

In case of upgrade from OpenSTLinux ecosystem release v5.0.0, check first the previous release change notification available in the wiki dedicated to the v5.y.z ecosystem releases:

STM32 MPU OpenSTLinux release changes notification – v5.1.0

3. Impacted domains[edit | edit source]

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

For the process to enable secure boot from Distribution package updated, refer to dedicated wiki page.

3.2. Hardware configuration[edit | edit source]

Check the device tree files for the STMP32 MPU board for more details:

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

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

Alignment with Linux^® kernel device tree

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

Alignment with Linux^® kernel device tree

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

Alignment with Linux^® kernel device tree

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 v6.1-stm32mp-r2 v6.6-stm32mp-r1 -- arch/arm/boot/dts/stm32mp1*

3.3. System configuration[edit | edit source]

The configuration of optee profile are now centralized via the usage of boot scheme:
- BOOTSCHEME_LABELS += "opteemin" for system_services
- BOOTSCHEME_LABELS += "optee" for secure_and_system_services

3.4. Boot stages[edit | edit source]

None

3.5. Security[edit | edit source]

None

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

None