STM32CubeProgrammer (MCUs)

I'm trying to load firmware through UART (not SWD/ST-Link) to my STM32G031F6P6 prototype board using STM32CubeProgrammer but can't get it to work (although it works fine through SWD and STM32CubeIDE). Note: BOOT0 and SWDCLK are shared on the same Pin 19 (PA14/15) for this MCU. Am using RS422/485 transceiver (ADM3485EARZ) to go between PC USB/RS4222 (DTECH USB 2.0 to RS422/485 dongle) and MCU UART1. Have verified that serial transceiver works properly after firmware is properly loaded through SWD. Per AN2606 Section 41.1, I tried 2nd Option (nBOOT_SEL is NOT checked, nBOOT1 is checked, and nBOOT0 is checked - set previously using SWD) of Pattern 11 by tying Boot Pin high (VDD), pressing reset, hitting connect on STM32CubeProgrammer v2.10.0, releasing reset. Get "Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again…". Have tried variations over many months and am stumped. How do I know STM32Cube

..

Hi,I am using MB1549C devkit for STM32U5. I have enabled trust zone and created one application. Now I wanted to update firmware via native bootloader over UART. I have tried to connect it over UART2, I got read error over 0x0C00 0000 where secure firmware is loaded. even I am not able to erase firmware. I am able to read data from 0x0810 0000.Here my secure and non secure code .ld file mapping.  Can you please guide me, How can I update firmware of mcu which has trustzone enabled via native bootloader using uart?Please check option byte of needed. I have attached image. 

When using STM32CubeProgrammer to program STM32F103VET6, it is found that using the "page erase" function will erase the first page error by mistake (erase pages 1, 3, 5). Upon inspection, it is found that the page erase data sent by STM32CubeProgrammer v2.13 is 0x03 0x01 0x03 0x05 0x00 0x04, while the data sent by STM32CubeProgrammer v2.7.0 is 0x02 0x01 0x03 0x05 0x05.  By consulting the AN3155 manual, it is found that the data sent by v2.7.0 is correct and the data stream sent by v2.13 is wrong.

Platform: Windows 11 22H2 (x64)CubeProgrammer version: 2.12After updating CubeProgrammer from 2.6 to 2.12 we end up with issues where selecting sectors to erase does not work with UART connection mode. What we observed is that program sends wrong data.We're using custom bootloader but its functioning was made in line with ST documentation (AN3155) and was verified to work with STM32CubeProgrammer in version 2.6.Example:What I want to do: Erase single sector '17' (0x11)Version 2.6:Frame: 0x001111Version 2.12:Frame: 0x01118696According to documentation first byte should be "number of sectors to erase - 1", so for 1 sector it should be '0'. Looking at logs from CubeProgrammer (2.12) it sends 1 extra sector and what's more it's a sector that does not exist.Below small snippet from logs from CubeProgrammer (2.12):11:46:46:713 : Flash sector erase ... 11:46:46:713 : Sending Erase command and its XOR: 11:46:46:714 : byte 0x43 sent successfully to target 11:46:46:714 : bytesToWrite before

Hi, I have an ELF file modified to write to the main memory address 0x08004000 instead of 0x08000000. Please find the screenshot below and the ELF file in the attachment.But instead of writing to 0x08004000 it constantly writes to 0x08000000. Why is this happening?

Hi,I have acquired a new STM32G031 microcontroller that has not been previously flashed and have observed an unexpected behavior when powering up my circuit prior to the initial software upload.Upon further investigation, I discovered that multiple registers were not at their reset values, but instead at different values that were not anticipated. Specifically, the registers of GPIOA (such as MODER) had critical (in my application) pins set to pull-up (e.g., MODER set to 0xEBEB FFAF).As such, I would like to know:Is the initial state of the registers documented anywhere? I was unable to find such information in the reference manual (RM0444.pdf).When in production with the final PCB already assembled, what is the safest approach to ensure the registers are at their reset values even when flashing fails (e.g erasing the device prior to flashing)?I appreciate your assistance with this matter.Note: While I understand that the safest solution would be to ensure that the external circuit can

Hi.I tried update STM32CubeProgrammer to 1.13 version through "software update" tab, but STM32CubeProgrammer says there's no update. I have 1.12 version.

Hi there, I'm starting to use the stm32cubeprogrammer sw, and don't know how to practice sending valid commands through this interface. I have located the CLI.exe but every time I click on it, the program executes and then closes. What am i doing wrong?

