RN0109 STM32CubeProgrammer Release Note v2.13.0

Introduction

This release note is updated periodically to keep abreast of the STM32CubeProgrammer (STM32CubeProg) evolution, problems, and limitations. Check the STMicroelectronics website at www.st.com/stm32softwaretools for the latest version. For the latest release summary, refer to Table 1.

Table 1. STM32CubeProgrammer v2.13.0 release summary

Customer Support

For more information or help concerning STM32CubeProgrammer, contact the nearest STMicroelectronics sales office or use the ST community at community.st.com. For a complete list of STMicroelectronics offices and distributors, refer to the www.st.com webpage.

Software Updates

Software updates and all the latest documentation can be downloaded from the STMicroelectronics support webpage at www.st.com/stm32cubeprog.

General Information

Overview

STM32CubeProgrammer is a tool that allows STM32 device programming through debug interfaces (JTAG and SWD) and bootloader interfaces (UART, USB, I2C, SPI, and CAN). The range of supported bootloader interfaces depends on the microcontroller connected. Refer to the STM32 microcontroller system memory boot mode application note (AN2606) for details.

The tool offers a wide range of features to program STM32 internal memories (flash memory, RAM, OTP, and others) and external memories, verify the programming content (checksum, verify during and after programming, compare with file), and automate STM32 programming.

The STM32CubeProgrammer package also offers the optional installation of the STM32 Trusted Package Creator tool, which is used to create secure firmware files for secure firmware install and update. For more information, refer to the STM32 Trusted Package Creator tool software description user manual (UM2238).

STM32CubeProgrammer supports STM32 32-bit microcontrollers and microprocessors based on the Arm^® Cortex^® processor.

Arm is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.

Host PC System Requirements

Supported Operating Systems and Architectures

• Windows^® 7, 8, 10, and 11: 32 bits (x86) and 64 bits (x64)
• Linux^® 64 bits (tested on Ubuntu^® 64 bits)
• macOS^® (minimum version OS X^® Yosemite)

Windows is a trademark of the Microsoft group of companies. Linux^® is a registered trademark of Linus Torvalds. Ubuntu^® is a registered trademark of Canonical Ltd. macOS^® is a trademark of Apple Inc., registered in the U.S. and other countries and regions.

Software Requirements

For STM32CubeProgrammer versions earlier than v2.6.0, the Java^® SE Runtime Environment 1.8 (version 1.8.0_121 or newer) must be installed by Oracle^® (only Java^® 8 is supported).

Since STM32CubeProgrammer version v2.6.0, the tool can be installed without prerequisite JRE^™ installation, because the STM32CubeProgrammer release package contains a JRE^™ bundling.

After the Oracle^® announcement related to the “End of Public Updates for Oracle JDK 8”, access to OpenJDK is possible via adoptopenjdk.net.

Oracle is a registered trademark of Oracle and/or its affiliates. All other trademarks are the property of their respective owners.

Setup Procedure

Refer to the STM32CubeProgrammer software description user manual (UM2237) available at www.st.com.

Licensing

STM32CubeProg is delivered under the Mix Ultimate Liberty+OSS+3rd-party V1 software license agreement (SLA0048).

The software components used in the development of STM32CubeProgrammer and their licenses are listed in Table 2.

Table 2. List of software components licenses

1. License identifier as defined by OSI (opensource.org/licenses) or SPDX (spdx.org/licenses).

The software bundled with STM32CubeProgrammer and their licenses are listed in Table 3.

Table 3. List of software bundled with the tool

STM32CubeProgrammer v2.13.0 Release Information

New Features

• Added support for the STM32H5 series:
• STM32H563/573
  • Debug authentication with password or certificate
  • Authentication key provisioning
  • Key generation
  • Firmware encryption and signing
  • Certificate generation
• STM32H503
  • Debug authentication with password or certificate
  • Firmware encryption and signing
• Added support for the STM32WBA series:
• Flash memory and OTP programming, and option bytes
• Updated support for the STM32U5 series:
• STM32U535/545:
  • SFI support (user interface and command-line interface)
  • Flash memory, option bytes, RDP regression with password, and OTP programming.
• STM32U595/5A5:
  • SFI update (user interface and command-line interface)
  • SFIx update
  • Via debug: user interface and command-line interface
  • Via bootloader: command-line interface only
