STM32CubeProgrammer (MCUs)

I am using STM32CubeProgrammer (2.14.0) on Linux/Ubuntu 22.04 with NUCLEO-H563ZI.I do not observe any problem when I use the GUI application but I would like to use the CLI.I do not observe any issue when I write/download a program (elf or bin) to bank 1 (no bank swap) at 0x08000000 (or 0x0C000000). When I write to 0x08100000, I usually experience a problem, like this:Opening and parsing file: firmware.elfFile : firmware.elfSize : 4.28 KBAddress : 0x08100000Erasing memory corresponding to segment 0:Erasing internal memory sector 128Download in Progress:Error: failed to download Segment[0]Error: failed to download the FileI realized if a mass erase (-e all) first, then the problem does not happen, and not happen in subsequent tries. But if I write to bank 1 once, then it fails again. Is there something special writing to bank 1 vs. bank 2 ? What could be the reason ? The device has trust zone enabled but product state is open.

Dear ST Community, I would like to address an issue we have encountered while flashing the program on the STM32L562VETb microcontroller using different versions of the STM32 CubeProgrammer software. Our observations indicate a significant performance difference between STM32Programmer version 2.13.0 and version 2.8.0 when it comes to flashing the bin file of size 248 KB  onto the STM32L5xx. Specifically, version 2.13.0 takes approximately 1.07 minutes, while version 2.8.0 completes the same task in approximately 10 seconds. Are there any known reasons why the newer version of STM32Programmer (2.13.0) might exhibit slower flashing performance compared to the older version (2.8.0)? Could there be specific configurations or settings that need to be adjusted to improve the flashing speed? I have attach the Document and bin file please look into it Thank you for your attention and assistance. Best regards, kavan

Dear ST Community,I would like to address an issue we have encountered while flashing the program on the STM32L562VETb microcontroller using different versions of the STM32 CubeProgrammer software.Our observations indicate a significant performance difference between STM32Programmer version 2.13.0 and version 2.8.0 when it comes to flashing the bin file of size 248 KB  onto the STM32L5xx. Specifically, version 2.13.0 takes approximately 1.07 minutes, while version 2.8.0 completes the same task in approximately 10 seconds.Are there any known reasons why the newer version of STM32Programmer (2.13.0) might exhibit slower flashing performance compared to the older version (2.8.0)? Could there be specific configurations or settings that need to be adjusted to improve the flashing speed?I have attach the Document and bin file please look into itThank you for your attention and assistance.Best regards,kavan

I am attempting to flash a TSV file using a command-line tool under Linux. In the documentation, I have found that the syntax is as follows:STM32_Programmer_CLI -c port=<DEVICE_PORT_LOCATION> -w [<file.tsv>]Additionally, there is information that if the Flashlayout and binaries are not in the same directory, then the path to the Flashlayout files must be precised. So my question is how to pass path to the directory containing binary files?

When starting install as described in documents, the setup icon appears and disappears directly. I tried to open the installer from the command line and then the following error message appears "LSOpenURLsWithRole() failed with error -10810 for the file /Users/joszelf/Downloads/en/SetupSTM32CubeProgrammer-1.1.0.app. "Latest version of Java is installed. MacOS Latest version

I just got the STM32F429I and cannot install STM32CubeProgrammer (STM32CubeProg) on my Mac running Ventura. Any guidance would be appreciated.It is quite sad and I can't return the devie to get a refund.

Hello,I'am use the STM32CubeProgrammer v2.60In the USB programming mode, I cannot load DFU files.Is it possible that this option is added, and a possibility to create DFU files ?Thanks Hans

