STM32CubeProgrammer (MCUs)

Hi,I've 12 build and test servers to install the STM32Cubeprogrammer on.I'm not looking forward to going this manually.Especially as I've got to side install 2 versions.I'd very much like to make this part of our infrastructure configuration as code (in ansible).Is there a way to silently install the STM32Cubeprogrammer?Pete.P.S It will also be useful for automation prep of new start dev machines.

Hi,I'm encountering an issue while trying to install an SFI using STM32_Programmer_CLI within a GitLab pipeline.Context:I'm using a GitLab runner with executor = shell (cmd), so the commands are executed directly on the PC where the microcontroller is physically connected.I'm executing the following command:STM32_Programmer_CLI.exe -c port=SWD mode=HOTPLUG -sfi %SFI% %HSM_LICENSE% -rsse enc_signed_RSSe_sfi_U5_2M.bin %SFI% and %HSM_LICENSE% refer to the corresponding .sfi file and HSM license. The AES key and nonce used to generate the RSSe are also the same in all cases.Issue:The command fails with the following error:Error: Execution of RSS CMD failed, returned value = 0xF6F6F6F6 Additional Info:I’m running the same command on another PC with a different GitLab runner, using the same HSM license and the same AES key and nonce, but with a different RSSe file (in this case, a basic LED test for the microcontroller) — and it works fine there.Both target microcontrollers are the

I've written an external loader for a flash memory chip.  I'm able to program the flash chip using my external loader with STM32CubeProgrammer v2.19.0, but when I try to use my external loader with v2.20.0 it doesn't work. I've attached logs from both a good run with v2.19.0 and a bad run with v2.20.0.  I don't know how to debug this, because I naturally don't have access to the source code of the STM32CubeProgrammer CLI tool. Have there been any changes to the requirements of an external loader as of v2.20.0? Alternatively, can I somehow downgrade the STM32CubeProgrammer version that STM32CubeIDE uses? I'd really like to use the most current tools, but right now I'm stuck... 

Hi, I have a problem about upload program. I make size photocell with STM32F030F4P6 MCU. After I set hardware and software, I can not upload programming to MCU. I try to upload programming with ST-LİNK V2. And writing problem at console. Error is that ;Target no device foundError in initializing ST-LINK device.Reason: No device found on target.What can I do?I control connection pinout. Coming 3.3V and connection pinouts is correct. Please Can you give advice?Thank you.

Hi @stm32 I have a STM32U5G9 chip connected to a NOR_FLASH Memory MX25UM51245G using OctoSPI. I created an External Loader for the setup, but unable to read/write using the stm32 programmer. The custom driver I developed for the particular flash is proved to work with the same hardware setup, so i can confirm that the bridging between the working driver and the STM2Programmer is somewhat missing. Steps I Followed to create the Loader are:1) Created a CubeMx project for stm32U5 with OctoSPI enabled in my case.2) Manually copied the loader files from the link https://github.com/STMicroelectronics/stm32-external-loader/tree/contrib/Loader_Files and also integrated my custom driver for the particular NOR_FLASH. The driver is tested and verified separately,So it works.3) In the build configurations, pasted the command cmd.exe /C copy /Y "${BuildArtifactFileBaseName}.elf" "..\${BuildArtifactFileBaseName}.stldr" to create stldr. After further debug

I'm jumping to the bootloader from my application so that I can flash via USB in the end product.The end product has a permanently connected battery, and other means of hardware reset are not accessible.I'm trying to use STM32CubeProgrammer for this and can successfully connect and flash via USB under the "Erasing and Programming" tab. I have Verify and Run after Programming checked.However after successfully flashing, the MCU hangs and does not jump back to the application.At this point I can't reconnect via USB either in the tool. I do not think a hard reset is done after flashing.CLI is not an option based on the internal users I plan to give this to as a tool.What is the correct approach to make sure I actually get a clean reset and run of my application after flashing with the GUI?

 dear ST and/or Users,we’re using a STM32H743I and are planning to implement eeprom emulation as per an ST sample code.The algorithm employed in this code uses Flash Bank 2, Sectors 6 and 7 - we would store a few calibration values in these sectors of non-volatile memory.  The remainder of Flash memory is then available for our program memory.Once the product reaches customers there is always a possibility that the program may need upgrading.  How would we use the STM32CubeProgrammer to update program memory without touching the two sectors that are being used to store calibration data which must remain unchanged, please ?Is it sufficient just to tick <Skip flash erase before programming> and NOT to tick <Full chip erase>, and then commence programming ?  These two options are shown in the “Erasing & Programming” page of the STM32CubeProgrammer.Thanking you in advance for your assistance.

