STM32 MCUs Software development tools

Hi,I'm trying to move towards developing in VSCode to not rely on VMs for the IDE. While code generation via CubeMX and flashing the device works as expected, I'm having issues trying to use the debugger on my STM32H747 DISCO board.When using the latest (v3.6.4) It kept prompting command not found error.Downgrading it to v2.1.1 seems to fix the issue and the debugger manages to run. However, it seems to always timed out waiting for the other core (CM4) to enters in stop mode. p.s. I am trying to debug the CM7 at the moment.Is there something that needs to be done on the STLink server or .ioc file to make the debugger works? Any help will be be much appreciated 

Has anyone had success installing the Cube IDE on a Raspberry Pi 5?  I first got the error message "Installation dir cannot be temporary one: /home/my_name/Downloads/makeself_dir_o70WRx"I tried various workarounds suggested by Gemini, ultimately creating new directory/opt/stm32_installermoving the unzipped file to this new directory and then trying .../opt/stm32_installer$ sudo ./file_name.shIt went right ahead and created a new temporary folder in opt/stm32_installer and failed in the same way again!If anyone has succeeded in getting the Cube IDE to work on a R Pi 5, please let me know how you did it.Thanks for reading this far.

 You flipped the power on and… nothing. USB won’t enumerate. The device resets intermittently. Or ADC samples at the wrong rate. Before blaming the hardware, check the clock tree and flash latency. CubeMX gives a helpful UI, but you must interpret the numbers — PLL inputs/outputs, AHB/APB prescalers, timer clock doubling, and flash wait states or subtle configuration mismatches will bite you.The big pictureSYSCLK (system clock) drives the CPU and the AHB bus.AHB/APB prescalers split SYSCLK into peripheral bus clocks (APB1, APB2). Peripherals (UART, SPI, I2C, ADC, timers) use these derived clocks.PLLs are used to multiply/divide crystal or internal oscillator frequencies to reach the target SYSCLK and special 48 MHz domain for USB, RNG, etc.Flash latency (wait states) must be configured so the CPU can read Flash at the chosen SYSCLK. If flash latency is too low the CPU will fetch wrong instructions → crashes or strange behavior.Voltage scaling / power range often limits maximu

The project is a TouchGFX demo running on the STM32H735G-DK.Building works (vscode+plugin+cmake+clang). Flashing works with STM32CubeProgrammer.Debug/flashing doesn't work with STM32Cube plugin, it does work with cortex-debug plugin with a custom launch.json file. Since that is incompatible with the plugin it will require using VSCode profiles and switch between them constantly.If I try to debug using the plugin I get this:STMicroelectronics ST-LINK GDB server. Version 7.11.0Copyright (c) 2025, STMicroelectronics. All rights reserved.Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : EnabledInitWhile : EnabledWaiting for debugger connection...GNU gdb (GNU Tools for STM32 13.3.rel1.20250523-0900) 14.2.90.20240526-gitCopyright (C) 2023 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>This is free software

Hello,while configuring the CSI interface for camera , on its enablement in the STM32CubeMX why I can’t see the GPIOs corresponding to it in the flip section? does it has any dependency on any other peripheral?or clock setting?under the configuration it says warning: this peripheral has no parameters to be configured.Unlike in any other peripheral like I2C or  SPI where I can see the corresponding GPIO i am checking this on STM32N657X0HxQ .regards, 

Using an STM32H7Rx or Sx, using I2C2 clocked by PLL3R at 10 MHz:If you set the I2C speed to 10 kHz with analog filter disabled, you get a timing value of 0x1010F1FF, with SCLH and SCLL values of 241 and 255. This seems reasonable.However, if you enable the analog filter, you get 0x400007BE. This does produce the correct frequency - but the SCLH and SCLL values are 7 and 190, which do not appear to be sensible.Is this a bug?(I've sent an IOC file to @Souhaib MAZHOUD ; you'll need to edit the I2C2 settings to see this happen.) 

The login via HELP->STM32Cube Updates->Connection to myST   does not seem to be working properly. Trying to login I first get a small splash window with a button which I can press which opens a webview(?) which sometimes displays an "Accept Cookie" dialogue. That seems to go away by itself, but I am unfortunately unable to enter anything into the username and password fields, they are unresponsive.I'm using Wayland on Linux, but my colleague running on MacOS is experiencing the same issue.Browsing through the forum, the advice I find seems to be "try again tomorrow, there seem to be issues on ST's side of things".  Is there currently maintenance going on? Is the CubeIDE backend particularly slow at the moment, or is this how things always work with Cube?

in default situation, you could not call c++ function in C file.  So the main.c  is not suitable file in C++ project.   if user choose C++ project,the generated main.c ,stm32h7xx_it.c should sufixed with .cpp.

Hi all,I recently updated the IDE to v1.19 and MX to v6.15.0, and the MX code generation is no longer working for me.After some testing, I found out I can create new projects and code is (apparently) well generated. After this first generation, if i change anything in CubeMX and regenerate, the .ioc file is updated accordingly but the code is not changing at all.My device is STM32U575VG (FW package 1.8.0).As an example I created a project with just TIM1, generated the code, added TIM2 through CubeMX and renegerated.I attach the first .ioc file (DELME_New_Project.ioc) and the updated (DELME_Updated_Project.ioc) for reference. The code has not been updated:Any ideas? Am I missing something? Is anyone else facing this problem?Alex   

