STM32CubeProgrammer (MCUs)

I'm working on the NUCLEO-G071RB development board, using the IAR-EWARM (8.50.9) tool-chain.I've created a very basic program that only toggles user led (LD4) at 500ms intervals (using a wait loop with NOP instructions).The program doesn't use RAM (however it is initialized by the start-up code from IAR).With the RAM_PARITY_CHECK option bit set, the program runs as expected and the led blinks every 500ms.When i clear the RAM_PARITY_CHECK option bit (using STM32CubeProgrammer) the program doesn't run, and the debug environment of IAR points to address 0xFFFFFFE when i halt the processor.When the RAM_PARITY_CHECK option bit is restored (set) again, the program again executes as expected.What can be the cause of this strange behavior?

I encountered an issue(v2.7.0) like the title and I fixed it just removing the "config.properties" file located in "C:\Users\Administrator\STMicroelectronics\STM32CubeProgrammer\config.properties" path.I attached my "config.properties" file which not working.I think it would be better to have a function to check the path is valid or not before working the "open file" button.

Hi,We are having problems with one of our STM32F767 when we try to write on odd 16 Byte aligned internal flash memory.The screenshot is from after programming a well-known binary (that works on other MCUs) and reading from 0x08000000 address. We see periodically all 0xFFFFFFFF. We cannot change those 0xFFFFFFFF, the STM32CubeProgrammer give us a error popup with: "Memory edition verification failed".It is important to mention that finalizing, the programming of the well-known binary, the STM32CubeProgrammer shows a warning popup with: "Warning: The core is locked up".All "Option bytes" was verified and are equal to other STM32F767 that works correctly.What could be the cause of such behavior?Thank you

..

We use the Virtual COM port of a Nucleo F070RB and often reset the board using STM32_Programmer_CLI -hardRst. Since version 2.5.0, the hard reset seems to break data transmission from the host to the microcontroller. The microcontroller can still transmit data to the host. This happens fairly often but not always, let's say after 15-30% of hard resets.We have not been able to reproduce this issue with an STLinkV3 dongle. Upgrading the firmware of the STLinkV2-1 on the Nucleo did not resolve the issue. Using only softreset (-rst) or hard followed by soft (-hardRst -rst) works around the issue.Tested CLI versions without the problem: 2.3.0, 2.4.0Tested CLI versions with the problem: 2.5.0, 2.6.0, 2.7.0

I was able to run STM32CubeProgrammer on Mac OSX 11.3, but was not able to detect or connect to my STLink V2 Mini. It appears to just not be recognized at all. My STLink V2 Mini worked on another computer running Ubuntu 20.04.Is anyone else able to connect to their STLink from STM32CubeProgrammer on Mac OSX 11.3+?Thanks!

When the installation comes to the 7th step, it does not do anything, it wants me to exit the installation. When I looked at the directory where the program should be installed, there is no exe file.

First it looks like STMCubeProgrammer will be a useful tool for field upgrades - thank-you ST!Is it possible to have a short delay (100ms is enough) between opening the UART and beginning communications? My product has an isolation barrier for safety reasons and the PC side is powered by the handshake lines. This needs a short time to power up.

i use STM32CubeProgrammer.​but i know that STM32CubePorgrammer don't support STM32G070RB.​where can i see information about whether STM32CubeProgrammer supports MCU series.​

https://sips2017.sciencesconf.org/data/STM32CubeIntro_demo.pdf 50page show backup files.it explains that backup folder exists in Src folder in Project folder.but i check backup previous generated files when re-generating.but i can't find backup folder in src folder in project folder.where can i see backup folder.i spend about 1 hour from finding backup folder, but i can't backup folder. also, where can i find stm32cubeprogrammer.pdf like https://sips2017.sciencesconf.org/data/STM32CubeIntro_demo.pdf .I am appreciated that it explains everything wonderfully and perfectly.

Used tools:stm32cubeprogrammerSTLink-v2 (wired pins: 7:swdio, 9: swclk, 1: vcc, 8: gnd), the dev board usb is plugged to supply the chip.tried with all reset combinations, bus clock configs and boot0 config.tried with openocd as well (see console log below)tried with one of my own board (stm32f4x) to check if my tools are still working properly, I can read memory of the chip perfectly.Questions:Do I miss something to make chip debug probe connection working ? I generally never had trouble to connect it to my boards. Anyway this is the first time I work on STM32f0 series.I heard possible fake MCU's sold on some websites (I used banggood, the price were quite low), do you thing it could be the case ?Log of stm32cubeprogrammer:16:12:13 : ST-LINK SN : 55FF6F06498656572853128716:12:13 : ST-LINK FW : V2J37S716:12:13 : Board      : --16:12:13 : Voltage    : 3.28V16:12:13 : Error: ST-LINK error (DEV_TARGET_CMD_ERR)16:12:18 : ST-LINK S

