STM32CubeProgrammer (MCUs)

Hello ,I recently purchased the STM32N6570-DK Discovery Kit. When I first powered it on, it showed a default video demo on the LCD along with live imaging, which I assume is the factory firmware.Now, I would like to try some basic operations like UART communication and toggling an LED, so I created a new project for that.Before flashing my custom code, I used STM32CubeProgrammer to read and save the default firmware as a .hex file from the board.Before running my custom application, I wanted to restore the default original  demo by reloading the saved .hex  file. However, when I tried to program the board with this .hex file using STM32CubeProgrammer, it failed to load and showed an error (attached in the image).So here are my questions:Is it possible to directly reload the saved .hex  file to get back the default factory demo?

Hello all,I have a custom board with an STM32U5A9 mcu with an external MT25QL128 flash for TouchGFX assets.I have a working loader for IAR Embedded workbench and I'm trying to port it to work with the STM32CubeProgrammer.When building as a normal project - that is a minimal cubemx project with just ospi and clocks enabled and with my ospi functions it runs fine, read/write/erase the flash without any issues.However, when I move it to the loader framework the init function crashes - I believe in a hard fault or some kind. It's difficult to tell for certain since debugging the loader is tricky.The cube programmer only tells me "Error: Data read failure".I realized that if I return early from the Init, no error is issued and the flash only read zeros - which makes sense because the ospi is not initialized yet.Thus I found out that the issue so far is on HAL_OSPI_MspInit function that was generated by cubemx.This part of the code r

Almost all development boards produced by Chinese vendors use CH340 as the uart converter chip, I would like stm32cubeprogrammer to be able to control the RTS and DTR of this chip.If the feature works fine for the FT232RL, I don't know why it won't work for the CH340.https://community.st.com/t5/stm32cubeprogrammer-mcus/boot0-nrst-control-with-dtr-rts/td-p/255331 

Dear All, Hi, I am using STM32CubeProgrammer in Ubuntu system, but the resolution is not right. Could you please help me fix the problem? Thank you so much!Best

Hi,I have got a HDMI monitor and I am hardly able to see what is displayed. This issue has been around for years. Apparently, the issue is because of an old java version. My question is if that is ever going to be fixed and when? No next version please.Thanks,Hans

Hey, I'm just trying to use the BLE STM32UB5x in the board B-U585I-IOT02A. I used the following configurations for the STM32CubeProgrammer like suggested here (https://wiki.st.com/stm32mcu/wiki/Connectivity:STM32WB_BLE_Hardware_Setup)SW4 OFF, SW5 ON, SW3 SYS, SW6 0stm32w5x_FUS_fw.bin @ 0x080EC000stm32w5x_BLE_Stack_full_fw.bin @0x080C7000ble_at_server.hex Then, I switch SW4 ON, SW5 OFF and added this to main.c/* USER CODE BEGIN 0 */ static HAL_StatusTypeDef BLE_SendCmd(const char *cmd) { HAL_StatusTypeDef ret; const char crlf[] = "\r\n"; char response[64] = {0}; printf("Sending BLE command: %s\r\n", cmd); ret = HAL_UART_Transmit(&huart4, (uint8_t *)cmd, strlen(cmd), 100); ret |= HAL_UART_Transmit(&huart4, (uint8_t *)crlf, sizeof

I want to use stm32H5 series microcontroller and I am trying to write from STlink... I can access the microcontroller by SWD (I can check Option Byte), but I can't write. I can write to the USART via the bootloader with TrustZone disabled, but... I would appreciate it if you could provide me with some information about this.

Hi all,I am working on the development of an external loader for STM32CubeProgrammer.CPU is STM32H743, flash memory is W25Q512 in quadspi mode.I have a problem in indirect mode: it's working (read and write), but in read I have long timeouts: //Send command if (HAL_QSPI_Command(&FLASH_QSPI_PORT, &sCommand, QFLASH_DEF_TIMEOUT) != HAL_OK) { return HAL_ERROR; } // Receive data if (HAL_QSPI_Receive(&FLASH_QSPI_PORT, buffer, QFLASH_DEF_TIMEOUT) != HAL_OK) { return HAL_ERROR; }  It seems that HAL_QSPI_Receive goes ok on the first chunk of data, then when cubeprogrammer calls a Read for the following chunks I always have a timeout in HAL_QSPI_Receive, as if this call never finds the FTF or TCF flags active (QUADSPI_SR): HAL_StatusTypeDef HAL_QSPI_Receive: ..... while(hqspi->RxXferCount > 0U) { /* Wait until FT or TC flag is set to read

