STM32CubeProgrammer (MCUs)

..

H723ZGT6 Nucleo-144CubeMX 6.3.0CubePro​grammer [ data sheet ]   H723: DS13313 Rev2[Reference manual]   H723: RM0488 Rev2[User Manual] H723: UM2407 Rev 2​I'm currently investigating to implement the update feature.This time I will not use the built-in boot loader.So I can't even use STCubeProgrammer.The CubeProgrammer User's Manual states that the following file formats are supported:[ bin, binary, hex, srec, elf, out,axf ]​Also, I was able to confirm the same with Cube Programmer.​​I checked the H723 reference manual, user guide, and datasheet, but could

..

hi,   I'm trying to run STM32CubeProgrammer_api project, I could build the STM32CubePrgAPI.exe with no error, but I got the 0xc000007B error when I run it; it seems that missing some runtime DLLs, I tried to install vs2015, vs2013, vs2010 runtime, but got the mistake; my environment as blow:os: win7 64bitbuild with VS2017 version 15.6.6 and Windows SDK version 10.0.16299.0;

..

We faced that issue on a couple of diffeent PCs working under Windows 7/10 x64.We experience this for some (not all) STM32H7xx and STM32F7xx MCUs.Trying to connect to system bootloader over USB directly connected to PC we often see something like this: 14:48:19 : STM32CubeProgrammer API v2.8.0 14:48:44 : USB speed  : Full Speed (12MBit/s) 14:48:44 : Manuf. ID  : STMicroelectronics 14:48:44 : Product ID : STM32 BOOTLOADER 14:48:44 : SN     : 00000008FFFF 14:48:44 : FW version : 0x011a 14:48:44 : Device ID  : 0x0449 14:48:44 : UPLOADING OPTION BYTES DATA ... 14:48:44 :  Bank     : 0x00 14:48:44 :  Address    : 0x1fff0000 14:48:44 :  Size     : 44 Bytes&n

Hi: I've installed STM32CubeProgrammer and when connecting to the STLink debug programmer it worked ok. But now, it just crashes. I've tested three different probes, on two different computers.Both computers are running Linux (Arch Linux), kernel version:Linux devmachine 5.15.4-arch1-1 #1 SMP PREEMPT Sun, 21 Nov 2021 21:34:33 +0000 x86_64 GNU/LinuxThe crash report:jar:file:/opt/STM32/stm32.programmer/bin/STM32CubeProgrammerLauncher!/fxml/Config.fxml 72 external Loader list   2.8.0 1.0.0 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fc9464320a3, pid=26309, tid=0x00007fc92825e640 # # JRE version: OpenJDK Runtime Environment (8.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) # Problematic frame: # C [libCubeProgrammer_API.so+0x500a3] connectStLink+0x293 # # Core dump written. Default

Hi, we are using an STM32G05 series processor (STM32G051K6T6).The default setting in the Cube Programmer software sets the option byte nBOOT_SEL to high. This effectively disables the BOOT0 pin and prevents reprogramming if the option byte was not cleared before writing.Is it possible to overwrite this in the firmware, I presume in the linker, so that even if the option byte is written as high we will not be locked out from entering programming mode.Thanks in advance

I'm trying to program firmware of more than 1Mb into an STM32L4R5 that has 2Mbyte flash in dual bank. The STM32FlashProgrammer reports a device with 2Mbytes, but during programming only 1Mbyte is reported, and firmware is not transferred.DBANK bit in OPTR register is set, and I couldn't find any help on documentation and websites.Thank you for any suggestions!

Hai, I am using ST NUCLEO-H7A3ZI-Q board and I am new it. It worked properly for first one or two times. But now I cant flash code into it, it say "unable to connect to the target". Then I tried STM32CubeProgrammer to connect it and ts connected in 'Power down' mode. Then I performed Full chip erase. After that the board worked properly. But the problem arises again when I reconnected the board and I done the full chip erase again. That is I need to run the full chip erase every time I power the board.How can I resolve the problem?Thank you.Sachin