I can't flash hex/elf file with my compiled program via UART bootloader, using CubeProgrammer CLI.During the download, there occurs an error: "Write address was not acknowledged 0x20000000"and downloading stops.The project I'm flashing has a few RAM sections added in linker script:/* used for thread stacks */.thread_stack :{. = ALIGN(4);. = ABSOLUTE(0x20000000); /* start addres for thread stack area */*(.ThreadStackSection) /* thread stacks section name */. = ALIGN(4);} >DTCMRAM/* used for network buffers */.net_buff :{. = ALIGN(4);. = ABSOLUTE(0x2001D800); /* start addres for Tx/Rx network buffers area */*(.NetworkBufferSection) /* netowrk buffers section name */. = ALIGN(4);} >DTCMRAM/* used for storing network packets (NetXDuo packet pool) */.nx_section 0x24000000 (NOLOAD):{*(.NetXPoolSection)} > RAM_D1/* used for events recording (TraceX) */.trace :{. = ALIGN(4); /* start addres for trace buffer */*(.TraceSection) /* trace buffer section name */. = ALIGN(4);} > RAM

Hi,Since I updated the STM32CubeIDE to v1.8.0 each second flash process fails with Error: Data mismatch found at address. With the STM32CubeIDE v1.6.0 everything works fine.In the project the start address of the flash area is set to 0x08010000 because on 0x08000000 the bootloader is located.STMicroelectronics ST-LINK GDB server. Version 6.0.0 Copyright (c) 2021, STMicroelectronics. All rights reserved.   Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled   Waiting for debugger connection... Debugger connected Waiting for debugger connection... Debugger connected Waiting for debugger connection... ------------------------------------------------------------------- STM32CubeProgrammer v2.9.0-RC01 ------------------------------------------------------------------- ST-LINK SN : 49FF67066584525744110987 ST-LINK FW :

I am trying to flash a custom PCB having STM32H743IIK6 MCU using SWD interface. I have tried below methods but all are Failing. Flashing using 'STM32CubeProgrammer' using all 'Mode' and 'Reset Mode' options FailedFlashing using STM32CubeIDE tried using STLINK SWD and J-Link SWD FailedFlashing using STM32 ST-Link Utility Failed.Below is the Schematic of the programming and power supply section of the MCU.I have assembled 2 different boards and in all 2 boards, Most of times, I am getting 0V on VCAP pins. but sometimes this VCAP voltage fluctuate around 0.7V to 1.1V. 

The EEPROM erase function doesn't seem to work with STM32CubeProgrammer v2.13.0, but works fine with STM32CubeProgrammer v2.11.0. Although v2.13.0 reports that the erase worked, the content of the EEPROM remains unaltered. Furthermore, something else in the flash microcontroller seems to be altered. I tried with multiple PCs, boards, and STLINK-V3MINIE programmers. The issue appears both on GUI and CLI versions.There are 2 obvious differences in the logs below:1) Time difference: v2.11.0 takes around 10s, while v2.13.0 only takes around 1s2) v2.13.0 periodically reports this: "fail @0x00000001"v2.11.0:11:57:53:622 : Flash sector erase ...11:57:53:635 : halt ap 011:57:53:635 : r ap 0 reg 15 PC 0x0000000011:57:53:636 : PC value=0 :11:57:53:636 : Flash erase...11:57:53:636 : halt ap 011:57:53:636 : w ap 0 reg 15 PC (0x20000000)11:57:53:636 : w ap 0 reg 17 MSP (0x20000500)11:57:53:636 : w ap 0 reg 16 xPSR (0x01000000)11:57:53:637 : w ap 0 @0x20000B80 0x00000200 bytes Data 0x00000

I want to see the RAM content of a Running Device. I suspect it might be got corrupted. Also, I don't want to Reset the device. I think connecting the device using Hot Plug mode in STM32Cube Programmer is the solution for this. But I am not able to connect these devices with Hot Plug Mode. Normal Mode is also not working. But I can connect devices using Power Down and Under Reset mode.I am using ST-Link V2 As a hardware debugger.MCU is - STM32L152RCWhat can be the issue?

Dear allUnder windows 11 the 64 bit setup (2.11) startswith extracting the file and after that I see sometimes the busy signal, but... There are no entries in the windows event logger.I know, that windows 11 isn’t mentioned in the release notes (RN0109).Can I start the setup with command line parameters?Thanks in advance,Franz

