STM32CubeProgrammer (MCUs)

Hello everyone, I'm sending the command"C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=COM3 br=9600 rts=high -w C:\BinFiles\FirmwareLoader.bin 0x08005000 -v"from STM32Programmer CLI. Sometimes it just works fine and downloads and verifies the file written, but sometimes it shows the output as below. Does anybody have any idea what "Reemission of GetID command", "GETID command not acknowledged!" means, and what might have caused it and how it  can be resolved ?P.S. : As I have already said the command works perfectly fine sometimes, so please focus on the output below, not the command. Thanks in advance. -------------------------------------------------------------------STM32CubeProgrammer v2.15.0 -------------------------------------------------------------------Serial Port COM3 is successfully opened.Port configuration: parity = even, baudrate = 9600, data-bit = 8,stop-bit = 1.0, flow-control = offActivating device:

Hi,I am using Clives loader for the STM32H with the correct pins etc but it never works in the STM IDE, so I thought I would follow controllertechs videos to try and make my own loader, that didn't work either, but I did verify all the QSPI parts reading/wriitng etc are working. I also learned a good test using the CubeMX Programmer (and that fails using my loader for a different reason) but, I then thought OK will test it with Clives and MX Prog, and that fails on verification when I try and load a 1MB test file. I have emailed Clive and he has been incredibly helpful already, but thought I would also ask in the community in case someone has a quick solution?  

I have a design that I'm trying to bring up and program using the USB DFU capability. The board enumerates correctly in windows, but does not get into programming. It seems as though I have forgotten something, but don't know what to look for. I have checked the "Read Unprotect (MCU)" box. I have attached the verbose log of one cycle. What happens when I try to connect is shown there and after a bit a window pops up saying to turn off the power to my device. When I do, the cycle repeats! Thanks for any pointers...

I am trying to use CLion to program STM32 MCUs as an alternative to other IDEs. For flashing and debugging, I want to use the Embedded GDB Server provided by ST, specifically ST-LINK_gdbserver.exe.I prefer not to use OpenOCD because I have found it to be less stable for my use case. The Problem:I am struggling to find the correct configuration to make ST-LINK_gdbserver.exe work properly with CLion. I tried using a configuration I found in this GitHub issue:Link: Official ST-LINK gdbserver support · Issue #354 · Marus/cortex-debugHowever, when I try to run the GDB Server with this configuration:I receive the following error: C:\ST\STM32CubeIDE_1.13.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.0.202409170845\tools\bin\ST-LINK_gdbserver.exe -p 3333 -cp C:\ST\STM32CubeIDE_1.13.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin -k STMicroelectronics ST-LINK GDB server. Versi

Hi everyone,I'm trying to flash my STM32WB55 and the connected MX25R64 external memory.I have already created my external loader and tested it with the CubeProgrammer, feeding it with a .srec file containing only external addresses (>= 0x90000000).However, I was trying to unify the flashing process by using the external loader option present in STM32CubeIDE. This option generates a STM32_Programmer_CLI command and feeds it with a .srec file that covers both external and internal memory:C:\ST\STM32CubeIDE_1.18.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.100.202412061334\tools\bin\STM32_Programmer_CLI.exe --connect port=SWD speed=fast mode=UR reset=hwRst --extload <path/to/extloader> --download <pat/to/srec> --verify --log <path/to/log>srec_info output:Format: Motorola S-RecordHeader: "ST-LINK GDB server"Execution Start Address: 00000000Data: 08000000 - 0800013B08000140 - 0800014308000150 - 0806F1B90806F1BC -

