STM32CubeMX

Table Of Contents

- STM32CubeMX documentation
- CubeMX User Manual
  - 1 STM32Cube overview
  - 2 Getting started with STM32CubeMX
  - 3 Installing and running STM32CubeMX
  - 4 STM32CubeMX user interface
  - 5 STM32CubeMX tools
  - 6 STM32CubeMX C Code generation overview
  - 7 Code generation for dual-core MCUs (STM32H7 dual-core product lines only)
  - 8 Code generation with TrustZone enabled (STM32L5 series only)
  - 9 Device tree generation (STM32MPUs only)
  - 10 Support of additional software components using CMSIS-Pack standard
  - 11 Tutorial 1: From pinout to project C code generation using an MCU of the STM32F4 series
  - 12 Tutorial 2 - Example of FatFs on an SD card using STM32429I-EVAL evaluation board
  - 13 Tutorial 3 - Using the Power Consumption Calculator to optimize the embedded application consumption and more
  - 14 Tutorial 4 - Example of UART communications with an STM32L053xx Nucleo board
  - 15 Tutorial 5: Exporting current project configuration to a compatible MCU
  - 16 Tutorial 6 - Adding embedded software packs to user projects
  - 17 Tutorial 7 - Using the X-Cube-BLE1 software pack
  - 18 Creating LPBAM projects
  - Appendix A STM32CubeMX pin assignment rules
  - Appendix B STM32CubeMX C code generation design choices and limitations
  - Appendix C STM32 microcontrollers power consumption parameters
  - Appendix D STM32Cube embedded software packages
  - Revision history
- Release Notes
  - Release details
  - Release fixes
  - Known limitations
    - Miscellaneous
    - 2.1. When selecting microcontrollers in the STM32C0 series
    - 2.2. When selecting microcontrollers in the STM32G0 series
    - 2.3. When selecting microcontrollers in the STM32G4 series
    - 2.4. When selecting microcontrollers in the STM32H5 series
    - 2.5. When selecting microcontrollers in the STM32H7 series
    - 2.6. When selecting dual-core microcontrollers in the STM32H7 series
    - 2.7. When selecting microcontrollers in the STM32L5 series
    - 3.4. How to improve the wake-up from Stop sequences without relying on the global SystemClock_Config()
    - 3.3. List pinout-compatible microcontrollers
    - 3.2. DDR binaries for the STM32MP1 boards
    - 3.1. Command line authentication required
    - 2.21. Symbolic links on Ubuntu
    - 2.20. User manual
    - 2.19. DDR test suite
    - 2.18. STM32CubeIDE toolchain
    - 2.13. When selecting microcontrollers in the STM32WL series
    - 2.11. When selecting microcontrollers in the STM32WB series
    - 2.17. When using additional software packs
    - 2.16. When using the Example Selector
    - 2.15. When using the Memory Management Tool
    - 2.14. When selecting microprocessors in the STM32MP1 series
    - 2.11.1. When selecting microcontrollers in the STM32WB0 product lines
    - 2.12. When selecting microcontrollers in the STM32WBA series
    - 2.13.1. When selecting microcontrollers in the STM32WL33 product lines
    - 2.10. When selecting microcontrollers in the STM32U5 series
    - 2.9. When selecting microcontrollers in the STM32U3 series
    - 2.8. When selecting microcontrollers in the STM32N6 series
- Running STM32CubeMX in command-line mode
- FAQ
- Community

# 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.