Hello,I renamed my custom external loader and now STM32CubeProgrammer gives an error each time I launch it. The new external loader is loaded without problems but I keep getting this error. Is there a way to clean the list of expected external loaders of STM32CubeProgrammer?

Hello Everyone,I'm working on the Mikromedia 7 Capacitive board and I'd like to store my fonts and images in my external Flash Memory, the SST26VF064B. I searched in /bin/ExternalLoader and there is no example for this Flash.So I decided to make my own, following this documentation with dev_inf and loader_src files : https://www.st.com/resource/en/user_manual/dm00403500-stm32cubeprogrammer-software-description-stmicroelectronics.pdf#page=25 But, I don't manage to have my .stldr file working. It seems like this : Do you have already an example of an external loader for this SST26VF064B or would you have some advice to make my own. Thanks!

Using ST-link V3.MCU: STM32L031First programming was ok. After disconnecting and reconnect with second device, nothing happen.Using same set of hardware, but changed software to ST-LINK Utility.Result: ok. Automatically programmed the second device.

Has anyone experienced issues trying to run STM32CubeProgrammer on Apple Silicon, and overcome them?I am trying to use it to flash to an STM32F103 micro, but the flashing fails partway through.The issue reproduces using the CLI version of STM32CubeProgrammer, too.Using STM32CubeProgrammer with the same fixture & target on Windows works fine, though.Notably, it looks like STM32CubeProgrammer bundles its own JRE, and is an x86_64 executable - so this whole thing must be running through the x86 emulation layer! I tried opening a tech support ticket with STMicro themselves, asking if a build for Apple Silicone is available or will be any time soon, but they're stuck on asking me about what kind of USB cables I am using ... an abject dead-end there, for sure.

I was trying to modify the option bytes (changing the bit nSWBOOT0) on my STM32G491VC with STLinkV2 (latest firmware).After writing was succesfull, I was no longer able to flash my chip or read the flash content. it tunred out that somehow the read-out protection and write protection got enabled. The level was still showing 0xAA for the read out protection.This has cost me quit a lot of time to disable again, since I did not plan on using the protective features at all.  This happend twice to me already.Please fix this beahviour.

Hello,I followed the STMicro YouTube tutorial for developing an external QSPI loader. I am using the W25Q128 attached to the NUCLEO-H7A3ZI-Q. The flash is working fine with my driver using the test program "main_test.c" provided with the tutorial, and I can access the flash contents at 0x090000000 in memory-mapped mode from the STM32CubeIDE debugger. I compile the external loader with the linker script provided in the tutorial and move the .stldr file into the external loader folder for STMCubeProgrammer. I select my loader from the list of loaders, but when I try to view external flash contents at 0x090000000, I get data read failed. If I try to download data to the external flash from STMCubeProgrammer I get:16:35:41 : Time elapsed during the read operation is: 00:00:00.00916:35:50 : Memory Programming ...16:35:50 : Opening and parsing file: testbinary1M.bin16:35:50 : File : testbinary1M.bin16:35:50 : Size : 1.13 MB16:35:50 : Address : 0x0900000016:35:50 : Erasing memory correspondin

While reading the UM2237 (STM32CubeProgrammer software description - User manual) data, I came up with a question.The FUS/Stack upgrade order is explained in Table of Contents 2.7 Flash the co-processor binary using graphical interface. Do I have to connect via ST-Link to do FUS/Stack upgrade?I tried to do Firmware Upgard using the USB bootloader, but it didn't work.Also, when connected via ST-Link, all the WB Command buttons are activated, but when connected via USB, the WB Command buttons are deactivated.question1. Is it possible to use Firware Upgrade Services using a USB bootloader?2. Can't use WB Commands button when using USB bootloader? Specifically the Start Wireless Stack button

