STM32CubeProgrammer (MCUs)

I downloaded and installed stm cube programmer, but every time I try to open it, I immediately get an error message saying that it quit unexpectedly. Currently running mac high sierra 10.13.6. How can I fix this problem?

Hello,I inherited an old software project from a colleague who retired. (He originally worked on Windows XP.)The software was designed to run on an STM32L-Discovery board.Since some packages need to be maintained, I want to build the software on a Linux machine (Ubuntu 24.04.4 LTS). I managed to create a CMake project that successfully builds the binary for the target.The issue I’m facing now is that I can’t flash the binary to the target hardware because STM32CubeProgrammer displays the following message:“Error: Old ST-LINK firmware version. Upgrade ST-LINK firmware.”I also tried on a Windows 10 machine and got the same result.On the official board page [1], there’s no mention of STM32CubeProgrammer.I’ve been searching for a solution since this morning, but I haven’t found the right hint yet.Can anyone confirm whether CubeProgrammer is unable to write to this Discovery board?Can anyone recommend a programmer I can use to flash the binary? (I know a few are listed in the documentation,

HelloI am connecting the ST-LINK and downloading the firmware to the programmer.I have a question. Can I do power from ST-LINK and download firmware instead of supplying external power to the MCU? Currently, I use external power, but I wonder if there is such a way.Thank you.

 I'm currently working on a project using an STM32G473RCT6. I've integrated the STL Lib (Self-Test Library) and intended to use STM32_Programmer_cli.exe with the -sl option to add the CRC block.The application starts at 0x08040000 and continues for a maximum of 128K, up to 0x08060000.There will therefore be an area of 0x20000/1024=128 CRCs, which will occupy 128×4=512 bytes.In practice, the application itself can only occupy 0x1FE00 bytes because the last block will be available for the CRC Area.Based on the STL documentation, these CRCs will be inserted at address 0x08060000−512=0x0805FE00.The command I'm using is:STM32_Programmer_cli.exe -sl "firmware.bin" 0x08040000 0x08060000 0x400The resulting binary has the entire section between the end of the original binary and 0x0805FE00 padded with 0xFF.Upon checking the CRCs that were inserted starting from 0x0805FE00, I can see that the first ones correctly match the CRC of the application blocks. However, when it reaches the CRCs cor

Hello Community,I'm currently facing an issue with entering the USART bootloader mode on my STM32U5 development kit (STM32U5A9JDK). Despite following the standard procedure, the device refuses to enter bootloader mode, and I'm hoping someone here might have insights or experience to share that could help resolve the issue.Here's a breakdown of the situation:I'm using a USB to UART converter that I've confirmed is pulled high.The BOOT pin configuration is set to '0' as required for USART bootloading.While the STM32 reference manual indicates the need for an RS232 transceiver, I've come across posts suggesting that it's not necessary if the voltage levels are correctly maintained.The voltage levels between my converter and the STM32U5 seem to be compatible, yet the bootloader mode remains elusive.I'm wondering if there's a nuance I'm missing here, especially regarding the RS232 transceiver. Has anyone successfully entered the USART bootloader mode under similar conditions? Could there be

HelloI am new to this forum, so if I am at the wrong place, let me know. How can this software: https://www.st.com/en/development-tools/stm32cubeclt.html be installed from a script? Namely into docker container? I get the following error: ``` DISPLAY not set. Cannot display license. Aborting. ```Thanks in advance.

As mentioned in the AN2606 document for STM32F412VGTx MCU(Custom chip), I am using USART2 (PD6/PD5) for UART bootloader using STM32CubeProgrammer. But I am getting an error message as attached. Help me to resolve this issue.

My goal is to use the STM32_Programmer_CLI.exe  from an application, but, for the moment, I just write down command lines in the Command Prompt (cmd.exe).However, the commands of writting the flash ( -w yourbinfile.bin )and erasing it completely (-e all) does not return any kinf of results. I just delivers a "STM32CubeProgrammer v2.21.0" response. Why?      

Hi,This might be a bit of a noobish question but despite my best efforts at searching I could not find a suitable answer. This forum may also be the wrong place for this question but since it is related to the new "cube" Swiss knife tool I thought this might be the right place to start. Feel free to move this question elsewhere if appropriate.I have a VS Code project that uses STM's extensions and bundles, and thus I can use "cube programmer" to invoke the STM32CubeProgrammer binary. In VS Code side I have a launch.json which allows me to build, flash and start debugging the application I've built on an STM32F0 series microcontroller. It works completely fine. Device appears in Windows, enumerates as a USB device, and everything just works as expected.What I want to do now is execute the build and flash steps, and then instruct the MCU to begin executing the program. I tried to do this by invoking the "cube programmer" with the following litany: cube programmer -c port=SWD mode=UR

Hi,STM32H563 chiprev Z.I am trying to work through How to start with OEMiRoT on STM32H573 and 563–Arm® TrustZone® enabled - stm32mcu using a NUCLEO-H563ZI MR1 board but using the latest STM32CubeProgrammer (2.18.0) and ST32Cube_FW_H5 (STM32Cube_FW_H5_V1.4.0).Section 2.5 is intended to demonstrate booting securely and then dropping into the System flash bootloader from non-secure application and connecting to it via UART. In my case, I use the virtual COM-port provided by the ST-Link provided on the board. I have not dared to go all the way to CLOSED but have chosen to tell the provisioning.sh that I want PROVISIONED state. I have confirmed using the SWD-connection that the TZEN is enabled after this and that PRODUCT_STATE is iROTProvisioned. I type 1 in the terminal displaying the "UI" of the non-secure app and then disconnect TeraTerm and in ST32CubeProgrammer I select connect method UART and Port = COM20, Baudrate = 115200, Parity = Even, Data

Hi all,I'm looking for a way to remotely *flash* a B-U585I-IOT02A | Product - STMicroelectronics eval board using the built-in STLINK-V3.Remotely means over TCP. Can be at the same computer (e.g., to pass-through debuggers to Docker containers), or across computers.This works well with GDB for debugging, but I need this to get running with flashing, too.Questions:Is there a way to make STM32_Programmer_CLI or related ST apps connect via TCP instead of directly to the debugger? I found ST-LINK-SERVER | Software - STMicroelectronics which seems to create the TCP bridge, but do any ST tools actually use it?Are you aware of this working with free tools like openocd?I could also flash via GDB, but I'm concerned about the special parts like trust-zone, option bytes, etc. Plus, I'm evaluating Zephyr, and the default way to flash the board is to use the stm32cubeprogrammer: B-U585I-IOT02A Discovery kit — Zephyr Project DocumentationThanks.

I've noticed a behavior with MX25UM5124G_STM32U5x9K-DK External loader over the past 2 years that I feel is a bug. I think the bug lies within the sectorwise erase of the MX25UM5124G_STM32U5x9K-DK External loader fw. If you flash a bin to external flash using the external loader with "erase before programming" enable , there is near 100% likelihood the verification step will fail. I believe this caused by the sectorwise erase not working as intended. The work around has been to do full chip erase on external flash then attempt the flash again. This will succeed almost every time. The behavior that led me to suspect the issue lies within the external loader is when I wrote a proprietary external flasher onboard the stm32. It uses sectorwise erase and has high reliability. This proves to me that flash chip and flash driver on the STM32 are working as intended. Note: We use this proprietary flasher for customer flashing updates but still use Cubeprogrammer for developm

The callback messages seem corrupt and I get a connection error or -162025-12-09 12-05-03.130|INFO||: Type = 0 Message = USB speed : Full Speed (12MBit/s)2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Manuf. ID : 2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Product ID : STMicroelectronics2025-12-09 12-05-03.130|INFO||: Type = 0 Message = SN : STM32 BOOTLOADER2025-12-09 12-05-03.130|INFO||: Type = 0 Message = DFU protocol: 1.12025-12-09 12-05-03.130|INFO||: Type = 0 Message = Board : --2025-12-09 12-05-03.130|INFO||: Type = 0 Message = Device ID : unknownShould be:2025-12-04 14-55-46.892|INFO||: Type = 0 Message = USB speed : Full Speed (12MBit/s)2025-12-04 14-55-46.892|INFO||: Type = 0 Message = Manuf. ID : STMicroelectronics2025-12-04 14-55-46.892|INFO||: Type = 0 Message = Product ID : DFU in FS Mode2025-12-04 14-55-46.892|INFO||: Type = 0 Message = SN : 2003645000002025-12-04 14-55-46.892|INFO||: Type = 0 Message = DFU protocol: 1.1|2025-12-04 14-55-46.892|INFO||: Typ

Been working on this for a few weeks now, I'm losing my mind. In STM32CubeIDE, only time I can get anywhere is in hardware reset, and there it times out. In STM32CubeProgrammer, it does connect. It can read the MCU name, flash size, all of that. All addresses read 00000000. However, I can't write in the programmer, and I just can't figure out why. Write to memory failed. Failed to erase data. Failed to download data. This is my first time doing something like this, so maybe I'm missing something. But nothing I've looked up has helped.

Best Fake USDT Sender Software Download Flash USDT Sender App Real Fake USDT Sender Software, Fake USDT Transaction App, Flash USDT Sender App, USDT Flashing software, Fake Tether Sender Software, Flash USDT Sender Tool, As cryptocurrencies like USDT (Tether) gain popularity, so do developers works in creating an innovative software for users, tools like the Fake USDT Sender Software or Flash USDT Generator. GET LIVE VIDEO DEMO:https://wa.me/447782260422What is FAKE USDT SENDER SOFTWARE ? This is a software that can generate and send flash usdt to any wallet of your choice and the fusdt perform and works just like the real usdt for 180 days and after the 180 days the fake usdt dissappear from the wallet and the software generate up to $500k daily. It’s a lifetime software which works on phone and PC, and remember it supports all wallet. There is a live test and demo to your USDT wallet to make sure the software is working perfectly FEATURES OF THE FAKE USD

Hi,I am working with the STM32N6570-DK board. Initially, I am using the GPIO_IOToggle example project to verify the basic board functionality.I configured the hardware using STM32CubeMX v6.16 and generated the project using the STM32CubeIDE toolchain. The project was built successfully using STM32CubeIDE v2.0.0.When I run the project in debug mode from CubeIDE, the LED toggles correctly.However, the device does not boot when I flash the binary manually using STM32CubeProgrammer v2.21.0. Signing and Flashing DetailsI am using the following command to sign the output binary generated by CubeIDE:STM32_SigningTool_CLI -bin <path to fsbl project.bin file> -nk -t fsbl -hv 2.3 \-o <path to fsbl project-trusted.bin file> \-dump <path to fsbl project-trusted.bin file> -align After generating the trusted binary, I flash it at address 0x70000000 using STM32CubeProgrammer.Boot ConfigurationBOOT0 switch: position 1–2BOOT1 switch: position 1–3After flashing the trusted bi

Dear community supporters,I would like to add ability to share STM32 projects platforms to my team. I have setup a server on Debian 13 and setup the STLink server tool, and using a SSH tunnel to do port forwarding from the attached STLink port on the linux server (localhost:7184) to a Windows client machine where I plan to use the STM32 Cube IDE, STM32 Cube Programmer.The tunnel is operational, and I have added a wireshark capture showing discussion from my Windows client when using the STM32 Cube Programmer, and a log from a STM32 Cube IDE debug configuration. For both, the Shared STLink is ticked, and in STM32 Cube IDE, I am able to see (the snapshot STM32 Cube IDE Debug Configuration.png shows it) the STLink SN from my remote STM32 Nucleo board attached to my linux server. Though, the STM32 Cube Programmer is unable to show the SN, seems it is unable to detect the probe devices, as shown in the st-link_gdbserver_log when starting the debug session.It seems the STM32Cube Programmer i

Hello,I am experiencing a persistent verification error when flashing an STM32H7 via USB DFU using the STM32_Programmer_CLI. The exact same command and hardware work perfectly on Windows, but fail consistently on macOS.Environment:Tool: STM32CubeProgrammer CLI v2.9.0 (also tested on newer versions)OS: macOS vs Windows 11Hardware: STM32H7 custom boardConnection: USB DFU ModeFile: .hex file (approx. 44MB) containing internal flash and external memory data.The Problem: On macOS, the download reaches 100%, but the Verification fails at 98%. The error always points to the start address 0x0800E000 reporting a byte mismatch (0x00 instead of 0x70).Log Comparison Observations:Windows (Working): The log explicitly shows individual sector erases: erasing sector 0003 @: 0x0800c000 done.macOS (Failing): The log shows Erasing memory corresponding to segment 0... but never confirms the individual sectors as "done." It seems the erase operation is being skipped or failing silently on the Mac DFU stack

When I attempt to power cycle a STM32N6570-DK or NUCLEO-N657X0-Q board via the STM32_Programmer_CLI, I get the following error message:Error: Failed to Power ON the board ! Here is the full log:❯ STM32_Programmer_CLI --power off index=0 --power on index=0-------------------------------------------------------------------STM32CubeProgrammer v2.21.0 -------------------------------------------------------------------Power OFF...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Power OFF the board finished with success !Power ON...Drives the target power pin out of the (onboard) ST-Link.Info: Power ON/OFF maybe not available on your Board [also not available on standalone probes]Error: Failed to Power ON the board !  However, when I attempt the same command on other Nucleo boards, I don't get this error. Here's the same command run on the NUCLEO-H533RE:❯ STM32_Progr

Hi,I'm having trouble getting my ST-Link V2 dongle to be recognized by Cube Programmer. It is recognized by Windows 10 in the device manager, I have been able to update the firmware, and I can get it to load in STM32 ST-Link Utility, but that program doesn't support the .elf file format I need.When I launch Cube Programmer, it does recognize something as shown by the voltage and the firmware (image attached), but when I click the refresh button next to the serial number it says "No ST-Link detected."I've read from others that there are a lot knockoffs of these dongles floating around that don't work anymore. That might be the problem with mine (this is the second one I've bought and tried). Can anyone point me to a good source to buy a legit one? In the products page, I've only seen the bigger ST-Link V2 unit and the smaller USB-C V3 unit, but not the V2 Dongle.I'm trying to flash a board for an Atari 2600 homebrew game I made and I attached a diagram of what the instructions show

Hi, I have brought 2 STlinkV3MODS. I have soldered wire at CN5 connector with 5+3 pin general connector to target the bluepill(not sure original or clone) the target MCU is STM32F103C8T6. when i select STlink at cube programmer shows error: debug authentication or STM32 target not found. Where as clone stlink V2 (usb dongle) type detected target MCU (cap1.jpg) Now question: 1) if cloned or fake chines STM32F103C8T6 is the cause?                                                             2) i am waiting from supplier the original STM32F103C8T6 chip, and they                                                                           suggest not