In our project, we are using flash loader to write/read/erase the external flash memory connected with microcontroller. This read/write/erase operation is working as expected.However, if we perform the full chip erase, it erases only part of the external flash memory (till 512KB) and not the complete external flash memory. We found that ST cube programmer is sending only end address till 512KB only if we perform the full chip erase than complete flash memory area. seems ST cube programmer is considering the external flash memory size equal to the microcontroller flash memory causing this issue.In our project, we are using external flash memory of 16 Mbyte. Once we perform the full chip erase of external flash memory, it sends the end address as 0x9007FFFF than 0x91000000(see the attached screenshot).Can you please check it at our end and see if you see the same issue.

I am using 70STM32H7 board and STM32H_IPS_QSPI_Loader_CM7 external loader.I can program from the IDE but that doesnt affect images in external memory. So I tried programming from the programmer and it fails to write to external memory. Then I tried to delete the sectors manually and I can't understand how or why but that sometimes works and sometimes doesn't. Even when it does work, trying to program it afterwards results in an error again, even if I uncheck the option to erase sectors before writing.nwrp0 -15 are all checked which sounds like they are not write protected but I have no idea if that is the correct thing to check. btw when we did the initial test we managed to program ext flash correctly as all images were displayed nicely. I then started working on the actual project and when it was time to try it I saw this problem. I went back to the test project and could not make that one work either so I have no idea what could have changed in meantime or what I did differently.

Hi,I had been using ST/Link 2.1 nucleo header so far to program and debug custom STM32 H723 ZG boards and wanted to switch to ST/Link v3 in order to debug with compact probes. Thus I ordered two genuine ST-Link/V3 MINIE from Mouser. My custom board and debug connector is confirmed to be working since I can connect and program with STLink V2 and V2.1 .I've tried to connect through CN2 B2B connector as well a CN4 STDC14 Connector but I can not connect to the target via either method on both MINIE board I purchased.I've updated firmware to V3J10M3, tried versions with and without Mass Storage. I've tried all Modes and Reset Modes.Still I can not get target informations. Interestingly, CubeProgrammer states that the (target ?) voltage is 0.24V.Wondering if there is an issue with my custom STD14 to JST-SH6 cable, i've tried to use a V3-SET with the very same cable and I can successfully connect to the MCU. Displayed voltage is 0.0V which is surprising because I get 3.25V with ST-Link V2.My

Hi,I'm using latest STMCubeProgrammer/ST-Link-Utility releases. My goal is to provide the option bytes directly in the .elf/.hex file, so our manufacturing department only needs to download this file.I already managed to get the settings into the .elf/.hex file automatically. But when I try to program the device, I got verification error. It seems(!) that the device is programmed correctly, but I want to be sure.The device is a L011F4. There are two configurations for the option byte corresponding to the debug and release builds. For the debug build, the option bytes are the same as for a blank device delivered from factory. For the release build, the RDP level is 1, and the bootloader pin is disabled. No write protection fro both configurations.Even for the debug build with no RDP, the verification fails and I don't know why. Here's my call to STM32_Programmer_CLI.exe:-c port=swd freq=4000 ap=0 index=0 mode=normal -vb 1 -rdu -e all -d %1 -v%1 is replaced with the name of the .elf/.hex

I have about 40 devices with identical hardware (STM32G071K). All devices will have the same firmware, but i need to distinguish them by custom unique "ID" (numbers from 1 to 40) - which will serve as address at RS485 network. How to do that ? On STM32F0 it can be done using "user bytes" in option bytes by CubeProgrammer. But STM32G0 have not this feature. How to simply write number somewhere into flash ?

I have a board with STM32L552RCT6 micro. I plan to update software using the usb port but I have an issue. The connection between STM32cubeprogrammer and the micro seems to be somehow instable. I can make conenction, read, write memory as expected but after some time the connection get lost. The reason is that ht RST pin of the micro goes low so the micro is reset. But there's nothing pulling down the RST pin except the micro itself. The PIN in fact is connected only to a pull-up resistor and a capacitor. So I assume the micro is pulling down the RST pin during the boot process. What's stragen is also that the time when the reset occurs is somehow randomic and it's different using different PC for programming the device.I've checked the power supply but there's nothing strange on it. And also the data signals have a normal behaviour. I kept some oscillo waveform.1) Vcc is going on still at around 3.3V2) RST go down and then back up loadin the RC pullup3 and 4) are the USB data signalsA

Hi, I am working on making firmware write work using System Bootloader and USART1 interface on NUCLEO-G491RE. I have a code snippet taken from the internet which jumps to the System Bootloader section of the code once the User Button is pressed. I have interfaced a USB to UART converter at PA9, PA10, and GND as suggested in the AN2606.void BootloaderInit() { void (*SysMemBootJump)(void);   volatile uint32_t addr = 0x1FFF0000; HAL_RCC_DeInit();   SysTick->CTRL = 0; SysTick->LOAD = 0; SysTick->VAL = 0;   __HAL_SYSCFG_REMAPMEMORY_SYSTEMFLASH(); __disable_irq(); SysMemBootJump = (void (*)(void)) (*((uint32_t*) (addr + 4))); __set_MSP(*(uint32_t*) addr); SysMemBootJump(); }But once the User Button is pressed and tried to connect to the UART interface using STM32CubeProgrammer it showsWhy is the firmware upgrade not working?