If TrustZone is enabled on a device, I cannot use STM32_Programmer_CLI.exe -d to program high-cycle count flash.If TrustZone is disabled, it works.Based on STM32_Programmer_CLI -w16 not working in high-cycl... - STMicroelectronics Community I have reason to believe that it does work with TrustZone on if you have working secure boot code that puts the device in a higher HDPL before programming is attempted. But I have not tested this myself. And if there needs to be some data in high-cycle count for the boot loader to start, you are stuck. In theory you could catch the double ECC-error and program the sectors with default values from the application, but that is a hassle.I'd love to get some feedback from ST on if I am doing something wrong here or this is a bug in either the programmer or the MCU. STLINK-V3SET FW V3.J16.M8.B5.S1STM32H563 Rev XBootloader Version 0xE4STM32CubeProgrammer 2.19.0Steps to reproduce (last command is failing)EDATA.bin is nothing special - j

 Problem DescriptionI'm working with the B-L072Z-LRWAN1 development board and trying to configure the SX1276 LoRa transceiver DIO pins manually (without using ST's HAL middleware). I want to use an external LoRaWAN library (LDL) that requires explicit DIO pin configuration.Current ConfigurationBased on my research, I have the following pin mapping:  c#define DIO0_PIN GPIO_PIN_4 // PA4 #define DIO1_PIN GPIO_PIN_1 // PB1 #define DIO2_PIN GPIO_PIN_0 // PB0 #define DIO3_PIN GPIO_PIN_2 // PC2 #define DIO4_PIN GPIO_PIN_3 // PC3 #define DIO5_PIN GPIO_PIN_5 // PC5 QuestionsAre these DIO pin mappings correct for the B-L072Z-LRWAN1 board?Which DIO pins are actually connected/used on this board? (I understand some may not be connected)Where can I find the official schematic or documentation that shows the exact DIO pin connections?

Hi, we're having some issues while trying to connect a STM32F030C6 to the Stm32CubeProgrammer via USB, through the embedded STM32 Bootloader.Using the same working sample of one of our devices, we perform several connection tests on different Windows 10 PCs, all set up with the following configuration:STM32CubeProgrammer V. 2.10USB plugged directly in the laptop portSTM32 drivers properly installedAll the PCs were able to properly detect the device in bootloader mode, showing "STM32 BOOTLOADER" in "Device Manager" and some of them were able to properly connect to the device, allowing us to perform DFU operations.However, on some PCs, the following warning appeared, and no matter what we tried (flag set on "read unprotected", power cycles..etc), we weren't able to connect to the device: Strange thing is, on those problematic PCs, if, instead of using the embedded laptop USB port, we connected the device through an external USB HUB, we were able to connect properly.This issue is cau

STM32CubeProgrammer v2.21.0  

Hello,     I am using NUCLEO-WB55RG board to implement BLE and I got error when I was Upgrading my STACK Version currently which is v0.0.0.0 in STM32CubeProgrammers FIRMWARE UPGRADE SERVICE option, I select stm32wb5x_BLE_Stack_full_fw.bin with 0x080D4000 memory location for stack upgrade which is preferred by STMicroelectronics official documentation, I have post my Screenshot after multiple attempts no update in STACK Version.--> It is mandatory to upgrade STACK Version for implement BLE?--> Also want better suggestion & Guidance Documents for BLE implement from basic to advance?it would be grateful for any guidance!... Thank you.

My STM32H573 option bytes are in weird state which might be the reason that the device could not run any fw even if the flash still can be programmed; I imported the option bytes from a 'good' device, but could not apply the changes to the device, any idea?  Tried "Reset MCU to Factory settings" did not work either. Also, although the CubeProgrammer can connect to the device, CubeIDE cannot debug the device, the discovery.bat cannot even read the device IDs:c:\> discovery.bat-------------------------------------------------------------------STM32CubeProgrammer v2.19.0-------------------------------------------------------------------Start Debug Authentication SequenceOpen SDM LibSDMOpen : 624 : open : SDM API v1.0SDMOpen : 625 : open : SDM Library version v1.2.0open_comms : 513 : open : Asserting target resetopen_comms : 517 : open : Writing magic numberopen_comms : 537 : open : De-asserting target resetopen_comms : 584 : open : Communication with the target established su

