STM32CubeProgrammer (MCUs)

Hello,I'm learning STM32 and wrote an quadspi external loader for my NUCLEO -144 (STM32743ZI) and 1M external flash. I've it tested in the Cube IDE and everything looks OK, I can read and write the external flash. When I use the loader in STM32CudeProgrammer I managed to read , but not erase and write accordingly.  Any help will be appreciated. Please find attachments.Thanks

When I use STM32Programmer IDE I can erase external flash sector by sector.When I use STM32_Programmer_CLI.exe I cannot erase the external flash.Board info:I get following error from STM32_Programmer_CLI.exe:STM32_Programmer_CLI.exe -c port=swd -e all -el C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\ExternalLoader\N25Q128A_STM32L476G-DISCO.stldr ------------------------------------------------------------------- STM32CubeProgrammer v2.15.0 ------------------------------------------------------------------- ST-LINK SN : 0671FF565588494867121539 ST-LINK FW : V2J43M28 Board : 32F746GDISCOVERY Voltage : 3.22V SWD freq : 4000 KHz Connect mode: Normal Reset mode : Software reset Device ID : 0x449 Revision ID : Rev Z Device name : STM32F74x/STM32F75x Flash size : 1 MBytes Device type : MCU Device CPU : Cortex-M7 BL Version : 0x90 Debug in Low Power mode enabled Mass erase ... Error: Mass erase operation failed. Please verify flash protectionSince the erase fail

We have implemented a custom tool, which transfers a hex firmware file via USB DFU protocol to the control. While testing we had several problems sending the firmware to the control.First we extract the memory model out of the descriptor infromations of the DFU device. Then we erase all eraseable memory blocks and afterwards we write the firmware information to the specific addresses.Afterwards we use the CubeProgrammer to read out the whole memory information. Then we upload the Firmeware via the CubeProgrammer and also read out the whole memory information. We could find out that the hex file which we are sending consists of 3 different Memory parts which we send differently to the control. But the CubeProgrammer seems to merge the first to blocks and send them as one memory block sequential to the usb device. We also found out that the end of the first block is 4 bytes earlier than the start of the second block and that the CubeProgramme fills this "empty block" with FF bytes.So aft

helloI used ST link to connect to stm32H743 and reported an error during the Programmer download process:"Error:ST-LINK error(DEV_TARGET_CMD_ERR)“.But,I used j-link to connect to stm32H743 and there were no errors during the stm32IDE download process.Can you provide some suggestions,thanks

Hi,    I am using ST-LINK/V2 to flash my boards. My issue is that when I tried to flash the boards using OpenOCD, I am getting the error "No device matches the serial string". So I checked ST-Link/V2 serial number using STM32CubeProgrammer, it showed me a 12 byte value. If I used that serial number I am getting the same error. OpenOCD version: Open On-Chip Debugger 0.10.0STM32CubeProgrammer Version: 2.14.0ST-LINK/V2 Firmware: V2J42S7 I also found a work around for this issue by replacing the serial number byte1, byte5 and byte11 with 3F values. I tried with multiple ST-Links and this work around is working. Serial Number from STM32CubeProgrammerbyte 0byte 1byte 2byte 3byte 4byte 5byte 6byte 7byte 8byte 9byte 10byte 1149FF6866684565731361387The Red Highlighted bytes need to be changed to 3FFixed Serial Numberbyte 0byte 1byte 2byte 3byte 4byte 5byte 6byte 7byte 8byte 9byte 10byte 11493F686663F56573136133F

Hi Team,I am using stm32g0x mcu to store the default chunk of data in to internal specific location for our data storage. Once it reboot it should read the default data.I tried with different mcu calls which will not synchronize with our platform.Please share some examples based on our platform Regards,Kumar 

Hello,The latest STM32CubeProgrammer (V 2.15.0) appears to be unable to program an STM32L471 microcontroller.It communicates successfully but fails with error:    Error: Operation exceeds memory limits    Error: failed to erase memoryThe hex file memory size is 781.64 KB, the micro's flash size is 1 MB.This file programs without issue with an older version of STM32CubeProgrammer (v 2.4.0).   