• Added support for the STLINK-V3PWR:
• Debug
• Bridge to bootloader interfaces (SPI, I2C, and CAN)
• Added new calculator features:
• Number converter
• File and flash memory checksum

Fixed Issues

Table 4. Main issues fixed in STM32CubeProgrammer v2.13.0

Known Problems and Limitations

Table 4. Main issues fixed in STM32CubeProgrammer v2.13.0 (continued)

• Integrity check:
  • STM32H7 microcontrollers: support integrity check for SFI/SMI:
    • Only the devices with a bootloader version higher than 0x91 are supported.
    • STM32CubeProgrammer v2.13.0 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/SMI/SFIx:
    • Only the devices with a bootloader version higher than 0x93 are supported.
    • STM32CubeProgrammer v2.13.0 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/SMI/SFIx:
    • Only the devices with a bootloader version higher than 0x92 are supported.
    • STM32CubeProgrammer v2.13.0 does not support the devices with older bootloader versions. Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.
• Auto mode (Linux^® platform):
  • The SPI interface quits after starting without a connection.
• STM32G0 microcontrollers:
  • The .hex file does not modify the WRP and PCROP option bytes of bank 2 for the devices with 512 Kbytes of dual-bank flash memory.
  • The SWD RegDump command-line instruction does not work on STM32G081xx devices.
• STM32H5 microcontrollers:
  • SFI and SSFI (secure manager) are not supported.
• STM32H503 microcontrollers:
  • A total of 64 bytes are programmed to the OTP area with STM32CubeProgrammer after password provisioning.
• STM32H7 microcontrollers:
  • STM32CubeProgrammer does not support combined SFI and SMI.
  • SMI programming fails.
• STM32MP15x microprocessors:
  • It is not possible to program a .tsv file when some partitions are not selected.
  • An error occurs when saving the OTP partition in a macOS^® platform.
• STM32U5 microcontrollers:
  • RDP regression with password is not working on macOS^®.
  • It is impossible to set OEM keys through DFU.
  • STM32U59xxx microcontrollers: SFIx only supports the area E installation with OTFDec region 1 (region 0 on TPC).
  • STM32U58xxx and STM32U59xxx microcontrollers: for the SFIx area K, the size value must be 32-bit aligned inside the .kcsv file.
• STM32WBA microcontrollers:
  • SFI is not supported.
  • OpenBootloader via SPI: cannot connect to STM32CubeProgrammer when the baud rate is below 3000 Bd.
• Azure^® RTOS USBX:
  • For STM32U575/585 microcontrollers, erasing sectors from "C" to "F" fails.
  • For STM32U575/585 microcontrollers, some extra data is added at memory programming.
• Debug authentication is not supported on macOS^® and Windows^® 32 bits operating systems.
• The input of checksum files other than .bin files is not supported in the GUI.
• The maximum firmware size for SFx generation with STM32U599xx/595xx/5A5xx microcontrollers is limited to 3 Mbytes.

Previous Release Information

STM32CubeProgrammer v2.12.0 Release Information

New Features

• STM32 Trusted Package Creator: enhanced SFI UI
• STM32MP1 series: added SSP GUI
• STM32WB series: upgraded the wireless stack and enhanced the UI
• STM32WL series: added module support
• Script manager: added loops and conditional statements
• External flash memory programmer: added B-U585I-IOT02A for SFIx
• 32F746GDISCOVERY and STM32F7508-DK: new external flash loaders

Fixed Issues

Table 5. Main issues fixed in STM32CubeProgrammer v2.12.0

Known Problems and Limitations

• Integrity check:
  • STM32H7 microcontrollers: support integrity check for SFI/SMI:
    • Only the devices with a bootloader version higher than 0x91 are supported.
    • STM32CubeProgrammer v2.12.0 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/SMI/SFIx:
    • Only the devices with a bootloader version higher than 0x93 are supported.
    • STM32CubeProgrammer v2.12.0 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/SMI/SFIx:
    • Only the devices with a bootloader version higher than 0x92 are supported.
    • STM32CubeProgrammer v2.12.0 does not support the devices with older bootloader versions. Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.
• Command-line interface:
  • Shared devices listing issue with the -l option.
  • Missing data from the .hex file when using safelib.
• Graphical user interface:
  • Missing data from the .hex file when using save to file.
• Auto mode (Linux^® platform):
  • The SPI interface quits after starting without a connection.
