STM32CubeProgrammer (MCUs)

I'm having an issue with STM32CubeProgrammer v2.22.0. I'm making an external loader for the stm32U031R8 (on the nucleo board). My spi flash code works fine in the my actual application program. If I strip my code down (removing Read,Verify, instrumentation, etc) and get it under the 8K of SRAM1, the programmer works. Once my object is into SRAM2 (0x20002000-0x20002FFF) the programmer behaves incorrectly.First off, to make sure I understand whats going on, in the good case:every operation begins withw ap 0 reg 15 PC (0x20000000)w ap 0 reg 17 MSP (0x20000500)w ap 0 reg 16 xPSR (0x01000000)w ap 0 @0x20001CA0 : 0x00000200 bytes, Data 0x00000000...w ap 0 @0x20000000 : 0x00000004 bytes, Data 0x0000BE00...w ap 0 @0x20000004 : 0x0000186C bytes, Data 0xDEC0ADDE...Not sure why 0x20000500 is chosen as the SP, or what those 0x200 bytes written at 0x20001CA0 are, but I see that a bkpt instruction is written at the base of SRAM1 and then my object is written after that, which makes sense.Then I see

HelloAs I am trying to connect the STM32N6570-DK board on the STM32CubeProgrammer, initially the STM32CubeProgrammer recognises my device as in the following picture: When I press Connect on the STM32CubeProgrammer I get awarning: Connection to device 0x486 is lostas in the following picture: and then an error that says Data read failas in the following picture: I am using a MacBook Air M3, 2024, but even on windows (running on a virtual machine) I get the same error on the STM32CubeProgrammer windows version.Is there a way to overcome this issue? What could be the cause? Thank you 

Hello, This is a pretty straightforward bug report. For F767 Devices, when trying to configure dual boot mode over UART, the nDBOOT Option byte doesnt appear for Cubeprogrammer versions greater than v2.14 The typically workflow is1) uncheck nDBANK2) apply3) restart/reconnect4) nDBOOT option byte appears5) uncheck nDBOOT6) apply.This works on all versions of Cubeprogrammer using an STlink - good! But when executing this same sequence using the UART Bootloader on version v2.15 to v2.22, the nDBOOT option bytes never appears after step 3.  This regression is preventing us from using newer versions of CubeProgrammer. Best,Daniel   

Hello,I tried to install STM32CubeProgrammer, but the installer always gets stuck at Step 8. I searched online and found that some people from my country solved the problem by changing the Windows region and language.However, my Windows 11 license only supports a single language, so I cannot change it.Is there any other solution for this issue?Thanks in advance.

STM32C5 unlock RDP2 need OEM key, How to use STM32CubeProgrammer to set the OEM key and RDP0 to RDP2? Please provide me with a correct operation procedure. Thank you.  

I updated the STM3CubeProgrammer to version v2.22.0, and after restarting the app, it started showing a blank page. I was also not able to close the application directly. I had to end the task from the task manager. I uninstalled the latest version and installed v2.20.0, but it is also showing a blank page. Also, in STM32CubeIDE, I am not able to run and debug code. It gets stuck at  "Download in progress". Are both problems related?

I am trying to do multidrop with STM32WL5MOC and STM32U031. I have some issues:[1] When WL5MOC is the only active MCU in the circuit (U0 is not powered on) I cannot connect M4 core using TargetSel=0x04970041 option:I can connect to M0+ core using tagetsel (STM32_Programmer_CLI -c port=swd TargetSel=0x04970041 ap=1 mode=hotplug)If I try the same with ap=0, CLI cannot connect to M4 core and retires with ap=1 and then connects M0+ core againThere is no issue when not using targetsel option and U0 is disconnected. I can connect both WL5 cores with ap=0 and ap=1 options.[2] If I power on U0 and try multidrop, I cannot connect any of the cores of WL5:I can connect U0 with targetsel option(STM32_Programmer_CLI -c port=swd TargetSel=0x04590041 ap=0 mode=hotplug).. At first CLI cannot connect with ap=0 and retries with ap=1 and then connects.Interestginly If I try ap=1 directly, it cannot connect to U0 (STM32_Programmer_CLI -c port=swd TargetSel=0x04590041 ap=0 mode=hotplug)Am I missi

