STM32CubeProgrammer (MCUs)

We have seen several signatures of this issue.Signature 1:The extracted binary shows that the image is located on Bank1. Also the extracted byte options show that the image should be located on Bank2 but it was empty and still the device boots up after hard power cycle(removed battery and put back)and work fine.Signature 2:When we took the same above image and flash it on to the new device, where code is in bank 1 but we set option byte swap bank to bank 2. The device consistently is in dfu mode and does not boot up like the above device after hard power cycle.How do we explain the above behavior. Is there anything else than the nbank swap option byte which control boot process?Apart from dfu and initial flashing using st link. Is there any other process which can change the nswap bank option byte?Also is there any difference between mcu boot via watchdog timer and hard reset like removing battery?Any insights.Thank you,Krishna 

Heyin a project of us we are using the legacy STMFlashLoader to flash firmware on a STM32F103 via the system bootloader on UART1, but wanted to migrate to STM32CubeProgrammer now. In this application the PC (Win10) which runs STMFlashLoader/STM32CubeProgrammer is not directly connected (via a USB-TTL adapter) to the UART1 of the STM32, but goes through a "tunnel". This works perfectly fine with the legacy STMFlashLoader but does not with STM32CubeProgrammer.The log generated by STM32CubeProgrammer clearly shows that things break when the first chunk of data to be written is being sent.The issue is that STM32CubeProgrammer sends a chunk of 256 bytes (0x31CE0800000008FF...), while STMFlashLoader sends only chunks of 128 bytes size (0x31CE08000000087F...), which perfectly explains the issue as the "tunnel" involves a buffer of size 128.Hence the question: Is it somehow possible to set the chunk size which STM32CubeProgrammer is using for UART uploads?If not, would it possible that such a

Hi,USB DFU did not work in STM32CubeProgrammer in Linux. The programm did not detect the usb port. But it works faultless in STM32CubeProgrammer in windows.I tested with STM32CubeProgrammer V2.10 and 2.12, same results.I have linux mint 20.3 Luna

(Project meant to run on STM32L4R9I-EVAL attached)Ultimately, I am trying to put my device into DFU mode by having the device erase its own flash and reboot into system memory (the erase and reset code executes from RAM). Then flash firmware to the device via STM32CubeProgrammer and have the device automatically restart into this newly flashed firmware without having to remove power from the device.The problem I am having is that after the device successfully wipes itself, boots into system memory, and is re-flashed, it restarts back to system memory (DFU). The BOOT0 pin is pulled low but regardless of my option byte user configuration in FLASH, or the MEM_MODE in SYSCFG, the device keeps booting back to system memory. If I fully power off the device or toggle any user configuration option bytes in flash (using STM32CubeProgrammer), it will boot into main flash. I need it to restart into main flash without changing option bytes or power cycling. I have tried all valid combinations of o

When using STM32CubeProgrammer and Silicon Labs CP2102 for USB-UART bridge, DTR state does not become "1 (Low)" when read unprotecting. No problem with FTDI FT232RQ.Our system uses DTR for RXD control, so if DTR is 0 (High), communication is not possible.Is it possible to fix STM32CubeProgrammer?

Trying the program STM32H750B-DK discovery board using STM32CubeProgrammer, but it fails. Here is the log: 08:47:43 : STM32CubeProgrammer API v2.11.0 | Linux-64Bits  08:47:45 : ST-LINK SN : 0036004A3137511133333639 08:47:45 : ST-LINK FW : V3J10M3 08:47:45 : Board    : STM32H750B-DK 08:47:45 : Voltage   : 3,28V 08:47:45 : SWD freq  : 24000 KHz 08:47:45 : Connect mode: Normal 08:47:45 : Reset mode : Software reset 08:47:45 : Device ID  : 0x450 08:47:45 : Revision ID : Rev V 08:47:45 : Debug in Low Power mode is not supported for this device. 08:47:46 : UPLOADING OPTION BYTES DATA ... 08:47:46 :  Bank     : 0x00 08:47:46 :  Address    : 0x5200201c 08:47:46 :  Size     : 308 Bytes 08:47:46 : UPLOADING ... 08:47:46 :  Size&nb

We are using STM32U575VGT6 MCU with 1 MB Flash(Two Banks of 512 KB).We are using entire flash as a single bank, by unchecking DBANK bit in Option byte).Start address of My image is 0x08000000 but when image size exceeds 0x8000(i.e. image spread across both bank), Then STM32CubeProgrammer write only upto 0x0807FFFF. (Facing same issue when download using IAR ).Then i tried to debug further and found that if i follow following steps then its work.Erase entire flash using STMCubeProgrammer (Full Chip Erase)Download the image(downloads succeeds with both IAR/STMCubeProgrammer).Repeat step 1 and 2 to re-download.Please help me to resolve the issue so that i would not require to erase entire flash every time manually. I think programmer shall erase all sectors of image and download the new image with out needs to be erase manually.For you info using ST link V2 programmer Thanks in Advance!!

