STM32CubeProgrammer (MCUs)

Hi,I started developing a project for stm32l072cz. After seeing dfu mode working correctly I realized a problem. The objects that I program through the j-link Segger are serialized and when I go to upload the dfu file, the serialization is deleted. Is it possible to protect some sectors in such a way that loading dfu does not delete everything?Thankyou,Davide.

I've connected an STM32F407-G-DISC1 board to debug a DIY-MORE breakout board. The debuggee is connected via SWDCLK,SWDIO, NRST to the STLINK-SWD interface of the DISC1 board. Discovery jumpers are off, ST-LINK enabled.I'm loading a blinky app but when starting (debug mode), I'm etting:                      STM32CubeProgrammer v2.10.0                      -------------------------------------------------------------------Log output file:  /tmp/STM32CubeProgrammer_LLTeBo.logST-LINK SN : 066CFF485153XXXXX7123124ST-LINK FW : V2J39M27Board      : STM32F4DISCOVERYVoltage    : 2.91VSWD freq   : 4000 KHzConnect mode: Under ResetReset mode : Hardware resetDevice ID  : 0x413Revisio

CubeProgrammer under Windows (graphical Version) is working fine. CubeProgrammer with Cmd Line brings error:Output     -------------------------------------------------------------------                     STM32CubeProgrammer v2.10.0    -------------------------------------------------------------------ST-LINK SN : 50FF6B067867515336372367ST-LINK FW : V2J39S7Board     : --Voltage   : 3.03VSWD freq  : 4000 KHzConnect mode: NormalReset mode : Software resetError: Unable to list supported devicesError: Cannot identify the devicePress any key to continue . . .This is my command in Batch File:STM32_Programmer_CLI.exe -c port=SWD -vb 3 -e all -w SmartStepper_BootAndAppl_Vn_nnn.hexpauseMy hardware is a STM32G431 with ST-Link V2 Iso. Hardware is completely working with the graphical version or wi

I have two identical pre-production PCBs containing fresh, unprogrammed 32F413VGT micros from our distributor. One board will program just fine but CubeProgrammer says "can't erase device!" when I try to program the other board.After first scanning the PCB for visible solder shorts and open pads, the next thing I verified was that the micro wasn't soldered into the PCB upside down. I tripped last year on this often-discussed snafu caused by the ejector dimple mimicking the pin #1 identification dot.Other early efforts to diagnose this PCB:--the redundant corner VDD power pins have the same (correct) voltages on both boards. --both boards have the same ~1V signal on their V_CAP pins.--the reset line is the same state on both. --both unprogrammed boards draw the same IDD current, a value near zero.Any suggestion re additional things for me to check? Does my primary 8MHz crystal oscillator have to work in order to program a 32F micro? I think no because an operating board could have an in

Running linux mint on both machines and STMCubeProgrammer 2.9. I am trying to use some older nucleo boards with the STM32F07RE

I have used STM32_Programmer_CLI before successfully. I just recently loaded 2.10.0 and now I cannot get my old command line to work. It keeps telling me "Error: Connection to target must be established first.". My command line is: "D:\ST_Micro\STM32CubeProgrammer\bin\STM32_Programmer_CLI" -c port=SWD -d EQ-100.elf -v -ob RDP=0xBB WRP1A_STRT=0x00 WRP1A_END=0x0D -log EQ-100_Prog.logWhy did this work before and not now? Thanks.

..

I tried to connect the STLink to the STM32G030K6T6 by connecting SWCLK SWDIO VDD and GND pins, but the STM32CubeProgrammer can't detect the MCU.I also tried to check with the logic analizer the pins and there is only a little signal from the stlink but no response from the MCU.I think the problem could be that the SWCLK and BOOT0 are in the same pin and this is pulled down internally. So how can I connect and program the STM32?Thank you so much

