Release limitations

STM32 series limitations

STM32 series

Limitations

STM32H7 microcontrollers

Support integrity check for SFI:

  • Only the devices with a bootloader version higher than 0x91 are supported.

  • STM32CubeProgrammer does not support devices with older bootloader versions. Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.

STM32H73xxx microcontrollers

Support integrity check for SFI/SFIx:

  • Only the devices with a bootloader version higher than 0x93 are supported.

  • STM32CubeProgrammer does not support devices with older bootloader versions. Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.

STM32H7Bxxx microcontrollers

Support integrity check for SFI/SFIx:

  • Only the devices with a bootloader version equal to or higher than 0x92 are supported.

  • STM32CubeProgrammer does not support devices with older bootloader versions. Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.

STM32H7 microcontrollers

  • STM32CubeProgrammer does not support SFI.

  • STM32H7Axxx/Bxxx microcontrollers: download verification issue with OTP.

STM32H7Rx/7Sx microcontrollers

  • Erasing the external flash memory is not supported using IWDG.

  • GUI: the external memory edition is not supported via USB and UART while connected to the OpenBootloader.

  • Option bytes are not supported via OpenBootloader interfaces.

STM32L0 microcontrollers

  • Register access mode incorrectly displayed for register viewer.

STM32L4R5xx microcontrollers

  • Issues occur when erasing sectors in bank 2 memory with the UART interface.

STM32U3 microcontrollers

  • Limited support via JTAG (functional only with mode = normal and reset = HWrst).

  • STM32U3C5/STM32U3B5: unable to program binary or change OB when IWDG_SW=0.

  • STM32U335/STM32U345: the programming operation fails when Swap_Bank is enabled.

STM32U5 microcontrollers

  • Unable to read the chip ID via J-Link when RDP is set to Level 2.

  • OTP memory programming failure with CLI when TZEN is enabled.

  • STM32U535/545 microcontrollers: SFIx is not supported.

  • STM32U59xxx microcontrollers: SFIx only supports the area E installation with OTFDEC region 1 (region 0 on TPC).

  • STM32U5Fxxx and STM32U5Gxxx microcontrollers: unable to program SFIx via SPI/I2C on GUI.

  • STM32U575/STM32U585 microcontrollers: for CPNs with flash size 1M, erase selected sectors fails when SWAP_BANK is enabled.

  • STM32U535/STM32U545 microcontrollers: for CPNs with flash size 2M, erase selected sectors fails when SWAP_BANK is enabled with the UART interface.

STM32L43 and STM32L45 microcontrollers

  • Failed to erase a part of the last sector using the GUI with the SWD interface.

STM32WBA microcontrollers

  • OpenBootloader via SPI: cannot connect to STM32CubeProgrammer when the baud rate is below 3000 Bd.

  • Connect Under Reset is not working when called by STM32CubeIDE.

STM32WBA2 microcontrollers

  • Erase operation failed when the external loader is selected. Note: deselect the external flash to be able to perform the erase operation.

STM32WL33 microcontrollers

  • Failed to connect with Hotplug mode on CLI.

  • STM32CubeProgrammer fails to program RDP=0xABACABAD on WL33.

STM32L5 microcontrollers

  • Unable to read, write, or erase the external flash memory when TZEN is enabled.

  • SFI programming failed via UART on Linux.

STM32V8 microcontroller

  • Erase NVM High Cycle data is not working; a workaround is to write 0xFFFFFFFF in the register.

STM32H74x/5x/7x microcontrollers

  • When connecting the target via J-LINK, the BCM4 option byte is removed from STM32CubeProgrammer if it has been disabled.

Additional limitations

  • SFIx fails when programming:

    • Large flash memory content on Linux via the UART interface.

    • Small flash memory content on supported bootloader interfaces with all platforms.

  • USB interoperability issue on macOS due to ST-LINK limitation.

  • Incremental programming :

    • Is not supported when TrustZone is enabled; the tool switches automatically to the normal programming procedure.

    • Is an experimental feature with limited test coverage:

      For internal flash programming, tested devices are: STM32C03x, STM32C05x, STM32C09x, STM32F101/F102/F103, STM32F37xx, STM32F411xC/E, STM32F72x/STM32F73x, STM32F76x/STM32F77x, STM32G03x/STM32G04x, STM32G0B0xx/B1xx/C1xx, STM32G491xx, STM32H50x, STM32H533/523, STM32H56x/573, STM32H72x/STM32H73x, STM32H7R/Sxx, STM32L05x/L06x/L010, STM32L4Pxxx/STM32L4Qxxx, STM32L4x1/STM32L475xx/STM32L476xx/STM32L486xx, STM32L5xx, STM32U0xx, STM32U3xx, STM32U535/STM32U545, STM32U575/STM32U585, STM32U59x/5Ax, STM32WB5x/35xx, STM32WBA52/54/55, STM32WBA6x, and STM32WLxx.

      For external flash programming, tested boards are: STM32H735G-DK, STM32H7S78-DK, STM32H573I-DK, STM32U575I-EV, STM32WBA65I-DK1.

  • The automatic mode does not work with the UART interface when using an ST-LINK with dual VCP. The ST-LINK configuration must be changed to single VCP.

  • In Windows 10 32-bit, STM32TrustedPackageCreator display can be cut when maximizing the window.

  • OBKey provisioning with J-LINK is not supported. Currently, the CLI says it clearly, but the GUI message does not.

  • Memory map export supports a maximum of 9 segments.

  • SWV feature is provided as a beta functionality for STM32V8 and STM32C5 devices. It is not fully validated.

  • MCU factory reset is supported only via ST-LINK.

  • RDP regression with password is supported only via ST-LINK.

  • SFI feature:

    • For the full list of supported devices, please refer to AN4992.

    • Parallel SFI Programming with Shared HSM is not supported.

    • SFI is not working with SWD multidrop.

  • Starting from STM32CubeProgrammer v2.21.0, the -align option when using STM32_SigningTool_CLI is mandatory with STM32N6.

  • Write and erase operations using an external flash with a start address of 0x00000000 are not supported.

  • Flash high cycle:

    • Programming is not supported at secure addresses.

    • A masse erase is required before programming the full flash high cycle area (bank1+bank2).

  • The flash high cycle programming is not supported on secure address.

  • The OTP memory programming is not supported when TZEN is enabled for CM33 SoCs.

  • Display issues occur on Fedora when the system display scale is set to 125%; the recommended scale is 100%.

  • Any file path provided as an input argument to the STM32CubeProgrammer CLI that contains spaces must be enclosed in quotation marks.