STM32CubeProgrammer (MCUs)

The App launches and immediately quits.App version 2.19 despite downloading 2.20 package.Any ideas? thanks! ./STM32CubeProgrammer?J2??chdir /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin/.current dir /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/binLoading PRG Library: /Applications/STMicroelectronics/STM32Cube/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/MacOs/bin/libCubeProgrammer_API.dylibTrackedData.json file does not exist !99 external Loader list

Hi,I'm looking into creating a custom tool to provision our STM32H533 boards which will allow a non-trusted 3rd party to flash the firmware, configure the Option Bytes and program secret keys into the OptionByte Key storage areas.I cannot see any way to program the OB Key data via the API.  Is it possible?For reference, the CLI parameter would be -sdp secret_key_file.obkThanks in advance.Michael Waites

HelloI have completed the verification of read/write/sector erase/mass erase operations in the firmware based on the main() function.I have created an external loader by writing link.ld, Loader_src.c and Dev_inf.c and tested the operation. Read/write/sector erase works fine. However, only mass erase does not work.The code for the MaseErase(void) function is below, but just in case, I commented out the content and returned only LOADER_OK;, but the same symptom occurred.STM32CubeProgrammer 2.19, 2.18 versions are the same, and the message of 2.17 is successful, but the 0x90000000 area is not cleared.Is there a problem with the STM32CubeProgrammer program?Or which part of my source code should I modify?STM32CubeIDE 1.17.0STM32H747 및 STM32H743MT25QL512A

STM32CubeProgrammer 2.18.0 and 2.19.0STLINK-V3SET FW V3J16M7B5S1.STM32H563RIT6 rev X. Bootloader version 0xE4.1. Connect under reset.2. Configure MCU with EDATA1_EN=1 EDATA1_STRT=0x73. Erase sectors 120–127 and fill them with byte 0xEC.4. Create a file file.bin file with 10 bytes of some data.5. STM32_Programmer_CLI.exe --connect port=SWD mode=UR speed=fast ap=1 -d file.bin 0x09001800I expect sector 121 to be erased and the first 10 bytes of it programmed with contents of file.bin.Actually, sectors 121–127 are erased and the first 10 bytes of sector 121 are programmed with contents of file.bin. I.e. it seems erase is done for the reminder of the bank instead of calculating the number of affected sectors from file length.But if you set EDATA1_EN=0 and download file.bin to 0x08002000 it works. The system only misbehaves when the flash is configured as high-cycle count flash.The problem can also be reproduced by using a .hex-file targeting these addresses. Would it pos

Starting from V2.13 the STM32CubeProgrammer_CLI adds strange empty lines into the .hex file when adding CRCs using the --safelib command.Example:...:20F9C000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF47:20F9E000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF010002010100000032B840D616:00FA000006:00FA000006:00FA000006...:00FA000006:00FA000006:020000044807AB:20FA0000D8E292E5D9D0BDBC4BA59A0800855CA4FBEF5C19E0AC58BC12F208DD16414D16DA:20FA20007C32E22F87D80DB1ACEF0F2AC0E8EA3883BA937EC9278191C221243352C16A6BDA...Each empty line has the address of the first free place into the original .hex (seme address where CRCs will be added) but no data and the number of lines seems to be equal to the number of CRC lines added.This is annoying because later I use srec_cat tool and I get lots of warnings about these empty lines! Any suggestione?Thanks!

I'm trying to flash an an NUCLEO-N657X0-Q board with the STM32N6 using STM32CubeProgrammer v2.20.0. I have two NUCLEO-N657X0-Q boards here: One of them flashes just fine, the other one refuses to work. Both boards are in development mode (BOOT jumpers set accordingly as described here https://github.com/STMicroelectronics/STM32N6-GettingStarted-ImageClassification?tab=readme-ov-file#boot-modes). In STM32CubeProgrammer, I have selected the appropriate External loader to be able to write to the external flash memory.As a simple experiment, I am trying to erase a sector of the external flash memory. I am using the exact same STM32CubeProgrammer settings for both boards. Erasing the flash works just fine on one of the boards, but on the other board, I get the following error:Did I accidentally enable some kind of flash memory protection? How do I disable it? Or is my board broken? The board still boots the old code in the flash memory when in flash boot mode, so I don't thin

