STM32CubeProgrammer (MCUs)

Hi All,GreetingsWe are using STM32U585 on custom board with Trust zone enabled and now facing a connection issue with stm cube programmer in hotplug mode, now unable to connect to the microcontroller and getting ST-LINK error  as : DEV_TARGET_CMD_ERROR.When NRST is low continuously(pressing the Reset Switch) the connection to the controller through Cube Programmer is happening, but we are unable to change any option bytes, to revert back to Non Trust Zone Code. Once the reset switch(NRST) is high, it is going back to the same error. Any suggestions for this issue and how can we resolve this?Thanks and RegardsPhilip  

Hi Everybody,     Now i met an issue for STM32U575/STM32U585 Programming time different, below is my test log, i don't why get the different time, since i do the erase in any time. The blank chip programming time is 34s, and NOT BLANK chip programming time is 13s. NOT BlankSTM32_Programmer_CLI.exe -c port=SWD sn=55FF69064978865014230767 freq=8000 -e all -w "D:\Download_Tool\FW\EVT_SMT_2.0.1.6\RLT_ReleaseStandaloneNoAlgo_2.0.1.6.bin" 0x08000000 -v      -------------------------------------------------------------------                       STM32CubeProgrammer v2.14.0                        ------------------------------------------------------------------- ST-LINK SN  : 55FF69064978865014230767ST-LINK FW  : V2J45S7Board       : --Voltage     : 1.86VSWD freq    : 40

Hi everyone,I’m experiencing a new issue with STM32CubeProgrammer and I’m wondering if anyone else has run into the same problem.Starting today, every time I try to select a file (for example, when choosing a .bin or .hex to flash), the program freezes as soon as the Windows File Explorer window opens. After a few seconds, the whole application closes without any error message.This has never happened before — the tool was working perfectly yesterday. The only thing that changed is that Windows installed an update overnight. Since then, STM32CubeProgrammer consistently crashes whenever it tries to open the file picker dialog.Has anyone seen this behavior after a recent Windows update?Any ideas on how to fix or work around it?Thanks in advance!

When we want to debug only the M7 core, we use the following line and connect from VsCode:/c/ST/STM32CubeIDE_1.14.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.200.202505060755/tools/bin/ST-LINK_gdbserver.exe -cp '/c/ST/STM32CubeIDE_1.14.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.200.202503041107/tools/bin/' -d -e -v -m 0 -gBut the problem is that always the whole processor is reset because of the following as described in https://www.st.com/resource/en/user_manual/um2576-stm32cubeide-stlink-gdb-server-stmicroelectronics.pdf-g, --attach Attaches to the running target. Attach is aimed to be used to connect to a running program in the device without doing a reset or downloading a new program. [STM32_Programmer_CLI is always started with “mode=UR reset=hwRst” so that a device reset is done when loading a new program independent of this option. This guarantees that the flashing of the device is mad

I get this Error when trying to install the Cube Programmer V2.5.0 on Windows 10 (latest update).I have installed Java jre 1.8.0_261.Thanks for any help com.izforge.izpack.api.exception.IzPackException: An error occuredin java.lang.Thread.run() at null:-1in com.izforge.izpack.installer.unpacker.UnpackerBase.run() at UnpackerBase.java:241in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at UnpackerBase.java:319Caused by: com.izforge.izpack.api.exception.InstallerException: File execution failedin com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at UnpackerBase.java:299in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at UnpackerBase.java:483in com.izforge.izpack.installer.unpacker.UnpackerBase.executeFiles() at UnpackerBase.java:959 

I've got a brand new VM running Windows 11 pretty much off the shelf. I can install and run Cube IDE but when I try to install the STM32CubeProgrammer (64 bit version) I get into an infinite loop where the following happens:- It opens the Install Wizard which then closes- It opens the blue "STM32 Cube Programmer" window, which then closes- It opens the Install Wizard which then closesHere is a video of the behavior: https://www.loom.com/share/b3ce5e7a79ad425d840296845fd0c1edThe only way I can exit this loop is to reset the whole machine. It's not installed, so I can't uninstall it. I tried removing everything, upgrading java, and still the same problem. Any suggestions would be appreciated. Thank you!