Hi everyone, I am facing an issue with an STM32U5 regarding the entry into STOP3 mode after a production programming cycle using the STM32CubeProgrammer CLI. I use a .cmd script to flash the device. In the script, I use the -c port=swd dLPM mode=UR flags to ensure the first connection during the multi-step programming of several binaries. At the end of the script, I perform a software reset via -c port=swd dLPM -rst. After the script finishes and I unplug the ST-Link, the microcontroller fails to enter STOP3 mode (current consumption remains high, in the mA range). I noticed that if I manually connect with the STM32CubeProgrammer GUI without the "Debug in Low Power Mode" (dLPM) option enabled, perform a software reset, and then disconnect the JTAG/SWD, the device enters STOP3 correctly. It seems that the dLPM flag used during the CLI session is "sticky": it sets the DBG_STOP and DBG_STANDBY bits in the DBGMCU_CR register, and these bits persist even after the programmer is physically d

I was trying to implement emulated EEPROM and I think I set the EEPROM page area right into the critical option bytes area. Notably, this didn't happen until I added the actual eeprom_emul.c and flash_interface.c files into the cmake configuration, compiled and flashed the program once. This obviously makes a call to "HAL_FLASH_UNLOCK()" so I think it's pretty messed up. Either way, after this, I could not flash the chip beyond 0x80000050, additionally, it would instantly lock up on boot. I believe my Option Bytes were also grenaded.  PCROP_RDP turned itself on, ESE turned itself on and the rest I am unsure of changes. Either way, I managed to turn off RCROP_RDP by setting RDP to 1 and then to 0. After this, flashing the chip, fills every line with the same repeating nonsense bytes. So I think write protection is disabled, but it's still uploading nonsesen. Notably, trying to hit "full chip erase" does not work, and just hangs. Now ESE remains checked. When trying to uncheck

Hello Team,Refering to this Thread : https://community.st.com/t5/stm32-mcus-products/updating-firmware-through-usb-dfu-with-readout-protection-level/m-p/838635We want to achieve same , Can I upgrade the firmware using USB DFU, with RDP set to level 1? We are fine setting RDP1 -> RDP0 and Erase Flash, then Flash the Firmware.I tried with Cubeprogrammers and CLI , but unroftunately USB1 ( STM32 Bootloader in PC device manager ) not showing and connection does not happen. Tried making BOOT0 pin high when Reset.However , Actual plan is jump to system bootloader from User code through jump address. Regards,@STOne-32 @j_filipe 

Hello,I am working on using NRST pin in stm32g031j6m6 as GPIO, but it fails every time. I've changed many option bytes and even options present only on stm32g0x1 have workwd on my chip, except of NRST_MODE. If i want to change this option to 2 (gpio mode) and try to apply, the progress bar stays at 0% endlessly until i quit the STM32CubeProgrammer. I didn't have any problems with communication between nucleo and stm32g031. I tried to program my chip with st links built in nucleo u031 and f303, everytime without success. What else can i try? 

Hello every people. I am new member. We have issue . We have one computer ( PC ) , it is working normaly, but when we setup for other devices , SMT32cube programmer not working.  Plz caution  , one PC working normaly, we received from custommer. New device although we setting , they are not working.They show error :Error unable to read device id from rom tableError ST-LINK error DEV_CONNECT_ERRPlz help us.Thank very much Tra cứuDịchCài đặtĐang tìm kiếm ...  

Hello,I'm working with the STM32H7S7L8 -DK and I need for final product to program the external OCTOSPI flash via usb DFU.So using V2.20.0 Cube programmer i'm able to use external memory loader to read and program the flash using SWDBut using the USB i see the DFU  and before i select the good external memory laoder but when i click to connect i can only programm the internal flash of the STM32 when i try to read or program the OCTOSPI flash i have error.Do you have any ideasThanks 

Basically continuation of https://community.st.com/t5/stm32cubeprogrammer-mcus/stm32cubeprogrammer-upload-fail-after-update-to-2-20/td-p/825113 - after fixing the hex to correctly span both the banks, upload error (using ST-Link) still persists. Firmware can be uploaded using USB bootloader, just the ST-LINK upload fails. It seems that this is a bug of the STM32CubeProgrammer.STM32CubeProgrammer v2.20.0.I attach the firmware hex. I also attach log from the programmer.@PKola.1 @STOne-32 @Maryem  