Hi everyone,I'm working on a custom external loader with an OSPI MX66LM1G45G memory and a STM32H7 A3.If I try to use my external loader in CubeProgrammer (in "Memory & file edition" tab) for reading OSPI at 0x90000000 for example, it works fine the first time, I read datas.But if I try to read the OSPI an other time at an other adress, the Init() function fails, despite working the first time.It seems that when my OSPI has been setup once, it can't be reinitialised properly a second time. I have to poweroff my board so that the Init function succeeds, but the Init always fails at the second call.So I investigate with my debug project for the external loader, and if I try to replay the Init function a second time, I can see that the problem occurs when I try to reconfigure the memory in octal mode, precisly at the configuration of the automatic polling mode to wait for write enable. Here's the part involved (in OSPI_NOR_OctalMode()) :sConfig.Match = WRITE_ENABLE_MATCH_VALUE; // 0x02

i use STM32CubeProgrammer.but i know that STM32CubePorgrammer don't support STM32G070RB(NUCLEO-G070RB).​STM32CubeProgrammer's Manual explains "STM32CubeProgrammer supports STM32 32-bit MCUs based on Arm®(a) Cortex®-M processors and STM32 32-bit MPUs based on Arm® Cortex®-A processors"​STM32G070RB is STM 32-bit MCU.why not support STM32G070RB???​where can i see information about whether STM32CubeProgrammer supports MCU series???

I have the ST-Link V2 debugger and have installed the STM32 CubeProgrammer. I am running it on macOS 11.2.3 operating system. The device is recognised perfectly from cube programmer but when I try to do a firmware upgrade and press the proper option in cube programmer nothing happens. I tried to install the STSW-Link007 (https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/stsw-link007.html) because I think that's the issue but the .jar file just won't open. I keep getting this issue:dlopen(/Users/teoprotoulis/Desktop/stsw-link007/AllPlatforms/native/mac_x64/libSTLinkUSBDriver.dylib, 1): Library not loaded: @rpath/libusb-1.0.0.dylib Referenced from: /Users/teoprotoulis/Desktop/stsw-link007/AllPlatforms/native/mac_x64/libSTLinkUSBDriver.dylibAny help would be greatly appreciated !

I use STM32CubeProgrammer, but i can't use STME2CubeProgreammerI try to connect it to board, but error message happen.below error message.07:02:43 : ST-LINK SN : 066DFF383337554E4312365507:02:43 : ST-LINK FW : V2J37M2707:02:43 : Board    : NUCLEO-G070RB07:02:43 : Voltage   : 3.22V07:02:43 : Error: No STM32 target found!i already did frimware upgrrade

HI, ST​Im trying to fw update using MFC Tool, STM32_Programmer_CLI.exe.​first, i checked that the fw download operation was completed using Terminal.so, I makeed the mfc tool in the way the terminal works in the background and checked the fw download works, but it doesn't work well.​this is the output on Debug message(using TRACE()):​[command : STM32_Programmer_CLI.exe -c port=usb1 -d C:\TEST\TEST.bin 0x08000000]​​​   -------------------------------------------------------------------            STM32CubeProgrammer v2.5.0             -------------------------------------------------------------------​​​USB speed  : Full Speed (12MBit/s)Manuf. ID  : STMicroelectronicsProduct ID : STM32 BOOTLOADERSN     : 205530724352FW version : 0x011aDevice ID  : 0x0470Device name : STM32L4Rxxx/S

New features• Added the support for the STM32WB15xx microcontrollers in the STM32WB Series• Added the support for the microcontrollers with 64 Kbytes of Flash memory in the STM32G0 Series• Added HardFault Analyzer support• Added Register viewer supportFixed issues58716 Error when trying to mass erase STM32L0 128K devices from the CLI.61638 DFU error with the STM32F746xx microcontrollers.64229 Impossible to erase sector 128 and upper on STM32L476RG with STM32CubeProgrammer.73928 [STM32CubeProgrammer] [CLI][STM32H7] STM32H745I-DISCO: Unable to read big data from the external Q-SPI Flash memory.78496 STM32F756 DFU Application Example does not work with STM32CubeProgrammer.80586 [STM32CubeProgrammer][STM32L0][CLI] Verification progress bar ends at 24%.85736 Empty area in HEX file is not well detected by STM32CubeProgrammer.85898 Option Byte IRHEN must be deleted from STM32CubeProgrammer.89140 [STM32CubeProgrammer v2.4.0][CLI]: Failure to recover when using the rdu option.90060 [STM32L4] ST

