STM32CubeProgrammer (MCUs)

The option bytes are wrongly set when using big flash derivative STM32G0B1RC and STM32CubeProgrammer 2.13 (it doesn't matter if CLI or GUI).The point is that the protection is set for the second bank.Documented on pictures, the state of OB in MCU before flashing hex file (containing OB) - 2023-05-09_09_35_57.png,and the state of OB after programming is done - 2023-05-09_09_39_46.png.Also, attached output from CLI after OB was wrongly programmed, and protection was set, we couldn't do mass erase - 2023-05-09_09_40_16u.png.I noticed the document https://www.st.com/content/ccc/resource/technical/document/release_note/group0/0e/66/57/b4/f9/ee/4f/73/DM00441049/files/DM00441049.pdf/jcr:content/translations/en.DM00441049.pdf in which is described fix for STM32G0Bx in version 2.13.1, but I cannot find this version for Windows OS.Can you look at this issue and reproduce it?For now, we have a workaround - omit OBs from the hex file.

Dear ST Community,I would like to address an issue we have encountered while flashing the program on the STM32L562VETb microcontroller using different versions of the STM32 CubeProgrammer software.Our observations indicate a significant performance difference between STM32Programmer version 2.13.0 and version 2.8.0 when it comes to flashing the bin file of size 248 KB  onto the STM32L5xx. Specifically, version 2.13.0 takes approximately 1.07 minutes, while version 2.8.0 completes the same task in approximately 10 seconds.Are there any known reasons why the newer version of STM32Programmer (2.13.0) might exhibit slower flashing performance compared to the older version (2.8.0)? Could there be specific configurations or settings that need to be adjusted to improve the flashing speed?I have attach the Document and bin file please look into itThank you for your attention and assistance.Best regards,kavan

STM32CubeProgrammer Win64 v2-11-0Windows 10STM32F411xC/EDevice ID 0x431Can connect to MCU with STM32Cube via USB in DFU mode, can erase memory blocks, cannot write to memory blocks due to libusb control transfer error [-9].Can anyone help me fix this?Excerpt of Debug messages Below 09:19:32:270 : erasing sector 0005 @: 0x08020000 done 09:19:32:270 : erase: 4385ms 09:19:32:271 : Download in Progress: 09:19:32:271 :  Size     : 183204 Bytes 09:19:32:271 :  Address    : 0x08000000  09:19:32:276 : DFU status = 0 09:19:32:276 : DFU State = 5 09:19:32:276 : Status: 0, State: 5 09:19:32:276 : setting the address pointer to address: 0x08000000 09:19:32:283 : DFU status = 0 09:19:32:283 : DFU State = 4 09:19:32:283 : DFU status = 0 09:19:32:284 : DFU State = 5 09:19:32:284 : sending packet nbr: 0 09:19:32:284 : DFU status = 0 09:19:32:284 : DFU St

Hello, do you know how to configuration Manager Run Time Environment Keil for STM32F407ZGT6 microcontroller?I want in Keil to configuration Manager Runtime Environment for my development board with STM32F407ZGT6 microcontrollers. I hope they will after configurations keil generated example.Also, if know examples to keil to STM32F407ZGT6 microcontrolers please sher me. I new in keil and STM microcontroller. I other use CubeMX tools to configuration my microcotollers . Thanks a lot!

I am currently using a STEVAL-PLC001V1 board.I am trying to program it using CubeProgrammer. I am just trying to reprogram the demo mode at the moment. If I program it on the board without the option "Run after programming", the download is succesfull, but nothing happens on the board. But as soon as I check the option, I have the errors "Core is locked up" or "The core is kept under reset".I already tried to erase the chip, to connect it using the "under reset" mode, and I still have the same issue.Did someone have the same issue before me ? How can i solve it ?

Please see the screeshot

STEVAL-FCU001(STM32F401CC) .hex STM32cubeprogrammer programming issues:I bought the product "STEVAL-FCU001' (https://www.st.com/en/evaluation-tools/steval-fcu001v1.html) and I am trying to program the .hex code(or bin code?) into "STM32F401CC" via "STM32Cubeprogrammer"_SWD. The first step I did is to extract the original code(.hex) inside the F401CC and successful.After that, I can program the extracted code(.hex) into STM401CC again and successful.However, I found that the code I extracted from "STM32F401CC" is not the same as "DroneKit_301018_official.hex" from Github(https://github.com/STMicroelectronics-CentralLabs/ST_Drone_FCU_F401/tree/master/STM32%20FW%20Project/Official%20release%20with%20BLE%20Remocon%20-%20170318/EWARM/ToyDrone_Configuration/Exe)Because of that, I t downloaded the code "DroneKit_301018_official.hex" and tried to program into my "STM32F401CC", but failed.The environment of the disconnected conditionThe environment of the connected conditionIt shows me 11:

Hi I am trying to install STM32CubeProgrammer. At step 8 installer stalls as shown below and does not go any further. Only option that I can is pressing Quit button. I have tried to install 32 and 64 bits versions and also 2.13, 2.10 and 2.6 version.What should I do? Thanks in advance.Note: I do not know which category to post this issue.

..

Hi everybody, i've developed an external loader for a STM32H7A3IIK6 MCU to write and read, using STMCubeProgrammer, an ISSI QSPI External Flash [IS25LP128F]. The External Loader works perfectly except for the following issue : the first time i open Cube Programmer and try to access the External Flash Memory [read or write] the Init function fails [even if i do not power cycle the electronic board]. Could it be a problem related to the "ld" file [here attached]?

Wanted to follow up on https://community.st.com/s/question/0D53W00001EEBXXSA5/stm32cubeprogrammer-incorrectly-erases-on-dual-bank-1mb-stm32f7internal ticket number: 120183Internal ticket number: 144023

Hi, I'm recently working on an iOS app that communicates with an STM32F401 via Bluenrg-lp using UART. The goal is to update the STM32F401 firmware through the Bluenrg-lp with a mobile phone. I've encountered some issues with the F401 and I was wondering if there is anyone who is more familiar with this area that could help me out.The main problem is that if unexpected power loss or reset occurs during the transmission process, the STM32F401 may enter a protected state, and it won't be able to erase/program the F401 again. I've tried sending the bootloader commands 0x73 Write Unprotect and 0x92 Readout Unprotect, but it didn't help.I've used a USB to UART tool to connect to the computer and used STM32CubeProgrammer to check the F401. The RDP is 0xAA, but the SPRMOD is 1 (refer to 1.png). When I uncheck the SPRMOD through the software and then apply, it only shows an error message (refer to 2.png).I've also tried using ST-Link, but I still couldn't disable SPRMOD in STM32CubeProgrammer.

Hi guys! Good day and hope you are doing well.I am currently working with STM32H573VIT6. I have enabled the Trustzone by using STM32CubeProgrammer (i.e., from the "Option bytes" feature). After that I am having an issue of "Hardfault exception" during debugging(FYI, I am using IAR as IDE). I have got the following logs from the debug log.Mon May 29, 2023 16:46:55: Breakpoint hit: Code @ startup_stm32h573xx.s:235.1, type: default (auto)  Mon May 29, 2023 16:46:55: HardFault exception. Mon May 29, 2023 16:46:55: The processor has escalated a configurable-priority exception to HardFault. Mon May 29, 2023 16:46:55:  Mon May 29, 2023 16:46:55:  A bus fault has occurred on an instruction prefetch (CFSR.IBUSERR, BFAR). Mon May 29, 2023 16:46:55:  Mon May 29, 2023 16:46:55:  Attribution unit violation: Mon May 29, 2023 16:46:55: An attempt was made to access parts of the address space that are marked as Secure with NS-R

I have a custom PCB using STM32H750VBT6 MCU and QSPI memory chip S25HL512TFAMHI010. I have written an external loader file as per the instructions in the STM32 MOOC [I tried to put a link here but the forum doesn't let me]. Testing the QSPI driver in STM32CubeIDE works fine, but when I try to write to the external memory using the .stldr file in STM32CubeProgrammer (v2.13.0), it returns "Error: failed to download the file". The console output is below: 17:07:43:167 : Memory Programming ... 17:07:43:176 : Opening and parsing file: myFile.bin 17:07:43:176 : File  : myFile.bin 17:07:43:176 : Size  : 1.60 MB  17:07:43:176 : Address : 0x90000000  17:07:43:177 : Erasing memory corresponding to segment 0: 17:07:43:177 : Memory erase... 17:07:43:178 : halt ap 0 Status = 0 17:07:43:179 : halt ap 1 Status = 32 17:07:43:179 : halt ap 2 Status = 32 17:07:43:355 : Erasing external memory sectors [0 6]&nbs

Hi.Before enter to standbyMode i can accesss to registers in "register" tab, but after return from standbyMode I can't. First picture present state before enter to stanbyMode After return from standbyMode I don't see registers: but there are still visible in "memory and file editing" tab: I also notice that after change MCU core state, a icon with text "CPU" doesn't update. I must click once again on icon on left bar to force update:

Hi,I am using MB1549C DK which has STM32U575ZIT6 MCU.I have enabled trust zone as well as dual bank.I have four hex file, Two files for bank1, secure and non-secure firmware. uploaded at 0xC000 0000Two files for bank2, secure and non-secure firmware. uploaded at 0xC100 0000At bootup, I have read swapbank bit of OPTR reg.uint8_t getActiveBank() { volatile uint32_t remap = READ_BIT(FLASH_NS->OPTR, 0x1 << 20); return remap == 0 ? 1 : 2; }I have used below reference function from standard example to modify swap bank bit.NUCLEO-U575ZI-Q\Examples\FLASH\FLASH_SwapBanksvoid toggleBankAndReset() { /* Unlock the User Flash area */ HAL_FLASH_Unlock(); HAL_FLASH_OB_Unlock(); /* Get the boot configuration status */ FLASH_OBProgramInitTypeDef OBInit; HAL_FLASHEx_OBGetConfig(&OBInit);   /* Check Swap Flash banks status */ if ((OBInit.USERConfig & OB_SWAP_BANK_ENABLE) == OB_SWAP_BANK_DISABLE) { /*Swap to bank2 */ /*Set OB SWAP_BANK_OPT to swap Bank2*/ OBInit.Optio

I´m programming a STM32F103RCT6 via command line via:STM32_Programmer_CLI.exe --connect port=SWD --erase allSTM32_Programmer_CLI.exe --connect port=SWD mode=UR reset=HWrst --download Output.hex --verifyWhile erasing and programming works flawlessly I´m facing the issue that the verify is failing. This is because after programming Output.hex the controller will start the programmed application.This is an issue, because the application will write to flash memory at address starting at 0x08037800 on startup, making the succeeding verify process failing of course. Is there a way to prevent STM32_Programmer_CLI from starting the controller after programming ?

Starting from STM32_Programmer_CLI version 2.13 I have strange lines into the output .hex file.Attached is the comparison between v 2.10 and v 2.13 output.Any ideas?Thanks,Davide

These are the 1st lines of stm32u5_tool.sh file from X-Cube AWS package.#!/bin/bash# Find STM32_Programmer_CLI# shellcheck disable=SC2154if [ -n "${cubeide_cubeprogrammer_path}" ]; then    PROG_BIN_DIR="${cubeide_cubeprogrammer_path}"    PROG_BIN_PATH=$(find "${cubeide_cubeprogrammer_path}" -name 'STM32_Programmer_CLI*' -type f)    PROG_BIN=$(basename "${PROG_BIN_PATH}")    export PATH="${PROG_BIN_DIR}:${PATH}"elif command -v STM32_Programmer_CLI; then    PROG_BIN="STM32_Programmer_CLI"else    echo "Error: STM32_Programmer_CLI could not be found."    echo "STM32_Programmer_CLI in not in your path and the cubeide_cubeprogrammer_path environment variable was not defined."    exit 1fiWhen I run this file in the cmd , I get this error: " Error: STM32_Programmer_CLI could not be found. STM32_Programmer_CLI in not in your path and the cubeide_cubeprogrammer_path environment variable was not defined. " I installed

When attempting to program an STM32G0B1KB MCU (128kB of flash) with the latest version of STM32CubeProgrammer (2.13.0) the target information flash size says it only has 63kB of flash. This is not a valid flash size for this family of MCUs, and it does not allow the MCU to program if the flash size is greater than 63kB but less than the maximum 128kB.  When I revert to STM32CubeProgrammer v2.11.0 this is no longer an issue and the proper flash size is shown. All other variables (hardware, programmer) are the same.  This is a major problem and delayed our manufacturing by ~2 days as we thought we had more serious hardware problems. This problem does NOT exist for the STM32G0B1KE variant (512 kB).Thanks,Rob

I have been using the ST-Link Utility for years to program a variety of boards. Today, I thought I'd give the new STM32CubeProgrammer a try - but it doesn't seem to work for me.The first difference I see in the logs is the line: "Debug in Low Power mode is not supported for this device."When using the ST-Link Utility, the log says: "Debug in Low Power mode enabled".I don't know if this is the issue or not, but the CubeProgrammer eventually reports a Data mismatch and then says, "Warning: The core is locked up".I am fairly confident that I have all the options set the same way on both utilities.Can anyone offer a suggestion on how to proceed?Thanks.

..

is it possible to send a command through CLI to return the software version of stm32cubeprogrammer that is being used? I didnt see it in the manual, but hoping this was do-able.

How to Enter boot loader in STM32H743BIT6 via USART1?pin BOOT0 is SET by SWITCH to "1" (VCC) (3.3V).the STM32H743BIT6 don't react to packets in USART1 from the STM32CubeProgrammer software.

l want to connect pcb board through stm32cubeprogrammer.But it posts pop-up like that.The error massage is "Error: Problem occured while trying to connect".And sometimes it connects well, so i can't find the reason.Could you give me some adivce to this problem?