Hey ho everyone I'm a Noob with all this, just surface level knowledge.I'm on Linux ((Ny)arch btw.) newest version. First everything worked switched boot mode (cant remember if boot 1 or 0 as no combination works now) and i could connect. Then i wanted to test 5V pins and out of laziness i shorted +5V with and LED. Had an error on the power status, repluged and everything worked again (proceeded testing pins without shorting). suddenly a few days ago i had the dev connect error solved it via boot 0 and 1 both to the right on the next day suddenly not even that worked. did a bit of switcheroo that worked until it suddenly didn't even with any position. tried reinstalling (MX, Prog and IDE) tried adding myself to the uucp group didn't work tried the whole procedure as root but Nyarch wouldn't let me open my files and i simply was to lazy to do it via CMD. now i have sometimes the problem with DEV_CONNECT_ERR in any boot position and sometimes it just tells me UR connection mode is define

# External Loader Issue: STM32U5G9ZJT6Q + MX25L12833FZNI-10G (Quad-SPI)## 1. Problem SummaryHello, I'm a novice developer who recently started working with embedded systems. I've been struggling significantly with implementing an external loader for several weeks now...I'm developing an external loader for **MX25L12833F** (16MB Quad-SPI NOR Flash) connected to **STM32U5G9ZJT6Q** via OCTOSPI1, but it continuously fails in STM32CubeProgrammer. The loader compiles successfully and generates a `.stldr` file, but programming operations fail.The problem is sector erase. Writing, reading, verification, and mass erase all function normally, but only sector erase does not work properly. What could be the reason? __attribute__((used)) int SectorErase(uint32_t EraseStartAddress, uint32_t EraseEndAddress) { OSPI_RegularCmdTypeDef sCommand; uint32_t SectorAddr; uint8_t status_before = 0; uint8_t status_after = 0; g_erase_input_start = EraseStartAddress; g_erase_input_end = EraseEndAddre

Hello,I'm trying to use STM32CubeProgrammer with STLink Debug Interface on remote Windows Serveur via RDP.I installed the driver, the device is detected via USB Redirectionbut STM32CubeProgrammer doesnt detect the interface:If I directly plug the device on a physical port, it works well. Do someone successfully set up such a configuration ? Is there any special detection on the app ? It would avoid us to install about 60 windows on our clients!Thanks :)   

Hello,STM32L4+, CubeProgrammer 2.21, ST-Link V2, Windows 10I need to do:* Full flash erase* Write Application image (.hex or .bin)* Write Bootloader image (.hex or .bin)* Set RDP level 1* Start the application at the Bootloader start address.-I am successfully doing this with the CubeProgrammer GUI, but I fail to get it to work with CLI.The "-e all" command works and says "Mass erase successfully achieved":C:\"Program Files"\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe -c port=SWD ap=0 -e all-However, I have tried numerous variants of the following command (and its separate parts alone) without success:C:\"Program Files"\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe -c port=SWD freq=3900 ap=0 -e all -w C:\SVN\Path\More_path\hex\Application.elf -w C:\SVN\Path\More_path\hex\Bootloader.hex -ob rdp=0xBB -s 0x08000000I have also tried with .bin files and their respective start addresses.The only response I get is the head

After updating and restarting my PC with Windows 10, my old version of CubeProgrammer would not open at all. The version number is unknown. Other STM32 software works without any issue such as CubeMX and CubeIDE.I then tried installing the latest version, 2.21.0. The program launched (even when run as administrator), but it did not function fully. I attached a screenshot for reference. None of the four icons on the top-left responded, and I received error messages when clicking the icons on the right.I also tried installing previous versions from 2.16.0 to 2.20.0, but none of them worked. Specifically:Versions 2.16.0, 2.18.0, and 2.19.0 briefly showed the launch logo, then closed immediately.Versions 2.20.0 and 2.21.0 would open, but the program remained unusable. 

