2026-03-02 7:18 AM
Hello,
I Installed STM32CubeMX v6.17.0 with STM32MP2 Software Pack 1.3.0.
I see that code generated for CA35 differs from the one generated by the previous version of STM32CubeMX v6.16.1.
By the diff below I see that 6.17.0 expects Yocto tree version openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18:
- model = "STMicroelectronics STM32MP257F-DK STM32CubeMX board - openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11";
+ model = "STMicroelectronics STM32MP257F-DK STM32CubeMX board - openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18";
These are not the only differences between CubeMX versions, there are more in the .dts/dtsi definitions.
In the Project Manager window I see that the OpenSTLinux Manifest version is set to openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18.
However I'm not planning to switch to Yocto openstlinux-6.6-yocto-scarthgap-mpu-v26.02.18 just now.
Is it possible to use CubeMX v6.17.0 with the older Yocto tree version openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11?
Regards,
Sergei
2026-03-02 7:24 AM
Hi @sergei.poselenov ,
CubeMX version is indeed always strongly related to an associate OpenSTLinux release.
DeviceTree generated with 6.17 will likely generate error if compiled with openstlinux-6.6-yocto-scarthgap-mpu-v25.06.11 source and SDK.
Better to stick on 6.16.1.
Olivier