STM32 MCUs Software development tools

I was able to install and open the STMCubeIDE for my macbookpro with M1 apple silicon. But cannot obtain .iop files as the STMCubeMX plugins .mx and .mcu do not unpack and get installed. I have checked my firewall and any blockages created by mac but nothing is being blocked in quarantine or privacy as well. I tried to completely delete and reinstall the software 5 times but nothing is working. As the plugins are default no manual intervention can be done as well. Please help!

So here is a weird thing I've noticed with a STM32U073... CubeMX shows that this CPU has the "Trace Asynchronous SW" option, but for this mcu it is no longer listed under SYS, but under its own category: "Trace and Debug" -> "DEBUG". Anyway, after enabling it, the signal shows up on the graphical pinout, with the name "DEBUG_JTDO-SWO". This is pretty much the same as i was used to with other STM32 mcu's. So when i was designing a PCB for this new STM32U073 MCU i assumed it had support for SWO (or SWV or whatever the name is). But now when I'm trying to debug this MCU, the debugger doesn't allow me to enable "Serial Wire Viewer (SWV)" in the debug configuration properties of STM32CubeIDE. The option is just greyed out. So I did some more digging in the datasheet for the STM32U0, and I'm starting to wonder if it even has support for SWO/SWV?  Can anyone enlighten me? Is this just a problem with the debug config in STM32CubeIDE, or does the STM32U0 have no SWO/

Hello ST community I'm trying to install SetupSTM32CubeProgrammer-2.16.0.linux in docker But getting error like below root@1694a12cc06d:/home/app/en.stm32cubeprg-lin-v2-16-0# ./SetupSTM32CubeProgrammer-2.16.0.linux./SetupSTM32CubeProgrammer-2.16.0.linux/home/app/en.stm32cubeprg-lin-v2-16-0chdir /home/app/en.stm32cubeprg-lin-v2-16-0/.current dir /home/app/en.stm32cubeprg-lin-v2-16-0SEVERE: com.izforge.izpack.api.exception.IzPackException: Console implementation not found for panel: com.st.CustomPanels.AnalyticsPanels Thanks in advance.

STM32Cube MCU Package for STM32U0 Series 1.3.0  + STM32CubeMX 6.15.0 + STM32U083RCT6You can configure the SWO output in the configurator (CubeMX), but in fact, SWO is not present in the microcontroller. 

Hi I am using STM32H7S78-DK.I don't understand how to use the compare tool in cube mx project.My project consists boot and application software, i.e., a total of four different software versions. Which software does the compare tool compare? How can I select the software?    

I'm running into a strange issue: the following function compiles cleanly on one machine but triggers a compiler error on another. Both machines are running the same version of STM32CubeIDE (2.0.0), and the project is shared via a Git repo on Azure DevOps.Here is the function in question:#ifdef __cplusplus extern "C" { #endif #include "aws_iot_json_utils.h" #include <stdio.h> #include <inttypes.h> #include <stdint.h> #include <string.h> #include <stm32l4xx.h> IoT_Error_t parseUnsignedInteger8Value(uint8_t *i, const char *jsonString, jsmntok_t *token) { if(token->type != JSMN_PRIMITIVE) { IOT_WARN("Token was not an integer"); return JSON_PARSE_ERROR; } if(('-' == (char) (jsonString[token->start])) || (1 != sscanf(jsonString + token->start, "%" SCNu8, i))) { IOT_WARN("Token was not an unsigned integer."); return JSON_PARSE_ERROR; } return SUCCESS; }And here is the compiler error:../Controller/mqtt/aws_iot_json_utils.c:84:101: error:

Following the directions in https://docs.zephyrproject.org/latest/boards/st/stm32n6570_dk/doc/index.html images signed using STM32_SigningTool_CLI version 2.20.0 run OK on the board.However, after upgrading to STM32CubeProgrammer 2.21.0, images no longer run (I believe the signature check is now failing on the device).Reverting back to 2.20.0 fixes the signing issue on Windows, macOS, and Linux for the STM32N6570-DK board.However, this is a blocker for developers using the Nucleo N657X0-Q board on Windows & Ubuntu because 2.20.0 has a bug which causes west flash to fail for this board on both Windows & Ubuntu. This west flash bug is fixed for Windows & Ubuntu in 2.21.0, but we can't use that version due to the signing issue in 2.21.0.

