Showing results for 
Search instead for 
Did you mean: 

STM32CubeProgrammer 2.2.0 released

ST Employee

Dear community

We are pleased to announce the release of STM32CubeProgrammer 2.2.0

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 2.2

Fixed issues

58587 STM32CubeProgrammer does not support STM32L433RC-P and STM32L433RB.

61375 STM32L073 - How to erase the Data EEPROM?

61731 CLI Device not supported but programmed. RDP not programmed.

68802 USB DFU for STM32L452 and STM32L476 device IDs is unknown while connecting with the USB.

68916 STM32CubeProgrammer does not recognize STM32F413 USB DFU.

69927 IAP DFU is not working with STM32CubeProgrammer: Error Unknown or unsupported device (DevID = 0x0000).

71074 STM32CubeProgrammer v2.1.0 defect - DFU mode sector erase fails on STM32H743 2MB Rev V. 2.3

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.

Get the new version now


Hi @Nawres GHARBI​ ,

Thanks for the notification.

What is the timeframe for the integrated-JVM version and non-JVM-dependent installer?

I'd also suggest to rework the GUI to follow the industry standard for hierarchical menus design, with top menu being a top horizontal bar, containing File etc.. The current look is very amateurish, and the haphazardly scattered controls require unnecessary effort from the users to learn to use them.


Jan Waclawek

Thanks for the update, will be doing some loader testing with it later this evening.

I will note it has not been packaged with the most recent firmware update, this has v2.33.25 and not v2.34.25 attached.

ST-LINK firmware

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Uwe Bonnes
Principal III

2.35 is recent firmware!

Uwe Bonnes
Principal III

I still do not see an option to restore the Option byte factory setting as requested July 29, 2018 as "Request for feature: Restore factory (option bit ) settings"

Yes, 2.35.26, the download page could be a lot clearer

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
ADi M.507


Upgrading to version 2.2.0 i get this error using the option " --mergesbsfu" (Add a binary header and a sbsfu segment to an elf file):

arm-none-eabi-gcc -o "STM32F769I-Discovery_AWS.elf" @"objects.list"   -mcpu=cortex-m7 -T"../STM32F769NIHx_FLASH.ld" --specs=nosys.specs -Wl,-Map="" -Wl,--gc-sections -static -L../../../../../BootLoader_OSC/2_Images_SBSFU/SW4STM32/STM32F769I_Discovery_2_Images_SBSFU/Debug -Xlinker -L../../../../../BootLoader_OSC/Linker_Common/SW4STM32 --specs=nano.specs -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -u _printf_float -Wl,--start-group -lc -lm -Wl,--end-group
Finished building target: STM32F769I-Discovery_AWS.elf
arm-none-eabi-size   STM32F769I-Discovery_AWS.elf 
   text	   data	    bss	    dec	    hex	filename
 248680	  13240	 242064	 503984	  7b0b0	STM32F769I-Discovery_AWS.elf
Finished building: default.size.stdout
arm-none-eabi-objdump -h -S  STM32F769I-Discovery_AWS.elf  > "STM32F769I-Discovery_AWS.list"
Finished building: STM32F769I-Discovery_AWS.list
arm-none-eabi-objcopy -O binary "STM32F769I-Discovery_AWS.elf" "STM32F769I-Discovery_AWS.bin"
arm-none-eabi-size "STM32F769I-Discovery_AWS.elf"
   text	   data	    bss	    dec	    hex	filename
 248680	  13240	 242064	 503984	  7b0b0	STM32F769I-Discovery_AWS.elf
"../../../../../BootLoader_OSC/2_Images_SECoreBin/SW4STM32/" "../.." "./STM32F769I-Discovery_AWS.elf" "./STM32F769I-Discovery_AWS.bin" "1" "bigelf"
prepareimage with windows executeable
Generating the global elf file SBSFU and userApp
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
STM32_Programmer_CLI.exe -ms ./STM32F769I-Discovery_AWS.elf ../../PostBuild/STM32F769I-Discovery_AWSsfuh.bin C:/dev/Cloud_AWS/Projects/STM32F769I-Discovery/Applications/BootLoader_OSC/2_Images_SBSFU/SW4STM32/STM32F769I_Discovery_2_Images_SBSFU/Debug/SBSFU.elf : failed
make[1]: *** [makefile:90: post-build] Error 1
make: *** [makefile:57: all] Error 2
"make all" terminated with exit code 2. Build might be incomplete.

with 2.1 it works fine..

can you fix this?

Thank you in advance, regards

Alessio DM

Won't the Programmer have option to get latest ST-link firmware from the website?

-- pa

Associate III

It really seems that this version has some bugs on macOS at least. I try to use STM32_Programmer_CLI to program my custom board. no problem at all with the version 2.1, but version 2.2 always give me an error of unsupported device 0x0000. The GUI version has really no problem to connect the IC in both version and program it. However, the CLI version is stuck trying to connect. This is not due to the connection settings as the previous version is working like a charm with the exact same command.

I am using a STM32H750XB if relevant (1.8V, SWD 4MHz or JTAG 9MHz). No other choice than roll back this version :\ Still happy that this version is still available for download.


still problem with openjfx (debian)...