I've been using a STM32U585 Discovery kit for a few days and have succesfully run several programs on it. However today I suddenly got this error in STM32CubeIDE when trying to run a new program:---------------------------------------------------------------------------------------------------------------Error: Data mismatch found at address 0x0800899C (byte = 0x31 instead of 0x33)Error: Download verification failed---------------------------------------------------------------------------------------------------------------Trying to upload different programs gave the same result, but with the mismatch at different addresses.Using STM32CubeProgrammer I can erase the flash completely and then normally upload and run code with CubeIDE once, but after uploading a different program again I will get the same error.I've upgraded the ST Link firmware, no change.I would appre

Hi,I'm able with the following script "myScript.prg" to write a single byte of data:-c port=SWD #Write8(0x08000428,0xAB)This script is then called with the batch:STM32_Programmer_CLI.exe -script myScript.prgBut the problem here is that there's no possibility in this .prg script to parse external files and write in memory the content of this file.Note: with this script the content is written in flash, no matter what the memory content is, same as writing a byte into the STM32CubeProgrammer user interface.When I use this command instead, the write fails:STM32_Programmer_CLI.exe -c port=SWD -w8 0x<address> 0x<value>The error message in the cmd is:Error: Downloading 8-bit data failed... If it's a Flash memory, it may be not erased or protectedTought that the problem might be the 32 bit alignment or not erasing the memory firs

Hello,I want to flash micropython in one of my stm32 devices. In order to flash micropython I need to put the stm32 board in DFU mode connecting the VDD pin to BOOT0.When I do this and I reboot the board, the behaviour of the board changes (the default demo application does not run). Therefore I suppose that it entered to DFU mode, the problem is DFUse program does not list my device in the "Available DFU Devices" section.I have installed the drivers and in the device manager the device is detected as "ST-Link Debugger" I have tried with different STM32 board such as STM32F412 Discovery Kit, STM32F767 Nucleo-144 and STM32F429 Discovery kit.Whats wrong? How can I detect the STM dfu devices using DFUse?Thanks.

BackgroundHardware:STM32L4R9ZGJ6 (1 MB flash)Custom boardSoftware:STM32CubeIDE v1.6.1STM32CubeProgrammer v2.8.0Hello,I have a couple questions.Question 1: What is the difference between the user configuration option bits DB1M and DBANK?According to the STM32L4 reference manual:DB1M: "The dual-bank feature on 1 Mbyte devices is enabled by setting the DB1M option bit"DBANK:"Single-bank mode DBANK=0: read access of 128 bits" "Dual-bank mode DBANK=1: read access of 64 bits"Based on the descriptions in the reference manual and STM32CubeProgrammer, they do the same thing. Having two bits with the same functionality seems unlikely, so there must be a difference.Edit: Looks like someone asked the same question 3 years ago:

Erasing memory corresponding to segment 0:Erasing internal memory sectors [0 64]Download in Progress:Error: failed to down In this case, I am erasing with STM32CubeProgrammer(v2.8.0). When I run it again with STM32CubeIde I get the following message and it works without errors.Erasing memory corresponding to segment 0: Erasing internal memory sectors [0 64] Download in Progress: File download complete After the application exceeds 128Kb, STM32CubeIde cannot erase the chip. But the application can be written to a previously erased chip.Thank you

I have a Mikroe Fusion for STM32 V8, I'm using the external DBG selection using an STLINK V3 plugged into the debug port. I can get Cube Programmer to load code onto my F302VC. When I load up STMicroelectronics ST-LINK GDB server. Version 6.0.0, I get the "No device found on target.". Making sure it was hardware related, i tried a Nucleo-F302r8 and that works. I've tried playing with the different reset behavior, specifying a stlink s/n, nothing seems to help. I assume its a problem with the fusion and the way its connected. Boot0 is grounded through a 10k. The only suspect i have is this MUX that switches between GPIO input and JTAG/SWD/TRACE. I'm still investigating. Hope someone else had this issue and has a solution! Appreciate any advice!