It would be great if the STM32CubeProgrammer would do proper error handling for J-Link debug probes instead of crashing.Issue:Every times I try to the connect to a STM32 target that is not powered, or not properly connected the GUI pops up three error messages that need to be close separately and on the next connect it pops up another error message and gets stuck. So that the program needs to be completely restarted. Preferred behavior:STM32Cubeprogrammer show only a single pop up or only log a warning message and recovers from this situation in a way that that allows it to connect to a STM32 target again. This is no regression and has been observed since j-link probes are supported.The last time it has been observed is on a Windows 11 PC with intel CPU, targeting a STM32G4 MCU with STM32Cubeprogrammer v2.21.0, J-Link HW version V11.00(latest FW Apr 1 2025) 

If on a STM32H747 the Cortex-M4 (BCM4 or BOOT_M4 Bit) is disabled by software, it is impossible to reactivate it with the STM32CubeProg v2.18.0 because the checkbox disappears in the user interface. But this happens only if you do a power cycle and reconnect to the target.

Hi,I've recently been trying to get an LRUN application up and running on the NUCLEO-N657X0-Q board. Similar to the posts in https://community.st.com/t5/stm32cubeprogrammer-mcus/stm32n6570-dk-unable-to-erase-external-flash/td-p/757897, I cannot access the flash for erasure, with errors indicating to verify flash memory protection. I currently have the BOOT0 jumper on 1-2 (for 0) and BOOT1 on 2-3 (for a logical 1), which should be putting me into the Development boot mode. For external loaders, I have MX25UM51245G_STM32N6570-NUCLEO selected. I've tried both full chip erase and sector erase, both giving me errors that tell me to verify flash memory protection.Please advise, I'm not sure what I'm doing wrong. This is my first time attempting to flash the memory.EDIT: I should've mentioned, I'm using STM32CubeProgrammer 2.20.0. I've tried this on both Windows 11 and Ubuntu 24.04EDIT #2: I have also attached the verbose log file after I hit "full chip erase" and a single

We are pleased to announce that STM32CubeProgrammer 2.21 is available What is new in 2.21: • Support for the STM32WL3Rxx microcontrollers:         – Internal memory programming        – Option byte and OTP programming         – PKCS#11        – Firmware authentication • STM32MP21x microprocessors: SSP support on Linux®• STM32WBA6xxG microcontrollers: Support for 1-Mbyte flash memory size • Support for new devices in the STM32C0 series: STM32C011xx, STM32C031xx, STM32C051xx, STM32C071xx, STM32C091xx, and STM32C092xx microcontrollers• Support for the factory reset of option bytes:         – STM32WBA5xxx and STM32WBA6xxx microcontrollers         – STM32U375/385 microcontrollers • Dynamic upgrade of components • Support for SWD multi-drop • Fast read new CLI command Main fixed issues in 2.21: Refer to the STM32CubeProgrammer wiki at: STM32CubeProgrammer err

I noticed that the V 2.20 STM32CubeProgrammer erase function doesn't work under Pop_OS!, a Linux distribution.  It does however work on Windows 10.  I don't think this is a logic failure within the STM32CubeProgrammer but some weird interaction with the USB Driver.  Just to be clear I am using STLink on a STM32N6 evaluation board.  Interesting that this function does work on a STM32h747i_disco board.  Another difference is I am using an USB A to USB C cable, but all the other functions work, after erase on the Windows machine.  I have the erase under Windows workaround but it is a little inconvenient. 

Hello Team,To address mass Programming of Customized board , Looking help to have Batch File / Python Script which accomplishes Following Task :1. Flash The Hex file2. Set RDP13. Read UID (96-bit ) of MCU4. Log UID and Time into CSVI tried with batch File using STm32Cube Programmer CLI.exe , but Failed to connect with ST-Link.yes, I am Using SWD Debug Interface. I am not sure uf any scripting Template is alraedy ready with CubeProgrammer.   

