STM32CubeProgrammer (MCUs)

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/ExternalLoader/MX25R6435_STM32WBA65-LEGATO.stldr 08:50:10:520 : Error: Flash loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX25R6435_STM32WBA65-LEGATO.stldr cannot be loaded.Here's the StorageInfo:struct StorageInfo __attribute__((section(".Dev_Info"))) const StorageInfo = { "MX25R6435F_Legato", // Device Name + version number SPI_FLASH, // Device Type 0x00000000, // Device Start Address 0x800000, // D

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"/> </FlashSize> </Configuration> </Interface> <!-- Bootloader Interface --> <Interface name="Bootloader">

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_Programmer_CLI -c port=swd -swv freq=400 portnumber=0", it successfully connect

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.I don't know what to try

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 described in the documentationI understand that, as a first step, the correct DTM / firmware binary (.hex or .bin) located in the Utilities folder must be programmed into the STM32WB05N using STM32CubeProgrammer. Howeve

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 en external loader but I can't find anything. So I created a new main function (different from my application) with only an infinite loop (for the record I also made a return 0 main function which l

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.

I am having to program a unit via UART, and every time I open the STM32CubeProgrmmer GUI the interface selector shows J-Link/Flasher.It remembers if I choose ST-Link.If I manually edit the "interface=" entry in config.properties to 2, STM32CubeProgrmmer opens with UART selected.On exit, the "interface=" entry is rewritten to 1.If I select USB as the interface, the "interface=" entry is rewritten to 2, which opens as UART the next time, and then the "interface=" entry is rewritten to 1 on the next exit.

 # External Loader Issue: STM32U5G9ZJT6Q + MX25L12833FZNI-10G (Quad-SPI)## 1. Problem SummaryHello, I'm a novice developer who recently started working with embedded systems. I've been struggling significantly with implementing an external loader for several weeks now...I'm developing an external loader for **MX25L12833F** (16MB Quad-SPI NOR Flash) connected to **STM32U5G9ZJT6Q** via OCTOSPI1, but it continuously fails in STM32CubeProgrammer. The loader compiles successfully and generates a `.stldr` file, but programming operations fail.---## 2. Hardware Configuration### 2.1 MCU: STM32U5G9ZJT6Q (LQFP144)- Cortex-M33, up to 160 MHz- 2.5MB SRAM- OCTOSPI peripheral### 2.2 External Flash: MX25L12833FZNI-10G (Macronix)| Parameter | Value ||-----------|-------|| Capacity | 16MB (128Mbit) || Max Clock | 133 MHz || Page Size | 256 bytes || Sector Size | 4KB || Block Size | 64KB || Operating Voltage | 2.7V - 3.6V |### 2.3 Pin Mapping (OCTOSPI1 Port 1)| Function | STM32 Pin | Flash Pin ||--

Hi all.I tried to upgrade my onboard ST-Link V3 (STM32U5G9j-DK2).I use STM32CubeProgrammer for MAC V2.21.The upgrade process breaks with this message:"ST-Link device lost when exiting upgrade mode"In this situationthe COM-LED red is ON,the COM-LED yellow is BLINKING,the PWR-LED is OFF.How can I reactivate the onboard ST-LINK V3 in this situation?Kind regardsT3-Uwe

CubeProgrammer doesn't work with OpenJFX 11, but OpenJFX 8 cannot handle HiDPI screen, which makes Cube Programmer almost illegible.Since you were able to release several new versions in the past months, could you please also update to Java 11, or fix the HiDPI issues yourself?

Where to start...I have mave made a bootloader (done this before), which is placed in the low end of the flash memory. The application is in the subsequent flash.My board has a USB port and a DIP switch for forcing the BOOT input pin high. When I flip the DIP switch on, and power the board, I can connect STM32CubeProgrammer to the internal DFU bootloader via the USB port. I can also upload my application through the USB port. But when I try to upload my own bootloader, it fails. This is the output from STM32CubeProgrammer:However, if I connect an ST-LINK programmer to the board, I can upload the very same file with no issues. Output from STM32CubeProgrammer:Clearly, something starts to go wrong at "Not flash Memory: No erase done"Just now, I upgraded STM32CubeProgrammer to the latest version (2.21.0), but this made no difference.But why does it work with the ST-LINK programmer, and not through the USB port? And why can I upload the application through the USB port, but not the bootload

While installing the program for my windows 10  it hangs at step 8 which is shortcuts set ups. So I have been reaserching the internet and forums for a while still didn't manage to find a solution

