STM32CubeProgrammer (MCUs)

I need to flash a bin file on STM32F105 MCU. To do so, I use a ST-Link V3 SET connected threw ARM20-10 Pin Adapter to Tag-Connect 2050. I send this command to STM32_Programmer_CLI.exe:C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin>STM32_Programmer_CLI.exe -c port=SWD -rdu -w "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\Software_For_Target\program.bin" 0x08000000 -v -hardRstIt workes fine, but the MCU doesn't run after programming. When I send:STM32_Programmer_CLI.exe -c port=SWD -scoreI get "Core is halted".To get the MCU up running, I need to disconnect and reconnect the power supply of the target. Is there any way to avoid that?

when running STM32CubeProgrammer 2.13.0 under macOS 13.2.1 Ventura on Apple M1 the application allocates excessive amounts of Memory. This was observed when running the programmer in automatic mode for several days. The allocation was about 69 GB. MacOS warns with a nagging low memory warning.

I am trying to use the windows version of STM32_Programmer_CLI.exe (version 2.13.0) to write bytes to a flash (windows 10). The command I am using is like./STM32_Programmer_CLI.exe -c port=SWD mode=HOTPLUG -w8 0x08080000 0x00 0x00 0x00 0x00 0x00 0x00 -w8 0x08080C00 0xAA 0x00 0x00 0x00 0x00 0x00 -vand although I use the "mode=hotplug", each time I run this command a restart is triggered. I did expect no restart when using "mode=hotplug". Can I try something else to be sure to avoid a restart/reset?

