STM32CubeProgrammer (MCUs)

Hello,I'm working with the STM32H7S7L8 -DK and I need for final product to program the external OCTOSPI flash via usb DFU.So using V2.20.0 Cube programmer i'm able to use external memory loader to read and program the flash using SWDBut using the USB i see the DFU  and before i select the good external memory laoder but when i click to connect i can only programm the internal flash of the STM32 when i try to read or program the OCTOSPI flash i have error.Do you have any ideasThanks 

Basically continuation of https://community.st.com/t5/stm32cubeprogrammer-mcus/stm32cubeprogrammer-upload-fail-after-update-to-2-20/td-p/825113 - after fixing the hex to correctly span both the banks, upload error (using ST-Link) still persists. Firmware can be uploaded using USB bootloader, just the ST-LINK upload fails. It seems that this is a bug of the STM32CubeProgrammer.STM32CubeProgrammer v2.20.0.I attach the firmware hex. I also attach log from the programmer.@PKola.1 @STOne-32 @Maryem  

I bought an ST-link V2 from amazon, this error occured, fearing it may be counterfeit, I then bought another St-link v2 from STM website itself so there is no way it is fake, but the same error still occured. I am on Mac M3 using Cubeprogrammer. There is utterly no documentation on this error. What do i do.

I am using CubeCLT v1.18.0 on an Ubuntu host. I recently got a new J-Trace and ran into warnings about the firmware version not being recognized. I traced the root of the problem being the version of `libjlinkarm.so.7` that ships with this version of CubeCLT.  I need to upgrade to a newer version of the library to resolve the warning. I am already using J-Link v8.48 elsewhere, so I plan to follow this guidance from SEGGER to upgrade the so file. Should it be safe to do this upgrade from v7 to v8? I also noticed that SEGGER release v9.20 of J-Link and was considering going to that. I assume that would include a v9 so. Would that be safe to go to as well? I have a logistical question regarding how ST manages the shipped version of libjlinkarm. It looks like CubeProgrammer specifically expects `libjlinkarm.so.7`. Is there

After evaluating/flashing the SBSFU examples on the NUCLEO-G071RB evalboard it's not possible to erase full flash anymore. I get the error below. How to set factory defaults that erasing is possible again?STM32_Programmer_CLI.exe -c port=SWD -e all   -------------------------------------------------------------------            STM32CubeProgrammer v2.12.0   -------------------------------------------------------------------ST-LINK SN : xxxxxxxxxxxxxxxxxxxxxxxST-LINK FW : V2J40M27Board    : NUCLEO-G071RBVoltage   : 3.21VSWD freq  : 4000 KHzConnect mode: NormalReset mode : Software resetDevice ID  : 0x460Revision ID : Rev BDevice name : STM32G07x/STM32G08xFlash size : 128 KBytesDevice type : MCU

When using a STM32H757, with external QSPI, on an STM32H757I-EVAL, I am experiencing some programming issues when programming an .elf file with sections pointing to external QSPI. I am using the ST External Loader for MT25TL01G_STM32H747I-EVAL. Programming does work successfully, but on newer versions of cube programmer, there are warnings about 32 byte alignment, and then verification fails. The addresses mentioned are in AXI SRAM, and are .bss sections, which are marked NOLOAD, so it's confusing why that memory is trying to be programmed and this error is coming up in the first place. Manually setting the ALIGN markers in the linker file to be 32 instead of 4 does seem to get rid of the warning, and fix the issue. I've seen this issue on with versions 2.19 and 2.21 Is this a known issue? I haven't seen this issue with 2.17. Attached are logs files with the warnings and errors. Thanks for the help!

Hi ST Community,I try to write the OTP Memory on NUCLEO-H563ZI Board with STM_Programmer_CLI (Debian Linux).With STM32CubeProgrammer GUI application I can access OTP memory (beginning 0x08FF_F000).When I try to access the otp memory via CLI:./STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -otp displI receive:Error: OTP programming commands are not supported with STLINK interfaces for this device. With lsusb I can see my STLINK-V3:Bus 001 Device 011: ID 0483:xxxx STMicroelectronics STLINK-V3 But also with the command (port=usb1 or usb0):./STM32_Programmer_CLI -c port=usb1 mode=HOTPLUG -otp displI receive:Error: Target device not found.Establishing connection with the device failed.&n

