STM32CubeProgrammer (MCUs)

I'd like to restore my Nucleo-u575zi-q to the stock firmware with the alternating green-blue-red LED progression but I can't find the original firmware app. I have the support pack but I can't identify that particular firmware example. Where can I find that, or, how can I retrieve the firmware from an unmolested, new board?  Thanks,tjm

..

The execute() API starts execution of the application but is there an API to halt, stop or pause execution?The STM32CubeProgrammer GUI has a Halt button...How does the GUI use the API to Halt the CPU?

Seems that if STM32CubeProg is installed in a path with diacritic characters it simply won't work.For example, my user path on Windows is C:\Users\JoséSimões. If STM32CubeProg is installed there it simply wont work.Any chance you can improve this? I mean, in this day and age, it doesn't make sense to have a limitation such as this on a modern CLI tool.Thanks!

I'm having a problem with STM32CubeProgrammer and a 1MB STM32F767ZG configured in dual bank mode. On the left, I tried to flash a 520k bin to the device, over the top of previous firmware.Expected behavior: erase sectors 0-7, 12, then write 520K bytes starting at address 0x08000000.Actual behavior: erases sectors 0-8, then write 520K bytes starting at address 0x08000000.Since it tries to erase the non-existent sector 8, sector 12 (the actual sector at 0x08080000) doesn't get erased and as such the contents of sector 12 get corrupted by the multiple writes without an erase.See screenshot below: stm32cubeprogrammer tries to erase sector 8 at 0x0808 0000, but in dual bank mode, there is no sector 8!

I want to start the application after programming it and setting the readout protection. But when the readout protection is set to level 1 this is no longer possible. With level 0 it works as usual.

2.8.0 doesn't handle multiple ST-LINKs correctly. A new instance of CubeProgrammer usually makes the absolute wrong decision to use an ST-LINK already assigned to another CubeProgrammer instance. 2.8.0 seems to have become more unforgiving with issues on the target processor (being held in reset, etc.) and simply crashes.

Hi all, I am new at STM32 world, however I had a 1-2 days long meeting with Bluepill board about two years ago. That time I used succesfully Atollic studio to do my first steps with Bluepill and ST-LINK clone bought on ebay. Now I want to re-start with some led-blinking program. I use the devices successfully used before. The difference is that I have just-installed STM32CubeIde and STSW-LINK004. There is an error I cannot overcome. The programming device is recognised but the connection lost soon. Than I guessed the ST-LINK clone is not supported any more. So I tryed programming part of 32F072BDISCOVERY board. I made a successful version upgrad but the error is the same. However the command line st-flask erase is working. I found same issues but the answer - if was there any - did not help. Please help to solve this phenomena. Istvan ---------------------------------------------------------------------------------------------------------------------------------------------------------

I'm trying to program a STM32G491CEU6 by using BOOT0 and NRST but I'm not able to connect unless I power cycle the MCU while BOOT0 is pulled HIGH. What I'm trying to achieve is:Provide PowerSet BOOT0 pin HIGHPulse the nRST pin LOWProgram MCUWhat is causing the connectivity issue? Is it a matter of timing issue or is it my FLASH_OPTRs not configured correctly unless the MCU is power cycled.Below is my nRST pulse

Hi, I am trying to program stm32 through SPI. I am trying to use C232HM USB 2.0 HI-SPEED TO MPSSE CABLE (C232HM-DDHSL-0 - FTDI (ftdichip.com)). I have connected the microcontroller through SPI1. The SPI connections is as follows with the FTDI cable:SCK: Pin 11MISO: Pin 12MOSI: Pin 13CS: 10When I run the STM32CubeProgrammer software and try to detect it in the software, the software does not detect it. I am not sure if the steps that I am following is correct. I selected USB as an interface in the software if that matters (since I am using USB to SPI converter). Any suggestions?

After Completion of build with STM32CubeIDE in headless build mode,Is there an automated scrit that we can use STM32CubeProgrammer to program the binary to the STM32 board ?.

