STM32CubeProgrammer (MCUs)

Before you say "Well act-chilly", no, the processor is not level 2 locked. Just level 1.Using STM32CubeProg 1.4.0 on MacOS or Windows 10, STM32F405, serial port.I am bootloading a bunch of processors using their serial ports.If I put the processors into booload mode, fire up STM32CubeProg 1.4.0 on Windows, connect to the processor, I get a message that reads:"Device is under Read Out ProtectionDo you want to disable it?"I say OK and it always says:"Error: Disabling memory Read Protection failed"I get the same result if I run it on a Mac.But if I use that crunchy program called "Demonstrator GUI" / Flash Loader Demonstrator it works as it always has.Here is the level 3 log from STM32CubeProg from Windows 10:11:38:47 : STM32CubeProgrammer API v1.4.011:38:58:298 : Serial Port COM6 is successfully opened.11:38:58:310 : Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off11:38:58:310 : No Init bits value is : 011:38:58:310 : Sending init com

Hi there,First time to this community, glad to see you!I have an weird programming issue when using STM32CubeProgrammer.I use NUCLEO-F302R8, and try to download a blink.elf to the MCU.I can have successful download, and the LED is blinking. However, if I then try another download, it failed by saying "failed to erase memory", below is the log:09:57:07 : Memory Programming ... 09:57:07 : Opening and parsing file: STM32F302R8-Nucleo.elf 09:57:07 : File : STM32F302R8-Nucleo.elf 09:57:07 : Size : 3420 Bytes 09:57:07 : Address : 0x08000000 09:57:07 : Erasing memory corresponding to segment 0: 09:57:07 : Erasing internal memory sectors [0 1] 09:57:07 : Download in Progress: 09:57:07 : File download complete 09:57:07 : Time elapsed during download operation: 00:00:00.247 09:57:07 : Verifying ... 09:57:07 : Read progress: 09:57:07 : Download verified successfully 09:57:16 : Memory Programming ... 09:57:16 : Opening and parsing file: STM32F302R8-Nucleo.elf 09:57:16 : File : STM32F302R8-Nucleo.e

Hi, still have problems with Java (Oracle) versions & getting the S/W to launch (v1.3). If I have 32 bit Java 8 update 201 installed the programs runs fine, so I presume it is a 32 bit app. However, if I install 64 bit Java 8 update 201 (needed for my Eclipse OpenSTM32 as I have the 64 bit version), then the program no longer runs, although the 32 bit Java is still installed . Seen this many times. There seems to be a versioning problem or maybe a setting that I need to adjust?

Hi, I just populated a custom board with STM32F413RGT6 and tried putting FW on it via USB DFU. The Board is recognized as STM32 bootloader, Cube Programmer 1.4 detects a FW 0x011A Bootloader on the chip but complains that the device is not supported. I cannot find any device list in the cube documentation, so I assume all devices should work.I tested on a different PC using DFUSE Demo and there everything works as expected so i would rule out it's a bug in my Hardware. (see screenshots and Logfile) Can someone from ST test & comment on this?

I'd like to read and write OTP memory with STM32CubeProgrammer, but this does not seem to be possible via SWD.Error: STM32AP OTP programming commands are not supported with JTAG/SWD debug interfaceThe subject of OTP programming seems to be missing from the User Manual. Given the potentially destructive nature of the operation, I'd like to ensure I am programming my device properly. I tried using DFU via USB:Error: OTP programming is currently not supported on STM32F & STM32L devicesSo, a complete bust for me. When is this expected to be supported?

Thank you for this program. i will make use of it, if it'll be stable enough.I got it to work for about an hour, and i have a bug to report.Effect - under specific conditions the program become non responsive for a long period of time. (the non-responsiveness is not similar to any non-responsive behavior that i am familiar with under the windows OS)Reproduce - run under windows 10, select flash via UART, (force your device to go to bootloader), select any connection parameters and then connect, select a hex file. THIS BIT IS IMPORTANT --- select Verbosity level 3 on the log panel ---.then try to flash the hex file.The program will start flashing and pretty soon the process will sow down more and more, until the window of the application becomes non responsive. though, the window can be moved but with great and long delay. I also noticed that windows does not turn the window content gray-white and puts up front a message that says that the window is not responsive.This makes me think th