Hi,I am attempting to jump to system memory to be able to update the firmware via UART. Due to design constraints, BOOT0 pin will not an option for accessing the bootloader thus jumping to system memory within the application is needed.I'm using the following code to jump to system memory: __enable_irq(); HAL_RCC_DeInit(); HAL_DeInit(); SysTick->CTRL = 0; SysTick->LOAD = 0; 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();In AN2606 there is a note for MCUs that use the dual bank feature, I believe this is the part that is preventing the system from bootloading correctly. I jump to system memory in main() and using STM32CubeProgrammer attempt to connect via UART. However, it timeouts since there is no response from the ST chip.I've tried this code both on my dev kit and custom

Running STM32CubeProgrammer v2.11.0, Mac version. It shows update is available, but update screen show current version is v2.11.0 and "No update available". The Updater is v.1.3.3 as shown on screen.After manually update by downloading from ST site, it is updated to latest version. But when clicking Connect button or any other button, it just locks up and no response at all.I have removed previous version and reinstall many times and still get the same result.Downgrade to 2.11.0 and it works again.

For everyday work I use ST-LINKs. Recently a customer gave me a JLINK for a board with a new QSPI flash chip, for this chip I could not find a ready external loader.Nevertheless the J-Flash software can program this chip, knowing only the the MCU and QSPI pins.It does this probably by decoding the built-in parameters table of the flash.Can CubeProgrammer do the same?Or is there already a smart QSPI flash programmer that works with ST-LINK?

Hello everybody!Our company's QA reported some devices with STM32U585VIT6 CPU in a state when write to Flash became impossible.As a developer, I tried to reproduce this and after some experiments got stuck in a strange state when HAL_FLASH_Unlock returns error. Cannot say exactly which steps led to this result. First I set RDB option byte to BB, then to AA in Cubeprogrammer. Changed WRP1A_PSTRT and WRP1A_PEND. And now:- write to Flash and OBs from software is impossible due to permanent HAL_FLASH_Unlock() error,- reset doesn't help,- at the same time chip can be programmed via J-link and ST-link.No such case described in errata sheet nor in forums. Below are option bytes read by Cubeprogrammer.STM32_Programmer_CLI -c port=swd freq=1800 -ob displ     -------------------------------------------------------------------                      STM32CubeProgram

I have an STM32F030K6T6, I 'm using STM32CubeProgrammer with ST-Link V2.I click 'connect' and I get this error:'Error: Data read failed'It gets connected to the MCU, reads correctly it's ID.I have checked all related connections: SWCLK, SWDIO, RST, 3V3 and GND. (I 'm not using the SWIM).Everything looks ok.I 've tried both options of BOOT0 (grounded & pulled up to 3V3).So what might be the problem? A damaged MCU? (maybe I overheated it during soldering)And if it 's damaged how does it get recognized by the STM32CubeProgrammer?

We are pleased to announce you that the official release of STM32CubeProgrammer v2.12.0 is available for download here.New Features (only some highlights):Script manager: add loops and conditional statements.STM32MP1: New SSP GUI.STM32 Trusted Package Creator: enhanced SFI UI.STM32WB: UI enhancement and better error handling.STM32WL: add module support.External flash memory programming: New SFIx Flashloader for B-U585I-IOT02A board.STM32F746GDISCOVERY and STM32F7508-DK: new external flash loaders.Main issues fixed in STM32CubeProgrammer 2.12.0:Only a sub-set of the fixed issues are mentioned below:[116538] [STM32CubeProg] Address is always equal to 0x0 when saving .bin as .hex file.[117842] [STM32CubeProg - STM32L0] EEPROM banks are erased for one EEPROM bank selected.[119632] [STM32L5][TZEN - Regression] Error occurred when TZEN regression field is checked.[122194] [API][ST-LINK] No error message displayed when the MCU is not powered.[122254] [STM32CubeProg - Documentat

Hello!I am trying to use the STM32CubeProgrammer API to create my own application with a simple GUI in C++. Currently my solution is compiling the STM32CubePrgAPI as static library and then include it in a MFC project.Basically user clicks OK from the GUI and then Example2 is executed. The getSTLinkList function executes with no issues, but connectSTLink fucktion gives me this error.int connectStlinkFlag = connectStLink(debugParameters);   0xC0000005: Access violation executing location 0x0000000000000000.If I compile STM32CubePrgAPI as .exe, it works with no problems.What am I not understanding? Is compiling it as a static library a valid choice? What other options do I have?I can't find any examples of applications created using this API. Has anyone done something like this?

HiI am struggling with the UART bootloader.My problem occurs when my firmware is greater than 128Kbyte. If it’s greater than 128Kbyte I get an error message with “operation exceeds memory limits.If I am doing the same with the ST-LINK interface there is no problem. My STM32CubeProgrammer is the latest 2.11. For both UART and ST-LINK I can read the full code, but I can only program 128Kbyte in UART mode.I can see a difference in the two ways. In the erase flash window only 1024 addresses is been addressed.In the ST-LINK the full memory has been addressed.See my screen shots below. Am I doing something wrong?

I just tried to disable BOOT_CM7 for option-bytes using STM32CubeProgrammer and after applying, I can't connect to the MCU. I tried again with R192 shorted out, but STLink still can't connect to the MCU: "The interface firmware FAILED to reset/halt the target MCU"This is on STM32H747-DISCO board.

1) I am able to connect the STM32-Cube-Programmer in USB-DFU-mode if existing or loaded firmware in to STM32-target-board is not read-protected.Image-1: Able to connect with target boardImage-2: Able to load firmware in to target board2) I am not able to connect the STM32-Cube-Programmer in USB-DFU-mode if existing or loaded firmware in to STM32-target-board is read-protected.Image-3: Not even able to connect with target boardIn this case I am keep getting the DFU connection error,How to resolve this application bug.Programmer seems to be not professionally viable,Has anyone in community found resolution to this application bug.Can anybody in STM comment?

