STM32CubeProgrammer (MCUs)

Hi, I am trying to bring up some software on an STM32N6570-DK.I'm able to upload example code from the STM32CubeIDE when the board is in DEV mode, e.g. when BOOT1 is set to 1. I followed the steps in this KB article: FSBL Explained However, I am unable to even connect to the board with STM32CubeProgrammer, even when in DEV mode. Here are the logs from STM32CubeProgrammer: Port 010:59:00 : STM32CubeProgrammer API v2.13.0 | MacOS-64Bits10:59:21 : UR connection mode is defined with the HWrst reset mode10:59:21 : ST-LINK SN : 002000413234510E3733393410:59:21 : ST-LINK FW : V3J16M910:59:21 : Board : STM32N6570-DK10:59:21 : Voltage : 3.29V10:59:21 : Error:

Split from Cannot connect to NUCLEO-N657X0-Q - which is solved.This is a new question.Follow up question: what should i do if i want to connect using flash boot?

Hello,(ST-LINK + CubeProgrammer UART/USB both failing)I am using a NUCLEO-N657X0-Q board. I cannot flashing my code via the ST-Link ( ST-Link windows driver is installed and detected through device manager and I had already updated the stlink). it throws this error:STMicroelectronics ST-LINK GDB server. Version 7.11.0Copyright (c) 2025, STMicroelectronics. All rights reserved. Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : EnabledInitWhile : Enabled Target unknown error 32 Error in initializing ST

Hi, I have been flashing STM32L151VE by using DFUSe tool for a while. But I could find some difficulty after the OS upgrade to windows 11. Also, I found that the DFUSe tool may not support new ST Boards as per official STM website, so I started using STM32Cubeprogrammer tool, with which I am unable to flash.When I select the erase option while flashing, it fails.When I skip the erase option while flashing, file download works, verification fails and it works inconsistently.Starting address for application part is 0x8008000.I tried integrating the DLLs and API provided in the installed tool's folder. By using methods: massErase() and sectorErase() as per the API, response is successful but when I manually check the memory, they are not erased and even the downloadfile() method

Hi Community,I am trying to get the Automatic Mode working, without success. There is a very similar (but locked) post about this going back to 2021 here, for which there is no accepted solution, so this may be an unresolved bug.I am using API V2.20.0 and my ST-Link/V2 firmware is up to date. My target device is STM32C071 on my own pcb, using SWD. I have no issue with manual programming but automatic mode is problematic. To keep it simple until working properly, I am not programming any option bytes at this stage.I start with the ST-Link connected to a board, then click Start Automatic Mode. After a delay of a few seconds it is programmed no problem and the dialogue then requests the device be disconnected and does recognise that it has been. So far so good.However, it then fails to recognise the second devic

I am using STM32G474RCT6 microcontroller, I want perform firmware upgrade through CAN communication. But my controller doesn't provide the feature of Firmware upgrade through CAN communication.is there any possibility to use CAN communication for firmware upgradation in my controller. 

  Hi, I created a project on the STM32N6570DK and I only have the project "in (STM32CubeIde)", I don't have the FSBL and the Appli. How do I flash my firmware? I tried to use the fsbl provided by the official ST repository, namely "ai_fsbl.hex", but the program does not start

Last week we ran into issues flashing our custom boards (STM32H7S3L8H6) with the STM32Progammer_CLI. Originally we were using the version packaged with CubeCLT 1.18.0 (STM32CubeProgrammer v2.19.0). I noticed that ~7% of flashes failed flash verification after a "successful" flash. The errors were always grouped within a small region of addresses, and this region stayed the same until a new .elf file was compiled. Using CubeProgrammer GUI i was able to validate that those memory regions were in-fact invalid. For example, here is one of the test runs on our custom board:=== Final Statistics === Total Flashes: 624 Successful: 580 Failed: 44 Success Rate: 92.95% Failed Addresses (failure count): 0x080065C8: 12 0x080065C9: 7 0x080065CE: 6 0x080065CF: 5 0x080065CD: 5 0x080065CA: 4 0x080065CC: 3 0x080065CB: 2 As you can see by the