• STM32G0 microcontrollers:
  • The .hex file does not modify the WRP and PCROP option bytes of bank 2 for the devices with 512 Kbytes of dual-bank flash memory.
  • The SWD RegDump command-line instruction does not work on STM32G081xx devices.
• STM32H7 microcontrollers:
  • STM32CubeProgrammer does not support combined SFI and SMI.
  • SMI programming fails.
• STM32L4 microcontrollers:
  • The full chip erase fails in SPI mode for devices with 1 Mbyte of flash memory.
• STM32L4+ microcontrollers:
  • It is not possible to write the WRP1B and WRP2B option bytes for devices with 2 Mbytes of flash memory.
• STM32MP15x microprocessors:
  • It is not possible to program a .tsv file when some partitions are not selected.
  • An error occurs when saving the OTP partition in a macOS^® platform.
• STM32U5 microcontrollers:
  • RDP regression with password is not working on macOS^®.
  • It is impossible to set OEM keys through DFU.
• STM32WB1xxx microcontrollers:
  • The register dump command is not supported.
• Azure^® RTOS USBX:
  • For STM32U575/585 microcontrollers, erasing sectors from "C" to "F" fails.
  • For STM32U575/585 microcontrollers, some extra data is added at memory programming.
  • For STM32F4 microcontrollers, rewriting at a same memory address fails.
• Debug authentication is not supported on macOS^® and Windows^® 32 bits operating systems.
• The input of checksum files other than .bin files is not supported in the GUI.
• The maximum firmware size for SFx generation with STM32U599xx/595xx/5A5xx microcontrollers is limited to 3 Mbytes.

STM32CubeProgrammer v2.11.0 Release Information

New Features

• Tool updater: can be used to upgrade STM32CubeProg from v2.10.0 to v2.11.0 for all supported operating systems (Windows^®, Linux^®, and macOS^®)
• SFI:
  • SFIx support for STM32U585xx microcontrollers via SWD/JTAG
  • New SFI/SFIx graphical user interface (GUI)
  • STM32 Trusted Package Creator SFI GUI enhancement
  • Support for integrity check with the STM32H7 series and STM32U5 series microcontrollers
• STM32U5 series: the GUI supports the RDP regression with password
• New bootloader support for STM32L476xx microcontrollers
• STM32MP13xx microprocessors:
  • Flash memory load via USB-DFU/UART
  • SSP (command-line interface only)
  • OTP: CLI/GUI

Fixed Issues

Table 6. Main issues fixed in STM32CubeProgrammer v2.11.0

Known Problems and Limitations

• No error message is displayed when the microcontroller is not powered.
• A segmentation fault occurs when the STM32CubeProgrammer CLI is executed with a wrong serial number.
• Integrity check:
  • STM32H7 microcontrollers: support integrity check for SFI/SMI:
    • Only the devices with a bootloader version higher than 0x91 are supported.
    • STM32CubeProgrammer v2.11.0 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/SMI/SFIx:
    • Only the devices with a bootloader version higher than 0x93 are supported.
    • STM32CubeProgrammer v2.11.0 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/SMI/SFIx:
    • Only the devices with a bootloader version higher than 0x92 are supported.
    • STM32CubeProgrammer v2.11.0 does not support the 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 combined SFI and SMI.
  • The Cortex^®M4 boot address for dual-core STM32H7 microcontrollers is not modified with the SWD interface.
• STM32U5 microcontrollers:
  • RDP regression with password is not working on macOS^®.
  • SFIx is not working for bootloader interfaces.
  • An RSS CMD error is returned on area C during SFI.
  • An incorrect RSSe version is displayed.
  • The SFI process is successful while generating errors.
  • RDP2 and BootLock fail to be programmed in one shot over SWD.
  • The SFI installation process ends with a segmentation fault (Linux^®/macOS^®).
• STM32G0 microcontrollers:
  • Extra data is added during OTP programming in DFU.
  • STM32G0B0xx device is missing from the device list with ID 0x467.
• STM32WB1xxx microcontrollers:
  • The register dump command is not supported.
• Azure^® RTOS USBX:
  • For STM32U575/585 microcontrollers, erasing sectors from "C" to "F" fails.
  • For STM32U575/585 microcontrollers, some extra data is added at memory programming.
  • For STM32F4 microcontrollers, rewriting at a same memory address fails.

STM32CubeProgrammer v2.10.0 Release Information

New Features