Hello Everyone!STM32CubeIDE version: 1.19.0STM32CubeProgrammer version: 2.18.0MCU: NUCLEO-STM32U575ZI-QI tried to use USBX DFU to update the firmware on the STM32U575ZI. The DFU mode was detected by STM32CubeProgrammer. However, when I clicked the connection button and disabled Read Out Protection, STM32CubeProgrammer was frozen as shown in the following picture Moreover, I tried to use DfuSe Demo to update the firmware. It erased the flash (I double‑checked this with STM32CubeProgrammer), but it could not write data to the MCU, as shown in the following picture. Could anyone provide us with some suggestions?We will be grateful for any help you can provide. reference:STM32Cube\Repository\STM32Cube_FW_U5_V1.8.0\Projects\STM32U5G9J-DK2\Applications\USBX\Ux_Device_DFU  

Hello everyone,I’m currently facing a blocking issue with SWD programming on an STM32U575VIT6Q placed on a custom PCB.Until today everything worked correctly: I use a CLI-based flashing procedure that programs a set of binary files (around a dozen) using commands like the following:%CLI_EXEC% -vb %VERBOSITY% -c port=swd dLPM -w "filename" %address% -vThe entire flashing sequence has always completed successfully, but during the last programming cycle I suddenly received the following error:Error: Cannot connect to access port 0! If you are trying to connect to a device with TrustZone enabled please try to connect with HotPlug mode. If you are trying to connect to H5 device and your target is already locked with password or certificate, please open your device using Debug Authentication.Since that moment, I have been completely unable to connect to the MCU with my ST-Link V2 in any mode.I tried:NormalUnder ResetHot PlugPower-downUnfortunately, all attempts fail with the same error.A few