Hello,I am trying to use STM32Cube Monitor USB PD with custom board.I see ST link v3 minie on a trace port. but I can't see any traces at all. Is there a dedicated package in CubeMX i can enable to see USB-PD traces ? Thank you. 

Hello Team,To address mass Programming of Customized board , Looking help to have Batch File / Python Script which accomplishes Following Task :1. Flash The Hex file2. Set RDP13. Read UID (96-bit ) of MCU4. Log UID and Time into CSVI tried with batch File using STm32Cube Programmer CLI.exe , but Failed to connect with ST-Link.yes, I am Using SWD Debug Interface. I am not sure uf any scripting Template is alraedy ready with CubeProgrammer.   

MCU : STM32U5G9ZJT6QExternal Flash : MX25LM51245GSPI Interface : HSPI1 When I use STM32_Programmer_CLI.exe I cannot erase the external flash.Board info:      I get following error from STM32_Programmer_CLI.exe: STM32_Programmer_CLI.exe -c port=SWD -el "C:\Users\USER\Desktop\Workspace\External_Loader\MX25LM51245G_STM32U5G9ZJ\Project\EWARM\Debug\Exe\MX25LM51245G_STM32U5G9ZJ.stldr" -e all-------------------------------------------------------------------STM32CubeProgrammer v2.20.0-------------------------------------------------------------------ST-LINK SN : 56FF70067287555130422267ST-LINK FW : V2J46S7Board : --Voltage : 3.21VSWD freq : 4000 KHzConnect mode: NormalReset mode : Software resetDevice ID : 0x476Revision ID : Rev ZDevice name : STM32U5Fx/5GxFlash size : 4 MBytesDevice type : MCUDevice CPU : Cortex-M33BL Version : 0x90Debug in Low Power mode enabledMass erase ...Error: Mass erase operation failed.Please verify flash protection How ca

OS: Ubuntu 24.04.2CubeProgrammer Version: 2.20.0Board: STM32F407G-DISC1Firmware Version: V15J63M63I am having intermittent connectivity issues with my discovery board and the STM32 IDE/Programmer. My system is able to detect the discovery board as it shows up when using the Linux command: lsusb. When launching the CubeProgrammer application it is able to (sometimes) detect the board after configuring the settings properly; after which the board setting are populated (see pic below)When trying to connect to the board, however, I receive fluctuating error message (see pic below). It is either the DEV_USB_COMM_ERR or the No debug probe detected errors. I am not sure what causes the errors to change but it usually happens when I reset the board because CubeProgrammer was unable to detect it and I am attempting to reestablish the connection (just having the board detected, not pressing the CONNECT button).The LD1 color is also intermittent and goes from RED to GREEN depending

STM32CubeIDE Version 1.19.0Build: 25607_20250703_0907I created a project using the STM32F107 and Ethernet. Everything was setup using the .ioc template with Ethernet and various GPIO stuff. Lwip was not included. I generated the code and all of the Ethernet configuration was created. Compiling the code worked with no errors.I have not connected my board and tried to program it as I just wanted to see if CubeIDE would generate the code properly for the STM32F107 part.I then re-opened the .ioc file and enabled Lwip since that was my goal. Now when I generate the code, it removes all of the Ethernet setup code. This means none of the Ethernet RMII pin mapping is in place and none of the Ethernet files are in the project.Is the STM32F107 no longer supported for Ethernet+Lwip applications? I just need a simple application with 2 buttons to control 2 relays. An STM32F7xx is overkill.I think I remember reading somewhere a couple of years ago that ST was no longer going to support Ethernet for

Hello,Do you think it's possible to flash an ESP32 through a STM32 using a .stldr and the CubeProgrammer ?Same way we flash an external memory through SPI interface.The ESP32 is interfaced with the STM32G4 through a UART.I just want to know if this can be done, and if someone already did it ?Thank you

Hi everyone,I’m working with STM32L010K4T6, which is based on the ARM Cortex-M0+ core.I’d like to use FFT (Fast Fourier Transform) functions in my project, preferably within STM32CubeIDE.However, I noticed that the CMSIS-DSP library (which provides FFT functions) seems to have limited or no direct support for the L0 series inside CubeIDE.My questions are:Is it possible to add and use the FFT / CMSIS-DSP library with STM32L0 series MCUs like STM32L010K4T6?If yes, what is the recommended way to integrate it in STM32CubeIDE (manual CMSIS-DSP source import, or any ready package)?Are there any performance or memory constraints I should be aware of when running FFT on Cortex-M0+?Thank you in advance for any guidance!Best regards,Burak

Hi,Using STM32CubeMX version 6.15.0When I start a new project from the NUCLDO-F767ZI board I just get a blank chip, none of the component configuration at all, I tried it on two PC's both the same.This used to work and was quite handy starting a new project.  At the moment I am going through a selection of processors so having to manually configure it before I can test it is a bit of a pain, any solutions? 