Hello,I am working with a custom PCB using STM32H745XI6 (dual core CM7 + CM4).I wanted to boot only the CM4 core.So, in STM32CubeProgrammer --> Option Bytes --> User Configuration:I unchecked BCM7 (CM7 boot disabled)BCM4 remained enabledI clicked ApplyThe operation completed successfullyNo mass erase warningNo security warningNo RDP Level 2 warningRDP was never changed manually.

Hello!I've was following this tutorial on Jtag locking for stm32h573RI using j-link. link to tutorial: How to enable RDP-like product state flash protect... - STMicroelectronics CommunityI made it to the updating the product state to 17 and was in the process of reconnecting under hot plug mode, however I didn't have success reconnecting. I get these 4 errors: 

Hello,What is the correct layout for the .tsv file for the STM32N6 with application?In this tutorial the FlashLayout.tsv is shown, however it only has the FSBL program in it. I cannot figure out what Id to use for the Appli (also Appli non secure), i tried 0x05 but i get error:Error: unable to get the associate alternate setting of partition ID: 0x 5 Error: please make sure that your alternate settings have string descriptors with the right format Error: unable to switch to partition with index: 0x05This document describes the Id's but i don't think that any of them apply, and the document is for the MPU's anyway.Thanks!

I have been running into an issue with the cubeprogrammer very recently where I am unable to connect to my MCU anymore. I get the following log: using v2.2212:41:28 : STM32CubeProgrammer API v2.22.0 | Windows-64Bits12:43:17 : UR connection mode is defined with the HWrst reset mode12:43:17 : ST-LINK SN : 34FF6A0630514B384036244312:43:17 : ST-LINK FW : V2J47S712:43:17 : Board : --12:43:17 : Voltage : 3.56V12:43:17 : SWD freq : 4000 KHz12:43:17 : Connect mode: Normal12:43:17 : Reset mode : Hardware reset12:43:17 : Device ID : 0x45012:43:17 : Revision ID : Rev V12:43:17 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!12:43:17 : Debug in Low Power mode is not supported for this device.12:43:18 : UPLOADING OPTION BYTES DATA ...12:43:18 : Bank : 0x0012:43:18 : Address : 0x5200201c12:43:18 : Size : 308 Bytes12:43:18 : Error: Up

Hi,I just noticed that CubeProgrammer v1.21.0 always shows me an update notification, but it is already the latest.Restarting the Cubeprogrammer or the operating system does not make any difference. Environment:- Windows 11- I have installed v1.21.0 alongside v1.20, but that should not make any difference, or would it? 

I used to work with Nucleo board STM32G474 and programm them. Recently I can not open the file to programm my devices. I looks a window problem.I installed again all the ST Tools but the problem remain.I can not open files.

I recently tried to use -noreconnect via the cli on windows and it still attempted to reconnect.I was connected via UART and programming option bytes. Here was the command I used:& "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=COM14 br=115200 -noreconnect -ob ndbank=0x0I see that there was fix put in for linux. Im wondering if the same bug exists on Windows.Thanks,Daniel 

Hello,Our project is based on the STM32WBA65MI, and we have an external flash chip on the board that we use STM32CubeProgrammer w/a custom external loader to program. This worked well with STM32CubeProgrammer v2.20, but when I updated to STM32CubeProgrammer v2.21, suddenly I was unable to connect to the board using the external loader.This happens as soon as I select the external loader andIf I select verbosity level 3, this is what I see:08:50:10:520 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/External

I want to set the BOR_LEV of H523 to 1. If you have any good ideas, please let me know.

Hi everybody, I'm using a custom PCB which is build upon a STM32L431CBT6 MCU. When connecting to the CUBE Programmer i had this error:Error: Database: There's no active configuration for this device. All the 1 configurations are disabled!Then, i confirmed the issue arose from the DeviceID 0x435 .xml file not having the 128K flash memory settings. What i did is code it myself like this:<!-- JTAG_SWD Interface --> <Interface name="JTAG_SWD"> <Configuration number="0x0"> <!-- 256KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0100"/> </FlashSize> </Configuration> <Configuration number="0x1"> <!-- 128KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0080"/> <

