STM32 MCUs Software development tools

HiAs I experienced some problems with 2.1.0, I reverted to 2.0.0 and in that process I seem to have gotten the error:Program "gcc" not found in PATH - "[Discovery options] page in project properties"I followed the instructions found in the stm32CubeIDE user guide https://www.st.com/resource/en/user_manual/um2609-stm32cubeide-user-guide-stmicroelectronics.pdf, but the problem persists.Is there a way to manually clear this from any of the configuration XMLs perhaps?The code does still compile and creates binaries, so the error is just a nuisance.[Edit] spellingBest regardsMartin 

在官网下载的CLT工具链安装包，管理员运行后显示如图报错该怎么办？

I updated the STM3CubeProgrammer to version v2.22.0, and after restarting the app, it started showing a blank page. I was also not able to close the application directly. I had to end the task from the task manager. I uninstalled the latest version and installed v2.20.0, but it is also showing a blank page. Also, in STM32CubeIDE, I am not able to run and debug code. It gets stuck at  "Download in progress". Are both problems related?

Code generation of the attached .ioc file (copy of ST example file of similar name) does not generate clock init for UART4.  This means the example application hard faults.  I see no reason why the UART clock should not be initialised here and would save someone time debugging in the future!In stm32mp2xx_hal.c:void HAL_UART_MspInit(UART_HandleTypeDef* huart) { GPIO_InitTypeDef GPIO_InitStruct = {0}; if(huart->Instance==UART4) { /* USER CODE BEGIN UART4_MspInit 0 */ // TODO: Need this here! __HAL_RCC_UART4_CLK_ENABLE(); /* USER CODE END UART4_MspInit 0 */ /**UART4 GPIO Configuration PH8 ------> UART4_RX PH7 ------> UART4_TX */ GPIO_InitStruct.Pin = GPIO_PIN_8; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Alternate = GPIO_AF4_UART4; HAL_GPIO_Init(GPIOH, &GPIO_InitStruct); GPIO_InitStruct.Pin = GPIO_PIN_7; GPIO_InitStruct.Mode = GPIO_MODE_AF_PP; GPIO_InitStruct.Pull = GPIO_NOPULL; GPIO_InitStruct.Sp

Hello,I found a bug in STM32CubeMX code generation for STM32H7S3.When configuring Ethernet with external clock input (ETH_CLK pin,PD6 with AF4_ETH) as PHY clock source, CubeMX does not generateGPIO initialization for this pin in HAL_ETH_MspInit().Workaround - must add manually:__HAL_RCC_GPIOD_CLK_ENABLE();GPIO_InitStruct.Pin = GPIO_PIN_6;GPIO_InitStruct.Mode = GPIO_MODE_AF_PP;GPIO_InitStruct.Pull = GPIO_NOPULL;GPIO_InitStruct.Speed = GPIO_SPEED_FREQ_HIGH;GPIO_InitStruct.Alternate = GPIO_AF4_ETH;HAL_GPIO_Init(GPIOD, &GPIO_InitStruct);Without this, Ethernet does not work even though all otherETH pins are correctly initialized by CubeMX.Steps to reproduce:1. Select STM32H7S32. Enable Ethernet (ETH)3. Set clock source to external clock via ETH_CLK pin (PD6)4. Generate code5. ETH_CLK pin GPIO init is missing in generated codeCubeMX version: 6.17.0MCU: STM32H7S3Thank you

Please use English on this forum.Translated: The development board is STM32H723, using stm32cubemx for development, debug is disabled, using stlink to burn found that it can be burned, and it can also be debugged, which is very strange! (The development board is STM32H723.) It was developed using STM32CUBEMX. The debugging option is set to "Disabled". Programming with stlink, discovering that it can be programmed and debugged. It's weird! ）Original:开发板为STM32H723，使用stm32cubemx进行开发，debug勾选禁用，使用stlink烧录发现可以烧录，并且还可以调试，非常奇怪！（开发板是STM32H723。它是使用stm32cubemx开发的。调试选项设置为“禁用”。使用stlink进行编程，发现可以编程，也可以调试。这很奇怪！） 

I am facing an issue in STM32CubeIDE on Windows where the I/O Configuration / Pinout & Configuration window is not appearing after creating or opening a project.Normally, when opening the .ioc file, the Device Configuration Tool (CubeMX interface) should open showing the MCU pin diagram and peripheral configuration options. However, in my case, this interface is not appearing.Issue Details:Operating System: WindowsSoftware: STM32CubeIDEWhen I create or open an STM32 project, the Pinout & Configuration view does not open.The .ioc file either does not open correctly or the graphical configuration window is missing.Because of this, I cannot configure GPIO, ADC, UART, or other peripherals.Expected Behavior:Opening the .ioc file should display:Pinout & ConfigurationClock ConfigurationProject Managerwith the MCU pin diagram and peripheral configuration options.What I Have Tried:Opening the .ioc file manually from Project Explorer.Restarting STM32CubeIDE.Resetting the perspective.

Hi,I am using the STMH745 MCU and trying to synchronize the ADC trigger to HRTIM. For HRTIM I set the "ADC Trigger Configuration" as given in figure HRTIM.jpg - it defines only a SINGLE trigger. However, in ADC configuration (figure ADC.jpg), TWO HRTIM trigger outs are visible.Can anyone explain the relation between these two option sets? How to correctly synchronize the ADC trigger to the given value value of a HRTIM timer?Thanks!

Hi,When I worked on the Discovery kit with STM32F769NI MCU it supported in the STM32CubeIDE/MX the  LWIP package (from 2025) with FreeRTOS/V1. Now when I pass my project to NUCLEO-H563ZI I see in the TM32CubeIDE/MX that ST will not support the LWIP with FreeRTOS anymore. FreeRTOS is only v2 in this board.Is someone integrete the LWIP package on NUCLEO-H563ZI with FreeRTOS/v2? The code main files that should be changed from STM32F769NI to NUCLEO-H563ZI  are LWIP/App/lwip.c, LWIP/Target/ethernetif.c/h, LWIP/Target/lwipopts.h, main.c.Is there any project in git that have done this miggration for LWIP package (code from 2025) and using FreeRTOS/v2 in it's LWIP package? Or share with me those 4 LWIP files for NUCLEO-H563ZI board. Thanks.

Hi everyone,I just started developing software for a new project containing on of the STM32L4P5 series microcontrollers. Therefore I bought the NUCELO-L4P5ZG starter-kit to get used to the IDE, HAL and so on. I use the STM32CubeMX IDE (Version 6.16.1) to configure the board and generate the basic initialization sources. Further code writing is done in STM32CubeIDE (Version: 2.1.1).For the beginning I configured three GPIO pins for the LEDs on the board and the LPUART for simple data transfer to terminal on host computer. For the transmission I want to use DMA . After generating the code with CubeMX and implementing some simple blink logic for the LEDs, I added the line HAL_UART_Transmit_DMA(&hlpuart1, buffer, 14); to the main loop. I debugged the code and saw that the code ran into the infinite loop in the DefaultHandler in the startup file startup_stm32l4p5zgtx.s: After searching for two and a half hour I finally found the problem: the generated names for the interrupt h

See Inconsistent pin naming for CubeMX - does the same apply to CubeMX2 ?   (Cross-posting at the request of @Ghofrane GSOURI; again, no label available for "Suggestions")

Hi. I want to use the A HRTIM timer to independently control two MOSFETs. Namely, I have a transformer with the midpoint connected to the positive pole of the power supply, and these two transistors switch the 2 halves of the winding as lower switches to generate 2 half-waves of a sine wave.But I can't configure it in STN32CubeMX for the second output the condition for set. STN32CubeMX "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources must be 0." although the channels are configured as independent. Moreover, before the update there was no such problem. Now STM32CubeF3 Firmware Package V1.11.5Why the problem? 

I've always found it a little irritating:#define CLK_A_Pin GPIO_PIN_0 #define CLK_A_GPIO_Port GPIOFWhy is it deemed necessary to have "GPIO" in one, but not the other? Surely, that should be either:#define CLK_A_GPIO_Pin GPIO_PIN_0 #define CLK_A_GPIO_Port GPIOF("GPIO" in both), Or:#define CLK_A_Pin GPIO_PIN_0 #define CLK_A_Port GPIOF ("GPIO" in neither) (There isn't a label for "suggestion" - so "bug report" is the nearest option)

Hi, I am not sure how to categorize this problem. I have a custom board that I had done an initial software development cycle on STM32CubeIDE. I am working a newer version in VSCode with the STM32 Extension. Everything is working with the exception of one problem. I am using a watchdog on my MCU (STM32L4R9ZGJ6), which triggers while I have the processor halted. I know how to fix this in CubeIDE (Debugger tab, Enable Suspend Watchdogs) but cannot figure it out on the VSCode/GDB side. Below is the launch.json I have so far:{ "version": "0.2.0", "configurations": [ { "cwd": "${workspaceFolder}", "executable": "./build/debug/build/test.elf", "name": "Debug with ST-Link", "request": "launch", "type": "cortex-debug", "runToEntryPoint": "main", "showDevDebugOutput": "none", "servertype": "stlink" }, { "name": "Launch", "type": "cppdbg", "request": "launch", "cwd": "${workspaceFolder}", "program": "${command:cmake.launchTargetPath}", "MIMode": "gdb", "miDebuggerPa

Hi I have created a project using STM32Cube.AI Studio. I am able to successfully run and generate the project from the tool. After that, I can open the project in STM32CubeIDE and build it without any issues.However, while debugging, I encounter the error shown in the image below.I am able to debug the image classification and face detection sample projects provided by ST without any issues. Therefore, I suspect that there may be a problem with the project configuration generated by STM32Cube.AI Studio.The evaluation board I am currently using is the STM32N6570-DK.Please help me to resolve this issue?

I am experiencing a problem with RTOS Proxy in STM32CubeIDE 2.0.0/2.1.0 when debugging a ThreadX application on STM32H753 using a SEGGER J-Link.The same setup works correctly with STM32CubeIDE 1.19.0, but after upgrading to 2.0.0/2.1.0 the debugger aborts during the flash download when RTOS Proxy is enabled. If I use J-Link Kernel Awareness instead RTOS Proxy everything works fine.ConfigurationMCU: STM32H753BIRTOS: ThreadXSTM32CubeIDE: 2.0.0RTOS Proxy: ThreadX / Cortex-M7Debug probe: SEGGER J-Link Ultra+J-Link GDB Server: V8.80Interface: SWDDebug configuration:RTOS Awareness: EnabledRTOS Kernel Awareness: RTOS ProxyRTOS: ThreadX (Cortex-M7)ProblemWhen starting a debug session, the debugger stops at the point where the firmware should be downloaded.The following error appears:Remote communication error. Target disconnected: Not a directory.Failed to execute MI command:load <path>/app_1500_xg.elfwhere <path> is the correct and full absolute path to my elf file.After the

Hello, I am using the STM32H503 MCU. When I configure the pins as follows:PB2 → OUTPUTPA8 → TIM1_CH1PB7 → I2C1_SDAIn the RCC section, I get red warnings for Master Clock Output1 (MCO), LSCO clock output, and SAI1 External clock. I cannot disable these clock settings. Is there a way to do this in CubeMX? How can I resolve this conflict in CubeMX?

Hi,Having just updated to STM32CubeIDE 2.1.1, I've created an STM32CubeIDE Empty Project (the only apparent relevant option) targeting the STM32F072 Discovery Kit as I want to experiment with the touch sensing capabilities, however when the project is created I don't see an IOC file. Has the workflow reverted to using STM32CubeMX to create the IOC file etc. please?Kind regards,Al

Why, oh why have you separated IDE and MX such that .ioc files can no longer be opened in IDE?I cannot imagine any benefits and it makes the IDE significantly worse, such that I've felt compelled to revert to version 1.19.0 ( go to Help -> About STM32CubeIDE -> Installation Details -> Installation History -> select version -> Revert)I couldn't find any other means of feeding back my strong dislike of this change other than a post like this. I hope version 2.1.0 comes out soon and re-integrates MX and IDE!

I am using STM32CubeMX (Version 6.17.0). Here is what happened. I created a PIN name "CLK-A". After some troubleshooting, I found a mistake in my pinout definitions. I named the correct pin as "CLK_A". However, I did not delete the "CLK-A" pin. When the C code was generated for the project, the "CLK-A" pin was defined as "CLK_A" in the output C file. The tool did not flag me that there were two pins with the same effective name. It took me some time to track down the issue. Once I deleted original "CLK-A" pin definition, my design worked. I added "CLK-A" back to the design on another pin". I got "CLK_A<pin name>" in the "header.h" file. The first pin defined seemed to have priority.  

 Hi everyone,I am experiencing issues with Task Aware Debugging (FreeRTOS Task List) in the latest version of STM32CubeIDE. The "FreeRTOS Task List" view is either empty or not populating correctly, despite the scheduler running and tasks executing effectively on the hardware.Environment:IDE: STM32CubeIDE (Latest Version)MCU: STM32H7S3L8H6xFreeRTOS Version: V10.6.2 (CMSIS-RTOS V2 wrapper)STM32Cube 2.0.0Interestingly enough, the runtimestats itsef are working.Does anyone have similar issues?   /* USER CODE BEGIN Header */ /* * FreeRTOS Kernel V10.6.2 * Portion Copyright (C) 2017 Amazon.com, Inc. or its affiliates. All Rights Reserved. * Portion Copyright (C) 2019 StMicroelectronics, Inc. All Rights Reserved. * * Permission is hereby granted, free of charge, to any person obtaining a copy of * this software and associated documentation files (the "Software"), to deal in * the Software without restriction, including without limitation the rights to * use, copy,

why?

Hi all, I've been using CubeIDE for a little while and decided to build my next project using the STM32 VSCode extensions, which I am still figuring out. I am also figuring out CMake for the first time, as I let CubeIDE handle all the build details previously. In the past, CubeIDE let me add .h and .c files through the UI and automatically added them to the build process. I've found that I can make my own files and still build by manually altering the CMakeLists.txt file under the stm32cubemx directory, but I find myself editing the ioc file often enough that I'd rather not do this every single time I want to make a small change, and as the project size grows. All the drivers I've needed so far are part of CubeMX's middlewares, but if I do download a third party driver I foresee this becoming an issue there as well. Are there any workarounds to include manual additions to the generated CMake file? I'd like to utilize an STM feature if possible before I try making my own cmake file

Can someone explain the difference between tools and fonts in a simple way? Like when should I focus on choosing the right tool vs the right font for a project?    

Create a FreeRTOS project, keeping all settings at default configuration. Use CMake for building. The steps for creating the project are as follows:When the first task is initiated, a large number of recursive functions will appear in the function call stack.