STM32CubeProgrammer (MCUs)

I did some AI examples at the STM32F4Disco Board. After that Cubeprog. doesn't connect to discoboard.When I connect the discoboard to my PC with usb, PC recognize the board but Cubeprog. doesn't connect to board.Error code is given below.12:45:29 : STM32CubeProgrammer API v1.4.012:45:29 : ST-LINK error (DEV_USB_COMM_ERR)12:45:29 : ST-LINK error (DEV_CONNECT_ERR)12:45:29 : ST-LINK error (DEV_CONNECT_ERR)12:45:40 : ST-LINK error (DEV_USB_COMM_ERR)12:45:40 : Error: Problem occured while trying to connectI think I broke the discoboard st-link firmware.:sleepy_face: I have external st-link V2. How can I update firmware of discobard st-link using external st-link V2?

I have an application built in CubeIDE that utilizes both cores on the H747I-Disc1 board. The M4 core collects data and uses HSEM to notify the M7 core to process it. In debug mode I can run this just fine by first launching the M7, letting it run and then launching the M4 core and stepping through it, (Similar to this guide https://www.st.com/resource/en/application_note/dm00629855-getting-started-with-projects-based-on-dualcore-stm32h7-microcontrollers-in-stm32cubeide-stmicroelectronics.pdf)However when I want to run the release build I typically use the CubeProgrammer to download the bin file to the MCU. The issue is I have no idea how to download both bin files (CM4.bin and CM7.bin) correctly. Do I need to change an offset somewhere in flash? Can I combine the bin files into one?In general I have found the documentation regarding dual core applications for this chip to be pathetic. Even the github examples (https://github.com/STMicroelectronics/STM32CubeH7/tree/master/Projects/STM3

Hello,Please move this to a more appropriate section if required, or let me know if there is a better way to report bugs.I have come across a couple of bugs whilst developing an STLDR for external flash access, note the memory arrangement of the flash used is 4096 4K sectors (MX25L12833F 16MB). Bugs:Under 'Erasing & Programming' not all sectors can be listed and individually erased under the 'Erase external memory' tab. When loading this view the following error is shown: External loader sector number is too big, displaying only the first 4000 sectors. The sector list is also corrupt after index 3999 showing invalid adresses and sizes:Under 'Erasing & Programming' a 'Full chip erase' only requests 0x1FFFFF to be erased before reporting success, not the full flash size. See log:12:05:09:859 : MASS ERASE ... 12:05:09:927 : Flash erase...12:05:10:003 : halt ap 0 12:05:10:003 : w ap 0 reg 15 PC (0x20000000) 12:05:10:004 : w ap 0 reg 17 MSP (0x20000500) 12:05:10:

Hi,I've create my own bootloader with USB DFU functionality. (I need some function that built-in bootloader can't provide)I'm able to read/write/erase application firmware by USB DFU now.however, I find the STM32CubeProg work differently with built-in and my bootloader.with my bootloader, STM32CubeProg will not display the information of sections, and it took more time to sync with device.I'm wondering did I missed something?I think the problem might be the response from MEM_If_GetStatus_FS function.I've seen some example on the internet:#define FLASH_PROGRAM_TIME (uint16_t)50 #define FLASH_ERASE_TIME (uint16_t)50   uint16_t MEM_If_GetStatus_FS(uint32_t Add, uint8_t Cmd, uint8_t *buffer) { /* USER CODE BEGIN 5 */ switch (Cmd) { case DFU_MEDIA_PROGRAM: buffer[0] = (uint8_t)FLASH_PROGRAM_TIME; buffer[1] = (uint8_t)(FLASH_PROGRAM_TIME >> 8); buffer[2] = 0; break;   case DFU_MEDIA_ERASE: buffer[0] = (uint8_t)FLASH_ERASE_TIME; buffer[1] = (uint8_t)(FLASH_ERAS

I have checked the java version (which I have in the PATH as C:\Program Files\Java\jre1.8.0_201\bin):C:\windows\system32>java -versionjava version "1.8.0_201"Java(TM) SE Runtime Environment (build 1.8.0_201-b09)Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)C:\windows\system32>set | findstr JREJRE_HOME=C:\Program Files\Java\jre1.8.0_201I noticed CubeProgrammer_API.dll is a 64-bit compiled with gcc 8.2.0 (MSys2) and STM32CubeProgrammer.exe is a 32-bit compiled with MinGWI have succesfully used the CLI version for interfacing with my ST-LinkV3 but I really would prefer to use the GUI.Thank you