Even I am using the latest CubeProgrammer v2.21.0, it indicates an update available but when I check it, there is no update and the updater log does not update, it cannot update its last update date as well.I know not so important but quite annoying problem, i`d like to mention, 

Have been fighting ST-LINK_gdbserver over the last few days and am hoping that someone can shed some light.  I'm using JetBrains CLion with the ST-LINK gdb server. I have this configured in the "Debug Servers" setting. I want to get my ITM / printf calls to appear in my "MCU Console" window in CLion. So I have my SWO Enabled, I specify my clock (400Mhz / STM32H743), my divider (1000, should give 400kbaud data coming out), and my TCP port for the SWO data to appear on (59999). I've overridden my `_write` function to push to the ITM_SendChar function.  I press debug, JetBrains compiles, runs the ST-LINK_gdbserver, passes in the correct flags, "-z 59999 -a 400000000 -b 1000 ", and the GDB then connects to the GDB port (61234 - default).  However I don't see any SWO output via ST-LINK_gdbserver. If I run the STM32_Programmer_CLI in a separate terminal window with "./STM32_

I have the Nucleo-144 board N657X0Q.It appears to work (i believe there is demo code pre-installed - it is flashing a red led and the frequency changes when I press the user button).  However, I cannot get the Cube IDE or Cube Programmer to work with it.  I am just trying to read memory using the cube programmer as a test.  It connects, gets the information about the board, uploads the loader firmware, and then when it tries to read it gets an error and disconnects.The log file is attached.  I have tried using two different machines as hosts, and tried 2 different usb cables (both are suggestions from several posts I found).  I have tried reducing the speed, and using the "under reset" and "hotplug" modes to no avail.  I have selected the correct external loader before doing the check.  I am using a separate power supply on the user USB to rule out any problems with enough power from the host machines on the USB port.

This fault is still happening since Oct 2024. However I found a workaround documented here -->https://stackoverflow.com/questions/78850472/stm32cubeprogrammer-flash-loader-cannot-be-loadedIn case the link has died, you need to do the following...Connect STM32CubeProgrammer to your STM32 device and note the "Device ID" listed in the "Target Information" window bottom right of the CubeProgrammer app, e.g. for an STM32F103 this will be 0x410.cd into your "STM32CubeProgrammer/bin/FlashLoader" folder.duplicate the file that matches your device ID (e.g. for an STM32F103 the file would be 0x410.stldr)and then rename the duplicated file "0x".Then restart STM32CubeProgrammer and it will now work properly. 

Hello,I have the issue that the FlashLoader is detected but not set correctly. The error message is:flash loader cannot be loaded. FlashLoaderPath = CubeProgrammer/bin/FlashLoader/0xAs a workaround I can create a copy of the correct FlashLoader and name it 0x, but I think this should work automatically. I am running on Linux and the issue exists for several versions of CubeProgrammer and on multiple Linux distros for me. My current version 2.21.0.The issue is really annoying if you switch boards and forget to copy-rename the correct FlashLoader.    

I have a NUCLEO-F030R8 development kit and an X-NUCLEO-WB05N-B01 (STM32WB05N) expansion board.I am using an ST-Link V3 for programming and debugging.I believe that I have connected the boards according to the official X-CUBE-WB05N Getting Started documentation (v1.1.0). The wiring, pin mappings, and configuration settings have been done based on the document.I am trying to communicate between the NUCLEO-F030R8 (host MCU) and the STM32WB05N over SPI.The SPI pins, IRQ, and reset connections are configured according to the documentation. However, in this setup, the STM32WB05N does not appear to reset properly, and SPI communication cannot be started.On the STM32CubeMX side:The X-CUBE-WB05N v1.1.0 expansion package is selectedSPI configuration and pin assignments are set as

Hi!I am making a custom external loader for my custom STM32F469 board equipped with a W25Q128 flash mermory on QuadSPI.To do so I am using vscode and a CMake project generated via CubeMX.I am able to generate and run programs on my STM32F469 (embedded flash), I can write, read and reset the external flash even using the memory mapped mode (verified through the debugger).Now I want to build an external loader based on this project. I copied the files from the STM external loader Github (contrib branch), updated them to match the W25Q128 configuration, and added an executable to my CMakeLists file to compile (and most importantly link) the external loader.My first problem is that the linker complains that there is no "main" function. I searched around for what could be the entry point of

I am using stm32cubeprg-win64-v2-21, and I am experiencing an error.After launching the program and clicking Open File, the Open File window appears briefly, and then the program closes unexpectedly.I uninstalled it and tried using a previous version of STM32CubeProgrammer, but the same issue occurs. Rebooting the laptop does not resolve the problem either.  I have captured a video of the issue and attached it.