STM32CubeMX2 Configuration Limitations

Contents

  • This page lists the Configuration Limitations when using STM32C5 SW Packs 2.1.0 with STM32CubeMX2 version V1.0.1.

  • These limitations will be addressed in a future official/alpha releases, planned for Q4 2026.

General

  • Start from board menu in STM32CubeMX2 does not pre-configure the Part drivers. An example_template_start_from_nucleo is provided to show how to start a project with button, LED and console activated.

  • The Generated Functions Calls feature is available in STM32CubeMX, but not in STM32CubeMX2. To achieve similar functionality in STM32CubeMX2, end-user should manually implement function calls in the user code sections after code generation.

STM32C5xx HAL Drivers Configuration

  • HAL/LL

    • The list of interconnects retrieved from the hardware capabilities may be incorrect because some peripherals are not available on certain STM32 devices. End-user should refer to the device datasheet to verify peripheral availability.

    • Resolution of components for STM32C5xx HAL Drivers Pack in integrated development environments other than STM32CubeMX2 is not automatic. End user should manually resolve STM32C5xx HAL Drivers Pack components when using other IDEs.

    • The privilege configuration for STM32C5xx HAL Drivers is not available in STM32CubeMX2.

  • ETH

    • When starting project from board (NUCLEO-C5A3ZG), the Ethernet (ETH) pins are not automatically reserved. When activating the ETH peripheral, end-user must manually assign the pins to the correct board pin configurations.

  • RTC

    • For STM32C542 and STM32C53x devices, the RTC panel configuration features are incomplete. In the Main features section, under Mode, only Free running BCD calendar is available in the pick list. The options Free running binary and Free running BCD calendar and binary must also be displayed.

  • TIM

    • When selecting STM32C531xx, enabling TIM2 channels, input selection of Channel displays FDCAN1 and FDCAN2 whereas it is not possible. As a consequence, an error when compiling the generated code could happen.

  • Timebase

    • When HAL timebase is set to timer or RTC, user must set manually the peripheral interruption priority to lowest values (15 for instance).

  • USART

    • In controller mode, RX DMA depends on the TX DMA trigger, although the trigger configuration applies only to TX DMA. The configuration panel does not currently force TX DMA to be enabled when RX DMA is enabled and controller mode is selected. A message has to be added to inform the user.

FreeRTOS Configuration

USBX Configuration

  • Possible compilation warning if the user configures the USBX core without selecting a USBX device class or host class.

EEPROM Emulation Configuration

  • The start address selected by the user must be one of the addresses in the valid start address list.

Thread Safe LibC Configuration

  • The user must manage specific toolchain settings when using STM32CubeMX2.

Open Bootloader Configuration

  • When a project is generated by using the USBX interface, STM32CubeProgrammer identifies the application as an in-application programming (IAP), not as Open Bootloader. The generated code can be adapted at the application level.