1. Article purpose[edit source]
The article aims to help you to rebase your STM32 MPU project on a new ecosystem release by focusing on main changes impacts.
2. Scope of this article[edit source]
This article provides some details for main changes between STM32 MPU ecosystem release v3.1.0 and new STM32 MPU ecosystem release v4.0.0 
, to help you for migration.
3. Impacted domains[edit source]
|
Ongoing |
3.1. Yocto build environment (Distribution Package)[edit source]
Yocto layers/recipes to update for new Kirkstone verson. Follow scripts available in OpenEmbedded-Core layer to help user:
- ./layers/openembedded-core/scripts/contrib/convert-overrides.py
- ./layers/openembedded-core/scripts/contrib/convert-spdx-licenses.py
- ./layers/openembedded-core/scripts/contrib/convert-srcuri.py
- ./layers/openembedded-core/scripts/contrib/convert-variable-renames.py
- (cf Yocto Kirkstone release note[1] for more information)
3.2. Hardware configuration[edit source]
Device tree board delta between V4 and V3
3.3. Software configuration[edit source]
FIP only on 4.0. NoFIP no more supported
FOTA (memory mapping if activated). if no FOTA activate, no change at driver level. Impact on flashlayout.
3.4. Boot stages[edit source]
3.5. Security[edit source]
BL2 more hardcoded and less configurable SPMIN deprecated (will be removed in OSTLv5.0), replaced by OP-TEE. OP-TEE:
- Memory mapping update linked to OP-TEE
- SCMI services usage
- bindings changes on OTP calibration
OTP provisioning protocol updated
3.6. User space and applications[edit source]
New "weston" user for wayland, which avoid executing some application with root profile
- su -l weston -c "<command>" could be used to specify the user profile
Graphic frameworks user change for security reasons (change from community)