Launched STM32CubeProgrammer v2.20.0 after a long time since last use - it prompts an update available via an icon button.Clicked the icon, clicked Next, ticked a box, clicked "install Now", it starts download ing a big file...When the file has finished downloading it then displays an error message - see attached screenshot.Unable to unzip file: /home.main/.STM32CubeProgrammer/downloads//STM32CubeProgrammer2.21.0_linux64.zipNote the double slash // in the path.Also tried launching it direct from a terminal prompt out of my /opt folder.... same result.  

Hi,I'm trying to work with the STM32N6. I have a NUCLEO-N657X0-Q board.When I use an external debugger via CN1 everything is fine, however I am experiencing a lot of trouble with the ST-Link.It seems like there is a small (0.01%) chance that attempting to access memory will cause the device to lock up.An example of the sort of command that gets sent to the ST-Link is: `[0xf2, 0x07, 0xfc, 0xff, 0x00, 0x34, 0xcc, 0x35, 0x01]`. That is, a simple command to the ST-Link to read or write memory.I am doing this as part of an attempt to implement support for the STM32N6 for probe-rs, however the problem seems to occur even when using ST tools. For example, the following has a good chance of locking up:./STM32_Programmer_CLI \ -c port=swd \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 \ -r32 0x34000000 32768 Once the ST-Link has locked u