Hi, i have recognize some odd behavior inside the CubeProgrammer external flashing feature.When flashing files less or equal to 128KB, then it flashes size at boundary of the block size of the Flash device which is 64K. As soon i get bigger than that it no more send data in that boundary but 67072 bytes. Why is that? I had to rewrite my APIs to get that working properly. I mean it is working now but sounds strange too me. Thanks

Hi everyone,I’m working on an STM32F4 project where I save a configuration struct to internal flash memory to preserve settings across power cycles.The first time I run my program and write the struct to flash, everything works fine. But the second time I try to debug, right after writing to flash, my debugger fails to halt the MCU and I get this error in STM32CubeProgrammer:Error: ST-LINK error (DEV_TARGET_NOT_HALTED)Encountered Error when opening C:\ST\STM32CubeIDE_1.15.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin\STM32_Programmer_CLI.exeError in STM32CubeProgrammerHas anyone experienced this issue when writing to flash during debugging?

Hello,I am currently trying to program a nucleo board using USART. For this I am using the bootloader and Cube Programmer. I first developed a program and tester it by programming via st link. My program worked with no problem. I then tried to program using UART. I was able to connect but as soon as I started programming, I get the message Error :GETID command not acknowledged and then the nucleoboard is disconnected.Here are my settings and the boot0 pin is tied to 3.3V.When I program I can see on the oscilloscope that some part of the program is on and working but not fully as well.Any idea ? Thanks very much 

Hello,i've set the PRODUCT_STATE of my STM32H7S78-DK in the STM32CubeProgrammer from Open (39) to Revisioning (17):When trying to reset the state to Open again I get following error:Is there a way to reset to the product state to Open again? I've read that there should be the possibility to do a full regression in PRODUCT_STATE Provisioning but how do I do that? Thank you an best regards,rk_iot  