Hi all!So I'm looking for the easiest and fastest way to create a firmware update desktop app for an STM32 device (Arm Cortex M7). I would like to have something like CubeProgrammer, but way less functionalities (just programming/flashing). Being a commerciall product for non-programmers CubeProgrammer is not fine. I want something proprietary with my GUI.So, .... the strategy I found online is to create a custom bootloader (like this: https://github.com/viktorvano/STM32-Bootloader) and control it with a Java app with serial communication libraries.But why do you NEED a custom bootlader? Can't I just flash to the flash memory (from 0x8000000) and let the default bootloader take care of things? Easier and less flash memory usage.Security is not the priority. Ease and fast implementation is the priority.It would really help me to clarify this, please. Any suggestion is welcome.Anything will do, really, as long as I can upload a .bin (or.hex) file to the MCU through my desktop app.Th

I am using development board MB1519C. I was trying to disable trust zone in my board. For that I have followed below step in stm32cubeProgrammer.Open option byte and set RDP level to 1 and apply and power reset and then RDP 0 along with trust zone uncheck (0).After that I am not able to connect with my board via stmCubeProgrammer.It shows below error. I also tried with hardware reset configuration. Guide me to resolve issue.  Also tried with UART mode, In that case I received below error.How to disable RDP?

Hi everybody,i've written an external loader for STM32H7A3IIK6 to manage, via CubeProgrammer, the external flash memory IS25LP128F-RMLE.The external loader works perfectly except for with the following issue : just the first time i open CubeProgrammer [version 2.13.0] and try to flash the external memory, even if i do not power cycle my electronic board, Cube Programmer gives me always the following error.Could this problem be related to the version of Cube Programmer or is it related to my external loader?

We want to allow customers to download firmware directly.Are you trying to pass the STM32CubeProgrammer\bin file, no licensing issues?I'm trying to make a batch file so that I can download it right away.I've tested it. If you pass only this file and the database file together, there seems to be no problem with downloading.We ask if there will be any licensing issues if we pass this file on.

Hi everyone, Could u help me how to update RTC time n date using serial Usart. Example code will help me to better understand , the date n time stored in this variable  sTime.Hours = 0x00; sTime.Minutes = 0x00; sTime.Seconds = 0x00; sDate.WeekDay = RTC_WEEKDAY_SATURDAY; sDate.Month = RTC_MONTH_APRIL; sDate.Date = 0x15; sDate.Year = 0x23;

From version 2.11 to 2.12 a change was introduced that results in the programmer reporting that the external loader "cannot be loaded" while loading via stlink v2 via the command line tool.----------------------------------------------------------- STM32CubeProgrammer v2.12.0 -----------------------------------------------------------   Error: External loader <file_name>.stldr cannot be loaded. Press any key to continue . . .The loader has not changed through many versions of the programmer and has been functioning as expected until now. Are there known updates to the loader api or other modifications documented somewhere?The issue came to light after updating to 2.13 from 2.9, after which I was able to narrow down at which release the issue showed up, between 2.11 and 2.12.DeviceSTM32H743IIT6 with and external QSPI flash memory

Hi,Does anyone are able to erase a memory page of BANK2 on a STM32U575 with ST-LINK/V2 in STM32CubeIDE or STM32CubeProgramer? The mcu is configure in dual bank by default. I'm only able to work with a SEGGER JLINK (in IDE) or it is possible to program mcu after a full chip erase. When I put it in single bank mode, the IDE only erase 8K of the 16K page and generate an error at verification.Thanks

Hi all, I'm new to STM32 and I encountered with an error when I run STM32CubeProgrammer after installing the tool on Ubuntu 18.04 according to STM UM2237 user manualthe error is : Could not find or load main class com.st.app.Main.I googled and it was said that it might be the CLASSPATH config problem which leads to the class cannot be found. But I searched the install path which is /home/mypath/STMicroelectronics/STM32Cube/ and cannot find any JAVA class looks like this main class(only 3 JAR file found: uninstaller.jar, OpenJFXWarning.jar and STLinkUpgrade.jar), and I even don't know which path to add to CLASSPATH. Does anyone have ideas about why this happened and how to fix it, thanks in advance.

For 2 weeks ago STM32CubeProgrammer started to hang when selecting a file to program with. I have updated STM32CubeProgrammer and JDK but problem is still there.The error message is:OpenJDK platform binary is not respondingHow to fix this?