I bought an ST-link V2 from amazon, this error occured, fearing it may be counterfeit, I then bought another St-link v2 from STM website itself so there is no way it is fake, but the same error still occured. I am on Mac M3 using Cubeprogrammer. There is utterly no documentation on this error. What do i do.

I am using CubeCLT v1.18.0 on an Ubuntu host. I recently got a new J-Trace and ran into warnings about the firmware version not being recognized. I traced the root of the problem being the version of `libjlinkarm.so.7` that ships with this version of CubeCLT.  I need to upgrade to a newer version of the library to resolve the warning. I am already using J-Link v8.48 elsewhere, so I plan to follow this guidance from SEGGER to upgrade the so file. Should it be safe to do this upgrade from v7 to v8? I also noticed that SEGGER release v9.20 of J-Link and was considering going to that. I assume that would include a v9 so. Would that be safe to go to as well? I have a logistical question regarding how ST manages the shipped version of libjlinkarm. It looks like CubeProgrammer specifically expects `libjlinkarm.so.7`. Is there a particular reason for expecting that fixed version name? For me, it would be preferable to expected `libjlinkarm.so` so that I could symlink i

After evaluating/flashing the SBSFU examples on the NUCLEO-G071RB evalboard it's not possible to erase full flash anymore. I get the error below. How to set factory defaults that erasing is possible again?STM32_Programmer_CLI.exe -c port=SWD -e all   -------------------------------------------------------------------            STM32CubeProgrammer v2.12.0   -------------------------------------------------------------------ST-LINK SN : xxxxxxxxxxxxxxxxxxxxxxxST-LINK FW : V2J40M27Board    : NUCLEO-G071RBVoltage   : 3.21VSWD freq  : 4000 KHzConnect mode: NormalReset mode : Software resetDevice ID  : 0x460Revision ID : Rev BDevice name : STM32G07x/STM32G08xFlash size : 128 KBytesDevice type : MCUDevice CPU : Cortex-M0+BL Version : 0xB2Debug in Low Power mode enabledMass erase ...Error: Mass erase operation failed.Ple

When using a STM32H757, with external QSPI, on an STM32H757I-EVAL, I am experiencing some programming issues when programming an .elf file with sections pointing to external QSPI. I am using the ST External Loader for MT25TL01G_STM32H747I-EVAL. Programming does work successfully, but on newer versions of cube programmer, there are warnings about 32 byte alignment, and then verification fails. The addresses mentioned are in AXI SRAM, and are .bss sections, which are marked NOLOAD, so it's confusing why that memory is trying to be programmed and this error is coming up in the first place. Manually setting the ALIGN markers in the linker file to be 32 instead of 4 does seem to get rid of the warning, and fix the issue. I've seen this issue on with versions 2.19 and 2.21 Is this a known issue? I haven't seen this issue with 2.17. Attached are logs files with the warnings and errors. Thanks for the help!

Hi ST Community,I try to write the OTP Memory on NUCLEO-H563ZI Board with STM_Programmer_CLI (Debian Linux).With STM32CubeProgrammer GUI application I can access OTP memory (beginning 0x08FF_F000).When I try to access the otp memory via CLI:./STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -otp displI receive:Error: OTP programming commands are not supported with STLINK interfaces for this device. With lsusb I can see my STLINK-V3:Bus 001 Device 011: ID 0483:xxxx STMicroelectronics STLINK-V3 But also with the command (port=usb1 or usb0):./STM32_Programmer_CLI -c port=usb1 mode=HOTPLUG -otp displI receive:Error: Target device not found.Establishing connection with the device failed. Do you have any ideas/hints what I am mistaking here?Thanks in advance!