Hello,I need to develop an external memory loader for a custom board with the STM32U375 and Macronix MX25U6432F NOR-Flash as external memory. The interface is via OCTOSPI1.I have already tested the interface functions to access the external memory and everything is working fine when used within a "normal" application running in the STM32U3 internal flash.As I am using the STM32CubeIDE, I created the code for the external memory loader based on the templates in https://github.com/STMicroelectronics/stm32-external-loader/tree/contrib. I am using STM32CubeIDE v 1.19.0 and STM Cube Programmer v 2.21.0.When I try to use the external loader in the CubeProgrammer, I can see (with some debugging) that the Init() function is called by STM Programmer, but fails quite early during HAL_Init(). With further debugging, I found out that the reason for the failing HAL functions seems to be the missing initialization of the global variables, i.e. the variables in the .data and .bss secti

Hi everyone,this is my first post, as I have always been able to solve my problems thanks to your help. Unfortunately, I can't find a solution regarding the CubeProgrammer API, which I am currently working on. I am developing an update tool that will use the internal bootloader of a STM32H743. For this, I am developing a C++ programm, using Visual Studio 2026 Version 18.2.0 with .Net Framework Version: 4.8.09221. CubeProgrammer_API.h and all neccessary .dll files are included as described in the documentation. There are no compiler errors or warnings. I used the attached UART example for testing but it is not possible to connect to my device. COM ports are detected by getUsartList function as expected. If I try to connect with function connectUsartBootloader as shown in the example I will get error -5 ( CUBEPROGRAMMER_ERROR_NOT_SUPPORTED ). Nevertheless, it is possible to establish a connection and execute a file upload with STMCubeProgrammer GUI and also with STMCu

0I have a device with an MCU in DFU-mode, and I want to flash new firmware to it. To do that I have the software we have developed at my company to interact with the device, mainly a Wpf-application written in C# and Xaml, which in turn uses the KSociety SharpCubeProgrammer library to make calls to the STM32 CubeProgrammer_API.If I use the STLink V3 SET hardware over I2C I get a CubeprogrammerErrorWriteMem error (return value -10), i.e. a memory write error, but using the same firmware file but instead directly over USB, i.e. not using the STLink, I get no error and the firmware is updated. In either way the calling code is almost identical, and I have checked that the data and address is the same when calling the API over both I2C and USB. The method called from the API is in either way WriteMemoryAndVerify(...).I found some information saying that it's the STM32_Programmer_CLI.exe that does the actual reflashing. If that's the case I have a vague idea that I must use the parameter --

Hi,if I connect the Cubeprogrammer via jlink to the custom board (STM32H562) and want to reset the option bytes by menu-selection "Reset MCU to factory settings", the process don't finish because the mentioned error pops-up.Is this caused due to a missing signal on the debug connector? The problem is now, that the mcu is in provisioning state and I want set it back to open state.Kindly regards,Stefan

I assume RDP means Readout Protection. Is there any means for disabling it programmatically with C#? How would it get enabled? I'm pretty sure I'm not enabling it with my program. I tried "–ob rdp=0x0" but got a -1 result, meaning Not Connected. So I'm in a situation where I can't connect because I'm getting -16 (RDP enabled) and I can't disable RDP because I'm not connected     

Hello,I have developed a external Loader for my custom projekt. It uses a W25Q128 QSPI conected to bank 2 and alternative Pin of CLK. (Worse!, but it is so...) So i Have no exactly example for it. Also it is a Dual Core, and no example i find have special definitions for it.I worked more days on it and it worked perfekt (now!) in a Cube Projekt.Erase, write and read (manual) and memory mapped mode are perfect.If I compile the stldr file, I can load ist in Cube programmer and stm prog utility.But then I could cry. I can't do anything. No read on QSPI and so on.....I think i will have trouble with the m4 Core. The M7 Core must wait for him.I don't know. How you can help me. What is wrong. Have you any Idea?

I have worked with ST-LINK/2 on Windows 10 for several years. I must upgrade to Windows 11 because Windows 10 support ended a few months ago. Today, I tried to program the WIO E5 Mini microcontroller, but I found it's impossible because there's no driver for it on my computer.I found some information that I should install version 9 of that driver. I downloaded it from the original STM source and ran it, but nothing changed. Is till don't see this driver among my devices. Installation ended without any error. Is there anybody who can point out what I am missing?

