STM32CubeProgrammer (MCUs)

Dear ST Community,Thank you for taking the time to go through this :)I had created the External Loader by following the Tutorial uploaded by STM on Youtube.Link to the Tutorial: https://youtu.be/XqCq0xtQmbII created the External Loader after seeing successful implementation of Sector Erase, Write and Memory mapped Mode in my Cube IDE ProjectCube Programmer (v.2.10.0) returns this when trying to program the Flash with a Binary File:An Interesting thing is that The file does get written till Address 0x900037FF but it fails afterwards as shown here: I have tried using older versions of Cube Programmer ( 2.8.0 and 2.7.0) but still the same result.Any help or direction from your side will go a long way. Thank you so much in advance!Attaching the Cube Programmer Log ( Verbose Level 3 ) in case it helps

Hello,I made a little test project with more than 1Mbytes flash size.No error on compile time, but faild to debug and flash programming with STM32CubeProgramming tool.Binary file size is : 1.6MBCubeProgramming Tool : file size is bigger than the flash memory sizeCubeIde 1.8 :STMicroelectronics ST-LINK GDB server. Version 6.0.0Copyright (c) 2021, STMicroelectronics. All rights reserved.Starting server with the following options:    Persistent Mode      : Disabled    Logging Level       : 1    Listen Port Number     : 61234    Status Refresh Delay    : 15s    Verbose Mode        : Disabled    SWD Debug         : Enabled    InitWhile    &nb

Hi, I've some problem using SMT32CubeProgrammer. i am trying to connect via uart to micro stm32g491 but i receive some error messages. 15:21:34:034 : RTS low 15:21:34:034 : DTR low 15:21:34:171 : Serial Port COM15 is successfully opened. 15:21:34:172 : Port configuration: parity = even, baudrate = 115200, data-bit = 8,           stop-bit = 1.0, flow-control = off 15:21:34:172 : No Init bits value is : 0  15:21:34:172 : Sending init command:  15:21:34:175 : byte 0x7F sent successfully to target 15:21:34:176 : Wait ends after 1 loop, dataready = 1, delay = 0 15:21:34:176 : Received response from target: 0x79 15:21:34:191 : Activating device: OK 15:21:34:192 : Sending GetID command and its XOR: 15:21:34:192 : byte 0x02 sent successfully to target 15:21:34:192 : byte 0xFD sent successfully to target 15:21:34:192 : Wait ends after 1 loop, dataready = 1, delay = 0

I just installed the CubeProgrammer and I'm following the Populate the target and boot the image guide. When I get to section 1.1.1.1.2.6 Populate the SDCard and click "Connect" I get this error: But if I execute this on the command line:sudo /opt/st/stm32cubeprgrammer_2.9.0/bin/STM32_Programmer_CLI -c port=usb1 -w flashlayout_st-image-weston/trusted/FlashLayout_sdcard_stm32mp157c-dk2-trusted.tsvEverything works perfectly fine. I get this: Is anyone familiar with that error on the GUI? If it works on the CLI it should work on the GUI too, isn't it?

I'm using the last 2 sectors in Flash for storing user data, but when I reprogram the firmware via STM32CubeProgrammer (uart) it automatically erases those sectors too.If I download the firmware via CubeIDE (jtag/swd port), the calibration sectors do not get erased.Is there a way to to configure the CubeProgrammer to only erase the first few sectors before programming?

..

..

I currently implement my booloader (bases on the OpenBootloader) and test it against the STM32CubeProgrammer. I use v2.9.0 on Linux. Unfortunately when erasing sectors it does not send the expected command sequences. The behaviour is identical on CLI and GUI.Two examples:I want to erase sectors 15 to 18Command line: ./STM32_Programmer.sh -c port=/dev/ttyUSB1 br=19200 -vb 3 -e 15 16 17 18Output:[...]data sent successfully to target:  0002000f001000110c[...]Sector 18 is missing in the listEven worse, only wanting to erase one single sectorCommand line: ./STM32_Programmer.sh -c port=/dev/ttyUSB1 br=19200 -vb 3 -e 42Output:[...]data sent successfully to target: 0xffff00[...]0xffff is a full chip erase?!Can someone tell me whats going wrong there? Do I miss something?Addendum:These errors only occur when conencted to the Bootloader with UART. With a direct swd connection everything works perfectly

I downloaded and installed STM32CubeProgrammer v2.9.0 on my Linux machine. The STLinkUpgrade.jar is nowhere to be found. I had a friend (also on Linux) download and install STM32CubeProgrammer v2.9.0 on his machine and he had the same problem.