Describe the SetupDevice: STM32WB55CGU6Tool: STM32CubeProgrammerDescribe the IssueWhen attempting to flash the BLE stack version 1.23.0 to the STM32WB55CGU6 using STM32CubeProgrammer, I encountered issues with the following firmware files:stm32wb5x_BLE_Stack_full_extended_fw.binstm32wb5x_BLE_Stack_full_fw.binstm32wb5x_BLE_Stack_light_fw.binThe version information is not displayed in the “Selected File” section of STM32CubeProgrammer. After flashing, the FUS reports version v0.0.0.0, indicating that the firmware may be invalid or improperly formatted. This makes it impossible to proceed with BLE stack initialization or further development.I would greatly appreciate any clarification on whether these binaries are compatible with the STM32WB55CGU6 and, if not, whether a corrected version of the BLE stack 1.23.0 can be provided.Additionally, since I’m unable to downgrade the firmware on my device, I would like to kindly ask if it’s possible to release version 1.24.0 of the BLE stack ahead

Hi  I use stm32f412 vet6.Flash size is 512kbye.But stm utility program is 1mbyte size. Why??

The issue is that after downloading the modelzoo pose estimation example code from  https://github.com/STMicroelectronics/stm32ai-modelzoo-services/tree/main/application_code/pose_estimation/STM32N6/Model/STM32N6570-DK for N6 board in the STM32N6570-DK and using cubeprogrammer to load the .hex file using the external loader and erasing and programming tab, it says everything has been done correctly and the application is starting. However on the board nothing happens. Is there a way to fix this? I tried originally with the dev mode set to 1 using the boot0/1 switches and also pressing the reset/user buttons and switching from dev mode, but nothing happens. I even tried to do full erase of the chip to get rid of the preinstalled intro application and still it seems to flash correctly, but does not do anything. I tried to build the .hex file using STM32CubeIDE 1.19.0 and that hasnt worked either (it worked, but nothing happens on the board - e.g. LCD is dark). I

Hi I'm trying to reset the stm h563 to factory settings because I do some test before and I would like to use the stm for other things but I can't reset the changes I made with CubeProgrammer. I have those errors....   

Hello,I'm using STM32CubeProgrammer v2.17.0 with Linux (Linux Mint 21.3). There are a some bugs/improvements I discovered:1. By default, USB DFU devices are not recognized by STM32CubeProgrammer in user mode due to a permissions issue. To resolve this, I manually added an udev rule to allow access to USB DFU devices without requiring root permissions. It's unclear why this isn't the default configuration, especially since udev rules for STLink devices are automatically set up during the installation process.My udev rule (new file in /etc/udev/rules.d/) Spoiler (Highlight to read)# stm32 dfu mode, give access for STM32 cube programmerSUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", \MODE="660", GROUP="plugdev", TAG+="uaccess"# stm32 dfu mode, give access for STM32 cube programmerSUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", \MODE="660", GROUP="plugdev", TAG+="uaccess" 2. It seems that the UI isn't displayed correctly for USB DFU mod

Steps to reproduce:Connect NUCLEO-H563ZI to host with USB-C (STLINK)Open STM32CubeProgrammer GUISelect option bytes in side bar (OB icon)In the middle right, click on the drop-down on the "Read" buttonSelect "Reset MCU to Factory Settings"Click "Start Factory Reset"Expected behavior: All option bytes reset to factory settingsActual behavior: Only "Performing system reset." action goes to "PASSED" status, a few seconds later a segmentation fault happens, likely during the "Setting TZEN=B4" phase, and the GUI disappears Console log output:The Analytics API is not enabled The Analytics API is not enabled Loading PRG Library: /opt/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/../lib/libCubeProgrammer_API.so 99 external Loader list # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f5ae492eb14, pid=69214, tid=0x00007f5aedbbd6c0 # # JRE version: OpenJDK Runtime Environment (8.0_432-b07) (build 1.8.0_432-b07) # Java VM: OpenJDK 64-

I have a STM32H730 device, with a STLINKV3-SET connected via SWD (3 pins).When I Connect using STM32CubeProgrammer I get the following popup message;Error: Database: There's no active configuration for this device. All the 4 configurations are disabled!However the Connection appears to be okay, I can read/modify the SRAM memory and erase the Flash.So what does this error mean?Does is need to be addressed? I have updated STM32CubeProgrammer and the STLINKV3-SET firmware to latest.Thank you.   

Hello,Do I need to change the version of STM32CubeProgrammer, or is it just an incorrect setting in the .pro file? Please help me fix it. Thank you in advance.//---------------------------------------------------------------------------------------------------- Environment ubuntu 22.04 Qt 6.5.3 qmake version 3.1 STM32CubeProgrammer 2.18.0 gcc version 11.4.0 //-------------------------------------------------------------------------------------------------------- qt pro file QT += core gui greaterThan(QT_MAJOR_VERSION, 4): QT += widgets CONFIG += c++17 #DEFINES += QT_NO_VERSION_TAGGING # You can make your code fail to compile if it uses deprecated APIs. # In order to do so, uncomment the following line. #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000 # disables all the APIs deprecated before Qt 6.0.0 SOURCES += \ main.cpp \ mainwindow.cpp \ stm32downloader.cpp \ upgradeFirmware.cpp HEADERS += \ mainwindow.h \ stm32downloader.h FORMS += \ mainwindow.ui # Default rules for d

I bought an arm64 based PC a few months ago and I have been unable to connect to or detect stlink even after installing driver, is there a work around? has anyone successfully been able to use the snapdragon processor with stlink? is there another kind of debugger that works with arm based pc's? your help will be highly appreciated, thanks

