STM32CubeMX release note

Applicable for

STM32MP13x lines, STM32MP15x lines

1. STM32CubeMX 6.12.0 - MPU support[edit source]

1.1. New features supported in this releases[edit source]

Support of STM32CubeMP2 package running on the Arm^® Cortex^®-A35 and Arm^® Cortex^®-M33 processors.
Add a new feature called Resource Isolation Framework (RIF) which acts as a security guard for certain components of the microcontroller (peripherals) and its memory.

1.2. Features already supported in previous releases[edit source]

Support of STM32CubeMP13 package running on the Arm^® Cortex^®-A7 processor.
Support of STM32CubeMP15 package running on the Arm^® Cortex^®-A7 and Arm^® Cortex^®-M4 processors.
Support for Azure RTOS ThreadX, FileX, LevelX, NETX and USBX, for STM32CubeMP13 package release

1.3. Main changes coming with new release[edit source]

STM32MP135x A/C CPU max frequency was wrongly set to 900 MHZ instead of 650 MHZ.
CLK_RTC_LSE not generated in TF-A DT (default configuration)

1.4. Known limitations[edit source]

RISAF1(BKPSRAM)

====With STM32CubeMP25x package====

STM32CubeMX configurations (IOC) for STM32MP257F-EV1 and STM32MP257F-EV1 boards do not configure LTDC in secure mode (trusted UI is disabled). This differs from OpenSTLinux 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 w the assignments of their HW resources (OCTOSPIx peripherals and RAM regions). These assignments should be done manually to clock correctly the HW 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 you assign a peripheral to U-Boot should also assign it to 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 than OSPIx_CFGR one.
When FMC is assigned to a Cube Context, the NVIC panel is not displayed.
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:

1.4.1. With STM32CubeMP13 package[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 = .;

2. How to get STM32CubeMX[edit source]

	STM32CubeMX for Linux^®, Windows^® and macOS ^®
Download	Version 6.12.0 Download the preferred all-in-one installer from www.st.com Generic Linux^® installer - STM32CubeMX-Lin Windows^® installer - STM32CubeMX-Win macOS^® installer - STM32CubeMX-Mac
Installation guide	Refer to the installation guide section of the STM32CubeMX user manual (UM1718) available on www.st.com.
User manual	When the installation is completed, see additional information about STM32CubeMX from www.st.com in the STM32CubeMX user manual (UM1718)
Detailed release note	Details about the content of this tool version are available in the STM32CubeMX release 6.12.0 release note from www.st.com

Minor releases may be available from the update site.