Ask questions on STM32CubeProgrammer and find answers on device detection, connection failure, programming issues, and more.
We are pleased to announce that STM32CubeProgrammer 2.19 is available What is new in 2.19: Support for the STM32WBA6xxx microcontrollers: Internal memory programmingOption byte/OTP programmingRDP regression with passwordSFI support Support for MCE N...
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 "%fir...
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 ...
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?...
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 a...
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...
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 787...
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)) /...
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 ...