Using latest STM32CubeProgrammer v2.15.0Register name and description don't match (rising register, but falling description, and vice versa).Which one is correct? 

Me 2, having the same issue as STM32C011 QFPN20 not able to be programmed using stlink-v2   moved from this post.

Hi,We are using STM32H74 microcontroller STM Bootloader ST Version 0x91.We are using STMCube Programmer V2.9 while during the serial programming using UART.On few of the units , we get the erase issue : Failed to erase memory . And then GETId not responded. All the power supply of the units are stable. On checking the NRST , it went low for around 30us . Refer attached.On few good units , erase takes around 6.5seconds with V2.9 STM32Cube prograamer. This issue doesnt occur when we use STM32 Cube prograamer V2.19. Erase takes around 4.8secondsOn checking the difference between the two VERSIONS we found the command sent for erase is different in both the versions of STM32 Cube Programmer.V2.9 sends command 0xffff00 data size :3 Bytes. This is a mass erase.While V2.19 sends 0X0000000000 DATA size: 5bytes. It is a page wise erase. The erase time taken by V2.19  is less compared to V2.19.Once the unit switches to the STM Bootloader, the IWDG timeout will be 16

I've been playing around with an STM32F7508-DK, and I was successfully programming hex files with CubeProgrammer and running the application. I eventually tried doing a "Full chip erase", and now when I program the hex files that were working previously, the application does not seem to boot. There are no error messages from CubeProgrammer, just the application hanging at the "white screen".How can I recover the dev kit?

Hi,I am currently working with a custom PCB(Print Circuit Board) that features the STM32G031F4P6 microcontroller, and I am unable to locate the option to configure the Brown-Out Reset (BOR) in the Option Bytes within STM32CubeProgrammer for this device. Interestingly, I am able to see and configure the BOR on the Nucleo-G031K8 development board. Could you please clarify if there is a specific reason for this discrepancy? Is there a way to enable or configure the BOR on the STM32G031F4P6 on my custom PCB? Additionally, are there any alternative methods to monitor the power supply or track the voltage levels of the STM32G031F4P6 microcontroller?Thanks,

I'm trying to use the BOR in the STM32G031F4P6 microcontroler, as in the datasheet it shows that there is a BOR in this series. But, when I open the STM32cubeProgrammer, it doesn't show the BOR configurations at the Option Bytes window, and I couldn't arrive to activate it by code too.My question is if there is really a BOR available for all the G0 series or it is just for some of the microcontrolers in that series?If there is a BOR available, can I do it using the LL library?

Hi,I'm using STM32CubeIDE with an ST-LINK V2 debugger (possibly a clone). When I try to upload my program to the STM32 board, I encounter the following issues:1. ST-LINK not entering DFU mode, so I can't update firmware.2. STM32CubeIDE gives this error:Error with command: GNU debugger version --versionCannot run program GNU debugger versi: Launching failedSetup:- STM32CubeIDE 1.18.1- ST-LINK V2 - Board: STM32F103C8T6- Windows 10Things I tried:- Installed ST-LINK drivers (STSW-LINK009)- Installed STM32CubeProgrammer- Checked Device Manager: ST-LINK appears- Tried STM32CubeIDE reinstallNeed help with:- Forcing DFU mode for ST-LINK V2- Resolving GNU debugger version - issue in STM32CubeIDEThanks!

STM32CubeProg 2.19.0.  STM32G041F8. MacOS 15.5. ST-Link.I'm working on setting the brown-out rising, falling, and enable options on an STM32G041F8.I started out by just using CubeProg to set the BOR_EN enable bit in the option bytes. Works correctly. It gives me the reaction I expected and I'm able to reconnect via CubeProg.Next I wanted to set the BORF_LEV to something other than 3 so I can test my code. I set it to 1, hit Apply, Cube prog complains that the connection is lost and it has disconnected from the device, and now when I try and connect I just get:17:13:46 : UR connection mode is defined with the HWrst reset mode 17:13:46 : ST-LINK SN : 31FF6A064D4E353828580643 17:13:46 : ST-LINK FW : V2J46S7 17:13:46 : Board : -- 17:13:46 : Voltage : 3.31V 17:13:46 : Error: Unable to get core ID 17:13:46 : Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug AuthenticationNo, I did not mess with the RDP values, just BORF_LEV

Hi everyone,I recently flashed new firmware onto my STM32F4 board using STM32CubeProgrammer, and now the tool won’t detect the device over USB anymore.It was working fine before the flash, and nothing in the hardware setup has changed. The device still powers on, and I can see the USB connection briefly appear in Device Manager, but STM32CubeProgrammer shows “No ST-Link detected” or just hangs on connection.I’ve tried different cables and ports, and even reinstalled the drivers, but no luck so far. Is it possible that the firmware flash disabled USB or changed the boot mode somehow?Also, if anyone has recommendations for tools that start with S (like ST-Link Utility or Serial monitors) that might help troubleshoot STM32 connections, I’d appreciate it.Thanks!