Hi everybody,I use the STM32CubeProgrammer version 2.3.0Following issue occurs during programming of a hex-file:1.) do a mass-erase or a clear of all sectors of the device2.) read out some bytes (for example the first sector)3.) the device-memory tab shows "00" for every byte (and the whole flash)4.) load a hex-file which has wholes or gaps in the addresses For example like this::020000040800F2 :10000000005000208909000819050008190500089A :180028000000000019050008000000000000000019050008190500084E5.) The new hex-file tab shows that the gap from address 0x0800 0010 till 0x0800 0028 will be filled with 0xFF and not with the processor specific "unused/unprogrammed byte" which has to be 0x00.6.) programming the device and read out the first 40 bytes leads to this screenThe gaps from the hex-file are actually filled with 0xFF which is wrong from my point of view.The old STVP don't fill the address gaps with the wrong initial byte. It fills the gaps with the correct device depending initial f

I’m using a FTDI chip (FT230XQ) connects to PC through USB.The FTDI connects the STM32G70 with the UART, REST and BMODE pin.Would the CubeProgrammer supports this architecture? Is there an example hardware connectivity diagram?

I used STM32G070. According to the reference manual RM0454 rev2, it does not exist in this procesor Option byte IRHEN (in User Configuration). But the program allows you to set it.I did it, the processor stopped working, and no Option byte can now be written.How fix it ?Peter

I have a STM32H750 with external flash memory. An external loader was developed from the examples of the STM32CubeProgrammer. But I cannot make it working.When I try to use it in CubeProgrammer errors such conection to device (0x450) is lost, or 0x0.stldr appear. Or sometimes Device not supported. I have equivalent solution for STM32F750 and works fine.I have tried do nothing in functions (init, read, write, ..) and return 1, and still happens!STM32CubeProgrammer 2.1 (linux)ST-Link from NUCLEO H743ZI firmware version V2J33M25 (same happens whit others discoveries).What is wrong!?best regards,César Gomes.

I have a project using a STM32H750 and an external quadSPI flash memory MT25QL128A. I can find an external loader using the STM32H750 and another loader using a larger version of the flash memory, so I thought it should be possible to merge the two loaders to one that suited my setup. But it requires the source and project files for the loaders, and only a few - five - are available with the STM32CubeProgrammer download. So my question is: Where do I find the required files?Regards,Klaus Roy-Poulsen

Does anyone have a decent recipe for creating the ST-Link compatible driver for an SPI NOR device? Using the examples in STM32 ST-Link utility I have been able to create and debug the needed routines to intialize, erase, write, and read my flash in a stand-alone environment created by CubeMX. It has a main() that I just used to call and debug the SPI routines. I am really struggling with how to create the driver that will work with the ST-Link utility. My MCU is an STM32H7 device and the closest example code was for an F7 device. The very limited instructions say to just plunk their example code into the Projects director of your target device, and compile!The practice, especially with changing MCU cores is yielding layes and layers of errors that involve somewhat blindly copying over driver/include/startup files from other H7-based projects. I'm sure I could work through eventually, but seems much harder and error prone than it should be. Does anyone have a recipe for how to create th

https://www.usbgear.com/usb-to-can-bus.htmlhttps://www.kanda.com/products/Lawicel/CANUS

In order to see my microcontroller (G4 series) listed as Dfu device inside STM32CubeProgrammer the USB driver inside windows has to be of type "STM32 Bootloader"But to see it appear inside DfuSE Demo, the USB driver has to be of type "STM Device in DFU Mode". Why is that.I was able to upload a .elf file over dfu via STM32CubeProgrammer.But in DfuSE Demo I don't see the latest code active.I created a .dfu file from .bin file on target address 0x08000000 and use DfuSE Demo to program it. It notifies me that it was done. But the old code is still active in the MCU, also after reset.What am I doing wrong?

Given that Oracle has changed their Java license to a commercial license that many developers and companies will be reluctant to accept, the dependency of STM32CubeProgrammer on it is problematic. Although the documentation suggests that it will work with OpenJDK if you install OpenJFX, I have not been able to get that combination to work, and judging from the commentary on the internet, a lot of developers are having the same issue.Since STM32CubeProgrammer is now the only STM tool that supports newer STM32 uControllers for UART flashing, please consider releasing detailed instructions on how to make it work with OpenJDK.

I am using STM32L072RB microcontroller,new to stm32cubeprogrammer,does all interfaces (UART, USB DFU, I2C, SPI, and CAN bootloader interfaces) support debug and programming ?What hardware changes are required to implement programming features via these interfaces ?Are these interfaces can be multiplexed . for e.g. same UART can be used to send data to PC and can be used to program microcontroller using PC ?Is this software free?Does my current microcontroller supports this or any specific requirements for using these interfaces for programming?

I tried to compile the example project STM32CubeProgrammer_2.2.0/api/project/Qt/STM32CubePrgAPI using mingw32, the project compiles perfectly but doesnt do anything at startup. When I compile it with mingw64 it works. STM32CubeProgrammer_2.4.0 does the same, and is buggy and hangs when I try to write to STM32L0 EEprom section.Any hints about that?

