STM32CubeProgrammer (MCUs)

I am having to program a unit via UART, and every time I open the STM32CubeProgrmmer GUI the interface selector shows J-Link/Flasher.It remembers if I choose ST-Link.If I manually edit the "interface=" entry in config.properties to 2, STM32CubeProgrmmer opens with UART selected.On exit, the "interface=" entry is rewritten to 1.If I select USB as the interface, the "interface=" entry is rewritten to 2, which opens as UART the next time, and then the "interface=" entry is rewritten to 1 on the next exit.

 # 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.---## 2. Hardware Configuration### 2.1 MCU: STM32U5G9ZJT6Q (LQFP144)- Cortex-M33, up to 160 MHz- 2.5MB SRAM- OCTOSPI peripheral### 2.2 External Flash: MX25L12833FZNI-10G (Macronix)| Parameter | Value ||-----------|-------|| Capacity | 16MB (128Mbit) || Max Clock | 133 MHz || Page Size | 256 bytes || Sector Size | 4KB || Block

Hi all.I tried to upgrade my onboard ST-Link V3 (STM32U5G9j-DK2).I use STM32CubeProgrammer for MAC V2.21.The upgrade process breaks with this message:"ST-Link device lost when exiting upgrade mode"In this situationthe COM-LED red is ON,the COM-LED yellow is BLINKING,the PWR-LED is OFF.How can I reactivate the onboard ST-LINK V3 in this situation?Kind regardsT3-Uwe

CubeProgrammer doesn't work with OpenJFX 11, but OpenJFX 8 cannot handle HiDPI screen, which makes Cube Programmer almost illegible.Since you were able to release several new versions in the past months, could you please also update to Java 11, or fix the HiDPI issues yourself?

Where to start...I have mave made a bootloader (done this before), which is placed in the low end of the flash memory. The application is in the subsequent flash.My board has a USB port and a DIP switch for forcing the BOOT input pin high. When I flip the DIP switch on, and power the board, I can connect STM32CubeProgrammer to the internal DFU bootloader via the USB port. I can also upload my application through the USB port. But when I try to upload my own bootloader, it fails. This is the output from STM32CubeProgrammer:However, if I connect an ST-LINK programmer to the board, I can upload the very same file with n

While installing the program for my windows 10  it hangs at step 8 which is shortcuts set ups. So I have been reaserching the internet and forums for a while still didn't manage to find a solution

Hi all,I've searched for similar post but solutions provided did not work for my case.For compatibility reasons I needed to upgrade from ST-Link to Cube programmer CLI but I've encountered roadblocks while using the -w commands with the Cube CLI.If I write directly with the CubeProgrammer UI, no issue at all, but if i try using CLI below error pops-up: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=SWD mode=UR -w8 0x08080000 0x02 -v -hardRst-------------------------------------------------------------------STM32CubeProgrammer v2.21.0-------------------------------------------------------------------ST-LINK SN : 54FF6C066685495431141687ST-LINK FW : V2J46S7Board : --Voltage : 2.71VSWD freq : 4000 KHzConnect mode: Under ResetReset mode : Hardware resetDevice ID : 0

Hi all,I m trying to enter DFU mode for my SensrTile.box PRO using my USB.the problem is STM32cubeProgrammer  couldn't connect to my board.However, when i try to use another PC it works perfectly.therefore i suspect the problem might be related to  a driver issue on my laptop.Could someone help me resolve this issue?Thank youFor reference, my laptop is an Asus TUF Gaming A15. I'm not sure if this information is relevant, but I thought I'd mention it.

There are STM32 models, where the suffix denotes a dramatic difference in the chip's pinout - either because of the USB-C PD -related variants, or because of SMPS variants. As the suffix is beyond the "lesser" parts of marking such as temperature range, sometimes distributors and vendors neglect/omit it, resulting in non-functioning products and frustration.For these models, CubeProgrammer should display the suffix along with the model number; it even should display something like "no suffix" for the variant without suffix, to be explicitly clear about this.This requirement stems from experiences like in this thread.JW

Hello,I had windows 10 and the CubeProgrammer was without problems.Now, on this PC with new windows 11 when I try to open file (hex, srec) in Erase & Programming  with Browse then a new windows is opening and after I can't choice my file and STM32CubeProgrmmer is closed.I tryed in administrator excecution but the problem is always.I looked this problem on all the windows with open file. Could you help me , please?Best regards  

When I open STM32CubeProgrammer (v2.21.0) it displays an error modal "Old ST-LINK firmware version. Upgrade ST-LINK firmware. If I click the "Firmware Upgrade" button an STLinkUpgrade 3.16.8 shows up with Current firmware: (blank)Type: (blank)Version: UnknownUpdate to Firmware: Unknown.The upgrade button does nothing when clicked. How do I fix this?I downloaded the software here  https://www.st.com/en/development-tools/stsw-link007.htmlAfter running/usr/lib/jvm/java-17-openjdk-amd64/bin/java -jar stsw-link007-v3-17-10/stsw-link007/AllPlatforms/STLinkUpgrade.jarThere is another upgrade dialog with version 3.17.10 displaying the same firmware info as above, with the upgrade button greyed out.Other commands ive run$ ls -l /dev/bus/usb/001/019

I've been trying to run code from the external QSPI flash (MT25TL01G) and have gone through an extensive debugging process that ended with a hard lockup. Below is a detailed log of my steps.1. Initial Setup & GoalBoard: STM32H750B-DK (MB1381-H750XB-B01, Product ID DK32H750B$AT1)Tools: STM32CubeIDE, STM32CubeMX (FW_H7 V1.12.1), STM32CubeProgrammer.Goal: Configure and debug an application to run from external QSPI flash at 0x90000000.. Initial Setup & GoalBoard: STM32H750B-DK (MB1381-H750XB-B01, Product ID DK32H750B$AT1)

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  : 55F

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 run

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

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

# 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_

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

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 0x08000000

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,

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

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