I am facing an issue while connecting my STM32H745 device with STM32CubeProgrammer.I tried various suggestions posted here by different users for similar questions. However, still, I am not able to connect my device with CubeProgrammerBelow are different ways I tried alreadyPlaced Boot pin to High state before power-up. So that STM32 boots from system memory. Also, tried to connect the device with CubeProgrammer by setting "Under Reset" mode in the CubeProgrammerTried with lower clock speed 8000 in the CubeProgrammerLet me know what else I can try to overcome this issue

Hey,today I update CubeIde to 1.8 (with new CubeProgrammer 2.9) and noticed that I can no longer flash my external QUADSPI memory as I used to before in version 1.7. I made custom external loader following this guide : https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/external_QSPI_loader.htmlIs there anything I need to change in my loader ? Or there is new bug present ?I get this console output:  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 LogFile Name : D:\Work\STM32CubeIDE\Projects

I'm trying to create a loader for external flash. I cannot use IAR EWARM and the only examples I find use that. (e.g. https://github.com/STMicroelectronics/stm32-external-loader)I need this to work with GCC from a make file using LD linker scripts.Any idea where I can find examples for this? Any information on making external flash loaders with make/gcc/ld is also appreciated.

STEVAL-FCU001(STM32F401CC) .hex STM32cubeprogrammer programming issues.STEVAL-FCU001(STM32F401CC) .hex STM32cubeprogrammer programming issues:I bought the product "STEVAL-FCU001' (https://www.st.com/en/evaluation-tools/steval-fcu001v1.html) and I am trying to program the .hex code(or bin code?) into "STM32F401CC" via "STM32Cubeprogrammer"_SWD.The first step I did is to extract the original code(.hex) inside the F401CC successfully.After that, I can program the extracted code(.hex) into S

 You mean, "editing" - surely ?

I'm working on a project where we are using the new STM32U575xx series. Now I created a bootloader and wanted to write protect the bootloader section. However I'm not able to disable the write protection using the ST-Link v3 and STM32CubeProgrammer.If I try to unlock the write protection I get the following error:Is there a way to fix this problem? Or do I have to file a bug report in the support section? How long will it take to fix this? I'm kind of stuck now because also the J-Link STM32 Unlock application doesn't support the STM32U575xx yet...

Hi all,i'm tryng to connect to STM32F048T6 by STM32CubeProgrammer.It is a virgin device, and it starts from System memory and i can see the device like STM32 Bootloader.When i'm trying to connect using USB in the STM32CubeProgrammer a pop-up message appears reporting: "Deevice is under Read Out Protection, Do you want to disable it?"I checked the RDP level and is set to AA, so level 0. Do you have some ideas?The voltage level are:VDD = 1.8VVDDA = 1.8V VDDIO = 3.3VI'm using HSI48This is the CubeProgrammer Log 10:14:37 : USB speed : Full Speed (12MBit/s) 10:14:37 : Manuf. ID : STMicroelectronics 10:14:37 : Product ID : STM32 BOOTLOADER 10:14:37 : SN : FFFFFFFEFFFF 10:14:37 : FW version : 0x011a 10:14:37 : Device ID : unknown 10:14:37 : Warning: Device is under Read Out Protection 10:14:37 : Device Read Unprotect requested 10:14:38 : Disabling m

Hii Everyone,I'm writing the STM32 DFU bootloader code for stm32f407VG. I configured USB in FS speed and DFU mode and rest are in default configuration. It is able to communicate with STM32 Cube Programmer and I'm able to read memory also but the problem is it's not sending the Board Id and therefore Target information block is empty. I've attached the log file also.  

I have STM32H753XI-EVAL2 board with CN2(USART1) connected to PC. Switch 1 position is set to 1(Sys Mem). I am getting error when tried to connect using STM32 CubeProgrammer.19:43:22 : RTS low 19:43:22 : DTR low 19:43:22 : Serial Port COM18 is successfully opened. 19:43:22 : Port configuration: parity = even, baudrate = 9600, data-bit = 8,           stop-bit = 1.0, flow-control = off 19:43:24 : Timeout error occured while waiting for acknowledgement. 19:43:24 : Timeout error occured while waiting for acknowledgement. 19:43:24 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again... Did anyone observe the same?