1. STM32CubeMX 6.12.1 - MPU support[edit | edit source]
1.1. Main fixed issues[edit | edit source]
The STM32CubeMX V6.12.1 solves the following issues:
- Device tree generation: Misconfiguration of some peripherals in the STM32MP257F-EV1 and STM32MP257F-DK ".ioc" files is causing issues in the device tree generation.
- DDR mapping: The address A19 cannot be assigned in DDR mapping.
- RCC configuration in Cortex®-M33: When configuring a peripheral in the Cortex®-M33 context, the FLEXCLKGEN settings for the RCC node in the device tree (DT) are not generated.
2. STM32CubeMX 6.12.0 - MPU support[edit | edit source]
2.1. New features supported in this release[edit | edit source]
- Support of STM32MP25x lines
- Add a new feature called Resource Isolation Framework (RIF) which acts as a security guard for certain components of the microprocessor (peripherals) and its memory (for STM32MP2 series).
2.2. Features already supported in previous releases[edit | edit source]
- Support of STM32MP13x lines
- Support of STM32MP15x lines
- Support for Azure RTOS ThreadX, FileX, LevelX, NETX and USBX, for STM32CubeMP13 package release
2.3. Main changes coming with new release[edit | edit source]
- Add new Intropack openstlinux-6.1-yocto-mickledore-mpu-v24.06.26 for STM32MPU (STM32MP1 series & STM32MP2 series).
2.4. Known limitations[edit | edit source]
2.4.1. With STM32MP25x[edit | edit source]
- Only STM32CubeIDE is supported.
- STM32CubeMX configurations (IOC) for STM32MP257F-EV1 Evaluation board
and STM32MP257F-DK Discovery kit do not configure LTDC in secure mode (trusted UI is disabled). This differs from OpenSTLinux software configuration where the trusted UI is enabled for these boards. - The synchronization between OSPIx peripherals assignments and the RCC features OSPI1/2_CFGR assignments is not "automatically" performed. OSPI1/2_CFGR features assignments should be done whenever OSPI1/2 are used in order to clock correctly the peripheral(s).
- The assignments of the RCC features OCTOSPIx_CFGR and xxxRAM_CFGR are not automatically synchronized with the assignments of their hardware resources (OCTOSPIx peripherals and RAM regions). These assignments should be done manually to clock correctly the hardware resources. STM32CubeMX displays tips helpers for each of these features.
- In the pinout & configuration view, the U-Boot context assignments are not synchronized with the Linux® context assignments. Whenever a peripheral is assigned for U-Boot, it should be also assigned for Linux®. (the opposite is not true).
- IOM/OSPI: to handle properly the clocks when OSPIx is used in Multiplexed mode and OSPIy is not used, the (RCC) OSPIy_CFGR feature should have the same assignment as OSPIx_CFGR one.
- When FMC is assigned to a Cortex®-M33 nonsecure Cube firmware (HAL & LL) context, the NVIC panel is not displayed.
- The device trees generated by STM32CubeMX for the STM32MP257F-DK Discovery kit and STM32MP257F-EV1 Evaluation board boards are fully functional. Although these device trees are close to the "STM32 MPU embedded software device tree" configuration, some differences may exist. Refer to the chapter External_device_tree for details on "STM32 MPU embedded software device tree".
- When creating a STM32MP25 empty project, a partial configuration of the (RIF) RISAFx and RISABx sub-system is pre-filled. This configuration is the OpenSTLinux one but limited to the definition of the regions name and size (security not defined).
These are the complete OpenSTLinux configuration including security aspects:
RISAF1(BKPSRAM)
RISAF2(OCTOSPI1&2)
RISAF4(DDR)
RISAF5(PCIE)
RISAB1(SYSRAM1)
RISAB2(SYSRAM2)
RISAB3(SRAM1)
RISAB4(SRAM2)
RISAB5(RETRAM)
RISAB6(VDERAM)
2.4.2. With STM32CubeMP13 package[edit | edit source]
- Only STM32CubeIDE is supported.
- Only application context is supported.
- Standard version of LevelX, USBX, NetX middlewares integrated without STM32MP13 platform specific patches.
- When using the STM32CubeMP13 package and activating Azure® RTOS ThreadX, the STM32CubeIDE linker file must contain the following section to avoid compilation issues:
.stack :
{
_stack_bottom = ABSOLUTE(.) ;
/* Allocate room for stack. This must be big enough for the
IRQ, FIQ, and SYS stack if nested interrupts are
enabled.*/
. = ALIGN(8) ;
. += 32768 ;
_sp = . - 16 ;
_stack_top = ABSOLUTE(.) ;
} >RAM
_end = .;
3. How to get STM32CubeMX[edit | edit source]
| STM32CubeMX for Linux®, Windows® and macOS ® | ||
|---|---|---|
| Download |
Version 6.12.1
| |
| Installation guide |
| |
| User manual |
| |
| Detailed release note |
| |
Minor releases may be available from the update site.