Hi,I'm trying to upload my code to a STM32L496G-DISCO board using the stm32CubeProgrammer command line interfac, using the following python script: os.chdir(CUBE_PROGRAMMER_CLI_PATH) os.system(f"STM32_Programmer_CLI.exe -c port=swd -w {PATH_TO_ELF_FILE} -v")Unfortunately, I keep getting "Error: Data mismatch found at address 0x90000000 (byte = 0x00 instead of 0x68)"the PATH_TO_ELF_FILE is the path to the elf file generated by the STM32CubeIDE. I've tried both the one in the DEBUG folder and the one in the Release folder.I'll note that when I use the one in the Release folder my project's images don't load and something is clearly wrong, while when using the one in the Debug folder everything seems fine, except for the error.I'll also note that the same thing happens when I try to use the .hex file.This happens when using the graphical interface as well, though not when using the 'run' in the stm32cubeide, so i'm not sure what's the difference.Thank you!

..

Hello! I'm using a nucleo board with STM32F411RE MCU. I can connect to my board in DFU mode and program the flash with an hex file but it seems impossible to write a specific start address (0x08000000) to run the program after it is programmed in flash. That doesn't happen with .bin files where I can set the correct start address. Is there any reason for that strange behaviour?

Hi,i'm a newbie to embedded programming.Sorry in advance If this comes out a little bit confusing, it is because I'm confused and not sure precisely what to ask for.I'm trying to flash the STM32F769I-DISCO through uart pins which connect to the board's gpio ports, and i'm a little bit lost about how to do it. I think I'm not even connected properly.my uart cables (one side usb other side rx,tx,ground) are connected to uart6, meaning gpio pins labeled D0 and D1 (and ground) as specified in the board's documentation.I know that the pins are connected correctly to uart 6, as when I run my software (flashing through touchgfx designer) I can receive and send uart communication.Only I'm not sure if those are the pins to which I should connect the uart in order to flash it to begin with :grinning_face_with_sweat: When I try to connect via the CubeProgrammer I get:Serial Port COM4 is successfully opened.Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit=1.0, flow

I am trying to directly write to some STM32G03 chips.I have an "STM32G030J6M6" and a "STM32G031F6P6" but I am unable to write to them.I can connect to them, using the CubeProgrammer, but only in "Hot plug" mode, and when I try to write anything, like flash or erase, it just disconnects.If I try erasing it, it says "Please verify write protection" but there shouldn't be any, as this is a new chip.If I try and connect to the chip in "Normal" mode, it just gives me an error, saying "DEV_TARGET_CMD_ERR"I have tried holding down the reset pin, but that doesn't help. When I release it, it just gives me the same error.This is the output when I try to connect in normal mode.09:42:02 : ST-LINK SN : 36FF73065648343826450743 09:42:02 : ST-LINK FW : V2J38S7 09:42:02 : Board : -- 09:42:02 : Voltage : 1.50V 09:42:02 : Error: ST-LINK error (DEV_TARGET_CMD_ERR)This is the output for "Hot plug" + erase.09:45:33 : ST-LINK SN : 36FF73065648343826450743 09:45:33 : ST-LINK FW : V2J38S7 09:45:33 : Board : -

When you place the STM32L471 in DFU mode and attempt to connect via UART, the following is displayed in STM32CubeProgrammer:14:39:27 : STM32CubeProgrammer API v2.5.014:39:28 : Serial Port COM9 is successfully opened.14:39:28 : Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off14:39:29 : Timeout error occured while waiting for acknowledgement.14:39:29 : Activating device: OK14:39:29 : Chip ID: 0x415 14:39:29 : BootLoader protocol version: 3.1It clearly sees the chip and communicates with it, but it never enters the connected state. A second attempt to connect indicates that the UART is busy (i.e. a thread is likely hung up in the STM32CubeProgrammer application) and I must exit the app and re-enter to access the COM port again. This is under Windows 10 x64. Everything works fine with other STM32L processors, but not with the L471. This issue has been open for several years and it would be awesome if ST would address it. Thanks!

Hello there,I am working on a project. In the project I want to implement, an external ADC module will collect the data and transfer it to the STM32F103C8. My STM32F103C8 microprocessor will transfer these data to my wireless module. Here I am having trouble with SPI communication. Using SPI1, the STM32F103C8 will be the master, while my other two modules will work as slaves. How can I compile this using single SPI?