I am experiencing issues when attempting to upload the code to the MCU mentioned above on my board. I am trying to upload the code using the programmer on the STM32F407 Discovery board. It reads the chip, it erases the chip, but it does not upload the code. What could be the reason? The log file and the schematic of the MCU section of my board are below. Thank you for your assistance.  08:47:43 : MASS ERASE ...08:47:43 : Mass erase successfully achieved08:47:43 : UPLOADING ...08:47:43 :  Size         : 1024 Bytes08:47:43 :  Address      : 0x800000008:47:43 : Read progress:08:47:43 : Data read successfully08:47:43 : Time elapsed during the read operation is: 00:00:00.01008:51:28 : MASS ERASE ...08:51:29 : Mass erase successfully achieved08:51:29 : UPLOADING ...08:51:29 :  Size         : 1024 Bytes08:51:29 :  Address&nbs

Hi Support team, I am working on the FREERTOS based project and i need to disable the code generation for pendsv handler, systick handler, svc handler . As this handlers are written in freeRTOS, I am getting error for multiple definations. I have seen the option to skip the code generation in previous versions of the software but now i am not able to do so. you can see an empty page in code generation option. Please help solve the issue.    

Hardware: STM32L071CZTXSoftware Versions:STM32CubeMX 6.14STM32CubeIDE 1.18Problem Description:I'm experiencing code generation issues with both Cube software tools on an existing STM32L071CZTX project:Issue 1 - STM32CubeMX 6.14:Code generation process gets stuck and becomes unresponsiveOnly way to terminate is through Task Manager (killing OpenJDK Platform binary process)Issue 2 - STM32CubeIDE 1.18:Code generation fails when modifying clock parametersNo code is generated after clock configuration changesSteps Already Taken:Performed complete uninstallation of all STM32 softwareFresh installation using newly downloaded files from ST websiteVerified MyST account login on both applicationsRequest: Has anyone encountered similar issues with these software versions? Any guidance on resolving these code generation problems would be greatly appreciated.Thank you for your assistance. 

Hi, I tried to build my project but I faced these errors :--------------------------------------------------------------------------------------------------------------------------------------------------C:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-closer.o): in function `_close_r':(.text._close_r+0xc): warning: _close is not implemented and will always failC:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eab

I'm trying to track down a memory corruption bug in my code. I can setup a Watchpoint for a specific variable (Expression to watch: *(uint32_t*)0x20024840), and get the debugger to stop at a breakpoint whenever the variable is written to (good!).However, my problem is that 99% of the time, it's a legitimate/intended write, and I'd like it to NOT break at those locations so I can focus on the problem area.I've tried using the "Conditon:" field in the breakpoint property in 3 different ways:1) Ignore breakpoint if at a specific address:  $pc != 0x80201cc2) Ignore the breakpoint if in a specific function:  !$_is_in_function("my_func")3) Ignore the breakpoint if the value being written to the variable is within a range:  *(uint32_t*)0x20024840<3000||*(uint32_t*)0x20024840>4000In all 3 cases, it seems to have no filtering at all. I hit all the breakpoints any time the variable is written to no matter what I write on the "Conditon:" box. Is my syntax wrong? Do I need to

Hello,I have an STM32G474RE Nucleo board configured in Dual Regular Simultaneous Mode for ADC 3/4 using CubeMX. I noticed some strange behavior with ADC 4, specifically that its conversions freeze after operating for some length of time. I thought I was experiencing a software problem on my end, but after much testing and ordering another board, I believe the issue is inherent to the STM32G474RE. When I configure a simple test for ADC pair 1/2 with DMA, using Dual Regular Simultaneous Mode and triggered by a timer, and separate the resulting conversions into two 16-bit values in the debugging window, no issues arise. But when I repeat the test and only change the ADC pair to ADC 3 (master) and ADC 4 (slave), the conversions from ADC 4 freeze every time after some length of time. I also noticed that any other code makes the problem worse. For example, if I poll SPI Transmit/Receive in the while loop in main, the readings from ADC 4 freeze almost immediately. I even tested a simple "cnt_

Hello,I’m using an STM32F429I-Discovery board with an MT9M001 camera module, trying to display the camera image on the board’s built-in LCD.However, I found that the following pins conflict between the DCMI and LTDC functions (please correct me if I misread the pin mapping):PA4: DCMI_HSYNC vs LTDC_VSYNCPA6: DCMI_PIXCLK vs LTDC_G2PC7: DCMI_D1 vs LTDC_G6PB8: I2C1_SCL vs LTDC_B6PB9: I2C1_SDA vs LTDC_B7In this situation, what is the typical way to handle such pin conflicts?Would it be necessary to change the board or the camera module?Any advice would be greatly appreciated.Thank you in advance.

This software has too many bugs. Could the developers please look into the main issues? 1. If the downloader fails to connect, it spams dozens of error messages. 2. Frequent freezing, primarily when the downloader fails to connect—the software gets stuck and can't even be closed, which severely impacts usability.