STM32CubeProgrammer (MCUs)

Hello All,I have an STM32F407VET6 on a custom board. I am using a "magic word" stored at 0x2001C400 to persist through a system reset and drop into the bootloader.When I do this process while my ST-Link v2 is connected I can unplug the USB cable and plug it back in, open ST Cube Programmer, click on USB, and connect. The USB cable shows up in the device manager as STM32 BOOTLOADER. Everything's good.When I do this same process without the ST-Link being connected the USB shows up in the device manager as Unknown USB device and is not recognized in Cube Programmer.My ST-Link is connected using only PIN1 VAPP, PIN5 TDI tied to PIN6 GND, PIN7 TMS_SWDIO, and PIN9 TCK_SWCLK.What behavior is the ST-Link causing that I can reproduce in code as I switch to DFU through USB, and avoid needing the ST-Link connection?Thank you! 

I designed a custom PCB. It is designed to be used in a remote control car I want to make/to control a BLDC motor and servo wirelessly or through a potentiometer.When I attempt to program the microcontroller (connecting through STLINKV3) it seems to connect fine, and I am able to read the flash and option bytes. When I try to program a file, it fails with error "Error: failed to erase memory", except for one time where two blocks were written (see image) [the data is correct in the first but in the second only the 1 is correct].I have attempted in every combination of software/hardware/core reset in CubeProgrammer, and have read various other community posts, with no success. I'm not quite too sure where to go from here, whether it is a hardware issue or a software configuration issue.I have attached the Altium design files as well.Any suggestions would be appreciated.

So i installed the st-link utility from my.st.com and did all the installation but when i run it, it tells me there are some .dll files missing. Specifically, these are the errors; 1st error; "The code execution cannot proceed because mfc140.dll was not found. Reinstalling the program may fix this problem" and the 2nd error is; "The code execution cannot proceed because MSVCP140.dll was not found. Reinstalling the program may fix this problem." . So i did exactly that, uninstalled the st-link utility and installed it again but still same problem. Does anyone have the same problem and how, if you fixed it, did you do it? 

Bonjour, je n'arrive à me connecter avec mon stm32 st link V2.J'ai réussi à flasher mon module en V2J45S7 STM8/STM32 Debugger.Mais quand je veux me connecter j'ai un message "Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication"Je me dit que je dois de nouveau upgrader le module mais parfois j'ai un message "st-link is not in the dfu mode"J'ai essayé la mise à jour avec STSW-LINK007, cela a fonctionné mais je n'arrive toujours pas à me connecter.Que puis je faire ?Je reste disponible si vous avez des questions.Merci beaucoup--------------------------------------------------------------------------------------------------------------------------------------------------------In English :Hello, I can't connect with my stm32 st link V2.I managed to flash my module in V2J45S7 STM8/STM32 Debugger.But when I try to connect, I get an

Hello All, I am new to the STM32 platform and trying to learn.  I am working with a STM32F070F706 MCU.  I would like to use the MCU internal clock to support my peripherals  (I2C and USB 2.0).  The clock configuration tool cannot resolve the issue itself, so I modified the prescalers on my own and the issue seems (to me) to be gone. However,  if I select. "Resolve Clock Issues", STM32CubeIDE tells me it can't find a solution.  It will generate code for me, but warns me:  "- Main Config: These peripherals still have some not configured or wrong parameter values: [Clock]".  Does anyone see an issue with the clock configuration shown below?  To me, everything seems to be configured satisfactorily. 