When trying to connect:When trying the same thing on a different PC (works on 3 different PCs, doesn't work on 3 other PCs). with the same IC it connects and programs with no issues.I checked the SW version of Cube programmer, on the 3 PCs that it worked they had versions v2.2.0, v2.6.0 and v2.9.0. The PCs that did not work all had versions v2.9.0.Someone suggested I check what Java version is installed on the PCs. They all have(working and not working):java -versionjava version "1.8.0_321"Java(TM) SE Runtime Environment (build 1.8.0_321-b07)Java HotSpot(TM) 64-Bit Server VM (build 25.321-b07, mixed mode)I also checked what version of Drivers was beeing used all PCs are using the same version:I am not sure what else could be different between the different PCs that could be causing such an error, any help would be appreciated.Thank you Andre Allain

Why doesn't firmware upgrade to ST-LINK not stick?Cube Programmer says it upgrades it successful but it doesn't do it

..

I have been programming with the STM32F411CE and I have now had this happen multiple times to different boards. Basically I program the board a few times and then all the sudden it will no longer connect. I get the following message from cubeIDE, STMicroelectronics ST-LINK GDB server. Version 5.9.1 Copyright (c) 2021, STMicroelectronics. All rights reserved.   Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled   Waiting for debugger connection... Debugger connected ------------------------------------------------------------------- STM32CubeProgrammer v2.8.0 -------------------------------------------------------------------   ST-LINK SN : 2105041B2315303030303032 ST-LINK FW : V2J39S7 Board : -- Voltage : 3.16V SWD freq : 4000 KHz Connect mode: Under Reset Reset mode : Hardware reset Device ID : 0x431 Revis

I'm getting the following error when trying to install the STM32CubeProgrammer by executing: sudo ./SetupSTM32CubeProgrammer-2.9.0.linuxThe error is:./SetupSTM32CubeProgrammer-2.9.0.linux /home/mmalagon/Downloads chdir /home/mmalagon/Downloads/. current dir /home/mmalagon/Downloads Exec error: Permission deniedThe .linux file has the correct permissions:-rwxr-xr-x 1 mmalagon mmalagon 865328 Nov 23 03:07 SetupSTM32CubeProgrammer-2.9.0.linuxSo I don't know what's going on. What am I missing?

I received my stm32h7 nucleo board yesterday. It worked fine with StmCubeProgrammer and uploaded multiple programs on it but from today I can not connect my board to Cube programmer. The error code I am receiving is given below : 00:00:22 : STM32CubeProgrammer API v2.9.0 00:00:22 : ST-LINK error (DEV_CONNECT_ERR) 00:06:14 : ST-LINK SN : 002C00483038511834333935 00:06:14 : ST-LINK FW : V3J9M3 00:06:14 : Board    : NUCLEO-H7A3ZI-Q 00:06:14 : Voltage   : 3.26V 00:06:14 : No STM32 target found! 00:06:14 : ST-LINK SN : 002C00483038511834333935 00:06:14 : ST-LINK FW : V3J9M3 00:06:14 : Board    : NUCLEO-H7A3ZI-Q 00:06:14 : Voltage   : 3.26V 00:06:14 : Error: No STM32 target found!Things I have tried but was unsuccessful:*Reinstalling everything, drivers included.*Using a different windows computer.*Tried hardware button reset then connecting.*T

STM32G474RE flash in single bank configuration is not correctly managed with STMCubeProgrammer if connected to target in DFU USB mode. In that configuration always 256 pages of 2K size are shown. If I connect STM32CubeProgrammer via ST-LINK to the same target then 128 pages of 4K size are correctly shown. Is there any reason? Is it a known bug?

The STM32L152VT6X has 384KBytes of flash memory, but the STM32CubeProgrammer detects the flash size as being 128KB. When I try to flash an image of ~170KB it fails with the error "Operation exceeds memory limits". When I flash the same image with the STLINK Utility it flashes successfully.The first image is from the stlink utility and the second is from STM32CubeProgrammer

Hi,I am investigating usage of STM32CubeProgrammer API package to connect, download executables to connected STM32 MCUs.I was going through example Visual Studio project installed with STM32CubeProgrammer available at "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\api\project\Visual Studio".I was able to successfully compile the MSVS project successfully but while running the application, getting following error. Kindly guide to resolve the error.'STM32CubePrgAPI.exe' (Win32): Loaded 'C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\api\lib\STM32CubePrgAPI.exe'. Symbols loaded. 'STM32CubePrgAPI.exe' (Win32): Loaded 'C:\Windows\SysWOW64\ntdll.dll'. Cannot find or open the PDB file. 'STM32CubePrgAPI.exe' (Win32): Loaded 'C:\Windows\SysWOW64\kernel32.dll'. Cannot find or open the PDB file. 'STM32CubePrgAPI.exe' (Win32): Loaded 'C:\Windows\SysWOW64\KernelBase.dll'. Cannot find or open the PDB file. The thread 0x50c8 has exited with code -1073741701 (0xc

..

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 couldn't find a supported file format.Does this mean that the file formats supported by the H723 are the same as those supported by the Cube Programmer?Please let me know if there is an explanation somewhere in the bibliography.​Or, if the reference materials etc. describe the detailed operation when creating a hex file with Cube Programmer, please let us know.I would like to know how CubeProgrammer specifically

..

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 14:48:44 : Error: Uploading Option Bytes bank: 0 failed 14:48:44 : Error: Initializing the Option Bytes fa

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 location: /opt/STM32/stm32.programmer/bin/core or core.26309 # # An error re