Hello everyone, I'm sending the command"C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=COM3 br=9600 rts=high -w C:\BinFiles\FirmwareLoader.bin 0x08005000 -v"from STM32Programmer CLI. Sometimes it just works fine and downloads and verifies the file written, but sometimes it shows the output as below. Does anybody have any idea what "Reemission of GetID command", "GETID command not acknowledged!" means, and what might have caused it and how it  can be resolved ?P.S. : As I have already said the command works perfectly fine sometimes, so please focus on the output below, not the command. Thanks in advance. -------------------------------------------------------------------STM32CubeProgrammer v2.15.0 -------------------------------------------------------------------Serial Port COM3 is successfully opened.Port confi

Hi,I am using Clives loader for the STM32H with the correct pins etc but it never works in the STM IDE, so I thought I would follow controllertechs videos to try and make my own loader, that didn't work either, but I did verify all the QSPI parts reading/wriitng etc are working. I also learned a good test using the CubeMX Programmer (and that fails using my loader for a different reason) but, I then thought OK will test it with Clives and MX Prog, and that fails on verification when I try and load a 1MB test file. I have emailed Clive and he has been incredibly helpful already, but thought I would also ask in the community in case someone has a quick solution?

I have a design that I'm trying to bring up and program using the USB DFU capability. The board enumerates correctly in windows, but does not get into programming. It seems as though I have forgotten something, but don't know what to look for. I have checked the "Read Unprotect (MCU)" box. I have attached the verbose log of one cycle. What happens when I try to connect is shown there and after a bit a window pops up saying to turn off the power to my device. When I do, the cycle repeats! Thanks for any pointers...

I am trying to use CLion to program STM32 MCUs as an alternative to other IDEs. For flashing and debugging, I want to use the Embedded GDB Server provided by ST, specifically ST-LINK_gdbserver.exe.I prefer not to use OpenOCD because I have found it to be less stable for my use case. The Problem:I am struggling to find the correct configuration to make ST-LINK_gdbserver.exe work properly with CLion. I tried using a configuration I found in this GitHub issue:Link: Official ST-LINK gdbserver support · Issue #354 · Marus/cortex-debugHowever, when I try to run the GDB Server with this co

Hi everyone,I'm trying to flash my STM32WB55 and the connected MX25R64 external memory.I have already created my external loader and tested it with the CubeProgrammer, feeding it with a .srec file containing only external addresses (>= 0x90000000).However, I was trying to unify the flashing process by using the external loader option present in STM32CubeIDE. This option generates a STM32_Programmer_CLI command and feeds it with a .srec file that covers both external and internal memory:C:\ST\STM32CubeIDE_1.18.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.100.202412061334\tools\bin\STM32_Programmer_CLI.exe --connect port=SWD speed=fast mode=UR reset=hwRst --extload <path/to/extloader> --download <pat/to/srec> --verify --log <path/to/log>srec_info output:Format: Motorola S-RecordHeader: "ST-LINK GDB server"Execution Start Address: 000

If TrustZone is enabled on a device, I cannot use STM32_Programmer_CLI.exe -d to program high-cycle count flash.If TrustZone is disabled, it works.Based on STM32_Programmer_CLI -w16 not working in high-cycl... - STMicroelectronics Community I have reason to believe that it does work with TrustZone on if you have working secure boot code that puts the device in a higher HDPL before programming is attempted. But I have not tested this myself. And if there needs to be some data in high-cycle count for the boot loader to start, you are stuck. In theory you could catch the double ECC-error and program the sectors with default values from the application, but that is a hassle.I'd love to get some feedback from ST on if I am doing something wrong here or this is a bug in either the programmer or the M

 Problem DescriptionI'm working with the B-L072Z-LRWAN1 development board and trying to configure the SX1276 LoRa transceiver DIO pins manually (without using ST's HAL middleware). I want to use an external LoRaWAN library (LDL) that requires explicit DIO pin configuration.Current ConfigurationBased on my research, I have the following pin mapping:  c#define DIO0_PIN GPIO_PIN_4 // PA4 #define DIO1_PIN GPIO_PIN_1 // PB1 #define

Hi, we're having some issues while trying to connect a STM32F030C6 to the Stm32CubeProgrammer via USB, through the embedded STM32 Bootloader.Using the same working sample of one of our devices, we perform several connection tests on different Windows 10 PCs, all set up with the following configuration:STM32CubeProgrammer V. 2.10USB plugged directly in the laptop portSTM32 drivers properly installedAll the PCs were able to properly detect the device in bootloader mode, showing "STM32 BOOTLOADER" in "Device Manager" and some of them were able to properly connect to the device, allowing us to perform DFU operations.However, on some PCs, the following warning appeared, and no matter what we tried (flag set on "read unprotected", power cycles..etc), we weren't able to connect to the device:

STM32CubeProgrammer v2.21.0  

Hello,     I am using NUCLEO-WB55RG board to implement BLE and I got error when I was Upgrading my STACK Version currently which is v0.0.0.0 in STM32CubeProgrammers FIRMWARE UPGRADE SERVICE option, I select stm32wb5x_BLE_Stack_full_fw.bin with 0x080D4000 memory location for stack upgrade which is preferred by STMicroelectronics official documentation, I have post my Screenshot after multiple attempts no update in STACK Version.--> It is mandatory to upgrade STACK Version for implement BLE?--> Also want better suggestion & Guidance Documents for BLE implement from basic to advance?it would be grateful for any guidance!...

My STM32H573 option bytes are in weird state which might be the reason that the device could not run any fw even if the flash still can be programmed; I imported the option bytes from a 'good' device, but could not apply the changes to the device, any idea?  Tried "Reset MCU to Factory settings" did not work either. Also, although the CubeProgrammer can connect to the device, CubeIDE cannot debug the device, the discovery.bat cannot even read the device IDs:c:\> discovery.bat-------------------------------------------------------------------STM32CubeProgrammer v2.19

Hi, i have recognize some odd behavior inside the CubeProgrammer external flashing feature.When flashing files less or equal to 128KB, then it flashes size at boundary of the block size of the Flash device which is 64K. As soon i get bigger than that it no more send data in that boundary but 67072 bytes. Why is that? I had to rewrite my APIs to get that working properly. I mean it is working now but sounds strange too me. Thanks

Hi everyone,I’m working on an STM32F4 project where I save a configuration struct to internal flash memory to preserve settings across power cycles.The first time I run my program and write the struct to flash, everything works fine. But the second time I try to debug, right after writing to flash, my debugger fails to halt the MCU and I get this error in STM32CubeProgrammer:Error: ST-LINK error (DEV_TARGET_NOT_HALTED)Encountered Error when opening C:\ST\STM32CubeIDE_1.15.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin\STM32_Programmer_CLI.exeError in STM32CubeProgrammerHas anyone experienced this issue when writing to f

Hello,I am currently trying to program a nucleo board using USART. For this I am using the bootloader and Cube Programmer. I first developed a program and tester it by programming via st link. My program worked with no problem. I then tried to program using UART. I was able to connect but as soon as I started programming, I get the message Error :GETID command not acknowledged and then the nucleoboard is disconnected.Here are my settings and the boot0 pin is tied to 3.3V.When I program I can see on the oscilloscope that some part of the program is on and working but not fully as well.

Hello,i've set the PRODUCT_STATE of my STM32H7S78-DK in the STM32CubeProgrammer from Open (39) to Revisioning (17):When trying to reset the state to Open again I get following error:Is there a way to reset to the product state to Open again? I've read that there should be

Steps to reproduceYou can find the output files (ELF and bin) attached to this post. The steps to create them are as follows:Download and extract X-CUBE-CLASSB library for STM32H5, version 4.0.0Open the contained example project in STM32CubeIDE (we'll use the TrustZone one)Modify the secure application linker script to include a gap at the beginning (e.g. for MCUboot)--- STM32CubeIDE/Secure/STM32H563ZITX_FLASH.ld.bak 2025-05-20 10:05:08.623676118 +0200 +++ STM32CubeIDE/Secure/STM32H563ZITX_FLASH.ld 2025-05-20 10:05:13.813692793 +0200 @@ -46,7 +46,7 @@ MEMORY { RAM (xrw) : ORIGIN = 0x30000000, LENGTH = 320K /* SRAM1 + SRAM2 */ - FLASH (rx) : ORIGIN = 0x0C000000, LENGTH = 1016K + FLASH (rx) : ORIGIN = 0x0C008400, LENGTH = 983K FLASH_NSC (rx) : ORI

Situation context:We have a device with an STM32F103 mcu that has an IAP, that hasn't change in a few years, and we came up with a new version after a long without updating the device. The thing is that the new version works fine as long as the program is flashed via Keil either on Debug mode or Download mode over jtag. The problem comes with virgin devices, in production they download the new version using CubeProgrammer, the usual way of doing it is to perform a "Full chip erase" then download the IAP and then the program, this results in the device rebooting all the time and impossible to debug as it gets lost when we open a debug session in Keil. After discarding if it's a hardware problem I get one of this devices and redo the whole thing using v2.14, v2.18 and v2.19 of the CubeProgrammer with same results with each version. The funny thing comes when I use Keil on the same device, I erase the flash memory, download the IAP and then download the program, this