• Tool updater: can be used to upgrade STM32CubeProg from v2.10.0 to v2.11.0 for all supported operating systems (Windows^®, Linux^®, and macOS^®)
• SFI:
  • SFIx support for STM32U585xx microcontrollers via SWD/JTAG
  • New SFI/SFIx graphical user interface (GUI)
  • STM32 Trusted Package Creator SFI GUI enhancement
  • Support for integrity check with the STM32H7 series and STM32U5 series microcontrollers
• STM32U5 series: the GUI supports the RDP regression with password
• New bootloader support for STM32L476xx microcontrollers
• STM32MP13xx microprocessors:
  • Flash memory load via USB-DFU/UART
  • SSP (command-line interface only)
  • OTP: CLI/GUI

Fixed Issues

Table 7. Main issues fixed in STM32CubeProgrammer v2.10.0

Known Problems and Limitations

• SFI, SMI, and SFIx integrity check for the STM32H73xxx microcontrollers:
  • Only the devices with a bootloader version higher than 0x93 are supported.
  • STM32CubeProgrammer v2.10.0 does not support the devices with older bootloader versions. Users must use STM32CubeProgrammer v2.9.0 to use devices with old bootloader versions.
• Users who want to use SFI on STM32H75xxx and STM32H7Bxxx must use STM32CubeProgrammer v2.9.0 because of the broken compatibility with the integrity check mechanism.
• Refer to the application note AN5054 for details.
• STM32CubeProgrammer does not support combined SFI and SMI for STM32H7 microcontrollers.
• Azure^® RTOS USBX:
  • For STM32U575/585 microcontrollers, erasing sectors from "C" to "F" fails.
  • For STM32U575/585 microcontrollers, some extra data is added at memory programming.
  • For STM32F4 microcontrollers, rewriting at a same memory address fails.
• STM32 Trusted Package Creator on macOS^® fails to detect the HSM card reader.
• STM32 Trusted Package Creator on Linux^® does not detect HSM only when the TPC CLI is launched in sudo mode.
• STM32WB55xx microcontrollers / FUS_StackWB: After key update, the progress bar remains red even after the programming ended successfully.
• Address is always equal to 0x0 when saving a binary as .hex file.
• STM32CubeProgrammer fails to program any option byte or memory when WWDG_SW (or IWDG_SW) is unchecked.

STM32CubeProgrammer v2.9.0 Release Information

New Features

• Updated the programming mechanism for the STM32U575/585 microcontrollers via a flash loader usage in TZEN = 0, and a new programming mode in TZEN = 1 (fast/reliable)
• Added double authentication and user keys provisioning via JTAG for the STM32WB series (feature only available with bootloader in previous versions)
• Added a scripting mode including the existing STM32CubeProgrammer CLI commands and a new macro for data manipulation
• Added the support for the PKCS#11 protocol in the signing tool (STM32MP1 series).
• Added the support for Microsoft^® Azure^® RTOS USBX DFU stack

Fixed Issues

Table 8. Main issues fixed in STM32CubeProgrammer v2.9.0

STM32CubeProgrammer v2.8.0 Release Information

New Features

• Added the support for the STM32U575/585 microcontrollers
• Added the support for SFI via the JTAG interface for the STM32U575/585 microcontrollers
• Added the support for SFI via the bootloader interface (USB/UART/I2C/SPI) for the STM32U5 series
• Added the new FUS-Operator support for the STM32WB1xxx microcontrollers
• Added the anti-rollback support for the STM32WB1xxx and STM32WB5xxx microcontrollers
• Added the support of FUS version display for the STM32WB1xxx and STM32WB5xxx microcontrollers
• Added the support for the Live Grid Update feature
• Added the support for the Blank check feature
• Added the support for the Memory/File and File/File compare features
• Added the support for the bootloader version display feature
• Added the support for the Fill memory feature
• Added the support for UART interface RTS/CTS signals
• Added the support for Connect while Watchdog enabled

Fixed Issues

Table 9. Main issues fixed in STM32CubeProgrammer v2.8.0

Known Problems and Limitations

