Changes notification

BackToNavigationTree button.png



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 v6.1.0 More info.png and new STM32 MPU ecosystem release v6.2.0 More info.png . The aim is to help you to migrate your project.

All Information about the features delivered in the new release is available in the OpenSTLinux release note.

Warning DB.png Important

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

3. Impacted domains[edit | edit source]

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

  • Remove usage specific image for each partitions
  • Add image class to split rootfs image on several partitions: ST SPLIT PARTITIONS
  • "STM32CubeMP1" and "STM32CubeMP2" directories renamed (not the recipe name)
  • STM32CubeMP2: management of firmware ready to used via m33fw-stm32mp2 (default STM32CubeMP2 recipe provide only binaries that can be associated to others binary blob)
  • IMAGE: all partitions needed by the flashlayout are provided by the class stsplitpartitions with partitions split's of default rootfs image.

3.2. Hardware configuration[edit | edit source]

Check the device tree files for the STMP32 MPU board. For that, you compare the both versions of the following components:

Info white.png 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.6-stm32mp-r2 v6.6-stm32mp-r3 -- arch/arm/boot/dts/stm32mp1*

3.3. System configuration[edit | edit source]

  • Directory tree changed in External DT component
  • The configuration of OP-TEE profile is 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

4. References[edit | edit source]





No categories assignedEdit