Hi all. I am using STM32CubeProgrammer with an STM32G474VET6 target system on a Windows 10 box with a USB-connected STLink module. The programmer is v2.10.0, and the STL firmware is v2J3757.My problem is that the Cube programmer doesn't seem to be able to perform a mass erase on the target prior to programming. When I try to program, I get the following message:Error: failed to erase memoryThe Full chip erase button fails as well withError: Mass erase operation failed.Please verify flash protectionFlash write protection is not enabled on the target. I can erase and program just fine with the STM32 ST-LINK Utility. Also, Cube programs successfully if the target device flash is blank.I'm happy to provide any of the target settings on request.Any ideas?Thanks,Mike

Hallo,I am using STM32 CubeProgrammer and performed the "Full chip erase". after the Full chip erase some garbage value appears at EEPROM address (0x0808 0000 & 0x0808 0010) I have attached the image.Regards,Swapnil

Hi,I created one external loader to write and erase one NOR FLASH and works well (STM32H7A3 with S29GL512S11).When I try to access the memory in my application code the memory returns 0xFFFF every time. When I try to read the memory the first time when external loader is loaded to microcontroller, I read the same values. But if I click second time in Read button the STM32Programmer read the memory correctly.My question is, what are the commands sent to microcontroller when Read Button is clicked? In my custom external loader I don't have any function to read, and the read task is executed by STM32Programmer and works fine.Best regards,Luis Cristóvão

Hello,after reading a lot i am still confused.I am looking for a solution to flash the internal and the external memory of an STM32F4 (for testing i am using the F469 Discovery Board).There is no problem using the ST-Link on-board, but what about a solution for a mass-production board where no ST-Link is assembled and maybe the end-user needs to do an update?Well, i am using this code to enter the bootloader for USB:void goToBootloader(void) { HAL_RCC_DeInit(); SysTick->CTRL = SysTick->LOAD = SysTick->VAL = 0; __HAL_SYSCFG_REMAPMEMORY_SYSTEMFLASH();   const uint32_t p = (*((uint32_t *) 0x1FFF0000)); __set_MSP( p );   void (*SysMemBootJump)(void); SysMemBootJump = (void (*)(void)) (*((uint32_t *) 0x1FFF0004)); SysMemBootJump();   while( 1 ) {} }So far so good, i can connect to the device with the CubeProgrammer.And it seems that i can flash the internal memory but then failed at 0x9000000 11:57:01 : USB speed : Full Speed (12MBit/s) 11:57:01 : Manuf. ID