• Script Manager on Linux^®: STM32CubeProgrammer does not recognize a .prg file when the directory name contains capital letters.
• STM32 Trusted Package Creator on macOS^® fails to detect the HSM card reader.
• STM32 Trusted Package Creator on Linux^® does not detect HSM only when the TPC CLI is launched in sudo mode.
• STM32WB55xx microcontrollers / FUS_StackWB: After key update, the progress bar remains red even after the programming ended successfully.
• Address is always equal to 0x0 when saving a binary as .hex file.
• STM32CubeProgrammer fails to program any option byte or memory when WWDG_SW (or IWDG_SW) is unchecked.
• STM32L151RD: wrong flash memory size displayed (128 Kbytes instead of 384 Kbytes).

STM32CubeProgrammer v2.7.0 Release Information

New Features

• Added the support for the STM32WB15xx microcontrollers in the STM32WB series
• Added the support for the microcontrollers with 64 Kbytes of flash memory in the STM32G0 series
• Added HardFault Analyzer support
• Added Register viewer support

Fixed Issues

Table 10. Main issues fixed in STM32CubeProgrammer v2.7.0

Known Problems and Limitations

• STM32G030C6: extra option bytes displayed (PCROP1A_STRT, PCROP1A_END, PCROP1A_RDP, PCROP1B_STRT, PCROP1B_END, BOOT_LOCK, SEC_SIZE)
• STM32L151RD: wrong flash memory size displayed (128 Kbytes instead of 384 Kbytes)
• STM32U575/585 microcontrollers:
  • Bootloader version is not displayed
  • SFI via SWD fails when a USB cable is connected (a workaround is to use a USB wall charger)
  • On macOS^®, after setting RDP to 0x55 and TZEN to 0x1, a connection via SWD crashes the tool
  • Regression with PWD from L1 to L0.5 fails
• STM32 Trusted Package Creator tool: HSM cannot be detected on macOS^®
• Frequency parameters are not respected
• Azure^® RTOS USBX is not supported

STM32CubeProgrammer v2.6.0 Release Information

New Features

• Added the support for the STM32WB15xx microcontrollers in the STM32WB series
• Added the support for the microcontrollers with 64 Kbytes of flash memory in the STM32G0 series
• Added HardFault Analyzer support
• Added Register viewer support

Fixed Issues

Table 11. Main issues fixed in STM32CubeProgrammer v2.6.0

Known Problems and Limitations

• STM32MP1 mircoprocessor get certificate operation is not complete in the UART mode.
• Production programming issues occur when using multiple ST-LINK in parallel.
• Installer: Insignificant message is returned during the installation when other instances are already installed.
• On some macOS^® machines, the STM32Cubeprogrammer GUI fails to launch (must be launched in CLI mode).
• The SFI operation via UART is not achieved and returns an error on macOS^® machines.
• STM32WB55: When trying to upgrade more than one stack, the operation can be done only with a second try.
• SFIx operation for STM32L5: An exception appears while programming when the -elbl command is not the first one in the command line.

STM32CubeProgrammer v2.5.0 Release Information

New Features

• Added the support for STM32G491xC and STM32G491xE microcontrollers
• Added the support for STM32H72xxx and STM32H73xxx microcontrollers
• Added SFI support for STM32H72xxx and STM32H73xxx microcontrollers
• Added SFIx support for STM32H72xxx and STM32H73xxx microcontrollers
• Added SFI support via UART for STM32L5 series microcontrollers
• Added SFI support via USB for STM32L5 series microcontrollers
• Added support of Serial Wire Viewer (SWV)
• Board automatic recognition
• Revision ID display

Fixed Issues

Table 12. Main issues fixed in STM32CubeProgrammer v2.5.0

Known Problems and Limitations

• For the STM32L5 series, the Option Byte programming GUI is not intuitive enough. Refer to the STM32L552xx and STM32L562xx advanced Arm^®-based 32-bit MCUs reference manual (RM0438) for permitted accesses.
• For STM32L4Pxxx and STM32L4Qxxx devices, Option Byte programming via bootloader interfaces presents some limitations.
• For STM32H7Axxx and STM32H7Bxxx devices, Option Byte programming via bootloader interfaces (USB) presents some limitations.
• STM32L5 series programming presents limitation in macOS^® when TZEN=1 and RDP=0x55.
• Display issues depending on the monitor used can occur with Linux^®.
• SFI-HSM V2 get certificate fails with STM32L462xx devices.
• Parallel flash programming fails in macOS^® for microprocessors in the STM32MP1 series.
• Issues can be reported with some specific .elf file in CRC calculation safety feature.
• STM32MP1 mircoprocessor programming via UART presents limitations to program the whole boot chain.
• STM32MP1 mircoprocessor get certificate operation is not completed via a UART connection.

