STM32 MCUs Software development tools

 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? 

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

Create a FreeRTOS project, keeping all settings at default configuration. Use CMake for building. The steps for creating the project are as follows:

Dear STM32CubeIDE Support Team,while analyzing the memory usage of my STM32 project, I noticed a potential inconsistency in how memory units are displayed in STM32CubeIDE.Both the Build Analyzer and the memory overview label the values as “KB”, but the reported numbers clearly correspond to KiB (1024 bytes) rather than kB (1000 bytes). This behavior matches the output of arm-none-eabi-size, which reports sizes in bytes.For example:arm-none-eabi-size reports Flash usage as:text + data = 64824 + 148 = 64972 bytesConverted to kB (1000 bytes), this would be:64.972 kBHowever, STM32CubeIDE displays:64972 / 1024 = 63.45 KiB, while labeling the unit as “KB”As a result, summing RAM and Flash values only produces consistent re

Hi, I want to know when the C/C++ Indexer will be updated to the latest C standard, that is, C23? I want to use some new language features, like double square brackets for attributes, but it still shows a syntax error, even though the code compiles without problems.Also, I would like to know when GCC 15 will be available. Best regards,Artur 

I've just installed the new STM32CubeIDE 2.1.0 and I came across some issues that didn't exist in previous versions.First, I noticed that the compiler always compiles all the source files even though only one source file was modified. I have large project with many source files and it takes about 2 minutes to compile all files. It's very annoying.Second, when launchinig debug session all the source files are compiled again. It didn't work that way in previous versions of STM32CubeIDE. If the files were compiled previously, the debug session was launched immediately.Is it possible to change this behavior but turning off some options or do I have to install older version of STM32CubeIDE ? 

A few days ago I updated STM32CubeIDE from version 2.0.0 to 2.1.0. (Build: 27993_20260219_1630 (UTC))Now there is a problem. There seems to be no longer any such thing as a "partial" build. Example: My project consists of about 50 ".c" and ".h" files. In the old version, if I edited one of the ".c" files and did a build, only the file that was edited got re-compiled, followed by (as expected) linker and hex file generator. Now, in this version, every build re-compiles ALL the files, even if nothing was touched since the last build. This is time-consuming. How can I stop this and get it to re-compile only the changed files? (If it matters, target CPU is STM32H753BIT6; using FreeRTOS and FATFS.)

Cube IDEIf i create / Import STM32 ProjectI only got these options to pick from and i have the feeling something is missing.  So i select:- STM32CubeIDE Empty Project which leads me to this:So i select my MCU: STM32G474RETx (for example).This leads me to this:

I found what looks like a reproducible STM32CubeMX code generation bug for STM32H5 USBX device projects.I tested this on a fresh project, so this does not appear to be a migration issue from an older codebase.ProblemCubeMX generates these USBX init functions:MX_USBX_Init()MX_USBX_Device_Init()MX_USBX_Device_Stack_Init()However, the generated call flow only invokes:MX_USBX_Init()MX_USBX_Device_Init()and never calls MX_USBX_Device_Stack_Init().That is a problem because MX_USBX_Device_Stack_Init() contains the actual device stack setup:ux_device_stack_initialize(...)class registrationux_dcd_stm32_initialize(...)Without that function running, the USB peripheral can start and receive a reset interrupt, but USBX has not been given valid device framework pointers yet.Observed failure

I'm using STM32F2xx, STM32F4xx, STM32F7xx and STM32L0xx firmware supplied by STM32CubeMX. I need to generate an SBOM for cybersecurity purposes. Can ST provide that or provide documentaiton that can be referenced to generate the SBOM?

Hello,With the new STM32Cube Debug Jlink GDB Server V1.2.0 I'm not anymore able to start the debugging session. If I downgrade to V1.1.0 then it is working again. I get always the error message "No GDB Server running". I tried that with my old launch.json settings and with the new generated and adapted json settings.Do I miss some special settings or has the new extension a bug?Or do i need any dependency? error message: old launch.json

There is no USBX or other middleware in my cubemx2, but the connection introduction indicates that it is available. How to access middleware & utilities - STM32CubeMX2 1.0.0 documentation    

The STM32CubeIDE project output setting is not present in STM32CubeMX2. Is there a way to generate a project that STM32CubeIDE can use? How do I do this? I did try the "CMake" option but wasn't able to get a project to import correctly.

안녕하세요 STM32N6570-DK의 사용하기 위한 cubemx 설정이 필요합니다. 카메라, lcd, sd카드, usb, eth 등 기능을 다 살린 cubemx 설정 또는 ioc 파일을 받고 싶습니다. 확인 부탁 드립니다.   Hello, I need a cubemx setting for use of STM32N6570-DK. I would like to receive a cubemx setting or an ioc file that utilizes all the functions such as camera, lcd, sd card, usb, eth, etc. Please check it.