Steps to reproduceYou can find the output files (ELF and bin) attached to this post. The steps to create them are as follows:Download and extract X-CUBE-CLASSB library for STM32H5, version 4.0.0Open the contained example project in STM32CubeIDE (we'll use the TrustZone one)Modify the secure application linker script to include a gap at the beginning (e.g. for MCUboot)--- STM32CubeIDE/Secure/STM32H563ZITX_FLASH.ld.bak 2025-05-20 10:05:08.623676118 +0200 +++ STM32CubeIDE/Secure/STM32H563ZITX_FLASH.ld 2025-05-20 10:05:13.813692793 +0200 @@ -46,7 +46,7 @@ MEMORY { RAM (xrw) : ORIGIN = 0x30000000, LENGTH = 320K /* SRAM1 + SRAM2 */ - FLASH (rx) : ORIGIN = 0x0C000000, LENGTH = 1016K + FLASH (rx) : ORIGIN = 0x0C008400, LENGTH = 983K FLASH_NSC (rx) : ORIGIN = 0x0C0FE000, LENGTH = 8K }Change the post-build step to (STL_Single_Tests_Nucleo_H563ZI_Secure -> Properties -> C/C++ Build -> Setting -> Build Steps) make a backup copy and correctly call the programmer with the new addres

Situation context:We have a device with an STM32F103 mcu that has an IAP, that hasn't change in a few years, and we came up with a new version after a long without updating the device. The thing is that the new version works fine as long as the program is flashed via Keil either on Debug mode or Download mode over jtag. The problem comes with virgin devices, in production they download the new version using CubeProgrammer, the usual way of doing it is to perform a "Full chip erase" then download the IAP and then the program, this results in the device rebooting all the time and impossible to debug as it gets lost when we open a debug session in Keil. After discarding if it's a hardware problem I get one of this devices and redo the whole thing using v2.14, v2.18 and v2.19 of the CubeProgrammer with same results with each version. The funny thing comes when I use Keil on the same device, I erase the flash memory, download the IAP and then download the program, this works fine, as i

I have just downloaded the latest version but when I start CubeProgrammer, the window doesn't contain anything...The TrustedPackageCreator application which also came with the installer, does however seem to be working normally. (I am using Chrome Remote Desktop because this is on a remote PC) 

I've been using the programmer for a couple of week now and everything seemed to work fine.When I powered up my pc and tried to run the program I got a starting screen that quickly disappeared. This happened even after I reinstalled the program, anyone has had this problem and knows how to solve it?

Hi,I probably didn't search correctly in the documentation, but i didn't find a command to reboot the device using the USB Bootloader interface . I found a reset method but its with STLINK and its not what i'm using.Is there any method available ?thank you for all the help you can provide Sofiane

Hello,I am trying to figure out the ReadOut protection configuration from the CLI tool (STM32_Programmer_CLI) and I am encountering an issue.Setup :OS : Linux MintMCU : STM32F439Board : CustomSTM32_Programmer_CLI version : 2.19.0We have this custom board and use the system bootloader to flash a firmware when needed. Once the firmware is flashed, the RDP is enabled.When we want to flash the board again, we disable the RDP, flash the board, and reflash the board again.This works well with a debugger , using this command :STM32_Programmer_CLI -c port=SWD -ob RDP=170we can disable the RDP.However, we want to do the same thing from the UART3 in system bootloader and it doesn't work.When I try to disable the RDP with the UART3 port with the following command :STM32_Programmer_CLI -c port=/dev/ttyUSB1 -ob RDP=170 i get the following error :------------------------------------------------------------------- STM32CubeProgrammer v2.19.0 ---------------------------------------------------

HiI am trying to flash new FW to STM32L496 on custom board.When I try to flash the ELF file from the GUI Cube-Programmer on windows using STLINK all I have to do is select the .stldr file, .elf file, and the programming goes on smoothly.On my custom board I put the STM chip into bootloader mode, but when I try to flash the new FW I get Segmentation Fault error.It looks like the error occur only when I use the -el flag with a .stdlr file.Any help would be appreciated. 

Hello,I'd like to ask if there are plans to implement SWO support in Cube Programmer API? I would be very helpful to read the SWO ouput directly using the C++ API, not by using CLI. 

I've been working on my own code for using USB DFU with our device and it is failing with the downloadFile call. I decided to test with the CLT (command line tools) and am seeing similar results. If I tell STM32_Programmer_CLI.exe to use the STLINK-V3SET with my hex file, it pushes the file without issue: However, if I put the device into USB DFU mode, it fails as such:  This failure output is the same failure output I get when running STM32CubePrgAPI - USB_Example, as well as when I run my own application.  The HEX file being used is the same in all instances. I've also tried using the corresponding ELF file. The device is an STM32H747XI and should load code at 0x08000000 as shown. I do however have a modified linker file that defines a NOINIT section at the top of the DTCM block, as well as some data that is shared between the CM4 and CM7 cores in the top of the RAM D3 block. Could these be the source of the errors when trying to use USB DFU? Thanks, C-C

HI   I was using ST32 Cube Programmer, ST-Link v3, and target board well. However, the following error suddenly occurred. (The target board also continues to operate normally)   Symptom-1) The settings are the same, but the DEV_Target_Held_Under_Reset error suddenly occurred. The configuration was operating normally, and even after changing all the things that could be changed, such as the target board, cable, and PC, the error below continued to occur.   Symptom-2) When I changed the mode to Hot Plug, the connection was made, but a data read failed error occurred. Since the data read failed error occurred, I could not perform any functions such as download and erase.       Others - ST-Link v3 update works fine in cube programmer. - I tried downloading with ST-Link v2, which has a spare target board with the above problem, and it worked fine.   I wonder if ST-Link v3 is broken? At first, I thought so, but ST-Link v3 was updated and the mode was chan