STM32CubeProgrammer errata 2.21.x

This message will disappear after all relevant tasks have been resolved.
Semantic MediaWiki
There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.

1. Main fixed issues for 2.21.0

ID Summary
193410 Missing Character in Password Provisioning
216560 Sector erase failing on new STM32N6 Nucleo boards
214191 STM32U3 512K STM32CubeProgrammer fails to program flash when DBANK=0
210646 Wrong flash size and access on STM32C071
214133 [Register_Viewer] Hidden value and address of register in Chinese and Japanese languages
204571 [JLINK][GUI/CLI] BCM4 option byte disappears when disabled
215010 [JLINK][CLI][Linux] STM32CubeProgrammer CLI fails to Link the J-Link/Flasher Library
207456 [I2C][STM32L5] Issue with sectors erase
206698 [Uninstaller][Linux] The uninstaller.jar file doesn't work
208327 [STM32H5] Unexpected erase of High-Cycle Data sectors after programming
213383 Debug reopen reports authentication failure but connects successfully
197406 Error handling for missing or incorrect Debug Authentication files
208498 [CLI][CRC] Empty lines in HEX files after CRC injection
209082 [CLI][Linux] Libusb warnings when using serial number parameter
212409 [GUI][UART] Excessive 'Get ID' packets causing GUI freeze in STM32CubeProgrammer
212475 [Safety] No difference observed when using <pattern> option with the safelib command
209760 [STM32WB55] [CLI] RDP regression issue with Bootloader via USB
207265 [GUI] Incorrect reset log message for DFU connection
219756 [STM32WBAx][OTP] Partial write and error when programming OTP
218753 [Register Viewer][STM32WL33] Unable to read MCU registers

2. Known problems and limitations

  • Integrity check:
    • STM32H7 microcontrollers: support integrity check for SFI:
      • Only the devices with a bootloader version higher than 0x91 are supported.
      • STM32CubeProgrammer does not support the 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 the 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 the devices with older bootloader versions. Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.
  • Debug authentication is not supported on Windows® 32 bits.
  • SFIx fails for large flash memory content on Linux® via the UART interface.
  • USB interoperability issue on macOS® due to ST-LINK limitation.
  • 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.
  • STM32L5 and STM32U5 microcontrollers:
    • Unable to read, write, or erase the external flash memory when TZEN is enabled.
  • STM32U3 microcontrollers:
    • Limited support via JTAG (functional only with mode = normal and reset = HWrst).
  • 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.
  • 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.
  • Debug authentication is not supported on Windows® 32 bits.
  • SFIx fails for small flash memory content on supported bootloader interfaces with all platforms.
  • USB interoperability issue on macOS  due to STLINK limitation
  • Unable to read the Chip ID of the STM32U5 via JLINK when RDP is set to Level 2.
  • For MacOS, in order to build the API project, user must:
    • Copy the content of bin folder into API/Lib folder
    • Copy the Data_Base folder into the API folder
  • STM32H74x/5x/7x: When connecting the target via JLINK, the BCM4 option byte is removed from STM32CubeProgrammer if it has been disabled.
  • STM32WL33:
    • Failed to connect with Hotplug mode on CLI.
    • STM32CubeProgrammer fails to program RDP=0xABACABAD on WL33.
  • STM32L5: SFI programming failed via UART on Linux.
  • STM32U575/STM32U585: For CPNs with flash Size 1M, failed to erase using Erase selected sectors when SWAP_BANK is enabled.
  • Incremental programming 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, STM32WLxx
    • For external flash programming, tested boards are: STM32H735G-DK, STM32H7S78-DK, STM32H573I-DK, STM32U575I-EV, STM32WBA65I-DK1.
    • Incremental programming is not supported when TrustZone is enabled, the tool switches automatically to normal programming procedure.
  • SFI is not working with SWD multi-drop.
  • The automatic mode doesn't work with UART interface when using an STLink with Dual VCP, the STLink configuration must be changed to single VCP.
  • In windows 10 32 bits: STM32TrustedPackageCreator display can be cut when maximizing the window.
  • OBkey provisioning with JLINK is not supported, currently the CLI says it clearly, but the GUI message doesn't.
Retrieved from "https://wiki.st.com/stm32mcu/index.php?title=STM32CubeProgrammer_errata_2.21.x&oldid=82418"