..

I still have problems with the STM32 Programmer with USB connection to Controller in DFU Mode! The programming is running through with a verify error and the controller still has the old programm? See LOG from the programmer! Read and Connect is always possible but programming always comes with verify error? I am using 2.11 CubeProg Any suggestions? 11:29:32 : USB speed  : Full Speed (12MBit/s) 11:29:32 : Manuf. ID  : STMicroelectronics 11:29:32 : Product ID : STM32 DownLoad Firmware Update 11:29:32 : SN     : 206130A74734 11:29:32 : DFU protocol: 1.1 11:29:32 : Board    : -- 11:29:32 : IAP 11:29:34 : UPLOADING ... 11:29:34 :  Size     : 1048576 Bytes 11:29:34 :  Address    : 0x8000000 11:29:34 : Read progress: 11:29:35 : Data read successfully 11:29:35 : Time elapsed during the read opera

..

Hello ST Community,currently I am thinking about how to ensure that different developers working on the same project are able to keep exact results. Building, linking, debugging and flashing process should be reproducible and identical for my purposes. Any recommendations on this?When using STM32CubeIDE I had the problem that the project files, which contain information about the toolchain etc., are very difficult to manage. (XML files containing absolute paths, .cproject, .project files etc. are changing on every startup of IDE).Currently I manage in a separate GIT repository tools like:- GNU ARM Embedded Toolchain- Make- STM32CubeProgrammer- OpenOCDThe firmware is in a separate GIT repository and relies on a Makefile build process. There are only relative paths to the toolchain repository in the Makefiles. This means that as soon as all developers consider the hierarchy of the firmware and the toolchain folder, it should always be possible to reproduce identical results. The Makefile

If I set read protection (RDP=0xBB) on my STM32H7 MCU, it seems that both software reset and hardware reset commands stop working, e.g. I type:STM32_Programmer_CLI -c port=SWD sn=XXXXXXX reset=HWrst -hardRstand nothing happens. Also, the MCU will not reset after flashing if read protection is set to 0xBB. Is this expected behaviour?Edit. After some experimenting it seems that in the GUI STM32CubeProgrammer it is not possible to run the firmware by clicking Run button in MCU core view if RDB is set. I get "Error: Unable to run application"Edit. More experimenting: When I try to runSTM32_Programmer_CLI -c port=SWD sn=XXXXXXX --start -vb 3I get:RUNNING Program ... Address: : 0x8000000 STLink read from (0x08000000) returned: 0x00000020   2nd try fail!   STLink read from (0x08000004) returned: 0x00000020   2nd try fail!   w ap 0 reg 15 PC 0x000EFFFF w ap 0 reg 17 MSP 0x000EFFFF w ap 0 reg 16 xPSR 0x01000000 Warning: The core is locked up Start operation achieved success

New features • Tool updater: can be used to upgrade STM32CubeProg from v2.10.0 to v2.11.0 for all supported operating systems (Windows®, Linux®, and macOS®) • SFI: – SFIx support for STM32U585xx microcontrollers via SWD/JTAG – New SFI/SFIx graphical user interface (GUI) – STM32 Trusted Package Creator SFI GUI enhancement – Support for integrity check with the STM32H7 Series and STM32U5 Series microcontrollers • STM32U5 Series: the GUI supports the RDP regression with password • New bootloader support for STM32L476xx microcontrollers • STM32MP13xx microprocessors: – Flash memory load via USB-DFU/UART – SSP (command-line interface only) – OTP: CLI/GUI Fixed issues90858 [STM32WB][CLI] Optimize FUS, STACK, and USER app upgrading automatically. 104409 STM32H735xx: SFI is very slow over SWD. 109240 Extra option bytes displayed for STM32G030C6: PCROP1A_STRT, PCROP1A_END, PCROP1A_RDP, PCROP1B_STRT, PCROP1B_END, and BOOT_LOCK, SEC_SIZE. 110205 Fix the reading of CHIPID (DBGMCU_DBG_AUTH_DEV

..

When trying to install STM32CubeProgrammer, I get this message come up....."This application was configured to use a bundled Java Runtime Environment but the runtime is missing or corrupted." Can someone please assist me on what may be missing from my PC?I'm running Windows 10.