STM32 MCUs Software development tools

Hey Devs, I migrated my V2 extension to V3 (3.6.4) on Dec 11 2025 (just before the v3.7.0 release), updated my debug workflow / launch.json etc, my STM32H745I discovery board was running my TouchGFX application (basically stock TouchGFX Designer generated app w/ CMake) fine with Dual Core debugging (new shared debugger / simplified Launch/Tasks.json is a massive improvement on my old/convoluted tasks/launcher workflow, my sincere thanks).Just tried to re-run the same code stack with my code with the new 3.7.0 extensions, hit a launch error relating to my launch.json:Extension seems to have lost context of my ide.st

Hi,This might be a bit of a noobish question but despite my best efforts at searching I could not find a suitable answer. This forum may also be the wrong place for this question but since it is related to the new "cube" Swiss knife tool I thought this might be the right place to start. Feel free to move this question elsewhere if appropriate.I have a VS Code project that uses STM's extensions and bundles, and thus I can use "cube programmer" to invoke the STM32CubeProgrammer binary. In VS Code side I have a launch.json which allows me to build, flash and start debugging the application I've built on an STM32F0 series microcontroller. It works completely fine. Device appears in Windows, enumerates as a USB device, and everything just works as expected.What I want to do now is execute the build and flash steps, and then instruct the MCU to begin executing the program. I tried to do this by invoking the "cube programmer" with the following litany: 

I normally use the CMake Tools extension (by Microsoft) for compiling cmake projects in visual studio code.  After installing the STM32CubeIDE extension, the CMake Tools extension stopped working.  Presumably to do with the stm extension changing to using cube-cmake.  After uninstalling all STM32CubeIDE extensions, reinstalling CMake Tools, restaring VS code, the CMake Tools extension is still still broken.  Trying to configure a project through the IDE gives the following output:[cmakeExecutable] CMake executable not found in cache. Checking again.[proc] Executing command: cube-cmake --version[proc] The command: cube-cmake --version failed with error: Error: spawn cube-cmake ENOENT[proc] Executing command: cube-cmake -E capabilities[proc] The command: cube-cmake -E capabilities failed with error: Error: spawn cube-cmake ENOENT

Hello, I am getting really frustrated with this issue for almost a week.I am trying to read PA1 and PA4 in DMA but I get only the reading of one channel and not the other one! I tried everything and I also looked at all the example online. Please help. 

Hi, I found a small bug in STM32CubeMX for STM32WL55:Enabling the option "MSI Auto Calibration" for section "RCC" does nothing, i.e. generated code doesn't change.I think it should add a call to HAL_RCCEx_EnableMSIPLLMode() or LL_RCC_MSI_EnablePLLMode () in SystemClock_Config() - same as it does for STM32U0. This enables RCC_CR_MSIPLLEN.

Hi!Was hit by a non-obvious difference between the ARM and ST GCC toolchains.I installed the following toolchains (from the official ARM and ST websites) in two separate Docker containers.Their --version outputs are:ST toolchainarm-none-eabi-gcc (GNU Tools for STM32 13.3.rel1.20240926-1715) 13.3.1 20240614 ARM toolchainarm-none-eabi-gcc (Arm GNU Toolchain 13.3.Rel1 (Build arm-13.24)) 13.3.1 20240614 Then I compiled a simple main.c using the cyclomatic complexity option:

Hi there,I found an issue with the CubeMX 6.16.1 during the TouchGFX usage. I generated the files by TouchGFX 4.26 (selected the Stm32h7s7 development board with 24bpp project) and opened the cubemx to generate the code (I've been using vscode so I changed only the toolchain/IDE to Cmake and and with these settings the project was flashed and worked everything correctly.However, when I wanted to use the generate perpheral initialization as par of 'c/h' files and screen was struggled and couldn't read it's content. Nothing else was changed. In the visual studio I cleaned and rebuild the project but it did not work at all.Would it be possible to solve this?Thank you in advance!

Hello. My current set up is STM32Cubeide 1.19 which has an integrated version of the CubeMX (6.15)I'm currently working on some st git examples, that seem to have been created with CubeMX (6.16), thus i cannot open the .ioc file on cubeIDE. I installed cubeMX 6.16 in order to edit the .ioc file and hit generate. Once i tried to build the project on cubeIDE though i got various errorsmake: *** No rule to make target 'C:/Users/asantorinaios/STM32CubeIDE/workspace_1.19.0/BLE_Beacon/Drivers/STM32WBAxx_HAL_Driver/Src/stm32wbaxx_hal_gtzc.c', needed by 'Drivers/STM32WBAxx_HAL_Driver/stm32wbaxx_hal_gtzc.o'. Stop. "make -j12 all" terminated with exit code 2. Build might be incomplete.If i try to exclude

In STM32CubeIDE, it is possible to view two different source files side by side by dragging editor tabs with the mouse. However, there is no keyboard shortcut or command to move the active editor to the left/right split.This slows down workflow when frequently comparing files (e.g., main.c and app.c). A command such as “Move editor to right/left split” with assignable key binding would greatly improve productivity.Best regards.

Hi,   I have a functioning project that fully compiles with only three warnings, but when I debug it and examine C structures in the live expressions viewer the the data (GovTrimControl_P structure ) appears to be offset by 4 bytes, yet the memory browser shows the correct values and when the mouse hovers over a value that value is correct:    

Hello,I am trying to get the VS-Code extension to work on my Intel-Mac. I already have it running on my Windows machine no problem.The problem is, that the extensions won't activate. I have created a new project using CubeMX and choose CMake as the toolchain. Then I installed the STM32 CLI tools, as well as cmake and the ARM compiler.Then I am opening the project in VS-Code and CMake asks for a target. I choose Debug.CMake extension output:[proc] Executing command: /usr/local/bin/cmake --version [proc] Executing command: /usr/local/bin/cmake -E capabilities [kit] Successfully loaded 2 kits from /Users/jan/.local/share/CMakeTools/cmake-tools-kits.json [presetController] Reading and validating the presets file "/Users/jan/Dev/fischer-technik-motor-controller/CMakePresets.json" [presetController] Successfully validated /Users/jan/Dev/fischer-technik-motor-controller/CMakePresets.json again

The erroneous configuration in the tx_initialize_low_level.S is this: LDR r1, =0x40FF0000 // SysT, PnSV, Rsrv, DbgMThe tx_initialize_low_level.S file is generated upon selecting ThreadX 'Core' in the STM32CubeMX v6.15.0, and the above line is thereafter never changed. Specifically, upon enabling 'Enable BASEPRI support' and selecting a very common value of 5 for the TX_BASEPRI_VALUE, the above line is not updated accordingly. Not syncing the SYSTICK IRQ priority with the TX_BASE_PRI_VALUE of course leads to a system failure.This issue can be duplicated by creating a brand new project with STM32CubeMX v6.15.0 and it can be seen in the sample projects included in the Applications/ThreadX in the STM32Cube_FW_U5_V1.8.0

Hi all, I am trying to get a zephyr project running on an STM32N6570-DK, including Camera, NPU, VENC and Ethernet.I have been using STMCubeMX 6.16.1 to create the project based on the provided DK default settings.For the Ethernet block, the configurator shows pin conflicts, I double-checked and the pins are not in use by the Ethernet driver:There are similar warnings for the SD/MMC2 block:

Installing STM32CubeMx on OpenSuse Tumbleweed using/st-stm32cubeide_1.1.0_4551_20191014_1140_amd64.rpm_bundle.sis missing libusbxsudo ./st-stm32cubeide_1.1.0_4551_20191014_1140_amd64.rpm_bundle.sh [sudo] Passwort für root: Creating directory st-stm32cubeide_1.1.0_4551_20191014_1140_amd64.rpm_bundle.sh.root Verifying archive integrity... All good. Uncompressing STM32CubeIDE installer 100% Verifying... ################################# [100%] Preparing... ################################# [100%] package segger-jlink-udev-rules-6.44c-4.noarch is already installed error: Failed dependencies: libusbx >= 1.0 is needed by st-stlink-server-1.2.0-3.amd64 Verifying... ################################# [100%] Preparing... ################################# [100%] package st-stlink-udev-rules-1.0.2-2.noarch is already installed error: Failed dependencies: st-stlink-server is needed by st-stm32cubeide_1.1.0-1.1.0-4551_20191014_1140.x86_64libu

 I was making a project with CUBE IDE and compiling it on the board, and I got this error while compiling the project I was doing on the new board.No source is available for "Call Signal Handler"() in 0xfffffffe.I'm sure they're using the same CPUI can't compile it because it's STM32 ST-LINKI don't think there will be any problems with the code or MX settings because if I modify the code on the existing board, the project will also change well.Even if I create a new project and add the above code, I get the same error, so I can't compile itI want to solve this phenomenon, how do I solve it?  int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MPU Configur

CubeMX 6.16.0 "Memory Management" used for ethernet and with enabled linker file generation creates the following [ORIGIN adapted from default]:RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 0K TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 0K Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1KWhat I would have expected was:RxDescripSection (rwx) : ORIGIN = 0x30040000, LENGTH = 96 TxDescripSection (rwx) : ORIGIN = 0x30040060, LENGTH = 96 Rx_PoolSection (rwx) : ORIGIN = 0x30040200, LENGTH = 1536[with just 1 ETH RX buffer - see this other post ].Can someone explain to me whether this is intentional - maybe because of a constriction with the MPU granularity?O

  drag and drop error I have a Mac Pro M4 with Tahoe 26.2 OS, STM32CubeIDE version 2.0.2, and I am having trouble selecting and copying a selection of lines. I tried several tests and that option disappeared. If I am comparing two files, dragging and dropping text works perfectly. Is there any notification about this? Is there a solution? Thank you.   Post edited by ST moderator: This post has been translated from Spanish to comply with the ST Community guidelines. Please use English language as it's an international community and to let others to understand your post. Thank you for your understanding

Using:VSCode version: 1.107.1 on Windows 11.STM32CubeIDE for Visual Studio Code version 3.7.0.I created STM32N6 project that builds two targets: FSBL and Application. I follow the instructions here: https://community.st.com/t5/stm32-mcus/how-to-debug-the-stm32n6-using-vs-code/ta-p/833499.clangd contents:CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: Appli/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - typename_requires_specqual If: PathMatch: Appli/.* --- CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: FSBL/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - type

Using:VSCode version: 1.107.1 on Windows 11.STM32CubeIDE for Visual Studio Code version 3.7.0.I created STM32N6 project that builds two targets: FSBL and Application. I follow the instructions here: https://community.st.com/t5/stm32-mcus/how-to-debug-the-stm32n6-using-vs-code/ta-p/833499This is a single folder project, not multi-root. The problem is that when I navigate to source code which is not under FSBL or Appli then clangd does not know which complication database to use.This disturbs during coding and during debugging when I step through grayed out code with false errors highlighted.CMake (or some STM32 utility) generates .clang file into the root directory. It's stripped down version looks like this:CompileFlags: Comp

Hello, I am trying to set up a project using STM32Cube Extension in VS Code. When I attempt to select the Nucleo‑F207ZG board in the Board/Device selector, the board does not appear in the list.The stm32cube_core output shows the CMSIS_PACK_ROOT environment variable, and under that directory the file .Download\cache\scanner_391867825626163.cache contains entries for nucleo-f207zg as well as STMicroelectronics.nucleo-f207zg_hw-board.1.0.0.pdsc. Despite these files being present, the board is still not discovered by the IDE. Could you p

Hello all,I get an error starting a debug session from STM32CubeIDE (1.18.1) (STM32 Nucleo-F767ZI):STMicroelectronics ST-LINK GDB server. Version 7.10.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 : EnabledTarget USB comms errorError in initializing ST-LINK de

Hi,STM32H563 chiprev Z.I am trying to work through How to start with OEMiRoT on STM32H573 and 563–Arm® TrustZone® enabled - stm32mcu using a NUCLEO-H563ZI MR1 board but using the latest STM32CubeProgrammer (2.18.0) and ST32Cube_FW_H5 (STM32Cube_FW_H5_V1.4.0).Section 2.5 is intended to demonstrate booting securely and then dropping into the System flash bootloader from non-secure application and connecting to it via UART. In my case, I use the virtual COM-port provided by the ST-Link provided on the board. I have not dared to go all the way to CLOSED but have chosen to tell the provisioning.sh that I want PROVISIONED state. I have confirmed using the SWD-connection that the TZEN is enabled a

Problem:I recently updated to 2.0.0 of STM32CubeIDE and I encountered an issue when attempting to build for Debug. I first noticed an issue when trying to run a Debug Configuration. Before 2.0.0, it would build Debug before flashing the built firmware and starting the debugging server; pretty much default settings. Today, it started skipping the build step. I tried building Debug manually with the dropdown on the hammer icon and clicking "Debug." Instead, it built for Release. Solutions:- Right click on the project -> Build Configurations -> Build Selected... and select Debug.AND- Setting Debug as the active build and right click on the project -> Build ProjectThese solutions would build for Debug AND clear both of the above issues. As in the hammer icon -> Debug would actually build for Debug and the Debug Configuration would build before flashing and debugging.

I have a requirement to implement CAN based bootloader in my STM32h503rbt6 controller. Right now iam working on the testing of Flash functions which i have written on my own.My flash write, read and erase all are working fine.but when iam erasing flash sector wise,here comes the problem.after sector 7, from sector 8 onwards with y function i cant abe to erase.but i want full memory controll over my st controller flash.then only i can decide which part of flash i can use for my bootloader and which part of flash i can use for my application.HAL_StatusTypeDef Flash_Erase_Sector(uint32_t sector) { while (FLASH->NSSR & FLASH_SR_BSY); if (FLASH->NSCR & FLASH_CR_LOCK) { FLASH->NSKEYR = FLASH_KEY1; FLASH->NSKEYR = FLASH_KEY2; } /* Clear valid flags only */ FLASH->NSCCR = FLASH_CCR_CLR_EOP | FLASH_CCR_CLR_PGSERR | FLASH_CCR_CLR_WRPERR; FLASH->NSCR &= ~FLASH_CR_SNB_Msk; FLASH->NSCR |= FLASH_CR_

Hi all,I'm looking for a way to remotely *flash* a B-U585I-IOT02A | Product - STMicroelectronics eval board using the built-in STLINK-V3.Remotely means over TCP. Can be at the same computer (e.g., to pass-through debuggers to Docker containers), or across computers.This works well with GDB for debugging, but I need this to get running with flashing, too.Questions:Is there a way to make STM32_Programmer_CLI or related ST apps connect via TCP instead of directly to the debugger? I found ST-LINK-SERVER | Software - STMicroelectronics which seems to create the TCP bridge, but do any ST tools actually use it?