MCU : STM32U5G9ZJT6QExternal Flash : MX25LM51245GSPI Interface : HSPI1 When I use STM32_Programmer_CLI.exe I cannot erase the external flash.Board info:      I get following error from STM32_Programmer_CLI.exe: STM32_Programmer_CLI.exe -c port=SWD -el "C:\Users\USER\Desktop\Workspace\External_Loader\MX25LM51245G_STM32U5G9ZJ\Project\EWARM\Debug\Exe\MX25LM51245G_STM32U5G9ZJ.stldr" -e all-------------------------------------------------------------------STM32CubeProgrammer v2.20.0-------------------------------------------------------------------ST-LINK SN : 56FF70067287555130422267ST-LINK FW : V2J46S7Board : --Voltage : 3.21VSWD freq : 4000 KHzConnect mode: NormalReset mode : Software resetDevice ID : 0x476Revision ID : Rev ZDevice name : STM32U5Fx/5GxFlash size : 4 MBytesDevice type : MCUDevice CPU : Cortex-M33BL Version : 0x90Debug in Low Power mode enabledMass erase ...Error: Mass erase operation failed.Please verify flash protection How ca

OS: Ubuntu 24.04.2CubeProgrammer Version: 2.20.0Board: STM32F407G-DISC1Firmware Version: V15J63M63I am having intermittent connectivity issues with my discovery board and the STM32 IDE/Programmer. My system is able to detect the discovery board as it shows up when using the Linux command: lsusb. When launching the CubeProgrammer application it is able to (sometimes) detect the board after configuring the settings properly; after which the board setting are populated (see pic below)When trying to connect to the board, however, I receive fluctuating error message (see pic below). It is either the DEV_USB_COMM_ERR or the No debug probe detected errors. I am not sure what causes the errors to change but it usually happens when I reset the board because CubeProgrammer was unable to detect it and I am attempting to reestablish the connection (just having the board detected, not pressing the CONNECT button).The LD1 color is also intermittent and goes from RED to GREEN depending

Hello,Do you think it's possible to flash an ESP32 through a STM32 using a .stldr and the CubeProgrammer ?Same way we flash an external memory through SPI interface.The ESP32 is interfaced with the STM32G4 through a UART.I just want to know if this can be done, and if someone already did it ?Thank you

I am experiencing issues when attempting to upload the code to the MCU mentioned above on my board. I am trying to upload the code using the programmer on the STM32F407 Discovery board. It reads the chip, it erases the chip, but it does not upload the code. What could be the reason? The log file and the schematic of the MCU section of my board are below. Thank you for your assistance.  08:47:43 : MASS ERASE ...08:47:43 : Mass erase successfully achieved08:47:43 : UPLOADING ...08:47:43 :  Size         : 1024 Bytes08:47:43 :  Address      : 0x800000008:47:43 : Read progress:08:47:43 : Data read successfully08:47:43 : Time elapsed during the read operation is: 00:00:00.01008:51:28 : MASS ERASE ...08:51:29 : Mass erase successfully achieved08:51:29 : UPLOADING ...08:51:29 :  Size         : 1024 Bytes08:51:29 :  Address&nbs

This software has too many bugs. Could the developers please look into the main issues? 1. If the downloader fails to connect, it spams dozens of error messages. 2. Frequent freezing, primarily when the downloader fails to connect—the software gets stuck and can't even be closed, which severely impacts usability. 

Hi,I'm having problems entering in DFU mode on Windows using a sensortile.box pro. The board doesn't even show up on device manager howerver using the same board, with the same USB cable, on the same USB port on the same PC running Ubuntu the board enters DFU mode normally. I tried reinstalling CubeProgrammer more than once and also removing and reinstallig drivers but to no avail.Has anyone had the same problem?