Hi, I have been recently trying to leave my shallow nucleo side of the pool behind and swim towards the deeper end of the pool. But I feel like I'm drowning a bit and could use a lifeline... (:I have so far managed to connect to and write to, a small 32-pin lqfp G0B1 mcu. But when trying to move to something more robust everything breaks down... Iv plugged in every power supply pin (but VREF, VBAT, and the SMPS ones) to a simple breadboard power line with an average of a 4.7uf capacitor between each pair of VDD and VSS lines as close as possible, by the book.to the STlink, I connected SWD clock+io, and reset.So, the first problem I butted heads with, was that my power miser computer wont supply enough current in each USB port so whenever I connected the power (from stlink to the mcu) it would just turn off the stlink.... I got around it by just connecting a different 3.3v line and it worked, the stlink powered on and connected with the board (this wasn't happening with the sm

I'm using the board SPIN3202. When but I can't flash. When acces to stlink info it displaysFound 1 stlink programmers version:  V2J39S27 serial:   0670FF545551677867033851 flash:   0 (pagesize: 0) sram:    0 chipid:   0x0000 descr:   unknown deviceAnd when I wan't to connect to the boardst-flash read dummy.bin 0 0xFFFFst-flash 1.7.02022-11-30T13:48:06 ERROR common.c: Can not connect to target. Please use 'connect under reset' and try againFailed to connect to targetSo I tried to connect to it using connect under reset it displaysst-flash --connect-under-resetinvalid command linecommand line:  ./st-flash [--debug] [--reset] [--connect-under-reset] [--hot-plug] [--opt] [--serial <serial>] [--format <format>] [--flash=<fsize>] [--freq=<KHz>] [--area=<area>] {read|write} [path] [addr] [size]command line:  ./st-flash [--deb

Hello,STM32 target : STM32H755Is it possible to see the content of BACKUPSRAM with STMCubeProgrammer?I created a project storing data at 0x38800000. The data is stored.but STMCubeProgrammer doesn't show the values stored. Regards,  

I've noticed what seems to be a bug when writing to flash with the '-w32' flag using STM32_Programmer_CLI. My order of operations is:I erase sector 0 of the flashI read the first 8 words of Flash and verified that it's erased.I write some words to flash with the command:stm32_programmer_cli -c port=SWD mode=NORMAL reset=HWrst -q -w32 0x08000000 0x00000001 0x00000002 0x00000003 0x00000004 0x00000005This write fails with the message:Error: Failed to download data! If it's a Flash memory, it may be not erased or protectedI read the first eight words of flash and it has this value:0x08000000 : 00000001 00000002 00000003 FFFFFFFF0x08000010 : FFFFFFFF FFFFFFFF 00000000 00000000So it writes the first three words correctly, skips three words, then fills from 0x0800_000C - 0x0800EC7C with zeros. Certainly not what I expected/hoped!I've attached a file showing all of the commands and the output. For reference, I'm using the STM32WLE5JC and version 2.15 of STM32CubeProgrammer.Next, I'll try the -

Hi,I am creating an application for a device built using a STM32L4R9ZIT6 board. However, it will not be recognised in DFU mode (or at all) unless the host machine which it is connected to by USB has STM32CubeProgrammer installed. I attempted to delete STM32CubeProgrammer but may not have done so thoroughly because it still works on my machine, and not others which have never had it.Is anyone aware of what drivers are installed with STM32CubeProgrammer, or what I could do differently?Thanks