Hello Guys,I am working on the L452RE_NUCLEO board and testing its embedded bootloader. The purpose is to implement flash updating feature, and therefore Flash-loader demonstrator (UM0462) is my test tool.​However I found L452RE_NUCLEO's bootloader cannot work well like other boards, such as stm32f0discovery. The following are some phenomenons I got:it is hard to connect to the bootloader via uart. I have to reset (i.e., power on/off) the board many times, but a successful connection once with Flash-loader demonstrator.After connected by Flash-loader demonstrator, there is no flash information on the screen. Normally I should see the flash information and can read/write the flash, but I can do nothing at all. The image attached is what I got.Please help on this. Thanks a lot!update:I Just found another issue here: https://community.st.com/s/question/0D50X00009XkYERSA3/problems-using-the-internal-bootloader-with-an-stm32f7. However its solution doesn't help. I have downloaded the newer

I found that by using the STM32CubeProg is impossible to erase sectors STM32L475RG, with a number greater than 127. How resolve this problem?

someone have the same problem,I try used answer ."When running administrator mode -> running ok"(https://community.st.com/s/question/0D50X0000A1lSUBSQ2/after-install-office-cubeprogrammer-failsolved)but Unable to solve the problem.CubeProgrammer V​1.3Java 1.8.0_191​windows 7 sp1 32bit

While working with NUCLEO-H743ZI​ board I noticed that if my already burned program use the UART port over the USB (multiplexed with ST-LINK/V2) I can't earse the FLASH using the STM32CubeProgrammer.Earsing the image with IAR IDE and program the FLASH with program that don't use the UART solve the problem and now I can erase the image with STM32Cube Programmer.Is it a known problem that the STM32CubeProgrammer is not working with an active UART port over shared ST-LINK/V2 USB ??

before install office Cube programmer run OKAfter install office, Cube programmer run failmessage is "CubeProgrammer_API or one of its dependencies is missing. Please try reinstalling the program or check your java architecture"see Attached file.I try, reinstall -> sameJave runtime module -> 1.8.0_191Please advice for me

I have the following boards:NUCLEO-L476RGNUCLEO-F466RENUCLEO-F401REI connected them via USB to my docking station of my laptop.I started STM32CubeProgrammer and wich shows that it couldn't find no ST-Link device.I looked into the device manager which showed everything connected.I started the old STM32 ST-Link Utility and it worked.What is going on? Is this a bug?

Hello,after some fiddling, I can run STM32CubeProgrammer and I can see/update/connect to the stlinkv2 on nucleo boards. On the same machine, I can also connect to a STLINKV3 when running STM32CubeProgrammer/windows in a virtual box. However STM32CubeProgrammer/Linux and STLinkUpgrade/Linux can not see the StlinkV3.Do I miss something? Is that known behaviour?

Is there any tool for communicating with STM32F723ZE MCU bootloader from ST?I have tried with cube programmer and flash loader demonstrator.These tools doesn't support this MCU.

I have succesfully installed STM32Cube Programmer v1.0 and v1.21 for OS X on three Macs. One Mac is a 2011. The other two are much newer. On the newer Macs the software detects the ST-LINK but shows the target voltage as .98V. On the old 2011 Mac, the target voltage is shown as 3.3V. I can connect to our PCB and load the Binary via SWD using the 2011 Mac, but I cannot connect to the target when using the newer Macs. After updating from V1.0 to V1.21, The issue is not related to the SW Version.I have tried direct USB ports, powered hubs, etc. Multiple STLINKs, same USB cable.I suspect this has to do with the lower target voltage, but I don't know why it would be lower.....Also don't know how to correct it.Anyone else have this issue ?

Posted on January 26, 2018 at 10:55Hello everyone,I am using STM32 Cube Programmer with STM32L0 device but whenever I try to flash a .bin file more than 50kb, it fails to verify and also does not run. Is it the problem for STM32L0 on STM32 Cube Programmer?

The following defines an Intel hex file that should program Internal memory at 0x08018040 with:0xFFFFFFFF, 0x00001520, 0xFFFFFFFF, 0xFFFFFFFF:020000040801F1:10804000FFFFFFFF20150000FFFFFFFFFFFFFFFF07:00000001FFWhen I use the Cube programmer to load this into the processor I find that the memory at 0x08018050 is set to:0x00DB385E, 0x00000000, 0x73617265, 0x30203A65 in addition to the desired operation

Hey there,I want to use bootlader with uart in my mcu. I just installed STM32 CubeProgrammer. When i try to reach flash memory with ST-LINK there is no problem. I can program it. But i want to reach flash memory with UART. My port is correctMy baudrate is correct And my parity is correct. When i try to Connect it says:Serial Port COM8 is successfully opened. Error: Activating device: KO. Please verify the boot mode configuration and check the serial port configuration. Reset your device then try again.I enable UART2 as asynchronus mode. Is there any spesific configuration in code to solve this problem.Thanks.

Hi, I just can see a flash of CubProgrammer when I double click its short-cut icon. I have re-installed it several times. It always can give me a flash. My OS is windows 10 and JAVA version is JRE 8. The java environment setting is Path: C:\Program Files\Java\jre1.8.0_181JAVA_HME = C:\Program Files\Java\jre1.8.0_181​The returned information of java -version isjava version "1.8.0_181"Java(TM) SE Runtime Environment (build 1.8.0_181-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)​Thank you for your helping.Best Regards,Allen

Posted on March 15, 2018 at 04:20Hi !!!I am new member of STM32 MCU. I'm working  on a custom board based on a STM32F7 MCU for a GUI projects. In my projects, I store a lot of data for GUI such as: Imgae data, Fonts, Audio data in QSPI Flash. My MCU is STM32F769NI and my QSP Flash is MX25L512, that is same of STM32F769I - Discovery. When I use STM32CubeProgramer  to program the demo file supply by CubeMX Driver to my board then every thing is OK. But When I build my external loader then change file extension  from *.out to *.stldr (I am using IAR ) this error is appear. My external loader is follow example in ''C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\ExternalLoader\N25Q256A_STM32L476G-EVAL_Cube''. In my program I use BSP funtion supply by CUBE MX, and I check funtion by funtion same work. I'm stuck in this problem.  Where is my error.  I attack my project in this post.  Can every one help me ? Thank you !!!#stm

Hello,I have used the STM32CubeProgrammer for update the firmware with the bootloader of the ST from USART1. It's works fine but now I have a problem. The MCU is the STM32L471.In my BoardI have several devices connect to peripherals of the MCU, SPI1, I2C1, USART2,USART3, UART5. The problem is with the USART2: The device connect to the USART2 is a Xbee module placed in a socket. The MCU controls the Power of this device with a digital output and a mosfet. This output is low active 0 = the Xbee is powered; 1: the Xbee is Off.When I remove de Xbee module of my board, the bootloader works fine, but when I placed the module in the socket the bootloader secuence does't work and I cant't connect with the MCU in the STM32CubeProgrammer, appear the msg : " Error: Activating device: KO. Please, verify the boot mode configuration and check the seria..."I have tried with start the boot bode with the pin boot 0 and with a Jump Software to the address of Bootloader and both methods works fine w

Recently I've download and installed Flash Loader Demonstrator v 2.8.0 and It turned out it doesn't support STM32H7 microcontrollers. Project I working on requires programming software using UART2 communication port. Flash Loader is able to connect with board but there is any avaible target on Target List. Target list remains blank, hence I cannot do any step forward. I've set pin BOOT = 1. ​ Will be any update to Flash Loader Demonstrator ? Is there any alternative tool to program STM32H7 microkontrolers via USART? Or maybe I'm doing something wrong?Looking forward for your answer.

Posted on September 13, 2017 at 13:25Hi,We are developed a proyect with teh MCU STM32L471. We have downloaded the appliacation Flash Loader V2.9  but don't have the file .STMap for this MCU.We have a questions:- Is there a newer version of the Flash Loader that includes the STM32L471?- Is it possible for the ST community to provide us with the .stmap file for the STM32L471 or how to do it ourselves?Thanks in advanceBest regards#flash-loader #stm32l471

Posted on July 16, 2018 at 16:12Hello,for the H743, the Stm32CubeProgrammer  lists Option-Bytes->User Configuration->IWDG1 as 'Unchecked: Controlled by software' and 'Checked: Controlled by Hardware'. However the meaning is inverted! With IWDG1 unchecked, I can see a Reset every 500 ms even for an empty device.The unexpected resets costed me hours!Please correct a.s.a.p.#stm32cubeprogrammer

Posted on July 12, 2018 at 01:45I'm having trouble getting the STM32CubeProgramer to connect to my STM32H753IIK6 chip using the serial port when going into boot loader mode. I'm using RESET and BOOT pins to get the chip into boot loader mode but the STM32CubeProgramer will not consistently connect. It seems to be very dependent on the timing of releasing RESET and BOOT to clicking connect on the programmer. Here is the error I get in the log window when it doesn't connect:14:36:29 : Serial Port COM8 is successfully opened.14:36:30 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again...This is same error I get I the chip is running and I try the connect but the chip appears to be in boot loader mode when I get this error. Repeated rebooting release of RESET and BOOT, clicking connect eventually results in the STM32CubeProgramer connecting and then I can erase and program the chip w