STM32CubeProgrammer v2.4.0 Release Information

New Features

• Added the support of the graphic user interface (GUI) for the firmware upgrade service (FUS) and stack upgrade for the entire STM32WB series
• Support of HSM V2 on all STM32 microcontrollers and microprocessors supporting SFI/SSP

Fixed Issues

Table 13. Main issues fixed in STM32CubeProgrammer v2.4.0

Known Problems and Limitations

• For the STM32L5 series, the connection via the ST-LINK protocol is allowed only when mode is set to hotplug with TZEN=1.
• For the STM32L5 series, the Option Byte programming GUI is not intuitive enough. Refer to the STM32L552xx and STM32L562xx advanced Arm^®-based 32-bit MCUs reference manual (RM0438) for permitted accesses.
• For STM32L4Pxxx and STM32L4Qxxx devices, Option Byte programming via bootloader interfaces presents some limitations.
• For STM32H7Axxx and STM32H7Bxxx devices, Option Byte programming via bootloader interfaces (USB) presents some limitations.
• STM32L5 series programming presents limitation in macOS^® when TZEN=1 and RDP=0x55.
• With some small-screen resolutions, the graphical interface of STM32CubeProgrammer presents anomalies such as inaccessible buttons.
• Display issues depending on the monitor used can occur with Linux^®.
• SFIx on STM32H743/753 devices fails via the debug interface.
• SFI-HSM V2 get certificate fails with STM32L462xx devices.
• Parallel flash programming fails in macOS^® for microprocessors in the STM32MP1 series.

STM32CubeProgrammer v2.3.0 Release Information

New Features

• Added the support of the STM32L4Pxxx and STM32L4Qxxx microcontrollers
• Added the support of the STM32H7Axxx and STM32H7Bxxx microcontrollers
• Added the beta support of the STM32WL series microcontrollers
• Added the official support of the STM32L5 series microcontrollers
• Added the support of HSM V1 SFI/SFIx for STM32H7Axxx microcontrollers
• Added the support of HSM V1 SFI/SFIx for STM32L5 series microcontrollers

Fixed Issues

Table 14. Main issues fixed in STM32CubeProgrammer v2.3.0

Known Problems and Limitations

• For the STM32L5 series, the connection via the ST-LINK protocol is allowed only when mode is set to hotplug with TZEN=1.
• For the STM32L5 series, the Option Byte programming GUI is not intuitive enough. Refer to the STM32L552xx and STM32L562xx advanced Arm^®-based 32-bit MCUs reference manual (RM0438) for permitted accesses.
• For STM32L4Pxxx and STM32L4Qxxx devices, Option Byte programming via bootloader interfaces presents some limitations.
• For STM32H7Axxx and STM32H7Bxxx devices, Option Byte programming via bootloader interfaces (USB) presents some limitations.
• STM32L5 series programming presents limitation in macOS^® when TZEN=1 and RDP=0x55.
• With some small-screen resolutions, the graphical interface of STM32CubeProgrammer presents anomalies such as inaccessible buttons.
• Display issues depending on the monitor used can occur with Linux^®.

STM32CubeProgrammer v2.2.1 Release Information

New Features

No new feature is reported for this release. Minor release v2.2.1 is dedicated to issue correction (refer to Fixed issues).

Fixed Issues

Table 15. Main issue fixed in STM32CubeProgrammer v2.2.1

Known Problems and Limitations

• For the STM32L5 series, the connection via the ST-LINK protocol is allowed only when mode is set to hotplug.
• For the STM32L5 series, the Option Byte programming GUI is not intuitive enough. Refer to the STM32L552xx and STM32L562xx advanced Arm^®-based 32-bit MCUs reference manual (RM0438) for permitted accesses.
• For the STM32L5 series, Option Byte programming via bootloader interfaces presents some limitations.
• STM32CubeProgrammer does not work under Ubuntu^® 18.04.
• With some small-screen resolutions, the graphical interface of STM32CubeProgrammer presents anomalies such as inaccessible buttons.

STM32CubeProgrammer v2.2.0 Release Information

New Features

• Added the support of the STM32L5 series
• Added the support of HSMv2
• Added the support of IAP for the USB-DFU interface
• STM32WB firmware upgrade via the ST-LINK interface
• Added the support of OTP for the STM32L5 series
• Added the support of SSP for the STM32MP1 series