I downloaded and installed STM32CubeProgrammer version 2.7. I connected a device (developed by the company I work for) on board of which the STM32L072KZU is located in DFU mode. I deleted all previously installed drivers and installed the drivers from the folder "C:\ProgramFiles\STMicroelectronics\STM32Cube\STM32CubeProgrammer\Drivers\DFU_Driver\Driver\". The STM32CubeProgrammer software does not find my device. Although it is in the device manager. I previously worked with the DfuSe Demo software (v3.0.6). Also, if you return the drivers from this software, everything works fine on DfuSe Demo software (v3.0.6). I used the libraries from the DfuSe Demo software (v3. 0. 6) to work with the microcontroller in DFU mode, using them in my own software, easily connecting them to a project written in .NET Framework (C#), for this I would like to express a special big thank you to the employees of STMicroelectronics. Since the STSW-STM32080 project has the status of NRND, I would like to use t

STM32L073RZWe are entering the BL via boot0. The STM32Cube Programmer software sees the USB port but when I try to connect, the part resets out of the bootloader.Appreciate any ideas.ThanksRich

Since I am using the version v2.7.0, I get this error after programming both cores after the first time:I can fix this by Disconnecting the STM32H7, and Connected again

Hello,CPU: ST STM32L151VCI do the following process:Starting from a running program I jump into DFU modethen STM32_Programmer_CLI -c port=USB1 -d "newprogram"then STM32_Programmer_CLI -c port=USB1 -s program start, but if I check the two first byte of the flash with J-Flash and I can saw that 2 first bytes are corrupted. AA AA in place of 00 80When I switch off/on the power the board doesn't restart (that is normal).If I don't use '-s' command and simply switch off/on the board program start normallyAttached: left normal program (reloaded after -d); right corrupted program (reloaded after -s)Thank-you for your adviceAlen

The MCU on my STM32F407-DISCO1 board is being misidentified as STM32F215 / 217. I'm pretty sure it is in fact STM32F407VG. What could be causing it?

I have NUCLEO-H743 board. After I load the firmware with this pin configuration, the board began to give an error STLINK (PB4 is NJTRST). Initially, the board was flashed even with this configuration, but after Debugging it stopped. I was advised to use UART, but I found no information on how to do this on boards with H7, only for older boards. Where do I need to connect the pins on the board to make the firmware possible?

I'm trying to utilize the STM32F72x's UART internal system bootloader with the STM32CubeProgrammer application. I am able to connect to the sys bl via uart, view memory, erase flash, but CANNOT program the target. Every time I do I get the following console error spew:12:59:46 : Memory Programming ...   12:59:46 : Opening and parsing file: C:\source_code\experiment_and_test_projects\f7_bl_chatter\Debug\f7_bl_chatter.hex   12:59:46 : File : C:\source_code\experiment_and_test_projects\f7_bl_chatter\Debug\f7_bl_chatter.hex   12:59:46 : Size : 15628 Bytes   12:59:46 : Address : 0x08000000   12:59:46 :   12:59:46 : Erasing memory corresponding to segment 0:   12:59:46 : Not flash Memory : No erase done   12:59:46 : File segment @0x08000000 is not 255-bytes aligned. It will be aligned to @0x07FFFFF8   12:59:46 : Download in Progress:   12:59:46 : Response received from device: NACK   12:59:46 :   12:59:46 : Error: Write address n

Trying to program over ST-LINK instead of DFU. Boot0 and Boot2 are both switched away from the card edge. Here is what I am seeing:letter@steve-T7500:~/work/Starter-Package/stm32mp1-openstlinux-5-4-dunfell-mp1-20-11-12/images/stm32mp1$ STM32_Programmer_CLI -c port=SWD -w flashlayout_st-image-weston/trusted/FlashLayout_sdcard_stm32mp157c-dk2-trusted.tsv     -------------------------------------------------------------------                       STM32CubeProgrammer v2.7.0                      -------------------------------------------------------------------ST-LINK SN : 0668FF303739465043112823ST-LINK FW : V2J32M22Board      : NUCLEO-NONE Voltage    : 3.23VSWD freq