Hi all,I've searched for similar post but solutions provided did not work for my case.For compatibility reasons I needed to upgrade from ST-Link to Cube programmer CLI but I've encountered roadblocks while using the -w commands with the Cube CLI.If I write directly with the CubeProgrammer UI, no issue at all, but if i try using CLI below error pops-up: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=SWD mode=UR -w8 0x08080000 0x02 -v -hardRst-------------------------------------------------------------------STM32CubeProgrammer v2.21.0-------------------------------------------------------------------ST-LINK SN : 54FF6C066685495431141687ST-LINK FW : V2J46S7Board : --Voltage : 2.71VSWD freq : 4000 KHzConnect mode: Under ResetReset mode : Hardware resetDevice ID : 0x482Revision ID : Rev XDevice name : STM32U575/STM32U585Flash size : 1 MBytesDevice type : MCUDevice CPU : Cortex-M33BL Version : 0x92Debug in Low Power mode enable

Hi all,I m trying to enter DFU mode for my SensrTile.box PRO using my USB.the problem is STM32cubeProgrammer  couldn't connect to my board.However, when i try to use another PC it works perfectly.therefore i suspect the problem might be related to  a driver issue on my laptop.Could someone help me resolve this issue?Thank youFor reference, my laptop is an Asus TUF Gaming A15. I'm not sure if this information is relevant, but I thought I'd mention it.

There are STM32 models, where the suffix denotes a dramatic difference in the chip's pinout - either because of the USB-C PD -related variants, or because of SMPS variants. As the suffix is beyond the "lesser" parts of marking such as temperature range, sometimes distributors and vendors neglect/omit it, resulting in non-functioning products and frustration.For these models, CubeProgrammer should display the suffix along with the model number; it even should display something like "no suffix" for the variant without suffix, to be explicitly clear about this.This requirement stems from experiences like in this thread.JW

Hello,I had windows 10 and the CubeProgrammer was without problems.Now, on this PC with new windows 11 when I try to open file (hex, srec) in Erase & Programming  with Browse then a new windows is opening and after I can't choice my file and STM32CubeProgrmmer is closed.I tryed in administrator excecution but the problem is always.I looked this problem on all the windows with open file. Could you help me , please?Best regards  

When I open STM32CubeProgrammer (v2.21.0) it displays an error modal "Old ST-LINK firmware version. Upgrade ST-LINK firmware. If I click the "Firmware Upgrade" button an STLinkUpgrade 3.16.8 shows up with Current firmware: (blank)Type: (blank)Version: UnknownUpdate to Firmware: Unknown.The upgrade button does nothing when clicked. How do I fix this?I downloaded the software here  https://www.st.com/en/development-tools/stsw-link007.htmlAfter running/usr/lib/jvm/java-17-openjdk-amd64/bin/java -jar stsw-link007-v3-17-10/stsw-link007/AllPlatforms/STLinkUpgrade.jarThere is another upgrade dialog with version 3.17.10 displaying the same firmware info as above, with the upgrade button greyed out.Other commands ive run$ ls -l /dev/bus/usb/001/019crw-rw----+ 1 root plugdev 189, 18 Feb 9 09:36 /dev/bus/usb/001/019$ lsusb | grep STBus 001 Device 019: ID 0483:374b STMicroelectronics ST-LINK/V2.1$ STM32_Programmer_CLI -l---------------------------------------------------------------

I've been trying to run code from the external QSPI flash (MT25TL01G) and have gone through an extensive debugging process that ended with a hard lockup. Below is a detailed log of my steps.1. Initial Setup & GoalBoard: STM32H750B-DK (MB1381-H750XB-B01, Product ID DK32H750B$AT1)Tools: STM32CubeIDE, STM32CubeMX (FW_H7 V1.12.1), STM32CubeProgrammer.Goal: Configure and debug an application to run from external QSPI flash at 0x90000000.. Initial Setup & GoalBoard: STM32H750B-DK (MB1381-H750XB-B01, Product ID DK32H750B$AT1)Tools: STM32CubeIDE, STM32CubeMX (FW_H7 V1.12.1), STM32CubeProgrammer.Goal: Configure and debug an application to run from external QSPI flash at 0x90000000.2. Step-by-Step Troubleshooting & ResultsA. CubeMX & Project ConfigurationCreated project via Board Selector (not MCU selector).Verified QUADSPI configured in Memory-Mapped mode (Clock Prescaler=2, CS High Time=2, Flash Size=26).Programming & External LoaderSTM32CubePr