Hello,I'm using STM32H735G-DK board and I can't read device memory using ST-LINK Utility.I wrote simple example with led blinking and it's correctly uploaded to flash by STM32CubeIDE - led is blinking. STM32CubeProgrammer can connect with ST-LINK and I see memory map but I can't select start address to write new program to flash or external memory (Start address window is locked). When I want to start programming, code is automatically written to address: 0x00000000Stlink Utility can't connect to the device.I read previous posts about H7 processors:https://community.st.com/s/question/0D53W00000LeYL1SAN/get-stm32h735gdk-out-of-deadlockhttps://community.st.com/s/question/0D50X0000BqBA6TSQW/error-to-connect-to-target-stm32h747idiscohttps://community.st.com/s/question/0D50X0000Bh5aWoSQI/stm32h747-discovery-kit-not-debugprogrammerI've also checked if the power configuration is set correctly:Neither of these solutions work. My code:/* Includes ------------------------------------------------

I am trying to program an STM32F103C8T6 over USART via the System Memory Bootloader. I've already tried with PL2023 and FTDI FTR232RL based USB-TTL converters. I've tried with multiple computers and multiple tools provided by ST. Also, I tried jumping from user code to bootloader besides pulling BOOT0 to HIGH. Whatever I tried, the chip is not responding. I can see the initial 0x7F bytes via a logic analyzer on the bus and the chip is just silent. I tried with BluePill and a custom PCB which is assembled using an F103 chip that was desoldered from an original Nucleo board (the chip was an STLink obviously, and I flashed the chip using another STLink).My main application which highly relies on USART1 works as expected. So I don't think there is an issue with the USART pins or PCBs I've used. STM32F103 is not listed in AN2026 AN2606, so is there any chance that particular model doesn't have a ROM bootloader?

Bug in STM32_Programmer_CLI! It always returns 0 even if post-write data verification fails.

Hello Manager,CubeProgrammer is not good, comparing with STlink Utility 4.6.Always this error message box is poped up on the screen on every jobs such as read, connect...etc.How to fix this?Current Version : 2.10.0Thanks.Best Regards,Tommy Lim

I have a challenge, I want to load program with system bootloader over TCP/UDP, I have some problems. My system is slow but working correctly. I tested with direct UART connect there is no error. But I tested over TCP there is timeout error. How can I increase the acknowledgement wait time?TCP to UART; NetBurner Virtual Comm Port Ver 2.4My set up;

i have stm32f429, I am happily updating firmware via DFUSTM32_Programmer_CLI.exe -c port=usb1 -w deliver/rusefi.hex --verify --start 0x08000000(STM32_Programmer_CLI.exe version 2.9.0)and I get "start operation achieved successfully" but code does not start to run until I hit 'reset' button on my device or power cycle.what could I be missing?

 Clearly, the angle brackets for the 'port' option are mismatched.It should say:port=<PortName>The error is repeated in UM2237 Rev 18 (the current version) - and note that the User Manual does not match the actual output:

Hi,I don't remember having this issue with v2.8 of STM32CubeProgrammer, but right now when I try to program a STM32L010 with an elf file that has the EEPROM part filed with values, both the GUI and the CLI fail to erase the EEPROM part of it, aborting and leaving the uC empty (because the flash sector erase did work). The only way to succeed is to perform a mass erase beforehand and then skip sector erase when flashing the elf file.This becomes a real issue when trying to debug with CubeIDE, because the debug session is started with CubeProgrammer CLI to program the flash before entering debug. The srec temp file generated does not have the EEPROM content by the way, only the flash so it does not mess with the EEPROM content, providing it has been loaded previously by other means (see above).I know these tools come for free, but the programmer deserves more care as it will steer customers away from working with your products in the long run.Please, have a look at this issue ASAP and pr

This is the text from the manual:For more information about the device option bytes, refer to the dedicated section in the programming manual and reference manual, both available on www.st.com.

In the Good Old Days, "Download" always meant sending stuff to the Target (ie, programming), and "Upload" meant getting stuff from the Target (reading).But the ones at Arduino have messed that up, saying "Upload" for programming the Target.eg, https://docs.arduino.cc/software/ide-v2/tutorials/getting-started/ide-v2-uploading-a-sketch :confounded_face: :\ Please clarify what STM32CubeProgrammer means when it says, "Download" and "Upload".The terms should probably be avoided now.:\

Followed STM tutorial on the subject. This is custom board STM32G484 with Winbond 25q128jvsq. Memory can read, erased and written to. It passes all the tests in quad mode (4 IO lines). However Programmer reads only single line, hence rather all FF's it reads all 88's after erase I used Loader_Src as per STM. Obviously fails programming reporting error deleting memory. Any ideas?

..

Hi,I have a STM32G030F6P6 connected to an STLink. I cannot upload at least an LED toggle code to the chip. I get the following messages in the CubeProgrammer. And I get "Cannot insert all breakpoints" error in the CUBE IDE.I double triple checked my voltages. They are 3.3V. But still the messages from the Cube Programmer shows as 2.93V. Can you please comment on this and help me. 09:30:41 : STM32CubeProgrammer API v2.8.0 09:30:41 : ST-LINK error (DEV_CONNECT_ERR) 09:31:01 : ST-LINK SN : 34FF6D064155303923251357 09:31:01 : ST-LINK FW : V2J38S7 09:31:01 : Board      : -- 09:31:01 : Voltage    : 2.93V 09:31:01 : SWD freq   : 4000 KHz 09:31:01 : Connect mode: Normal 09:31:01 : Reset mode : Hardware reset 09:31:01 : Device ID  : 0x466 09:31:01 : Revision ID : Rev 1.1 09:31:02 : UPLOADING OPTION BYTES DATA ... 09:31:02 :  Bank&nb