I have a Nucleo board with a new MCU, base board is the Nucleo-G070RB. Now it is a ST link with a STM32G0BORE. I have a problem with the internal bootloader where i cannot upload a new program via USB DFU. There is no hardware problem because VCP works just fine. No data corruption of something. I have tried .HEX .BIN and .ELF all have the same problem. This is the error log is have:18:04:57 : UR connection mode is defined with the HWrst reset mode 18:04:57 : USB speed  : Full Speed (12MBit/s) 18:04:57 : Manuf. ID  : STMicroelectronics 18:04:57 : Product ID : DFU in FS Mode 18:04:57 : SN     : 204E315A4630 18:04:57 : DFU protocol: 1.1 18:04:57 : Board    : -- 18:04:57 : Device ID  : 0x0467 18:04:57 : UPLOADING OPTION BYTES DATA ... 18:04:57 :  Bank     : 0x00 18:04:57 :  Address    : 0x1fff7800

Hi,I am working on Flash swap Banking.From STM32CubeProgrammer I wanted to change the SECWM1_End value and start address of Bank2 from 0x8100000 to 0x8040000 but it is giving me error.  Is there any possible way to change this configuration? And change the Bank2 swap address?Thanks. 

Using STM32_Programmer_CLI.exe (v2.13.0, on Win10) I try to connect via ST-Link / SWD, It works perfectly in the GUI but if I trySTM32_Programmer_CLI --connect port=SWD ap=1nothing happens, not even an error, it just terminates. I can even write nonsense after the --connect - no response. --list works fine:-------------------------------------------------------------------STM32CubeProgrammer v2.13.0-------------------------------------------------------------------===== DFU Interface =====No STM32 device in DFU mode connected===== STLink Interface =====-------- Connected ST-LINK Probes List --------ST-Link Probe 0 :ST-LINK SN : 003E00303331511134333834ST-LINK FW : V3J11M3B5SAccess Port Number : 1Board Name : STLINK-V3SET-----------------------------------------------===== UART Interface =====Total number of serial ports available: 1Port: COM6Location: \\.\COM6Description: STMicroelectronics STLink Virtual COM PortManufacturer: STMicroelectronicsWhat am I missing here? Thanks!

Hello Everyone,With STM32HSM -V2AE - 25-> Flashed the firmware version1.0  for 10 numbers and will the remaining 15 counts supports to flash the updated firmware version 2.0?-> If the firmware upgrade happened in field how does HSM support in that case.  Thanks In Advance    Regards,Surya S

Hello,I'm writing SPI code to communicate between an STM32 Nucleo Board and a TI Dev Board. I'm using a manually toggled chip select pin. The data my TI board is receiving is junk, and after probing the SPI output, It seems I'm getting random noise in the Chip Select. I've tried a lot of hardware debugging, I've changed the boards I'm using (same models but different boards), the wires, nothing seems to make the data readable. I'd appreciate any help or insight! I've included the code I'm running on the STM as well as an example of the noise I'm seeing through my Analog Discovery 2 scope. The two have common ground and 5V.   /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2023 STMicroelectronics. * All rights reserved. * * This software is licen

I am using STM32CubeProgrammer v2.6.0 with STLINKV3-SET and STLINKV2 without any trouble.   I have recently bought some STLINKV3-MINIE debug/programming probes but STM32CubeProgrammer does consider it "too recent" and I can not use them. I can not program with it, neither to update it. I just need to program a binary file. No debug. No SWO. Just SWDIO/SWCLK. Windows does detect it, and I can program with it using Simulink Embedded Coder Support Package, but I can not use it with STM32CubeProgrammer. Any tip for the easiest way to keep CubeProgrammer v2.6.0 (I need it for other toolchain) while being able to program (fast) a binary using STLINKV3-MINIE? I am deepening in a MSYS2 OpenOCD toolchain / VSC for STM32 for programing .elf/.bin files, but I should deepen about .cfg and .svd files for my microcontroller (STM32G474). I was also considering using IAR or Keil MDK, but I think it is to use a hammer to crack a nut, as I only want to program a binary file. Thank you in adva

