2.4. When selecting microcontrollers in the STM32H5 series

When creating a new STM32H5 project, enabling the JPEG peripheral and generating the code, the Utilities/JPEG folder containing the JPEG source files is not generated.

To avoid this issue, the user should add the missing folder manually by copying it from the firmware under this path:

Users\<User_name>\STM32Cube\Repository\STM32Cube_FW_H5_Vx.y.z\Utilities

The following configuration will be lost after migrating to STM32CubeMX version 6.15.0: an STM32H573ZITx project created with STM32CubeMX version 6.14.1, where the OctoSPI1 peripheral is enabled, the boot path is configured, and an MMT user application region is defined within the OctoSPI1-controlled memory range ( 0x90000000 to 0xA0000000). Additionally, the Application Regions Settings are applied to both the peripheral configuration and linker files.

Upon migration, a popup notification will inform the user about the MMT user application region loss. The Application Regions Settings will be disabled for both peripherals and linker files. Furthermore, the hardware memory range managed by OctoSPI1 will be split into two sub-regions: - The first region, labeled “External memory (OCTOSPI1)”, with a size of 2 bytes. - The second region, labeled “OCTOSPI1”, with a size of less than 256 Mbytes.

To avoid the issue, the user is recommended to: - Increase the Memory Size parameter under the OctoSPI1 Configuration tab to 2 Gbits (256 MByte). - Recreate manually the MMT user application region that was allocated to the memory range controlled by OctoSPI1. - Turn on the “Apply Application Regions Settings to Peripherals” and “Apply Application Regions Settings to Linker Files” toggle buttons in the MMT panel.

For STM32CubeMX 6.14.0 OEMiROT projects, the execution of provisionning.bat might fail due to wrong file path settings. To fix this failure, the user should either keep the default boot path configuration in STM32CubeMX, or edit env.bat and set oemirot_boot_path_project to %~dp0..\.

When migrating projects with OEM-iROT boot path from STM32CubeMX V6.8.x to STM32CubeMX V6.10.x or later releases, the user might need to reconfigure ROT_Provisioning.

The makefile generation no longer works as soon as the project structure is changed from “Secure Project only” or “Non Secure Project only” to “Secure Project and Non Secure Project enabled (dual project)”.

In Microsoft® Azure® NetX Duo, some configuration flags, which are not used in the STM32Cube firmware package examples, might be nonfunctional when combined.

When generating an STM32H5 project with the Makefile toolchain and ThreadX enabled, some errors can appear.

Workaround: Under the Project Manager tab, select Copy only the necessary library files option instead of Copy all used libraries into the project folder.