When using the command line version of STM32CubeProgrammer, I notice during the verification process (-v flag), the progress bar follows a sequence like 6%->12%->18%->24%-18%->24%... and ends at 24%, with a successful verification. Picture provided for clarity. I am using STM32L021F4 and STM32CubeProgrammer version 2.3.0.

I updated my tilebox firmware usisg STMCubeProgrammer. I updated the worng firmware version, and now my tilebox doesn't work and I doens't switch on. Is there any way of restoring the original firmaware?

Issue: When I try to start the STM32CubeProgrammer application the splash screen pops up for a short moment but then the application stops immediately. The CLI variant seems at least it's help dump is functional. The TrustedPackageCreator application starts up as well. I tried different ways to solve this issue. Switching between Version 2.2 and 2.3. Uninstalling the Java SDK. The USB driver seems to work properly. At least the attached STM32 BOOTLOADER is listed in the device manager. My colleagues have a similar setup on their machine and the STM32CubeProgrammer application works properly. Any advice how to solve this issue or identify the root cause? So far I was not able to find any CrashDumps on my machine. My environment: Windows 10 1809 17763.914 (defined by IT policy) Java(TM) SE Runtime Environment (build 1.8.0_231-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.231-b11, mixed mode) No JDK or newer version of Java installed. Update: It seems to be related to my users profile

Hi!I tried to use STM32CubeProg version 2.4.0 with Nucleo-L452RE by using repository example : stm32cube_fw_l4_v1150\STM32Cube_FW_L4_V1.15.0\Projects\NUCLEO-L452RE\Applications\USB_Device\DFU_Standalone As shown in the screenshot, the board is able to enumerate itself and after selecting USB interface out of many like UART/STLINK/ OTA it shows USB1 port with serial no. 206XXX, but when trying to load DFU file, its window does not show/ recognise DFU whereas the same is present in the destination folder.Kindly advice where I misunderstood the whole process? Whether Cube Programmer have been tested with any STM32 platform through USB DFU?

HI,   I am using windows 10 with visual Studio 2017. Stm32CubeProgrammer V2.3.0.   I like to use the CubeProgrammer_API.lib in my custom project.   one thing which is not clear to me. what is the purpose of "STM32_Prog_DB.xml" file.  Visual Studio is not generating "STM32_Prog_DB.xml".how you generate this file. if i change the name of "STM32_Prog_DB.xml" then visual studio example stop working. is the name and path is hardcoded inside api ?

Hi,I'm trying to slim down the required files to use the STM32CubeProgrammer CLI tool as mentioned in my other question.I noticed if i was missing the STM32_Prog_DB.xml file from one folder above, the erase operation of the affected sectors fails silently, but no error is reported or mentioned on some firmware files:> .\bin\STM32_Programmer_CLI.exe -c port=COM3 br=57600 P=EVEN db=8 sb=1 -w .\firmware_silent.hex ------------------------------------------------------------------- STM32CubeProgrammer v2.4.0 -------------------------------------------------------------------   Serial Port COM3 is successfully opened. Port configuration: parity = even, baudrate = 57600, data-bit = 8, stop-bit = 1.0, flow-control = off Activating device: OK Chip ID: 0x413 BootLoader protocol version: 3.1     Memory Programming ... Opening and parsing file: firmware_silent.hex File : firmware_silent.hex Size : 25104 Bytes Address : 0x08000000     Erasing memory corresponding

Hi,I'd like to integrate the STM32CubeProgrammer CLI into my own windows tool.Currently I'm investigating on the following questions:What files from installation directory are necessary to use the CLI tool for UART DFU? Can I safely remove some of the dlls, external flashloader files, GUI tools to reduce the size of the tool? (Almost 80 Mb!)Will there be seperate releases of the CLI tool in the future , which do not contain all the GUI tools and libs, or at least a list of neccessary files, updated for each release?Thank you and best regards!

Hi everyone,I am trying to understand the use of CubeProgrammer and CubeMonitor. With CubeIDE you can already program the MCU so what are the other 2 used for ? I read their descriptions in the STM website but I don't understand why they would be used. Thank you in advance.

Hi all, I'm usina a STM32F479 MCU and I'm tryng to build a software that can write and launch another software located in flash memory.The idea is that my main program (that handles the update and lanches the other program) shall be located in flash memory at address 0x08000000 (where the MCU starts executing code at power-on) and my child program shall be located at 0x08010000.Let's call them program A (the main one) and B (the child).Reading the manual and visiting other posts on the forum I understand that I need to relocate the interrupt vector table, so, in the main() of A i wrote:int main(){ SCB->VTOR = 0x08010000; //--relocate interrupt vector tabl callMainOfProgramB(); //-- Function to jump to 0x08010000}In addition to this, i edited the linker script file of A and B with the following:A: flash starts at 0x08000000, size: 64KB: flash starts at 0x08010000, size 1984KThe only problem is that if I flash them both at those addresses (I double checked the programming and the memo