I created a new board using STM32L431CBT6. The initial programming of the board was successful. However, once a program was written, I found that it couldn't be modified again. I suspected it might be related to Boot settings, so I tried changing Boot0 to High, NRST to Low, and various other attempts, but ultimately I couldn't access it. I thought it might be because I didn't set Debug to Serial Wire in SYS, but it seems unrelated.I am using STM32CubeProgrammer as the tool. When I try to access the board using a Chinese-made (purchased on Amazon) ST-LINK/V2, I cannot access it. However, writing was possible on the first attempt with this device.Simply connecting it, the Serial number becomes corrupted, and it cannot be connected.  Therefore, to check if ST-LINK is properly connected, I change Shared to Enable.  Updating Media Then, the Serial number is displayed correctly. However, when I try to connect in this state, it says there is no target.So, when I revert Sha

I need to write option bytes using HEX file, but so far can't work on STM32C0. It was working well in STM32L0.Any solution?Updating the option bytes using "-ob [OptByte=<value>]" is working, but I prefer using the HEX file. STM32C031STM32CubeProgrammer v2.15.0stm32_programmer_cli -c port=SWD freq=8000 mode=UR -e all -d "OptBytes_C0.hex"The program shows "File download complete"Before: 0x1FFF7800 : FFFFFEAA 00000155After: 0x1FFF7800 : FFFFFEAA 00000155 <<< Option bytes unchanged  STM32L031STM32CubeProgrammer v2.15.0stm32_programmer_cli -c port=SWD freq=8000 mode=UR -e all -d "OptBytes_L0.hex"The program shows "File download complete"Before: 0x1FF80000 = FF5500AAAfter: 0x1FF80000 = FFFF0000 <<< Option bytes changed as expected  

I have an RS585 1/2 duplex transceiver hooked to USART2 configured for hardware flow control (RS485) on an STM32L412 micro.Is it possible to program a virgin part using the STM32CubeProgrammer, and to later do a firmware update over this comm channel?I searched the forums but did not find a definitive answer.

Hello everyone, I encountered a problem while debugging my program.CubeIDE Version 1.14 , CubeProgrammer Version 2.9.0, ST-Link Version V2J43S7 The ST-Link/V2 is found. You can erase the Chip (STM32H753BIT6) but can't download the .elf file (CubeProgrammer).In the CubeIDE you can't debug but the ST-Link and the STM32-Controller is found.We tried following steps:switching the ST-Link on/offswitching our custom hardware with the STM32H7 on it on/offreinstalled the Workbenchtried downloading another program on my PC --> failedtried downloading another program with another PC --> successanother ST-Link at my workplace --> failedcompared the debugging configurations --> both the sameanother custom hardware with my PC --> failedThe error:The debug configurations: If you have any idea... 

I am developing a custom bootloader for a client on an STM32 system. I am using STM32CubeProgrammer to exercise the new bootloader and the built-in system bootloader to investigate the protocol being used over UART. In addition, I am referring to AN 3155, which describes the protocol.The issue/confusion I am facing is that when using the system bootloader and STM32CubeProgrammer and capturing the UART traffic for erasure of a single page, I see a different message sent from the programmer than that described in AN 3155, unless I am missing some important detail in the app note.For example, erasing the first page of an STM32F103 I capture the following output from STM32CubeProgrammer.:[43h] [BCh] [01h] [00h] [2Bh] [2Ah] The first difference to the app note is in byte #3, the number of pages to erase. According to AN 3155 this should be N-1, so I would expect this to be "00h."Secondly, byte #5 appears to be undocumented, the list of pages, in this case just page zero, should be foll

I'm using a STM32F105 and can program the firmware with an ST-Link to get firmware with USB DFU device driver on the device.The device gets recognised if I connect it with USB and I can connect and read the memory without issues.If I try to program a new firmware over USB it all looks good but after the verify step I get an error: Download verification failed.When I check the firmware is not updated at all. It's weird because in the log I see that the sectors get ereased and download is complete but it seems nothing is written to the flash.See print screen below.

HelloIs there a way to activate "POWER ON"  for programming or debbuging a STM32 with STLINKV3-PWR when using STMCube programmer or STMCube IDE ?