STM32 MCUs Software development tools

Dear all, when I press Install button in the Toolchain Manager of the 1.17.0 CubeIDE it hangs after opening the subsequent dialog. I cannot close this dialog with neither mouse nor ESC key, need to terminate the task.  Regards,Dmitry

Hello,I use last version of CubeIDE 1.15.1CubeMX proposes in tools a CAD tab, that allows to export symbols and footprints for the different EDA packages (ex KiCAD).I use CubeIDE for my projects. In "Tools", there is a "CAD" sub-tab. But it leads to a white page.Is there a specfic installation needed to have the CAD functionnality in CubeIDE (as exists in CubeMX)?Best regards,JMF

Are there any plans to upgrade STM32CubeIDE to include support for C23?It would be nice to have as it brings things like constexpr in, which makes the use of constants much better as they are subject to compiler checking and can call (constexpr) functions.

How can I debug an STM32N6 project when using a load-and-run configuration? CubeMX generates two separate projects, and I’m able to debug each one individually when the BOOT1 pin is set high. However, it seems that if I only debug the application project, the FSBL never executes, so the system clocks aren’t initialized. What’s the correct approach to debugging both projects together?I came across a debugging guide, but it only applies to the XIP configuration.

Hi everyone, I am facing an issue with an STM32U5 regarding the entry into STOP3 mode after a production programming cycle using the STM32CubeProgrammer CLI. I use a .cmd script to flash the device. In the script, I use the -c port=swd dLPM mode=UR flags to ensure the first connection during the multi-step programming of several binaries. At the end of the script, I perform a software reset via -c port=swd dLPM -rst. After the script finishes and I unplug the ST-Link, the microcontroller fails to enter STOP3 mode (current consumption remains high, in the mA range). I noticed that if I manually connect with the STM32CubeProgrammer GUI without the "Debug in Low Power Mode" (dLPM) option enabled, perform a software reset, and then disconnect the JTAG/SWD, the device enters STOP3 correctly. It seems that the dLPM flag used during the CLI session is "sticky": it sets the DBG_STOP and DBG_STANDBY bits in the DBGMCU_CR register, and these bits pe