Hello,I am working with a custom PCB using STM32H745XI6 (dual core CM7 + CM4).I wanted to boot only the CM4 core.So, in STM32CubeProgrammer --> Option Bytes --> User Configuration:I unchecked BCM7 (CM7 boot disabled)BCM4 remained enabledI clicked ApplyThe operation completed successfullyNo mass erase warningNo security warningNo RDP Level 2 warningRDP was never changed manually.Problem After ApplyingAfter applying the option bytes, I can no longer connect via ST-LINK.STM32CubeProgrammer shows:Error: Unable to read device id from ROM tableError: ST-LINK error (DEV_CONNECT_ERR)Error: Cannot identify the deviceEven in:Under Reset modeHardware reset modeHot Plug mode50 kHz SWD frequencyConnection always fails.What I Have Already TriedConnect under reset (holding NRST manually)BOOT0 high and lowVery low SWD frequency (50 kHz)Hot Plug modeHardware reset modeDifferent USB cableST-LINK V3SET firmware is detected correctlyI also even tried with J-link  Target voltage is ~3.2Vacc

Hello!I've was following this tutorial on Jtag locking for stm32h573RI using j-link. link to tutorial: How to enable RDP-like product state flash protect... - STMicroelectronics CommunityI made it to the updating the product state to 17 and was in the process of reconnecting under hot plug mode, however I didn't have success reconnecting. I get these 4 errors: To Note: I was able to flash initially with no issues. I've been trying to update the jlink version on the stm32cubeprogrammer and have had no luckI have updated my jlink version locally to 9.18vThank you for the any suggestions :D

Hello,What is the correct layout for the .tsv file for the STM32N6 with application?In this tutorial the FlashLayout.tsv is shown, however it only has the FSBL program in it. I cannot figure out what Id to use for the Appli (also Appli non secure), i tried 0x05 but i get error:Error: unable to get the associate alternate setting of partition ID: 0x 5 Error: please make sure that your alternate settings have string descriptors with the right format Error: unable to switch to partition with index: 0x05This document describes the Id's but i don't think that any of them apply, and the document is for the MPU's anyway.Thanks!

I have been running into an issue with the cubeprogrammer very recently where I am unable to connect to my MCU anymore. I get the following log: using v2.2212:41:28 : STM32CubeProgrammer API v2.22.0 | Windows-64Bits12:43:17 : UR connection mode is defined with the HWrst reset mode12:43:17 : ST-LINK SN : 34FF6A0630514B384036244312:43:17 : ST-LINK FW : V2J47S712:43:17 : Board : --12:43:17 : Voltage : 3.56V12:43:17 : SWD freq : 4000 KHz12:43:17 : Connect mode: Normal12:43:17 : Reset mode : Hardware reset12:43:17 : Device ID : 0x45012:43:17 : Revision ID : Rev V12:43:17 : Error: Database: There's no active configuration for this device. All the 8 configurations are disabled!12:43:17 : Debug in Low Power mode is not supported for this device.12:43:18 : UPLOADING OPTION BYTES DATA ...12:43:18 : Bank : 0x0012:43:18 : Address : 0x5200201c12:43:18 : Size : 308 Bytes12:43:18 : Error: Uploading Option Bytes bank: 0 failed12:43:18 : Error: Initializing the Option Bytes failed12:43:18 : Error: Unab

On Kubuntu 24.04 when double clicking onSetupSTM32CubeProgrammer-2.19.0.linuxan empty window appears and then closes again. If I runSetupSTM32CubeProgrammer-2.19.0.linuxvia the terminal (as admin or as user), I get this error:Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at sun.awt.X11FontManager.getFileNameFromPlatformName(X11FontManager.java:174) at sun.font.SunFontManager.initCompositeFonts(SunFontManager.java:3506) at sun.font.SunFontManager.access$800(SunFontManager.java:65) at sun.font.SunFontManager$2.run(SunFontManager.java:555) at java.security.AccessController.doPrivileged(Native Method) at sun.font.SunFontManager.<init>(SunFontManager.java:386) at sun.awt.FcFontManager.<init>(FcFontManager.java:35) at sun.awt.X11FontManager.<init>(X11FontManager.java:57) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62

Hi,I just noticed that CubeProgrammer v1.21.0 always shows me an update notification, but it is already the latest.Restarting the Cubeprogrammer or the operating system does not make any difference. Environment:- Windows 11- I have installed v1.21.0 alongside v1.20, but that should not make any difference, or would it?