Fixed Issues

Table 16. Main issues fixed in STM32CubeProgrammer v2.2.0

Known Problems and Limitations

• For the STM32L5 series, the connection via the ST-LINK protocol is allowed only when mode is set to hotplug.
• For the STM32L5 series, the Option Byte programming GUI is not intuitive enough. Refer to the STM32L552xx and STM32L562xx advanced Arm^®-based 32-bit MCUs reference manual (RM0438) for permitted accesses.
• For the STM32L5 series, Option Byte programming via bootloader interfaces presents some limitations.
• STM32CubeProgrammer does not work under Ubuntu^® 18.04.
• With some small-screen resolutions, the graphical interface of STM32CubeProgrammer presents anomalies such as inaccessible buttons.
• Display issues depending on the monitor used can occur with Linux^®.

STM32CubeProgrammer v2.1.0 Release Information

New Features

• Added support of STM32G4 series
• Added support of STM32G03x/STM32G04x microcontrollers
• Added support of dual-core microcontrollers in the STM32H7 series
• Added support of secure firmware install (SFI)

Fixed Issues

Table 17. Main issues fixed in STM32CubeProgrammer v2.1.0

Known Problems and Limitations

• The use of the UART bootloader prevents from increasing the RDP level and programming the second bank of Option Bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.
• External memory programming in only available with ST-LINK.
• Installing multiple instances of the same version of the tool in the same directory under Windows^® leads to issues when uninstalling.
• UART flash programming of devices in the STM32MP1 series may fail with big partitions.
• Programming issues are observed with the STM32H7 series when the STLINK-V3 I2C interface is used.
• GUI issues are sometines observed with the OTA programming of devices in the STM32WB Series.
• Linux^® 32 bits is not supported.
• STM32 Trusted Package Creator: only the CLI version is supported on macOS^®.
• Mass Erase is not working with the SPI bootloader interface on the STM32WB series.
• Mass Erase is not working with the I2C bootloader interface on the STM32G4 series; errors can occur when writing via the SPI interface.
• Shared mode: board detection failure is observed after multiple refresh operations.
• Writing 8-bit data in RAM on STM32L496G devices is not possible.

STM32CubeProgrammer v2.0.0 Release Information

New Features

• Added support of STM32MP1 series
• Added support of STM32WB series
• Added support of Automatic Mode for programming devices in a loop
• Added support of OTA programming for the STM32WB series

Fixed Issues

Table 18. Main issues fixed in STM32CubeProgrammer v2.0.0

Known Problems and Limitations

• The use of the UART bootloader prevents from increasing the RDP level and programming the second bank of Option Bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.

STM32CubeProgrammer v1.4.0 Release Information

New Features

• Added STM32CubeProgrammer C++ API
• Added support of secure firmware install on STM32L462CEU6F

Fixed Issues

Table 19. Main issues fixed in STM32CubeProgrammer v1.4.0

Known Problems and Limitations

• Read/write operations fail with the CAN interface.
• The use of the UART bootloader prevents from increasing the RDP level and programming the second bank of Option Bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.
• External memory programming in only available with ST-LINK.
• Installing multiple instances of the same version of the tool in the same directory under Windows^® leads to issues when uninstalling.
• The STLinkV3-I2C bridge may not work correctly with STM32F4 series, STM32F7 series, and STM32H7 series.

STM32CubeProgrammer v1.3.0 Release Information

New Features

• Added support of STM32G07x and STM32G08x microcontrollers
• Added support of STM32L010 microcontrollers
• Flash memory size displayed with debug interface
• Extended ST-LINK server interface support to Linux^® and macOS^®
• User interface enhancements
• Added contextual menu in main panel for programming, verification, and saving
• Added support of .binary files
• Added support of Unicode^® file path
• New panel for external loaders; possibility to search and filter with the loader or board name

Fixed Issues

Table 20. Main issues fixed in STM32CubeProgrammer v1.3.0

Known Problems and Limitations

• Read/write operations fail with the CAN interface.
• The use of the UART bootloader prevents from increasing the RDP level and programming the second bank of Option Bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.
• External memory programming in only available with ST-LINK.
• Installing multiple instances of the same version of the tool in the same directory under Windows^® leads to issues when uninstalling.
• The STLinkV3-I2C bridge may not work correctly with STM32F4 series, STM32F7 series, and STM32H7 series.