When I try to communicate my STM32L4P5-DK through SPI protocol. I fed the MOSI and SCK pin to the oscilloscope and checked the output there I got several doubts1) when I send a data 0xAA to the slave ( HAl_SPI_Transmit(&hspi2,0xAA,1,10) ) with the baud rate of 187.5kBits/sec the time period was 5us app(each bit is shifted at falling edge as per my configuration) but here MOSI otput is not as expected      2) when I try to send 0xFF the expected MOSI output is the MOSI pin should remain high for 8 falling edges of SCK but it was not that I got on the scope.The below picture shown the 0xFF data in  MOSI(Yellow) and SCK (Green) 3) also the SCK is not a continuous signal, SCK  maintains 0 for each 8 cycles with a regular period of time why? 

 HiI am using STM32WB55RG board and trying to run example code BLE_HID When I connected via ST-Link using the STM32cubeprogrammer tool, the binary I wanted was uploaded well as shown in the picture below, and I checked the Bluetooth operation by executing the BLE_HID code.  However, when connected via USB, as shown in the picture below, the binary I want is not upgraded and the tool is shut down. Occasionally, the binary is uploaded, but in that case, the WB command buttons are disabled, so I can't press Start Wireless Stack, so even when I run the BLE_HID code, it doesn't work well. In the BLE_HID example code, MX_APPE_Init(); When the function is executed, when the static void APPE_SysEvtReadyProcessing(void * pPayload) function in the app_entry.c file is executed, it is divided into Wireless_fw_running or FUS_fw_running.When the binary is upgraded using USE as a soft loader, fus_fw_running is always executed.I want to run it with wireless_fw_running.  &

Installation of all STM32Cube software on Macs is problematic and appears to poorly supported. Suspect that's a market share problem vs. Windows.  But that's a topic for a more thorough discussion elsewhere. (I responded to a recent automated survey with a request to contact me for a full discussion.)In this particular case, I'm installing STM32CubeProgrammer from en.stm32cubeprg-mac-v2-14-0.zip.  No installation guidance (either a Startup doc or README file) packaged in the zip as normally expected.After several failed installation attempts (based on prior experience installing STM32Cube apps, e.g., Running the ,app installer from the CLI or changing file settings using xattr, I did a careful review of Programmer documentation.  So I finally found macOS Installation instructions in paragraph 1.2.3 on page 12 of the UM2237 document (notably nowhere nearby when I was in the middle of the installation process).The normal procedure outlined there failed.  The

I have read a lot of threads on different forums regarding my issue but non of the solutions were able to help me out.I have a STM32F469 Discovery board and I am unable to connect to it. I initially tried building a program on STM32Cube IDE and putting it in debug but was unable to as the error said no target detected. After researching on the issue, I came a across a forum that linked to this page which reasoned out the issue. But this solution also did not help. I have attached an image of the STM32CubeProgrammer alongside to highlight my setting.PS. I noticed that when I set the Reset mode parameter to Software Reset and click Connect. The parameter changes from Software Reset to Hardware Reset. I am not sure why this happens. Could you explain this also to me?Thank you.

Hello, I'm currently working on controlling a board with an integrated STM32WB55VGQ6 chip. While running the BLE test example code on the STM32WB55, I was able to confirm that Bluetooth functionality is working.However, when I tried applying the same code to our custom board, it didn't work as expected.During my research, I came across information that the Arm Cortex-M0+ (CPU2) can't be written to directly by users. As a result, I downloaded the "Patch for STM32CubeWB" for M0+ and obtained BLE-related binaries from the STM32WB_Copro_Wireless_Binaries folder.I'm curious to know which binary is the default one running on the M0+ core of the STM32WB55 board. Furthermore, when I connect my board and access the Firmware Upgrade Services menu in STM32CubeProgrammer, I specified the File path and Start address before pressing the Firmware Upgrade button. I was able to confirm that the Stack Version was successfully uploaded.However, I've noticed that the WB Commands buttons are inac