Hi,among probably many other registers, the ITM registers like TCR and Stimulus Port Registers described in the ITM programmers model in ARM Cortex-M7 Processor TRM are missing. Which means I either have to adapt the svd file or go to memory view and translate and modify the registers manually. Is this on purpose and or are there plans to fix this? If you have a repository somewhere I can maybe fix that on my own and start PR.Ty in advance

I am setting up my STM32F303RET6 for four differential inputs to be sampled simultaneously. As seen in the screenshot attached. there is no option for differential inputs on CubeMX. Am I missing something here? I have reset whole project to ensure no pins are assigned elsewhere.

Hi everyone,I found a solution for a common issue when using the official STM32Cube for VS Code extension. If you disable the Microsoft C/C++ (ms-vscode.cpptools) extension to avoid IntelliSense conflicts, you might notice that "Format Document" stops working completely.The reason is that the STM32 extension's built-in clangd has its formatting engine disabled by default.To fix this:Go to VS Code Settings (Ctrl + ,).Search for: stm32cube-ide-clangd.enableFormatting.Check the box to enable it.If prompted, set "STM32Cube for V

Hi,I am using the latest version of STM32Cube extension for VS Code (3.8.0). I created a simple project for STM32H735G-DK board using CMake as the toolchain and ST-ARM-CLANG as the compiler. I do not know if it is relevant, but I also enabled FreeRTOS and configured the USE_NEWLIB_REENTRANT option to Enabled.I generated the project and I am compiling it with VSCode. I changed in the starm-clang.make to use the NEWLIB instead of the PICOLIBC:set(STARM_TOOLCHAIN_CONFIG "STARM_NEWLIB")The compilation works, but clangd complains about some errors. In the output of clangd, I can see multiple instances of:D:\ST\stm32cube\bundles\st-arm-clang\21.1.1+st.6\bin\..\lib\clang-runtimes\multilib.yaml:47:3: error: unknown key 'IncludeDirs' IncludeDirs: ^~~~~~~~~~~ D:\ST\stm32cube\bundles\st-arm-clang\21.1.1+st.6\bin\..\lib\clang-runtimes\multilib.yaml:21:1:

Is it ok to use different build configuations for different pinout version?As you may have experienced, sometimes pcb version how the pinout. Sometimes another UART or TIMER is used in another pin etc,... Is it ok to  use different build configuations for different pinout version?

A few direct questions about the current CubeMX2/HAL2 split. Are older STM32 series expected to stay on HAL1 + CubeMX permanently, or is there an actual plan to migrate them to HAL2 + CubeMX2? What is the long-term support model here?Are these two stacks supposed to coexist for years, or is HAL1/CubeMX effectively going into maintenance mode? Is there any official migration guide planned?Both for HAL1 → HAL2 API migration and CubeMX project → CubeMX2 project migration. How is the VS Code extension supposed to work with both ecosystems in practice?If one project is on CubeMX/HAL1 and another is on CubeMX2/HAL2, what is the intended workflow?Is proper support planned for both, or is the tooling mainly targeting the new stack? Where is the actual HAL1 vs HAL2 side-by-side data?Flash usage, RAM usage, performance, code size, same project, same MCU class, comparable buil

Hi,I found the same issue as in.https://community.st.com/t5/stm32cubemx-mcus/found-a-bug-with-the-latest-rev-of-stm32cubemx-rev-5-3-0/td-p/279154(thank you @MSilv for reporting this btw).Since a STM32CubeMx update and STM32F4 Cube update, the generated main.c is missing two lines in the end of the generated void SystemClock_Config(void) function :LL_Init1msTick(100000000);LL_SYSTICK_SetClkSource(LL_SYSTICK_CLKSOURCE_HCLK);The update was quite a big leap :CubeMx: from 5.2.1 to 6.16.1STM32Cube FW_F4: from 1.24.1 to 1.28.

Recently I’ve been learning about the updated STM32 software ecosystem, including the new HAL2 library and STM32CubeMX 2 tool. I have a few practical questions and would like to start a discussion with all STM32 developers here.   What are the new characteristics, improvements and advantages of HAL2 compared with the traditional HAL library?   Can STM32CubeMX 2 still support earlier and older STM32 MCUs, or does it only serve the latest chip series?   For those legacy STM32 microcontrollers, are they able to use the new HAL2 library, or can they only run the classic HAL as before?   If you have relevant development experience or official information, welcome to share your views and explanations.  

Hi all,   in the release note of the STM32C5 family it is mentioned that the family will be supported with STM32CubeMX2. May I please ask when is it going to be available?    With best regards, Dmitry

Hi everyone, I have a quick question regarding the upcoming release of CubeMX2 and its backward compatibility. Once CubeMX2 is released, will the older series before C5 (like the F4) support MX2 and HAL2? Also, if they do support it, will we be forced to bundle HAL2 for these older models, or will there be some flexibility? Thanks in advance for any insights or official clarification! Best,Leo