Confirming that CubeMX loading problem has been fixed. But I need to point out that RAMCFG enabling still comes with issue: AXISRAM clocks enabling code is not generated. As I wrote in another post, clocks are partially enabled by RIF code: STM32N6 RIF and MMT autoconfiguration errors - STMicroelectronics Community But AXISRAM3 clock is not enabled, so firmware halts. And power needs to be enabled also. My workaround is to enable all the AXISRAM clocks and power in HAL_RAMCFG_MspInit: void HAL_RAMCFG_MspInit(RAMCFG_HandleTypeDef* hramcfg) { /* USER CODE BEGIN RAMCFG_MspInit 0 */ /* USER CODE END RAMCFG_MspInit 0 */ /* Peripheral clock enable */ __HAL_RCC_RAMCFG_CLK_ENABLE(); /* USER CODE BEGIN RAMCFG_MspInit 1 */ /* AXI SRAM1-2 is already enabled by BootROM. * En

Hi there! First of all, thank you for taking the time to read this!!! Any input is welcome. I'm working on a project with a Nucleo-H563ZI board, and did something quite dumb: went and set the PRODUCT_STATE to CLOSED from within some dummy FW, and now I'm stuck. I can see the FW is running (LED task is blinking), but now I can't seem to access the device through Debug Authentication to bring it back to OPEN. When I click on Full Regression STM32CubeProgrammer complains about "Password file not found"

STM32H523CET6 stuck in PRODUCT_STATE=0x17 (PROVISIONING)TZEN=0xC3 (disabled), DA not configured, BOOT_UBE=0xB4CubeProgrammer v2.22, all regression attempts faildebugauth=2 returns: "unable to boot on RSS_DA or is in OPEN mode"After this function it bricked:void LockCode(void) { FLASH_OBProgramInitTypeDef OBInit = {0}; HAL_FLASH_Unlock(); HAL_FLASH_OB_Unlock(); HAL_FLASHEx_OBGetConfig(&OBInit); if (OBInit.ProductState == OB_PROD_STATE_OPEN) { OBInit.OptionType = OPTIONBYTE_PROD_STATE; OBInit.ProductState = OB_PROD_STATE_PROVISIONING; HAL_FLASHEx_OBProgram(&OBInit); HAL_FLASH_OB_Launch(); } HAL_FLASH_OB_Lock(); HAL_FLASH_Lock(); }Edited to apply source code formatting - please see How to insert source code for future refer

Hello,I would like to request an enhancement to the search functionality in STM32CubeMX's pinout view.Currently, the search works well for exact or partial matches — for example, typing "usart1_rx" highlights the relevant pins. However, it would be very useful to support wildcard characters, allowing searches such as:- usart?_rx — match RX pins across all USART peripherals (USART1, USART2, etc.)- usart1_?x — match both RX and TX on USART1- *art*_?x — match all RX and TX signals on LPUART, UART, USARTThis would be especially helpful on larger packages with many peripherals, where you want to quickly visualize all pins serving a particular role across multiple instances of the same peripheral.The implementation complexity should be low — this is essentially replacing the existing string match with a simple wildcard pattern matcher against the same search index.Thank you for considering this improvement!

If I add a new .c file to my project in core/src it does not get recognized and is not complled. How do I get it into the make list?Thanks

I am using the latest STM32CubeIDE on a Windows platform - developing code for a STM32G0B1.I have a version.c file in my project that uses the __DATE__ and __TIME__ macros to create strings that I use in other modules.To ensure this file gets compiled on every build, I have a custom Pre-Build step that "touches" that file.  This all works fine.However, if I use the IDE to load the code into my hardware, it always does a build beforehand.  Because of this "touch", I get a new date string every time I run a debug session.Is it possible to replace the "touch" step with some kind of dependency on "all source files"?  In other words, can I make it so my version.c gets recompiled ONLY if some other source file has been updated?I know that I can turn off the "Build (if required) before launching" option.  But I'd rather keep that option as is, unless  changing it is the only way to do what I want.Thanks. 

i have find the same issue with 3 system ..like whenever i try to generate new stm32 project i get the same error...before that i never get this kind of error why this happened now???

I just spent some time trying to get a debug session going in VSCode ony to be given the rather obscure error message: "bound doStepConnectToTarget Failed: could not connect (error 138): The system tried to join a drive to a directory on a joined drive."Eventually I realised what it was - I had enabled RDP protection on the device (STM32C5) so of course it could not connect.May I suggest that a more appropriate error message is given in such circumstances? (this is with stlink gdb debugger, latest version.)

(and why is this a problem?)It looks like the backup ram can not be called through unaligned access on my STM32U585. The mighty internet says that this should not be completely unexpected since it is basically a peripheral and no standard Ram.I have set up the BKPSRAM in the linker file like this:#include "partition.h" /* Entry Point */ ENTRY(Reset_Handler) /* Highest address of the user mode stack */ _estack = ORIGIN(RAM) + LENGTH(RAM); /* end of "RAM" Ram type memory */ _Min_Heap_Size = 0x000 ; /* required amount of heap */ _Min_Stack_Size = 0x800 ; /* required amount of stac

Hi communityI found a missconfiguration in CubeMX while using a MCU TFT with FMC.Description:Device: STM32N6 (STM32N645B0HxQ) / Cortex-M55CubeMX Version: v6.17.0Peripheral: FMC, LCD Interface, 16-bit data width, A16 as RS/DC (Register Select)Symptom: A single WriteCommand() call (one STRH instruction to 0x60000000) produces 3 WR pulses on the oscilloscope instead of 1. The LCD display remains gray despite a correct initialization sequence. All FMC timing parameters and Write FIFO settings were verified and are not the cause.Root Cause: The Cortex-M55 (ARMv8-M) treats 0x60000000 as Normal Memory by default. This allows the CPU to merge and reorder 16-bit write accesses into 64-bit bursts, resulting in multiple spurious W

I am currently working on a resolver ad2s1210. I have selected the required pins generated the code and entered my code and now it does not seems to be running. As the screen shows this Kindly let me know whats seems to be the issue here and how to rectify it.

Hi,I created a project in STM32CubeMX 6.17.0 targeting the NUCLEO-G491RE and successfully generated the code. I then imported the project into STM32CubeIDE 2.1.1 and as far as I can tell it looks ok. The only apparent issue was that when I clicked on the .ioc file I thought that the STM32CubeMX project was supposed to open inside STM32CubeIDE but instead I get an error saying:So that's one issue. But when I come to build the project in STM32CubeIDE there is no Build All (CMD+B) option available, or indeed any other build options available.

I got this error also.

I tried compiling the generated code of the MCSDKand compiling it by C++ compiler, but the error at the revup_ctrl.h file:   pHandle->pCurrentPhaseParams = MC_NULL;prevent such compilation.Will it be fixed soon ? 

Hi,I'm having trouble getting my ST-Link V2 dongle to be recognized by Cube Programmer. It is recognized by Windows 10 in the device manager, I have been able to update the firmware, and I can get it to load in STM32 ST-Link Utility, but that program doesn't support the .elf file format I need.When I launch Cube Programmer, it does recognize something as shown by the voltage and the firmware (image attached), but when I click the refresh button next to the serial number it says "No ST-Link detected."I've read from others that there are a lot knockoffs of these dongles floating around that don't work anymore. That might be the problem with mine (this is the second one I've bought and tried). Can anyone point me to a good source to buy a legit one? In the products page, I've only seen the bigger ST-Link V2 unit and the smaller USB-C V3 unit, but not the V2 Dongle.I'm trying to flash a board for an Atari 2600 homebrew gam

I normally use 1.19.0 because of the MX sillyness...When compiling you get warnings - let's take stm32h723xx.h as an example.Line 2516 is - #define GPIOB ((GPIO_TypeDef *) GPIOB_BASE)In 1.19.0 you get a warning - Description Resource Path Location Type(near initialization for 'output_port[9]') stm32h723xx.h /Cube-Wave-723/Drivers/CMSIS/Device/ST/STM32H7xx/Include line 2516 C/C++ Problem In 2.1.1 you get an error - Description Resource Path Location Typeinitialization of 'long unsigned int' from 'GPIO_TypeDef *' makes integer from pointer without a cast [-Wint-conversion] stm32h723xx.h /Cube-Wave-723/Drivers/CMSIS/Device/ST/STM32H7xx/Include line 2516 C/C++ ProblemAs it is actually your generated code I do wonder how this has slipped through your 'testing' process.I was awaiting a news item reporting on ST employees being treated for burns as their ears caught fire after

Hello, I was using CubeMX with CubeIDE and since the release of CubeMX2, VSCode is promoted as the go-to.At the same time, CubeIDE got an update to importe Cmake project. What are the plans ?Will MX2 continue to support CubeIDE with Cmake only ? Will CubeIDE project exports be added to MX2?Or will VSCode be the main target for MX2?In sumary, which workflow will be the best for future dev since ST seems to refactor its whole ecosystem ?

This software has started reporting memory issues and wanting to close every few minutes.  This never used to happen until I updated to 2.0.0 and I wrote a bunch of code in a fairly large project this week.  I have tried all the suggestions that I could, ending in updating to 2.1.1 and it doesn't go away.I tried updating the memory usage to 6GB of RAM (in steps) in the file stm32cubeide.ini  (-Xms and -Xmx).  I deleted a bunch of folders in the /Users/xxxxx/ directory that started with .stm which worked for another person on this forum.I can't do my work anymore.  This software has become unusable!  I really don't know what to do to get it back to the way it has worked for the past decade.Any advice would be greatly appreciated.  If I need to contact IT about something they might have installed on this computer that is breaking this program, I could use some direction as to what that might be. Thanks!

Environment:MCU: STM32WB09KE (Cortex-M0+)Board: NUCLEO-WB09KESTM32CubeIDE Version: 2.1.0STM32CubeIDE Build: 27993_20260219_1630 (UTC)STM32CubeMX Version: 6.17.0Operating under Windows 11 Home.The project previously built successfully before updating CubeIDE @ approx. 23 February 2026. The "Installation History" tab in CubeIDE poorly reflects this update action however.Toolchain / IDE: STM32CubeIDESetup:In this page, ST generously provides us a .zip folder containing existing application projects that STM32WB0-series users can import, edit, and build directly. Version: 1.4.0.After extraction, the project "BLE_DirectionFinding_Centra

I'm looking at setting the RDP Level to Level 1 for an STM32F103 and I don't see the AA BB CC type stuff like in the current manual. Is this something that STM32CubeProgrammer is doing on purpose for this MCU?  I definitely don't want to enable Level 2 by accident and brick my chip.  Here is a screenshot of what I see:Is it safe to check this?