STM32CubeProgrammer (MCUs)

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 pr

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 th

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 (Wo

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 att

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                                                                         

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.

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

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 32

Hi!I'm having trouble connecting to an STLINK ISOL via STM32CubeProgrammer. The STLINK is authentic, I purchased it from digikey. The programmer is detected under Device Manager. The programmer's LED remains static red at all times. Sometimes STM32CubeProgrammer detects an STLINK device, but when I click connect it gives 10:40:01 : STM32CubeProgrammer API v2.21.0 | Windows-64Bits10:40:09 : UR connection mode is defined with the HWrst reset mode10:40:14 : ST-LINK error (DEV_USB_COMM_ERR)10:40:14 : Error: Problem occured while trying to connect Changing to software reset10:41:23 : UR connection mode is defined with the SWrst reset mode10:41:28 : ST-LINK error (DEV_USB_COMM_ERR)10:41:28 : Error: Problem occured while trying to connect And then, when I click refresh interfaces the STLINK interface disappears.Disconnecting from USB and reconnecting, w

Good dayI have a Custom PCB with a STM32F217ZG populated.When trying to program with the STM32CubeIDE I get a No STM32 target found error.Then I tried with the STM32CubeProgrammer and get the following:20:27:26 : UR connection mode is defined with the HWrst reset mode20:27:26 : ST-LINK SN : 0670FF36344550304303404220:27:26 : ST-LINK FW : V2J46M3220:27:26 : Board : NUCLEO-F207ZG20:27:26 : Voltage : 3.26V20:27:26 : Error: Unable to get core ID20:27:26 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication In STM32CubeProgrammer I have tried the Modes in Normal, PowerDown and Under Reset. In Reset Mode i have tried Hardware Reset and Software Reset.When measuring with an scope on Pins 105, 109 and 25(NRST) I do see the Reset, Clock Pulses and something like Data Pulses but still get the error.Can someone Please

Hi. This is a Linux problem, because with the same parameters it works on Windows. I tested with v2.21.0.I am trying to use the UART connection mode with these parameters:RTS: HighDTR: Negative pulseI can see, with a voltmeter, that the RTS/DTR signals (MCU side) change states.This is what the log shows:17:32:36:714 : RTS High 17:32:36:714 : DTR Negative pulse with delay 200 17:32:36:935 : Serial Port ttyUSB0 is successfully opened. 17:32:36:935 : Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1,0, flow-control = off 17:32:36:935 : No Init bits value is : 0 17:32:36:935 : Sending init command: 17:32:36:936 : #byte 0x7F sent successfully to target 17:32:38:937 : Wait ends after 1 loop, dataready = 0, delay = 2001 17:32:38:937 : Timeout error occured while waiting for acknowledgement. 17:32:38:937 : No response from target received 17:32:38:937 : Retrying UART init co

Hi, I’m working with an STM32C011F6P6TR device, and after programming it via SWD using STM32CubeProgrammer, the MCU became completely stuck in resetSymptoms- After programming an ELF file through STCubeProgrammer, the MCU no longer runs.- The NRST pin stays LOW permanently, even after power cycling.- I cannot reconnect with STM32CubeProgrammer, even using “Connect Under Reset” mode.- The tool returns: DEV_HELD_UNDER_RESET.- Removing power, disconnecting ST-LINK, reconnecting, and trying again does not help.Before programming, everything worked normally and I was able to connect and flash multiple times (Using VS-CODE and ST extension).Questions:What could cause the MCU to remain stuck in reset after flashing?Is it possible that option bytes got corrupted or misconfigured during programming?Is there any way to force a full chip erase or restore factory option by

Hi ST team,I am using STM32U5G9J-DK2 board and the verson of STM32CubeProgrammer is v2.21.0.I tried to reset MCU to factory settings (in option byte tab) using STM32CubeProgrammer but failed.After that, STM32CubeProgrammer could no longer connect to the board with below log.14:23:14 : STM32CubeProgrammer API v2.21.0 | Windows-64Bits 14:23:25:813 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX66UW1G45G_STM32H7S78-DK.stldr 14:23:25:814 : External loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX66UW1G45G_STM32H7S78-DK.stldr is unloaded 14:23:25:814 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX66UW1G45G_STM32H7S78-DK.stldr 14:23:25:814 : External loader C:\Program Files\STMicroelectronics\STM32Cube\S

After update to the latest Cubu Programmer v2.20 a get this error when uploading the firmware:11:29:37 : Opening and parsing file: 1000BASET1-MC-ETH v1.3.hex11:29:37 : Memory Programming ...11:29:37 : File : 1000BASET1-MC-ETH v1.3.hex11:29:37 : Size : 56.78 KB11:29:37 : Address : 0x0800000011:29:37 : Erasing memory corresponding to segment 0:11:29:37 : Erasing internal memory sectors [0 28]11:29:38 : Erasing memory corresponding to segment 1:11:29:38 : Error: Sector size: 0x00000008 Bytes is out of range11:29:38 : Error: failed to erase memoryIn previous version (2.19) it works correctly.MCU: STM32G473RBT6Thanks

Hello,I try to connect the STM32CubeProgrammer (v2.20.0) to the STM32L496 that has enabled Read-Out Protection, but it is not possible. I need just to do the full chip erase and download new firmware.I remember that STM32CubeProgrammer (v2.0.0) allowed to erase the whole ship and connect to MCU successfully. Unfortunately, this old version doesn't work on Windows 11.Please help me to execute these two steps (full chip erase and connect) for the STM32L496 that has Read-Out Protection enabled.Thanks,Alex

 Hello ST Community,I’m developing a custom external loader for STM32CubeProgrammer where the STM32 acts as a bridge to program an external MCU (not external flash). The STM32 uses UART5 as a debug port and also as the communication interface to the external MCU.In testing, I see CubeProgrammer calling Write() repeatedly with non‑sector‑aligned sizes and addresses that don’t start at sector boundaries. Sample output from my loader:Starting... Address: 0x90000000 Size: 0x0003C700 Size is not sector aligned:0x0003C700 Address: 0x9003C700 Size: 0x0003C700 Size is not sector aligned:0x0003C700 Address is not start of sector:0x9003C700 ... Address: 0x901E3800 Size: 0x00018E00 Size is not sector aligned:0x00018E00 Address is not start of sector:0x901E3800 Address: 0x901FC600 Size: 0x00018E60 Size is not sector aligned:0x00018E60 Address is not start of

STM32CubeProgrammer CLI: v2.21.0STM32H573I-DKST-Link (part of DK)Experimenting with lifecycle states, I occasionally (maybe 1 in 3) get an mbedtls error when performing regression. This is with Trustzone enabled, using a leaf certificate. Sometimes running the command a second time will cause it to pass (as in the log below), sometimes the board needs to be reset in order to pass. This also happens using the regression.sh script and keys/certificates bundled with STM32CubeH5/Projects/STM32H573I-DK/ROT_Provisioning.A snippet of the error is below, and I've attached a log with the full command that failed, followed straight after by the same command that then passes.```STM32_Programmer_CLI -c port=SWD per=a key=Keys/leaf_priv.pem cert=Certificates/cert_leaf_chain.b64 debugauth=1....Certificates/cert_leaf_chain.b64load_trust_chain : 200 : error : sdm : Error calling mbedtls_pk_load_file()Error:

Where can I find the meaning of the returns from connectDfuBootloader? I'm getting -16 back and would like to know what it means.  

Hello ST community I'm trying to install SetupSTM32CubeProgrammer-2.16.0.linux in docker But getting error like below root@1694a12cc06d:/home/app/en.stm32cubeprg-lin-v2-16-0# ./SetupSTM32CubeProgrammer-2.16.0.linux./SetupSTM32CubeProgrammer-2.16.0.linux/home/app/en.stm32cubeprg-lin-v2-16-0chdir /home/app/en.stm32cubeprg-lin-v2-16-0/.current dir /home/app/en.stm32cubeprg-lin-v2-16-0SEVERE: com.izforge.izpack.api.exception.IzPackException: Console implementation not found for panel: com.st.CustomPanels.AnalyticsPanels Thanks in advance.

Following the directions in https://docs.zephyrproject.org/latest/boards/st/stm32n6570_dk/doc/index.html images signed using STM32_SigningTool_CLI version 2.20.0 run OK on the board.However, after upgrading to STM32CubeProgrammer 2.21.0, images no longer run (I believe the signature check is now failing on the device).Reverting back to 2.20.0 fixes the signing issue on Windows, macOS, and Linux for the STM32N6570-DK board.However, this is a blocker for developers using the Nucleo N657X0-Q board on Windows & Ubuntu because 2.20.0 has a bug which causes west flash to fail for this board on both Windows & Ubuntu. This west flash 

STM32CubeProgrammer v2.21.0 I implement Open Bootloader middleware to communicate USART protocol over USB CDC on Mbed OS 6 I found when I open STM32CubeProgrammer and click Erasing & Programming tab first time, program will freeze. But after first time does not freeze. After Click Erasing & Programming tab. Program send Get ID for 100 packets per sec Graph with 1 Sec interval, Get ID packets (I only filter 0x02) Graph with 100ms interval, Get ID packets

QuestionI implemented a custom bootloader with USB DFU. It worked without issues on my Windows 10 computer. After switching to a Windows 11 machine, however, my DFU device is no longer recognized.What I’ve triedConnected the device again on Windows 10. It appears in Device Manager, plays the connection/disconnection sound, and read/write operations work with STM32CubeProgrammer. This confirms that neither the bootloader nor the USB cable is the root cause.Installed STM32CubeProgrammer on Windows 11, but it reports “No DFU detected.”On Windows 11, there is absolutely no activity related to the DFU device in Device Manager. Other DFU devices, such as the STLink, are listed and working correctly.RequestWhat steps can I take to get my DFU bootloader detected on Windows 11?

Hello everyone,I’m working on a project based on the STM32H563RIT, and I’m encountering an issue related to SWV trace when using STM32CubeProgrammer.The firmware runs correctly in both debug mode and standalone. The problem appears only when I connect to the target with STM32CubeProgrammer and attempt to read the SWV trace. When I do so, the MCU freezes during the initialization phase, specifically inside MX_GPDMA1_Init(), where the DMA used for SPI communication is configured.As part of the investigation, I also provided the main.c file, where the full list of initialized peripherals and their initialization order can be seen.For testing, I tried swapping the initialization order between MX_GPDMA1_Init() and MX_SPI2_Init(). With this modification, the firmware starts even while connected to CubeProgrammer, but later freezes when SPI is used in DMA mode,

We encountered an issue with the STM32L562E-DK board when attempting to clear TZEN by changing the RDP level from 0 to 1 and then back to 0. Using the STM32CubeProgrammer, we can connect to the device via ST-LINK. The memory blank check indicates flash is empty, but the first byte verification fails during download. Additionally, the PC register value is 0xFFFF_FFFE, and the SP register value is 0xFFFF_FFFC.Could you please provide guidance on resolving this issue?