Hi everyone,I'm using STM32 Cube Programmer CLI to port an SBSFU example to STM32U5G9 platform (from U585). Other than shell script mess and no IOC files in this examples, I've managed to port the example and run it by using ST Link programmer under both Linux and Windows.The problem is that the newest release 2.20 has its J-Link functionality completely broken in Linux (I'm using Kubuntu 22.04 and 24.04, also tested in regular Ubuntu). Any command to STM32_cube_programmer_CLI ends up with:Error: Could not connect to the J-Link/Flasher, Library not found !The underlying issue is that libjlinkarm.so is not linked to the CLI executable: ldd shows it's linked for older versions, but no linkage for v2.20. I'm guessing this has happened since ST was finally moving away from weird versioned so names to non-versioned so's: i.e. libjlinkarm.so.7 -> libjlinkarm.soI'm hoping that someone from ST will rea

My project is using an STM32U575. I have been studying the DfuSe file format and wondered if this can be used to change the values of option bytes. I can see that CubeProgrammer_API used strings such as "-ob nSWBOOT0=1" with sendOptionByteCmd(). If I were to include a target in a DfuSe file whose address is one of the option byte registers, would this successfully change the option bytes? That is to say, is the bootloader smart enough to handle writes to option bytes (presumably by spotting the target address)? In firmware, this is more complicated than writing to regular flash. For context:  We are performing firmware update over USB using the built-in ST bootloader. The update is initiated in the firmware by changing the nSWBOOT0 option bit and resetting, which runs the bootloader. So far, we have then used STM32CubeProgrammer to connect to the device and send the latest BIN image. After that, we use STM32CubeProgrammer to change the option bit again

I'm trying to connect my STM32H743IGTX controller with JLINK using cubeprogrammerCLI. I am able to connect jlink with cubeprogrammer gui and able to flash. but when i tried using CLI it shows-------------------------------------------------------------------STM32CubeProgrammer v2.20.0-------------------------------------------------------------------Error: Could not connect to the J-Link/Flasher, Library not found !im trying to use external flash using my custom loader file generated from cubeide.the command i used is,/home/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/STM32_Programmer_CLI -c port=JLINK ap=0 sn=601003130 freq=4000 reset=SWrst -el /home/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/ExternalLoader/XIP.stldr -w /home/project/build/test.hex 0x90000000 -v

Hello,I am trying to get this STLink-V3set to connect for an STM32 board that my electronics engineer has designed.  Due to being at different locations, I need to get it linked at my location.  Several efforts have been made to install the software, install the driver, look at device manager, etc.  to no avail1. The COM light goes on when plugged into the USB on the computer2. The windows tone is heard when the plug in occurs.3. The STCube software consistently does not recognize the STLink.Preliminary questions1. To get a connection shall I have my board attached to the SWD pins or not, shall it be disconnected from my board?2. Is power supposed to be lit in the interface box? I only get COM to light up, not PWR How do I get this connection going?Below is a photo of my hookup, and a screenshot of the typical response I see from the STCube software.Thanks! 

hello~~NUCEO-stm32h563zi external loader => data read failed. I attaching ld file and source file.let me know how  to solve. please thanks 

Updating the flash software of a STM32F070CB microcontroller did not work:The STM32 is in BOOTLOADER mode and accessed from a Linux/Ubuntu PC using USB.STM32_Programmer_CLI (V2.20.0) does not work if the STM32 is connected directly to the USB port of the Linux-PC, but it does work if a simple USB2-hub is inserted between the PC's USB port and the STM32 USB port.In the non-working case the STM32_Programmer_CLI outputs this:-------------------------------------------------------------------STM32CubeProgrammer v2.20.0 -------------------------------------------------------------------

I keep getting warnings when using STM32CubeProgrammer_CLI that usb devices are still referenced: libusb: warning [libusb_exit] device x.x still referenced. This is a bit annoying.-------------------------------------------------------------------STM32CubeProgrammer v2.17.0-------------------------------------------------------------------libusb: warning [libusb_exit] device 4.7 still referencedlibusb: warning [libusb_exit] device 4.8 still referencedlibusb: warning [libusb_exit] device 4.6 still referencedlibusb: warning [libusb_exit] device 4.5 still referencedlibusb: warning [libusb_exit] device 4.1 still referencedlibusb: warning [libusb_exit] device 3.1 still referencedlibusb: warning [libusb_exit] device 2.1 still referencedlibusb: warning [libusb_exit] device 1.3 still referencedlibusb: warning [libusb_exit] device 1.2 still referencedlibusb: warnin

 Hi Team, I wanted to cross compile STM32CubeProgrammer API but it seems like we need libCubeProgrammer_API.so to be in the cross compiled version.Can you please help me and provide libCubeProgrammer_API.so file cross compiled for arm-none-eabi-g++NOTE: I have attached screenshot for the same. RegardsDanish Shaikh

Upon launching STM32 CubeProgrammer today, I encountered this dialog:In case the image doesn't show, the text reads:The server connection is not established.The network connection is required to download updates.Please check your Proxy Settings.This thread refers to the same error and is marked "Solved" but the solved problem is actually a different error, described in the same thread.This mes

I am flashing a hex file that has power management that enables the low power stop modes. On version 2.17 everything works fine, but when I upgrade to version 2.20 it starts to freeze when the board goes into sleep mode. I have been flashing using the CLI.I have tried multiple times on v2.20 and when I downgrade back to v2.17, it starts working again.I know that it works on v2.15 as well.I am using the exact same hex file each time.**edited for clarification**

HelloI am in the industrialization phase of a product based on STM32G0B0RE.In order to optimize the flashing process for my manufacturer I made a .bat file programming the product the MCU using the STM32_Programmer_CLI.exe commmand from STM32CubeProgrammer. Since I am not using the GUI of STM32CubeProgrammer is there any folder I can delete in the root to optimize the size of the package I'll provide. The STM32CubeProgrammer size is 1,36 Go if I can reduce it to 500 or 600 mO it could be very usefull. Best RegardsThibaud  

Version: v2.16.0I`ve downloaded and installed the latest application and was told that the CubeProgrammer could support J-Link now.the GUI shows that JLink device can be selected: I clicked the connect bottom, the chip select window of JLink was popped out:

Hello, Its just simple, when STM32_Programmer_CLI -c port=SWD mode=HotPlug -ob displ command is called - "Bit 21 DUALBANK: Dual-bank configuration" missing in report. stdout:       ------------------------------------------------------------------- STM32CubeProgrammer v2.18.0 ------------------------------------------------------------------- ST-LINK SN : ST-LINK FW : V3J15M7B5S1 Board : STLINK-V3SET Voltage : 3.27V SWD freq : 8000 KHz Connect mode: Hot Plug Reset mode : Software reset Device ID : 0x482 Revision ID : Rev W Device name : STM32U575/STM32U585 Flash size : 2 MBytes Device type : MCU Device CPU : Cortex-M33 BL Version : 0x93 Debug in Low Power mode enabled UPLOADING OPTION BYTES DATA ... Bank : 0x00 Address : 0x40022040 Size : 48 Bytes 0% 100% OPTION BYTES BANK: 0 Read Out Protection: RDP : 0xAA (Level 0, no protection) BOR Level: BOR_LE

Hello,I had generated an External QSPI loader for W25Q128JV and STM32H743 some 2 years ago.I originally used it with STlink Utility Programmer and then switched to STM32CubeProgrammer.  All good and working as expected with CubeProgrammer v2.17.I stopped updating the CubeProgrammer as every version after that including the latest v2.20 no longer functional with my custom .stldr file refusing to mass erase the device. Does anyone know what changed in CubeProgrammer support for External Loaders starting with v2.18 ?Thank you,Yuri

Hi. I just ordered a brand new NUCLEO-N657X0-Q, and cant connect to it using STM32CubeProgrammmer. I tried using ST-Link in different modes and reset modes. I also tried using external loader, and discovery under debug authentication, got the error message in the screenshot.Would appreciate some help.

Hello,   the STM32TrustedPackageCreator supports the obk-file-generation via CLI: STM32TrustedPackageCreator_CLI.exe -obk C:\OBKey.xml   This requires a xml-file. The gui-version allows the generation directly from a password. Is this also possible via CLI?   Best regards, Peter

I need to flash signed bootloader and signed firmware for ardupilot the file i am using is arducopter_with_bl.hexafter this I need to erase the entire chip and need to flash unsigned bootloader and unsignedfirmware again so that i can use that again. I want to achieve this without bricking the board because once it has happend.My board does not have BOOt0 pin and it does not have DFU mode. I am using ST-LINK using SWD.If any body can help me th how to achieve this. Thanks in advance.