Hi,I've started working with the SBSFU example recently on an STMU585. I have noticed that flashing the sbsfu_app_init.bin file is much slower (10x maybe?) if TrustZone is enabled.My workaround has been to create a script to do a regression to RDP level 0 with TrustZone disabled, which will mass erase the device, and then reflash both sbsfu_app_init.bin and the bootloader each time before renabling TrustZone at the end.I was wondering what the specific root cause of the slower flashing is, and if there is a better workflow that would allow me to update just the sbsfu_app_init.bin, or potentially just the NS part, with speeds comparable to those I get when the device is blank.Thanks,Mike

There is an uninstaller at ~/STMicroelectronics/STM32Cube/STM32CubeProgrammer/uninstaller/uninstaller.jarBut when I java -jar it, it just produce a log then exited, and nothing in the log actually mean anything useful.I see there is a old post about the same issue, but it never got any further.As a software product from an actual company, not provide a working uninstaller is unacceptable.Please fix this or provide a workaround ST.

Hi everyone,I’m facing a serious issue with my STM32F407 MCU on a custom PCB.I was flashing firmware from STM32CubeIDE using the onboard ST-Link from a Discovery board over SWD, and everything was working fine until one upload failed during the erase step.Since that moment, I can’t erase or reprogram the chip anymore, even from STM32CubeProgrammer or ST-Link Utility.le programming via STM32CubeIDE, I suddenly got this error in the ST-LINK GDB server console:Erasing memory corresponding to segment 0:Erasing internal memory sectors [0 2]Error: failed to erase memoryEncountered Error when opening ...\STM32_Programmer_CLI.exeError in STM32CubeProgrammerShutting down...Exit.After this, every subsequent attempt (from CubeIDE, CubeProgrammer, or ST-Link Utility) failed the same way.I have tried : Connect under Reset mode, SWD frequencies (from 4 MHz → 950 kHz → 100 kHz), RDP = Level 0 (0xAA), no write protection in Option Bytes, Tried Full Chip Erase several time

Hey there,Is there an option to turn off the prompts after programming in the STM32CubeProgrammer?The Log output is enough for me:Not really a problem, more like a QoL thingy - but i didn't see an option anywhere.Would be a nice addition if it's currently not present. Like "only prompt on errors"

Hello, I'm trying to download the program to the STM32H743VGT6 via the serial port. I keep getting the following error when using STM32CubeProgrammer. Do you have any solutions?

Hello everyone, I am facing a serious problem setting up the BLE_AT_Client example on my B-U585I-IOT02A board, as flashing the STM32WB5MMG radio module fails.Initial situation and cause of errorThe problem started when I aborted the flashing of the FUS firmware (stm32wb5x_FUS_fw.bin) via CN5 (external ST-LINK). Since then, the radio module has been in an inconsistent state.Error pattern and steps takenThe main problem is that I can no longer completely flash the three essential server files (FUS, BLE Stack, BLE_AT_Server).1. Connection: The connection to the STM32WB5MMG via CN5 (external ST-LINK) can be established in STM32CubeProgrammer (with low frequency: 4000 kHzand soft ware reset).2. RDP status: The Readout Protection (RDP) level is set to level 0 (AA) (no memory protection).3. Mass Erase: A ‘Full Chip Erase’ works, proving that the memory is not hard locked.4. Programming error: Immediately after the mass erase, any attempt to flash the FUS file (stm32wb5x_FUS_fw.bin at 0x080EC0

Trying to find a solution here. I have 2x STM32MP157 devices. I'm trying to do a cascade program here where the one device is put into DFU mode with the boot pins the a linux image is loaded to the other MPU and the image can be flashed via the CLI tool.for this part the DFU is only available on the OTG port and I dont have outside world access since they are connected to each MPU.  I see there are linux tool but those are x86_64 and not arm64. I see there is a MacOSarm64 but can't install that on debian/Yocto currently I can program with windows or linux(x86) with"STM32_Programmer_CLI -c port=usb1 -w .\FlashLayout_emmc_usb.tsv"  I need to be able to do this on an embedded system since I cant flash the eMMC  before SMT process.