Platform: Windows 11 22H2 (x64)CubeProgrammer version: 2.13I've got 2 devices:HW Controller which uses dual FTDI drivers (2 COM ports; 1 port connected to ST microcontroller and 1 port connected to ESP32)HW Adapter which uses software virtual COM (ST library) connects with ST microcontroller.Each of the devices are detected perfectly fine in CubeProgrammer 2.6, but are basically undetectable in 2.13 and for other reasons:Controller cannot connect because CubeProgrammer for some strange reason don't shows properly 2 available COM ports (one is correct and the second one is blank; see pictures in attachment). Selecting the blank one and trying to open end with information about invalid port name.Connecting with adapter is impossible because connecting routing seems to stuck at some point after trying to upload option bytes and right before trying to read memory (see logs in attachment for comparison between versions)It looks like 2.13 totally messes up handling serial ports (problems wit

Hello, I am using an STM32F427ZIT6 on a custom board for my project and it was working perfectly until now. I was able to programming it with an ST-Link V2 + ST-Link Utility as expected.I was working on adding DMA to my code but one day my chip stopped working and I was unable to flash code in it. In fact, I could flash data to the chip but it was flashing it in reverse order MSB LSB instead of LSB MSB.I tried updating and changing my ST-Link V2. I also tried using another similar board but I did not encounter the same problem. However, I did had strange behavior when flashing my other board (doesn't boot at start address when after power cycle).Here is the error message from St-Link Utility (Programming error @ 0x08000000!) :Here is the error message from STM32CubeProgrammer (Error: Data mismatch found at address 0x08000000 (byte = 0x8D instead of 0x00)) :Here is the difference between the data flashed in the chip and the data from the binary file I tried to flashed. As you can s

Hi,I'm using STM32CubeProgrammer CLI (2.13.0).I'm trying to write a file to my device using this command :"C:\Program Files (x86)\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -C port=SWD mode=UR -vb 1 -e all -w "%firmware%" 0x08020000 -V -w "%bootloader%" 0x08000000 -VI get this error :Warning: Wrong file path to be downloaded: "g:\.shortcut-targets-by-id\***\yyy" Error: The download command you trying to perform (-w "g:\.shortcut-targets-by-id\***\yyy" "firmwares\***\yyyy\zzz\firmware.hex" 0x08000000) is missing the filePath to be loaded or it has a wrong extension, please note that the supported extension are .bin, .hex, .srec, .s19 .elf, .stm32, .ext2, .ext3, .ext4, .vfat, .ubi, .jffs2, .img and .tsv files.I understand that the CLI parsed the firmware file path, which contains spaces, but I don't understand why as I put double quotes arround the %firmware% variable.Can you help me solving this issue ? Is there a way of forcing not to parse or conver

On windows 10 I have version 2.12.0 installed of the STM32CubeProgrammer, but on command line I have version 2.13.0. In order to update the GUI version to 2.13.0 as well I use the "Help" -> "Software update" button but I see the following: so either there is no version 2.13.0 for the GUI, or something is wrong? How can I find out if there is a new version for the CubeProgrammer (and how to install it) or not?In addition, the sentence "No previous are done" does not make any sense to me. What is the meaning of this sentence?

I am using the GUI version and the command line tool to work with a device, but one of these tools has a bug. Checking which bank is use to boot from I get clearly contradictory results. See screenshot. Which tool tells me the bank used to boot from?CLI: 2.13.0GUI: 2.12.0 (update not possible; that will be yet another bug report...)

I have been trying to read a memory area as follows on windows power shell:.\STM32_Programmer_CLI.exe -c port=SWD -r8 0x08080000 8 -r8 0x08080C00 8but that triggers a reset of the device. I do not want a device reset, I just want to read the memory as specified. How to do that?

On windows 10 I am using STM32_Programmer_CLI.exe (2.13.0) to flash bytes to memory using the following command linebut then I do so I get a very strange output:ST-LINK SN : 53FF71065056705420540981 ST-LINK FW : V2J29S7 Voltage : 3.22V SWD freq : 4000 KHz Connect mode: Hot Plug Reset mode : Software reset Device ID : 0x447 Revision ID : Rev Z Device name : STM32L07x/L08x/L010 Flash size : 128 KBytes Device type : MCU Device CPU : Cortex-M0+ BL Version : 0xB2     Downloading 8-bit data...   ██████████████████████████████████████████████████ 100%   Error: Failed to download data! If it's a Flash memory, it may be not erased or protected   Downloading 8-bit data done successfully   Downloading 8-bit data...   ██████████████████████████████████████████████████ 100% Downloading 8-bit data done successfully   Verifying ... Read progress: ██████████████████████████████████████████████████ 100% Download verified successfullyNow has the flash succeeded or

I am using STM32CubeProgrammer to access Option bytes of stm32g070kbt6. Everything is okay but I don't understand by STM32CubeProgrammer is using 0x40022020 to get option bytes when the documentation says it should be between 0x1FFF 7800 - 0x1FFF 787F.PS C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin> ./STM32_Programmer_CLI -c port=swd -ob displ   -------------------------------------------------------------------   STM32CubeProgrammer v2.12.0   -------------------------------------------------------------------       ST-LINK SN : 31FF74064D4E353830240243   ST-LINK FW : V2J40S7   Board : --   Voltage : 3.24V   SWD freq : 4000 KHz   Connect mode: Normal   Reset mode : Software reset   Device ID : 0x460   Revision ID : Rev B   Device name : STM32G07x/STM32G08x   Flash size : 128 KBytes   Device type : MCU   Device CPU : Cortex-M0+   BL Version : 0xB2   Debug in

Hello,to store my SW build information I defined in the linker file a section with a fixed address. like this: /* placing my build information at a named section: */ .BuildInformationSegment 0x0800F000 : { KEEP(*(.BuildInformationSection)) /* keep my variable even if not referenced */ }This works and creates the section containing the string in the .bin. and .elf.even when I misplace this part and dont sort it according to its address.When I load the .elf into the STM32CubeProgrammer it looks like the .map file (or similar information) is used to generate a different binary which, when flashed leads to an error.Here in the screenshot (some details removed) a difference between the bin. and the .elf is visible. This difference only occurs in STM32CubeProgrammer as the .bin is directly generated from the .elf via arm-none-eabi-objcopy. It occurs on the spot where the section is visible in the .map file: 0x000000000800bf22 STL_TM_RAM_BckUpBuf_MarchCXStep   .BuildInformationSegmen

..

I have attached the log output of the Programmer. Device enters DFU mode correctly and it is being recognised by windows but as soon as a connection attempt is done, the device resets after some time. Any way that I can debug the bootloader code and check what is going wrong?The chip used is : STM32F401CCU6And the binary available on the System memory is attached below which might tell what version it is.Edit:1- Added the chip version2- Attached the hex of the system memory

My Settings : STM32G070 mit BootLoader protocol version: 3.1STM32CubeProgrammer v2.13.0My plan : flash my file via UART(USART2) and my MCU should start automatically after programming is finished. I will reset the nBOOT0 bit in my programm, after my own evaluation.My result :I tried with "Run after programming" in CubeProgrammer and "Go 0x800000" in STM32_Programmer_CLI. In both case, downloading was successfull but MCU could not start. See attached log file : logCP_uart.logStep 1 : nBOOT0 = 0, nBOOT1 = 1, nBOOT_SEL = 1 : this combination by Stm32G070 leads to boot from System memory (Bootloader)Step 2 : I could access boot loader via uart (com16) and start programming.Step 3 : My Transmitter.elf file was downloaded (line 32) and the Verifying was also successfully (line 36).Step 4 : But the RUNNING Program from Address 0x08000000 (line 37 and 38) could not be executed. Error Message : Error: GETID command not acknowledged! (line 44)See attached log file : logCP_CLI.txtLog fi

..

we installed an application binary on NUCLEO-144/F429ZI with UART2 as an external interface and USB-UART for debugger.And the binary code been downloaded via the debugger port using STM32CubeProgramer with the tool option of "STM32CubeProgramer(SWD)" and "USB support(if possible): None"It goes well without readout protection of OB(Option Byte). Also well in serial out on USB-USART.By the way, once Read out protection was set to 'BB' from 'AA', it will not go well. no output on USB-UART.What's my misunderstanding on the Readout protection?

I recently bought an STM32H743IIT6 chip and received the Y version instead of the V version that we always work with in our projects. I'm having some issues with this Y version, especially when trying to read the chip with Cube Programmer. It identifies the chip as the V version, so I'd like to understand if I may have bought a fake chip or if there was a production problem where the chip encapsulation is wrong.

I have the ISSI IS62C1024AL-35TLI and I want to connect via SWD and a PCIe slot extender.But I have not this external loader in the available external loaders list in the STM32CubePorgammer. Could you transfer me the IS62C1024AL-35TLI_STM32xxx.stldr file to copy it in the "/bin/ExternalLoader" directory please ?Thanks

Hello,I am writing a custom bootloader for STM32L4P5RET6 largely based on the "How to Create a Super Simple Bootloader" videos:https://www.youtube.com/watch?v=OkUQ3iMmiYQWhen beginning, I was using CubeIDE 1.9.0 and whatever was the latest FW for the ST-LINK V2 dongle at the time of 1.9.0's release. It compiled without error and I could see the memory regions being filled with the expected content. However, when trying to debug, I received error messages on the theme of "Error: failed to download Segment[0] Error: failed to download the File" for the bootloader, but the debug started.After CubeIDE upgrade to 1.11.2 and also to the current FW for the ST-LINK V2 dongle, the nature of the errors changed and the debug was no longer started.This caused me to rearrange the layout of the flash memory to this:* Bootloader             0x0800 0000 - 0x0800 2FFF, LENGTH =  12 K, 3 pages in bank 1, pages 0 - 

https://community.st.com/s/question/0D50X00009Xkf0MSAR/iwdg-waking-up-stm32-from-sleep-mode?t=1677657345127what is exact command prompt to activate the IWDG_STDBY_FREEZE

Hello ST Community,This is the issue I'm facing when trying to connect to my board. I'm able to use the LINUX GUI to connect to the device and program it. No issues with it. I want to do the same using a script and the CLI doesn't seem to co-operate. My goal is to connect to the board and program my elf file on it. Nothing fancy. Can you help with this?./STM32_Programmer_CLI -c port=/dev/ttyACM0   -------------------------------------------------------------------   STM32CubeProgrammer v2.7.0   -------------------------------------------------------------------       Serial Port /dev/ttyACM0 is successfully opened.   Port configuration: parity = even, baudrate = 115200, data-bit = 8,   stop-bit = 1.0, flow-control = off       Timeout error occured while waiting for acknowledgement.       Timeout error occured while waiting for acknowledgement.   Error: Activating device: KO. Please, verify the boot mode con

I currently program a STM32F303 with the app STMFlashLoader Demo, using a USB-RS232 device. I want to replace that app with CubeProgrammer, but the app is sending an error. I already checked my FW, but it is OK.So, I want to know if you can help me to fix this error without affecting the programming of the device.

Hello,I have NUCLEO-G031K8 and want to change nBOOT0 using STM32CubeProgrammer (v2.12.0) but I'm unable to do so.I get four message boxes from STM32CubeProgrammer:"Warning: Option Byte: nSwap_BANK, does not exist","Warning: Option Byte: DUAL_BANK, does not exist","Warning: option Byte: DUAL_BANK, is not programmable","Option Bytes successfully programmed". Even though the fourth message box says that option bytes were successfully programmed - nBOOT0 value is unchanged.Here's log from STM32CubeProgrammer: 09:41:13 : Option byte command : -ob DUAL_BANK=1 nSWAP_BANK=1 IRHEN=1 nBOOT1=1 nBOOT_SEL=1 RAM_PARITY_CHECK=1 WWDG_SW=1 IWDG_STDBY=1 IWDG_STOP=1 IWDG_SW=1 nRST_SHDW=1 nBOOT0=1 09:41:13 : PROGRAMMING OPTION BYTES AREA ... 09:41:13 : Warning: Option Byte: DUAL_BANK, is not programmable 09:41:13 : Warning: Option Byte: DUAL_BANK, does not exist 09:41:13 : Warning: Option Byte: nSWAP_BANK, does not exist 09:41:13 : Bank : 0x00 09:41:13 : Address : 0x40022020 09:41:13 : Size :