Hi all,I'm using STM32Cube IDE (version 1.13.1, build 17479_20230728_0839 ) to manage my company project based on a STM32U5 MCU.More specifically, I'm using linked list feature (for playing audio with SAI + DMA transfer) and I have noticed what appears to me as a bug in auto-generated code.Basically, I have created through CubeMx one list named SAIQueue, with one node named NodeTx and the auto-generated initialization code is the following:  /** * @brief DMA Linked-list SAIQueue configuration * @PAram None * @retval None */ HAL_StatusTypeDef MX_SAIQueue_Config(void) { HAL_StatusTypeDef ret = HAL_OK; /* DMA node configuration declaration */ DMA_NodeConfTypeDef pNodeConfig; /* Set node configuration ################################################*/ pNodeConfig.NodeType = DMA_GPDMA_LINEAR_NODE; pNodeConfig.Init.Request = GPDMA1_REQUEST_SAI1_B; pNodeConfig.Init.BlkHWRequest = DMA_BREQ_SINGLE_BURST; pNodeConfig.Init.Direction = DMA_MEMORY_TO_PERIPH; pNodeConfig.Init

Dear all, when I press Install button in the Toolchain Manager of the 2.0.0 CubeIDE it hangs after opening the subsequent dialog. I cannot close this dialog or press any button with neither mouse nor ESC key. Workaround: return first back to the Toolchain Versions dialog and close it. Then I could press "Next" and continue installing GNU Tools for STM32 version.   Regards,Dmitry

Hi,I have noticed a little problem in the "Live Expressions" function.The first time I open STM32CubeIDE and debug my firmware, I can see the value of all expressions previously written by me.When I stop the debug and debug again, some expressions does'nt show the value. Instead this appears the message " Failed to evaluate expression".The curious is that if I "rename" the expression the correct value appears again. For example, adding a space (or removing a space) at end of a expression with the message " Failed to evaluate expression" solve the problem.This are happenning with anyone more?This is a real bug?! How this problem can be solved?Best regards, DIego Volpini

Hi everyone,I'm encountering a critical issue when attempting to debug/flash my STM32 microcontroller using my ST-LINK debugger in STM32CubeIDE.The Initial Error: When I start a debug session, I receive the pop-up: ST-LINK firmware upgrade required. Please upgrade the ST-LINK firmware using the upgrade tool. 

1. Issues with Headless Execution and CLI CommandsGUI Opens with CLI Flags: Certain CLI flags designed for automation still launch the AWT/Swing GUI components, which causes failures in headless environments (like Docker containers or typical Linux servers).Specific Example: The -P flag (Package Manager) throws a java.awt.AWTError: Can't connect to X11 window server error because it requires a display.Expected Behavior: All package management and code generation functions should have a truly headless (no GUI dependencies) CLI option that works universally in server environments.Lack of Clear CLI Documentation: Documentation for reliable, headless CLI commands (like swmgr install) is sparse or non-existent in the official user manual (UM1718), leading to trial-and-error with internal commands. 2. Issues with Offline Package Management and Database IndexingDiscrepancy Between Repository and Database Paths: Manually placing firmware p

Hello Team,I am trying to add CMSIS FreeRtos to empty project. But I can see that .ioc file is not generated under my project.I have also gone through the posts who have encountered the similar issue. but didn't get the resolution.While creating the empty project. There is no option for selecting Stm32 cube project or empty project. attaching the snippet for your reference.After creating the project successfully, I am getting the below build warningwarning: #warning "FPU is not initialized, but the project is compiling for an FPU. Please initialize the FPU before use." [-Wcpp]So, I request you to guide me to resolve this issue.I am using the Stm32CubeIDE: - V2.0.0 Thanks,Sagar 

When attempting to initialize a single GPIO EXTI as disabled, the generated code still enables the interrupt. I did notice that if I uncheck all of the EXTI lines, then none of them are enabled in the generated code. So it seems it's all or nothing. Is this the expected behavior?Thanks,FrankThis:Generates: /* EXTI interrupt init*/ HAL_NVIC_SetPriority(EXTI0_IRQn, 5, 0); HAL_NVIC_EnableIRQ(EXTI0_IRQn);   HAL_NVIC_SetPriority(EXTI2_IRQn, 6, 0); HAL_NVIC_EnableIRQ(EXTI2_IRQn);   HAL_NVIC_SetPriority(EXTI3_IRQn, 6, 0); HAL_NVIC_EnableIRQ(EXTI3_IRQn);   HAL_NVIC_SetPriority(EXTI4_IRQn, 6, 0); HAL_NVIC_EnableIRQ(EXTI4_IRQn);However, this:Generates: /* EXTI interrupt init*/ HAL_NVIC_SetPriority(EXTI0_IRQn, 5, 0); HAL_NVIC_SetPriority(EXTI2_IRQn, 6, 0); HAL_NVIC_SetPriority(EXTI3_IRQn, 6, 0); HAL_NVIC_SetPriority(EXTI4_IRQn, 6, 0);

Hello,I've recently created an External Loader to be used on a TouchGFX project (H563 with SPI LCD and SPI external flash). When I use this loader in Cube Programmer, it programs the processor and SPI flash, and runs as expected. So now I want to add it into my project in CubeIDE. Normally I would find the External Loaders under the Debugger tab (between SWV and Misc) but this seems to be missing. Is there a way to enable this?(This project was created un der CubeIDE 2.0.0, but this section also is missing in projects created by previous versions. Example projects created from TouchGFX does have this section).Any ideas?PP22

I noticed that running cube-cmake --version reports cmake version 4.0.1, but running the actual build commands with cmake 4.0.1 produces a different binary than when running with cube-cmake.Is it safe to build a binary for release using cmake instead of cube-cmake? My program seems to run just fine building with cmake but I am curious what the difference between the two is.

/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS. * ****************************************************************************** */ /* USER CODE END Header */ /* Includes ------------------------------------------------------------------*/ #include "main.h" #include "cmsis_os.h" #include "usb_host.h" /* Private includes ----------------------------------------------------------*/ /* USER CODE BEGIN Includes */ /* USER CODE END Includes */ /* Private typedef ---------------------------------------------------

Hi, Is there anyway to generate codes in such way that we can customize our sub-project paths? E.g. Instead of having project/core/src, we have project/src... etc? Thanks in advance!

Hi,I'm using CubeMX 6.16.0 with the EWARM setting.When I click "Generate Code," it creates the IAR project with the default name "project.eww."I open the project with IAR and save it with a new name.Then I click the "Generate Code" button on CubeMX, and it regenerates the workspace name, again as "project.eww."Is it possible to set the IAR project name from CubeMX to something other than "project.eww"?Thanks

Hi all I am a newbie to Linux and I badly want to excel in the system and currently i've stumbled upon an issue of not being able to run and debug my code to STM32-NUCLEO-F4460RE board through CUBE IDE. On running the program to my bord its i showing an error window and giving error message "Could not determine GDB version using command: arm-none-eabi-gdb --version". I asked Gemini and Chatgpt for help and got replies that made me symlink my libncurses.so.6.4 to .so.5 and similarly with libtinfo, then I installed gdb-multiarch as I was not able to download arm-none-eabi-gdb even with .gcc. Even I changed the prefernce to gdb-multiarch and its still the same. To add my Linux version is 24.04 LTS Noble. Kindly someone help me out of this mess.

Hi All!After the CubeIDE auto-update, the option to import example projects had disappeared. Or was it moved somewhere else now? Release Notes mention nothing about this.In the meantime I guess I can access the examples using CubeMX.

After (auto) migration the .ioc file to the actual CubeMX 6.15.0, the Dual Quad SPI mode got changed to Octo SPI mode and there seems to be no way to get back to Dual Quad SPI mode, since the mode selection entry "Dual-Quad SPI" is not shown as mode selection entry.After taking a closer look, I found out, that the Dual-Quad SPI mode is avail only for the OCTOSPI2 device, whereas the Dual-quad SPI option is not avail for the OCTOSPI1 device (tested with a "clean" configuration). Since my hardware was doing fine with Dual-quad SPI mode on OCTOSPI1 device there seems to be no reason for removing the Dual quad SPI mode from OCTOSPI1.I think, this behaviour is not intended ? Actually I found no workaround for this problem except for manually changing the auto-generated code so it would be nice to have that issue fixed. Even if changing the .ioc file manually the Dual Quad SPI mode option is removed on next load into the MX GUI again. Best regrads, Heino 

Hello ST team and community,I am working with STM32H755 and noticed a potential bug in the code generated by STM32CubeMX when handling the RCC_FLAG_D2CKRDY check during system initialization. CubeMX produces two variants of the loop:while((__HAL_RCC_GET_FLAG(RCC_FLAG_D2CKRDY) != RESET) && (timeout-- > 0)); if (timeout < 0) { Error_Handler(); }andwhile((__HAL_RCC_GET_FLAG(RCC_FLAG_D2CKRDY) == RESET) && (timeout-- > 0)); if (timeout < 0) { Error_Handler(); }Issue observedThe loop condition uses (timeout-- > 0).This means the loop exits when timeout reaches 0, but never decrements below zero.As a result, the check if (timeout < 0) will never be true, so Error_Handler() is never called — even if the D2 domain clock never becomes ready.Since STM32H755 relies on proper synchronization between the Cortex‑M7 and Cortex‑M4 domains, missing this error condition can mask serious startup failures. Developers may assume the system initialized correctly when

Hello,I created a project with an older version of the extension (v2.0.0) and everything worked fine. After coming back to it some time later, I found that I’m no longer able to run the code.I’m not sure if this is an issue with my setup or a more general problem, but I can’t select my MCU (STM32C071KBUx) in the VS Code extension’s project setup.When I manually set the deviceName property in launch.json I get an error:Is anyone else experiencing a similar issue?Thanks for any help!

Hi,in the latest cube (6.15) the STM32H573LI is not available, I can't start a project on this MCU.why is that? is there going to be a fix soon?