I wanted to connect to my STM32 MCU with STM32CubeProgrammer but forgot to power on the board. The programmers (I had 2 boards with 2 STLINK-v3MINIs connected) were detected but when I connected to one, STM32CubeProgrammer crashed. When powered everything worked fine. Something to look into for next version.System:Ubuntu 20.04.1 JRE version: OpenJDK Runtime Environment (9.0_265-b01) (build 1.8.0_265-b01) Java VM: OpenJDK 64-Bit Server VM (25.265-b01 mixed mode linux-amd64 compressed oops) STM32CubeProgrammer v2.8.0 STLINK version: V3J7M2

Hi, I used MT25QL128 flash memory in my project. This product was obsolute then, I decided to use AT12SF128 flash memory instead of MT25QL128 . Now, I use STM32 Cube Programmer and can not write external memory . Program give "memory edition verification error".help please?

I can use STM32CubeProgrammer to read and write code into external memory via ST-Link. However it fails to access the external memory via the bootloader interface(e.g USB).  Does any one know how to fix the issue?Thanks in advance

Hello every one,I have being used STM32CubeIDE to develop a project, and then using STM32Programmer to program the code into internal flash. with more features added, specially more images added, the internal memory is not enough to store the code, so we decide to use QSPI external memory to store the images' code. STM32Programmer is able to program the code into specific memory, either internal flash or external memory with external loader. If my understanding is correct, STM32CubeIDE generates only one executable file including the code stored in internal flash and the code stored in external memory. My question is how to get the separate files, one for internal flash one for external memory? Or is STM32Programmer able to program one file code into corresponding memory according to the code's address?Thanks in advance!

I was unable to run the setup program. I found this gist on how to do an install of STM32CubeMX:https://gist.github.com/Lanchon/2156953d18f7534a926bUsing that method I could run the installer via this method:sudo java -jar SetupSTM32CubeProgrammer-2.8.0.exeThat enabled a nice dialog based install to /usr/local. However afterwards I am unable to run the programmer. It has a similar problem as the installer.davis@twenty:/usr/local/STMicroelectronics/STM32Cube/STM32CubeProgrammer $ ls bin ExternalLoader libcrypto.so libstp11_SAM.so.conf STM32CubeProgrammer STM32_Programmer_CLI STM32WLScripts FlashLoader libcrypto.so.1.0.0 PersoPackages STM32CubeProgrammerLauncher STM32_Programmer.sh version HSM libssl.so platforms STM32MP_KeyGen_CLI STM32TrustedPackageCreator jre libstp11_SAM.so RSSe STM32MP_SigningTool_CLI STM32TrustedPackageCreator_CLI davis@twenty:/usr/local/STMicroelectronics/STM32Cube/STM32CubeProgrammer $ ./bin/STM32CubeProgrammerLauncher ./bin/STM32CubeProgrammerLauncher /usr/lo

Hi amazing forum.. I am wondering if there is a way to save as HEX file the memory read from the stm32 cube programmer.. I am asking this because I want to check that the bootloader that I am creating is exaclty writing what I expect ...Thanks a lot guys

New features • Added the support for the STM32U575/585 microcontrollers • Added the support for SFI via the JTAG interface for the STM32U575/585 microcontrollers • Added the support for SFI via the bootloader interface (USB/UART/I2C/SPI) for the STM32U5 Series • Added the new FUS-Operator support for the STM32WB1xxx microcontrollers • Added the anti-rollback support for the STM32WB1xxx and STM32WB5xxx microcontrollers • Added the support of FUS version display for the STM32WB1xxx and STM32WB5xxx microcontrollers • Added the support for the Live Grid Update feature • Added the support for the Blank check feature • Added the support for the Memory/File and File/File compare features• Added the support for the bootloader version display feature • Added the support for the Fill memory feature • Added the support for UART interface RTS/CTS signals • Added the support for Connect while Watchdog enabled Main issues fixed in STM32CubeProgrammer v2.8.0 64267 Fix issues with FUS via USART boot