STM32CubeProgrammer v1.2.1 Release Information

New Features

• Full-chip erase enabled for STM32L0 series and STM32L1 series
• Enhanced connection to STM32L0 series and STM32L1 with STLINK-V3
• Added support of Quad-SPI flash loaders:
  • N25Q128A_STM32F7508-DISCO
  • MX25L512G_STM32F7308-DISCO
  • MT25TL01G_STM32H743I-EVAL
  • MT25TL01G_STM32H747-EVAL

Fixed Issues

Table 21. Main issues fixed in STM32CubeProgrammer v1.2.1

Known Problems and Limitations

• Read/write operations fail with the CAN interface.
• The use of the UART bootloader prevents from increasing the RDP level and from programming the second bank of Option Bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.
• External memory programming in only available with ST-LINK.

STM32CubeProgrammer v1.2.0 Release Information

New Features

• Add support of STLINK-V3
• Add support of STM32L41x microcontrollers
• Listing of the connected ST-LINK probes using the --list command
• Digitally signed USB DFU driver for STM32 bootloader
• Add support of ST-LINK server interface

Known Problems and Limitations

• Read/write operations fail with the CAN interface.
• The use of the UART bootloader prevents from increasing the RDP level and from programming the second bank of Option Bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.
• External memory programming in only available with ST-LINK.
• Installing multiple instances of the same version of the tool in the same directory under Windows^® leads to issues when uninstalling.
• STLinkV3-I2C bridge may not work correctly with STM32F4 series, STM32F7 series, and STM32H7 series.

STM32CubeProgrammer v1.1.0 Release Information

New Features

• Add support of STM32F7x0 Value line and STM32H750 Value line
• Add support of M29W128GL external flash memory programming on STM32H743I-EVAL
• Dump device memory into an hex/srec/bin file
• Add Core debug commands in command-line interface
• Add support of data EEPROM programming on STM32L0 series and STM32L1 series

Known Problems and Limitations

• The use of the UART bootloader prevents from increasing the RDP level and from programming the second bank of option bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.
• External memory programming in only available with ST-LINK.
• Installing multiple instances of the same version of the tool in the same directory under Windows^® leads to issues when uninstalling.

STM32CubeProgrammer v1.0.0 Release Information

New Features

• STM32 flash programming and erasing over ST-LINK debug probe (JTAG/SWD) and over bootloader interfaces UART and USB DFU
• STM32 option bytes detailed display with description of each bit field
• Option bytes programming over ST-LINK debug probe (JTAG/SWD) and over bootloader interfaces UART and USB DFU
• External memories programming over ST-LINK debug probe (JTAG/SWD) for STM32 microcontroller evaluation and discovery boards
• Read, display and programming of binary files, ELF files, Intel hex files and Motorola Srecord files
• Read and display of STM32 microcontroller memory content
• Command line and graphical user interface
• Generation of secure firmware using the STM32 Trusted Package Creator tool

Known Problems and Limitations

• The use of the UART bootloader prevents from increasing the RDP level and from programming the second bank of option bytes, or from enabling the two user secure areas simultaneously on STM32H7 microcontrollers.
• Programming over USB bootloader is not reliable with USB2.0 for some devices.
• The erase command is not supported with data EEPROM on STM32L0 and STM32L1.
• External memory programming in only available with ST-LINK.
• Installing multiple instances of the same version of the tool in the same directory under Windows^® leads to issues when uninstalling.

Revision History

Important Notice - Read Carefully

STMicroelectronics NV and its subsidiaries ("ST") reserve the right to make changes, corrections, enhancements, modifications, and improvements to ST products and/or to this document at any time without notice. Purchasers should obtain the latest relevant information on ST products before placing orders. ST products are sold pursuant to ST's terms and conditions of sale in place at the time of order acknowledgment.

Purchasers are solely responsible for the choice, selection, and use of ST products and ST assumes no liability for application assistance or the design of purchasers' products.

No license, express or implied, to any intellectual property right is granted by ST herein.

Resale of ST products with provisions different from the information set forth herein shall void any warranty granted by ST for such product.

ST and the ST logo are trademarks of ST. For additional information about ST trademarks, refer to www.st.com/trademarks. All other product or service names are the property of their respective owners.

Information in this document supersedes and replaces information previously supplied in any prior versions of this document.

© 2023 STMicroelectronics - All rights reserved