I'm trying to develop a simple Flash tool for my company using the CubeProgrammer_API.dll.I got most things working so far, but I can't get the External Loaders to work.CubeProgrammer_API exposes some functions like:setExternalLoaderPathsetLoadersPathgetExternalLoadersremoveExternalLoaderBut ther is no place to pass a specific loader to a function like 'downloadFile' or to select one of the 91 Loaders provided by CubeProgrammer.How can I select one loader for my project using the CubeProgrammer_API?

The STM32L0xx series contains EEPROM located at 0x08080000. This is extremely handy for storing factory calibration data, serial numbers, license keys, etc.The STM32CubeProgrammer GUI can read this memory in the Memory & File editing view Device memory tab by entering the Address and amount of data to be read. You can enter and read any address and range within EEPROM.However the Memory & File editing view cannot be used to download data from a binary file into an arbitrary location in EEPROM such as 0x08080100. If you open a binary file in a new tab and try to set the address to 0x08080100, it will display an Address out of range error dialog.This is not critical since you can still download to an arbitrary address in EEPROM using the Erasing & Programming tool within the GUI (or use the CLI tool), but it seems to clearly be a bug and there's no need for everyone to have to figure out the problem and the workaround...so I'm documenting it here.Also annoying (albeit arguabl

I have been working with a custom board using the STM32U073 for while, and have made a program that can active the USB system memory DFU. After this I suddenly cannot program the board anymore using the STM32CubeProgrammer.I can read all the flash memory, but cannot program the flash anymore.... Debugger connected Waiting for debugger connection... vchg_ctrl_run (duration_ms=16174368) at xxx/vchg_ctrl.c:108 108 setVchg(vchg_state); // Set the charger state based on the conditions connected to remote target localhost:61234 Note: automatically using hardware breakpoints for read-only addresses. load "xxx/build/Debug/hp2_charger_stm32_new.elf" Loading section .isr_vector, size 0xc0 lma 0x8000000 Loading section .text, size 0x10318 lma 0x80000c0 Loading section .rodata, size 0x754 lma 0x80103d8 Loading section .ARM, size 0x8 lma 0x8010b2c Loading section .init_array, size 0x4 lma 0x8010b34 Loading section .fini_array, size 0x4 lma 0x8010b38 Loading section .data, size 0x138 lma 0x8010b3c

Hi, using STM32 Cube Programmer and STM32 Trusted Package Creator W2.21, I was unable to detect the HSM card, getting error 0x88000002. I had to downgrade to V2.14, as mentionned in several posts to get it detected successfully.I use HID Omnikey 3121 reader.Any solution to be able to use last version 2.21 and HSM card ?

The release notes for v2.2.0 say that feature is in there, but I can't seem to find it.I tried the "Full Chip Erase" feature & it cleared everything EXCEPT the EEPROM.

The STM32CubeProgrammer does not appear to be able to read system memory from an STM32L051 when using the UART interface however it is able to do so when using the SWD interface.  When using the UART interface, both flash and EEPROM can be read, but not system memory.  This is on a factory fresh part with no readout protection set (0xAA).c:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe --connect port=COM5 -r8 0x1FF80050 8 ------------------------------------------------------------------- STM32CubeProgrammer v2.21.0 ------------------------------------------------------------------- Serial Port COM5 is successfully opened. Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off Activating device: OK Board : -- Chip ID: 0x417 BootLoader protocol version: 3.1 Device name : STM32L05x/L06x/L010 Flash size : 64 KBytes (default) Device type : MCU Revision ID : -- Device CPU : Cortex-

I'm using STM32_Programmer_CLI software v.2.20.0 to program an ST Nucleo board (NUCLEO-C071RB).I wish the software were better at automatically handling situations that make it fail.For example, this command does work normally for uploading firmware to the board:STM32_Programmer_CLI --connect port=swd --download firmware.elf --startHowever, if you have enabled read-out protection (RDP) by setting RDP=0 in the option bytes, then it fails with "Error: failed to erase memory"  (and for some reason, it prints that message twice).  If read-out protection truly does prevent you from erasing, the software should be smart enough to detect that RDP is on and then turn it off temporarily.  Instead, we have to manually ask the software to do that:STM32_Programmer_CLI --connect port=swd -ob RDP=0xAA --download firmware.elf --startNext, if you have enabled write protection for a relevant portion of flash, the software fails with the same "Error: failed to erase memory" error messages