I was updating CubeProg on MacOS 14.5 and had a few issues, but first IT WORKED. It let me know that administrative privilege is required (it isn't), but it plowed ahead and worked anyway.Here are the things that I ran into:It does this on 2.16 as well as 2.17, but if there is an update it says that it will install from a local repository (?) and continues successfully.Next:

Hi,I want to install an SFI on my microcontroller (NUCLEO-U575ZI-Q) using the following script:#!/bin/sh# Set to the default installation path of the Cube Programmer tool# If you installed it in another location, please update pathtool_dir=~/STMicroelectronics/STM32Cube/STM32CubeProgrammer/binmy_curr_dir=$(pwd)sfi_bin=$my_curr_dir/../Binary/OEM_Dev.sfirsse_bin=$tool_dir/RSSe/U5/enc_signed_RSSe_sfi_U5_2M.bincd $tool_dirsudo $tool_dir/STM32_Programmer_CLI -c port=SWD mode=HOTPLUG -sfi $sfi_bin hsm=1 slot=1 -rsse $rsse_bincd $my_curr_dir The thing is, when I do it through the interface, I select the HSM license I want to use:

STM32CubeProgrammer version 2.16.0Target STM32G0B0RET6, device ID 0x467, Rev Z, 512KB flash, bootloader 0xD0When loading a large bin file (425kB), the programmer tries to erase 65364 sectors! There's only 256 sectors in target, and the image only needs 212 sectors erased.When using an ST-Link SWD interface it gets past this (albeit erasing entire flash) and programs the flash OK, but when using USB it just locks up.It doesn't happen with smaller files that will fit in bank 1, just larger files that require 2 banks.If I do a full chip erase first, then tick "skip flash erase before prog" then it avoids this problem. However I need to preserve config data at top of flash, so this is not a good workaround.I think it's a similar problem to this post so I replied to that, then thought I sh

I ran system bootloader, I can perform the bootloader process using the STM32CubeProgrammer software via USART. But what I want is to run the bootloader software over TCP or UDP using the USART protocol. Because my UART2 line is connected to a TCP converter.I wrote a piece of code using Python, but it's very slow and disconnects after a while. Is it possible to enable STM32CubeProgrammer to communicate with UART protocol over TCP?Softwareally, I used TCP to Uart converters, but STM32CubeRogrammer is getting a time delay error.My system is as follows;

HelloI'm using STM32429I-EVAL1 and its touchscreen is not working.When I plug st-link cable, originally touchscreen was initialized and displayed menu.But now, it only displays totally white screen and there is no reaction when I touch it.I did Software Reset and Hardware Reset with STM32CubeProgrammer, but is it effect to touchscreen?How can I solve this?

Hello,I have installed STM32CubeProgrammer (version 2.14.0) on a Linux machine. I have connected my NUCLEO-U575ZI-Q microcontroller to the machine, but the CubeProgrammer does not detect it (the machine does). I received this message on the CubeProgrammer:ST-LINK error (DEV_CONNECT_ERR)I tried the same setup on a Windows PC and it worked perfectly (with the same version of CubeProgrammer).What could be the possible solution?Best regards,

I want to write firmware to stm32u575 using cube programmer, but when I do download from the erase & programming section, it fails to write.Of course, I have turned off the "skip flash erase before programming" checkbox.However, if I run the program in automatic mode with the "full chip erase" checkbox checked, it writes successfully.With the L4 and G4 that I have used in the past, I was able to write successfully in both cases, but with the U5, it fails.When I use the U5, I use cube programmer.dll to perform full chip erase before downloading.,Has this behavior changed since the writing of u5 microcontrollers in the specifications?I have confirmed that the option byte is factory default. 

STM32_Programmer_CLI fails to list UARTs unless an STLinkV2 is also connected to a USB port (not even to any target).  If an STLink is connected, the UARTs are then listed!  Disconnect the STLinkV2 and the UARTs fail to list.  So the issue appears to be a bug in 2.16.  Note: I have tried with both -l and -l uartSeparate issue: none of my STLinkV3s enumerate in the STLink Probes list. You can see an MINIE in the UART list below at COM14. I suspect I need to update the driver, but the driver download link on the ST site is currently broken.  <sigh>. C:\Users\david>"C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -l ------------------------------------------------------------------- STM32CubeProgrammer v2.16.0 ------------------------------------------------------------------- ===== DFU Interface ===== No STM3

I executed this command : STM32_Programmer_CLI.exe -c port=SWD sn=xxxxxxxxx232xxxxxxxxxxxx and got the response that gave me details about the device, but not COM Port. Is there any command that gives me the COM Port number to which my device is connected ? I know about the "-l uart" command. any other command than that ? Thanks in advance. 

I am using the cube programmer API in a Qt C++ windows application and hit a problem where there is clash in naming of the disconnect() function. disconnect() is in both qobject.h and CubeProgrammer_API.hI am not a C++ expert, so please tell me if I have something wrong, however my understanding is that I would normally deal with this using namespaces. However I see no namespace defined in CubeProgrammer_API.h.I have worked around this by modifying CubeProgrammer_API.h to include a namespace. eg #ifndef CUBEPROGRAMMER_API_H #define CUBEPROGRAMMER_API_H namespace CubeProgAPI { #ifdef __cplusplus extern "C" { #endif . . . #ifdef __cplusplus } #endif } This allow me to call the functions using the namespace ( eg  CubeProgAPI::disconnect(); ) and it does build without error but my understanding is that is not correct as the CubeProgrammer_API.lib I am

Hi,I have a STM32HSM-V2AE and I tried to follow de "SFI Step-by-step on STM32 boards". In the part of "HSM programming" I connect the STM32HSM-V2AE to the computer with the smart card reader ACS ACR39U-UF but I have the following error:Error: HSM initialization error 0x88000002 What I have to do to continue from this step onwards?Greetings and thanks in advance.

Hello all, I am currently developing on the STM32H563ZI and encountered an issue where, when swapping to Bank 2 to erase/write flash, it simultaneously erases the same address in Bank 1. Here are the steps I followed: Swapped to Bank 2. Used STM Programmer 2.16.0 to flash a bin file to the address 0x8100000. Used STM Programmer 2.16.0 again to flash the same bin file to the address 0x8000000. At this point, the code initially flashed to 0x8100000 was erased. Subsequent tests with writing only a few bytes also resulted in the same situation. Are there any settings I can adjust to avoid this situation? Thank you very much!

If driver porting is successful, reading and writing eMMC from STM32CubeProgrammer should be feasible.I have tested that the read, write eMMC functions are ok and implemented in read, write, MassErase and SectorErase functions of Loader , but from the STM32CubeProgrammer it always fails.Can anyone help me?MCU: STM32H743BIT6eMMC: ISSI IS21ES08G-JQLI

Hey everyone,I was writing a 'How-To' for flashing an STM32F04 while I stumbled upon this phenomeon.After program&verify I read back the device memory and compared it to the file I downloaded.I then get the message 'Warning: difference found at 0x8000000" but the first and only difference that is marked is at 0x8007090 I then tried it with the ST Link Utility Tool and compared the device memory (without programming again, so still the download from the CubeProgrammer) with the result that the files are identical.If I read back the device memory with the CubeProgrammer, save it, download it and compare again they are also identical so it doesn't seem to be a general downloading problem.But for some reason my original .hex file seems to cause issues, but only with the Programmer and not with the Utility Tool. Am I missing some kind of setting here? Or what could be the issue?  Thanks in advance,

Hi,I am conducting tests with the HSM and SFI. I have tried the use case of attempting to install an SFI with an HSM that uses other keys. Obviously, I couldn't do it, but now I cannot connect the microcontroller in "normal" mode. If I connect it in "Hot plug" mode and try to change the RDP, it shows the following message:Enabling RDP when TrustZone is active!If no valid secure code booting and calling non-secure code, it may prevent disabling TrustZone And RDP.And if I click OK, it shows the following message:Your device may be lost FOREVERWhat should I do to fix this error so that I can reconnect the microcontroller to the STM32CubeProgrammer?Best regards,

Hi Everybody, I try to flash my firmware into NUCLEO-STM32F410CBT6,  first, I didn't remove CN2 Jumpers for nucleo ST-link V2. and then, select nucelo board in cube32Programmer after that, click connect button, it work

During the installation of the STM32CubeProgrammer creates some registry keys under:HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\STM32CubeProgrammer 2.16.0\One of them is "UninstallString" with the value:cmd /c start /min cmd /c "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\Uninstaller\unscript.bat" & "C:\Users\elkadmin\AppData\Local\Temp\7zS852D4102\jre\bin\javaw.exe" -jar "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\Uninstaller\uninstaller.jar" -f -xIf I run this command on in a cmd.exe with the same elevated credentials as the installer was started I get the initial uninstall screen as expected

 STMicroelectronics ST-LINK GDB server. Version 7.7.0Copyright (c) 2024, STMicroelectronics. All rights reserved. Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : Enabled Waiting for debugger connection...Debugger connectedWaiting for debugger connection...Debugger connectedWaiting for debugger connection...-------------------------------------------------------------------STM32CubeProgrammer v2.16.0 ------------------------------------------------------------------- &nb

Dear All, I have been trying to burn eMMC by CubeProgrammer.Unfortunately I encounter Error: fsbl1 (0x4):invalid address 0x4400(min=0x80000)This is my layout information in tsv file.#Opt Id Name Type IP Offset Binary- 0x01 fsbl1-boot Binary none 0x0 mfgimages/tf-a-stm32mp15xc-ya151c-512d-t-serialboot.stm32- 0x03 ssbl-boot Binary none 0x0 mfgimages/u-boot-stm32mp15xc-ya151c-512d-t-trusted.stm32P 0x04 fsbl1 Binary mmc1 0x00004400 mfgimages/tf-a-stm32mp15xc-ya151c-512d-t-trusted.stm32P 0x05 fsbl2 Binary mmc1 0x00044400 mfgimages/tf-a-stm32mp15xc-ya151c-512d-t-trusted.stm32PD 0x06 ssbl Binary mmc1 0x00084400 mfgimages/u-boot-stm32mp15xc-ya151c-512d-t-trusted.stm32P 0x21 boot System mmc1 0x00284400 mfgimages/st-image-bootfs-openstlinux-eglfs-myir-ya151c-t.ext4P 0x22 vendorfs FileSystem mmc1 0x04284400 mfgimages/st-image-vendorfs-openstlinux-eglfs-myir-ya151c-t.ext4P 0x23 rootfs FileSystem mmc1 0x05284

I am running into an issue with the latest release of the STM32CubeProgrammer.It seems that, at least for STM32F030 MCUs, it is unable to program option bytes. A similar error has been reported earlier (see this topic).The same error is present when I use STM32CubePorgrammer CLI, version 2.15.If I downgrade to version 2.10, the error goes away and I am able to program option bytes normally.