STM32 MCUs Software development tools

I can't seem to read the OTP bits on the stm32N6 with any of my boards with 2.22 of the stm32CubeProgrammer.   But i can on version 2.21 Everything else works fine with the chip. 

Hi there,I'm debugging an STM32L081 project with an ST-LINK/V2 ISOL, and the Live Expressions data during the debug session is corrupted.Sometimes, removing all expressions, stopping the debug session, and/or power-cycling the processor makes the data display correctly again. However, after a simple code update, or adding  new data on Live expressions; the data becomes corrupted once more.This has been a known issue since 2023. I’ve seen many colleagues reporting the same problem. Even ST technicians have escalated it under internal ticket IDs 222326 and 175214.Unfortunately, as of early 2026, there has been no update.I have installed the latest STM32CubeIDE 2.0.0, but the issue still persists. Come on, ST team!!!!You are aware of this issue. Please inform the community about when it will be fixed. Thanks in advance.

In CubeMX2 when configuring the I2S peripheral on an STM32C542 running from a clock of 144MHz and selecting an audio clock rate of 96000Hz, CubeMX2 computes a nearest reachable frequency of 97826Hz (I2SDIV = 23, ODD = 0). When code is generated and run on actual hardware, the HAL2 I2S driver computes a different value of 95744Hz (I2SDIV = 23, ODD = 1). The HAL2 hardware value has less error from the desired 96000Hz than the value reported by CubeMX2, but the CubeMX2 value may be used in designing other aspects of the firmware and result in unexpected performance.    

Hello,I am working on a custom PCB using the STM32H757IITx. While programming the chip with an ST-LINK/V2 SET programmer via STM32CubeProgrammer, I encounter the warning::warning: “The core is locked up”:cross_mark: Mass erase / flash operation failedAs a result, the board does not operate normally.Here is the log output:Error in final launch sequence: Failed to execute MI command: load D:\XXX\XXX\XXX-v1.0\CM7\Debug\Integra-v1.0_CM7.elf Error message from debugger back end: Error finishing flash operation Failed to execute MI command: load D:\XXX\XXX\XXX-v1.0\CM7\Debug\Integra-v1.0_CM7.elf Error message from debugger back end: Error finishing flash operation Error finishing flash operation.I have attached screenshots of the error for reference.Has anyone encountered this issue or can suggest possible solutions?Thank you.   

The STM32 toolchain based on gcc 13.3 already supports a lot of C23 features, e.g. constexpr. This is really awesome.But the current version of CubeIDE seems not to be able yet to parse these new features, so syntax checking / highlighting / code linking breaks.Is there any simple workaround for this? Or is there information available, whether the next version of CubeIDE will update this?

Hi,recently in STM32CubeProgrammer was introduced the Serial Numbering feature, which is much appreciated.However, it's limiting because the serial number is assigned manually, setting a starting value that is progressively incremented.In a production site with multiple test stations, it becomes difficult to synchronize the various stations on the SN to be used.Hence my request: it would be very useful if the Serial Numbering section were integrated with a "Script" field, in which the user can enter the filepath of a custom "C-style" script (or in the programming language of ST choice) whose return value is the SN to be programmed. The script (customizable by us) will provide the correct return value, based on the logic the end company wishes to use to assign the SN to its devices (e.g., databases, *.csv, etc.). Hoping for a future update, I look forward to hearing from you.Best regards,Matteo

Hello everybody.I try to convert an STM32CubeIDE project into a CMake project to be used on VSCode using the procedure included in "STM32CubeIDE for Visual Studio Code" extension.The procedure aborts with this error message:  [Error] [ide-project-convert] Bad escaped character in JSON at position 15583 (line 322 column 55). Line 322 of "stm32cubeide-export.json" file, created by the procedure itself, is this one:, "option.includepaths": "-I\"C:\Repo_mgo\STM32Workspace\NGDrive\Appl\dDrive_Fwk2\application\Display\TouchGFX\generated\texts\include\", -I\"C:\Repo_mgo\STM32Workspace\NGDrive\Appl\dDrive_Fwk2\application\Display\TouchGFX\", -I\"C:\Repo_mgo\STM32Workspace\NGDrive\Appl\dDrive_Fwk2\application\Display\TouchGFX\gui\include\", -I\"C:\Repo_mgo\STM32Workspace\NGDrive\Appl\dDrive_Fwk2\application\Display\TouchGFX\generated\gui_generated\include\", -I\"C:\Repo_mgo\STM32Workspace\NGDrive\Appl\dDrive_Fwk2\application\Display\TouchGFX\generated\fonts\include\", -I\"C:\Repo

Hello,I am using VSCode on Windows with the STM32CubeIDE for VSCode extension.Before installing the extension, I had already installed and configured these tools separately on my system:CMakeArm GNU Toolchain (arm-none-eabi-gcc, arm-none-eabi-gdb)clangdAfter installing the STM32CubeIDE for VSCode extension, build works, but debug fails to start. I get the following popup error:bound doStepStartGdbClientDebug Failed: Failed to get gdb version.I would like to ask whether this issue may be related to how the extension detects GDB, conflicts with environment variables, or path priority when multiple toolchains are installed.Observed behaviorI already had a standalone ARM toolchain installed before installing the STM32CubeIDE for VSCode extension.After installing the extension, debug no longer starts correctly.The popup error is:bound doStepStartGdbClientDebug Failed: Failed to get gdb version.My current suspicion is that the extension is either:not finding the correct arm-none-eabi-gdb, or

Title: STM32N6 (NUCLEO-N657X0-Q) unable to flash on M3 Mac - libusb timeout errorEnvironment:- Board: NUCLEO-N657X0-Q (STM32N657X0H3Q, STLINK-V3EC)- Host: MacBook Air M3, Apple Silicon- STM32CubeProgrammer: v2.22.0- STM32CubeIDE: v2.1.1- ST-Link Firmware: V3J17M10- libusb: 1.0.29 (Homebrew)Problem:Unable to flash the board from M3 Mac. STM32CubeProgrammer and STM32CubeIDE both fail to connect consistently.Error from STM32CubeProgrammer CLI:ST-LINK FW : V3J17M10Board : NUCLEO-N657X0-QVoltage : 3.28Vlibusb: warning [darwin_transfer_status] transfer error: timed outError: Unable to get core IDError: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug AuthenticationError from STM32CubeI

Hello ST Community,I am currently working on a project using the STM32WB05KNV6TR microcontroller. I am using STM32CubeIDE Version 2.0.0, and I have ensured that all MCU packages and embedded software packs are up to date.Specifically, as shown in the attached screenshot, I have the STM32Cube MCU Package for STM32WB0 Series (v1.4.1) installed. However, when I try to create a new project and use the Target Selector (MCU/MPU Selector), the STM32WB05 series—and specifically the STM32WB05KNV6TR—does not appear in the list.I urgently need to access the Pinout & Configuration view to finalize my hardware design and verify the pin assignments.Steps I have already taken:Updated STM32CubeIDE to the latest available version.Refreshed and installed the latest WB0 series patches via the Embedded Software Packages Manager.Restarted the IDE and checked the board/MCU selector filters.Questions:Is there a specific patch or an external ".pdsc" file required to enable STM32WB05 support in CubeIDE 2.0

Could I get some guidance on this? Presumably I can fix this by installing a package or something...Logs below (see second line from end).Thank you! 2026-04-12 17:30:29.505 [Info] [project-manager] STM32CubeIDE project manager activation....2026-04-12 17:32:30.960 [Info] [ide-project-convert] Starting project conversion...2026-04-12 17:32:31.263 [Info] [ide-project-convert] cube wrapper version: 0.10.22026-04-12 17:32:31.551 [Info] [ide-project-convert] Starting installation...2026-04-12 17:32:31.689 [Info] [ide-project-convert] Do you want to install the following bundles: ["osgi-exporter@0.0.4"] (yes, no, show)?2026-04-12 17:32:31.692 [Info] [ide-project-convert] Downloading osgi-exporter@0.0.4 to '/Users/me/Library/Application Support/stm32cube/bundles/osgi-exporter/0.0.4'...2026-04-12 17:32:32.004 [Info] [ide-project-convert] Downloading https://developer.st.com/bundles/o/osgi-exporter-0.0.4-all.bundleDownloading https://developer.st.com/bundles/o/osgi-exporter-0.0.4-all.bundl

I'm experiencing some issues with indexing of clangd. I'm working on a project including Bluetooth LE and the ble_types.h header file makes extensive use of the preprocessor define __PACKED_STRUCT which is defined in one of the CMSIS compiler header files (e.g., cmsis_gcc.h for GCC compiler). clangd is for some reason not able to resolve the typedefs using __PACKED_STRUCT which makes code browsing harder and auto-completion does not work for these types.I found a workaround by adding the __PACKED_STRUCT define explicitly in the .clangd config file.My current .clangd file looks as follows:CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' - '-D__PACKED_STRUCT=struct __attribute__((packed, aligned(1)))' CompilationDatabase: build/Debug Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - typename_requires_specqual Completion: HeaderInsertion: NeverSo I basically added the preprocessor define to the CompileFlags. Of course this is n

Hey all, just installed STM32CubeIDE on cachyOS and connected my HiLetGo STM32F103C8T6 dev board (https://www.amazon.com/dp/B07VKSVM21), and the IDE is giving me the following error when I try to debug or deploy:I tried installing ST-LINK-SERVER separately just to be safe, and it said that it was already installed. (I assume as part of the Cube IDE installation.) Also reinstalled libusb (Version 1.0.29-1.1).I can see STM32x_USB under Removable Devices in the system browser when plugged in, so I know the board is connecting at least. Any ideas here?

Board: NUCLEO-WL33 Toolchain: CMake + arm-none-eabi-gcc CubeMX version: 6.17.0 STM32CubeIDE version: 2.1.1I am trying to run a basic STM32WL33 project generated by STM32CubeMX using the CMake toolchain instead of the native STM32CubeIDE project format.The same CubeMX configuration, when generated as a native STM32CubeIDE project, works correctly and reaches HAL_Init() in main.c without any issue.However, when using the CMake-based output, the firmware crashes during startup andnever reaches main().SymptomsDebugger halts inside SystemInit() at line 200 (system_stm32wl3x.c), or jumps to an address outside valid memory (0x100004ee — inside the ROM region 0x10000000–0x100017FF) Is there a known-good CMake startup/linker reference for the STM32WL33?

After updating CubeMX to version 6.16.2, we are seeing HRtimer E and F problems which cause our product to fail.  Reverting back to 6.15 and regenerating the code allows our device to work.  I believe the issue is due to the change in the code database version: MxDb.Version=DB.6.0.161 but I can't be sure as the new version of cubeMX forces values into the HRtimer E and F configurations.Hoping for commiseration and resolution!ThanksRauk

Hi,I am trying to debug STM32N6 program loaded in external flash. When I started the debugger in the FSBL project I can put a breakpoint just before it jumps into application inside external flash. It is obvious I wont be able to see the symbols since it is not loaded. So I loaded my application elf file under debug_configuration/Startup/Load Image and Symbols (See attached image). When I start my debugging session, I encounter the following error and was unable to debug even FSBL code.Board: STM32N6 DKSTM32CubeIDE: 1.17.0Platform: Windowproject: Template_XIP_FSBL (found under Stcube package for N6).Here is the error:STMicroelectronics ST-LINK GDB server. Version 7.9.0 Copyright (c) 2024, STMicroelectronics. All rights reserved. Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : Enabled Waiting for debugger connection... Debugger c

The UCPD Dead-battery mechanism is a major gotcha in many new STM32, as it creates a surprising bond between seemingly unrelated pins, and is on by default. There cannot be enough warnings to this, as users not intending to use the PD (which is probably the vast majority) have no incentive to actively seek for such bond.As much as I abhor the whole Cube ecosystem, this is the one case where a sin committed in hardware design decision can be made right at least for those who click in the CubeMXes. The above bond can be highlighted in the pin diagram, and auto-generated code can disable DBCC automagically for all who don't actively enable PD.JW

Hello,I generated a project using STM32CubeMX2 for Nucleo-C5A3ZG and I imported the project using the 'STM32CubeMX2 Project' option into STM32CubeIDE. I can compile and link the code without any issues however I noticed that there is only one build configuration (debug_GCC_NUCLEO-C5A3ZG for my project). Can STM32CubeMX2 also create a release  build configuration?My second related question what is the best way to add compile flags? I managed to add a -DDEBUG flag to the flags.cmake file and it works fine. Is this the right way to do it? Would project regeneration be troubled by this change?Finally, if I opted in for 'Assert checks on function parameters' and 'Assert checks on module state' in STM32CubeMX2 HAL System Init is there a way to only have this functionality enabled only for a debug build? Thank you,Gil 

Is it possible to get pretty-print support for data-structures and custom types? It seems that not even STL types (e.g. std::vector) can be inspected easily by default: std::_Vector_base<int, std::allocator<int> > = {...} std::_Vector_base<int, std::allocator<int> > = Variable object not foundThis is all that is shown for a std::vector<int>.Looking into this, it seems that GDB can do this via python-based pretty printers, which even seem to be available for for the libstdc++ bundled with the IDE, e.g. "/opt/st/stm32cubeide_1.19.0/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.14.3.rel1.linux64_1.0.0.202510151430/tools/arm-none-eabi/lib/thumb/v7e-m+fp/hard/libstdc++.a-gdb.py"However, Python support seems to be disabled for GDB, which I guess is the reason this isn't working? > python print(True) Python scripting is not supported in this copy of GDB.So: Is there any current support for something like this? Or is it at least

Hello,According to Table 246 in section 27.3.3 Signal Routing of the STM32U3 Reference Manual, I should be able to configure ADC1_IN6 as an ADC input when using OPAMP1, or ADC1_IN13/ADC2_IN9 when using OPAMP2 such that the output of the opamps are routed internally to the input of the ADC.However, in CubeMX configuration for this device, enabling the Opamp in any capacity "red's out" the option to use the corresponding ADC input for any of these combinations. In this example, OPAMP1 is set to PGA Not Connected, and I am unable to  configure the ADC input on IN6.Am I doing something wrong here, or is this simply a bug related to the recent release of this product?Thanks!CubeMX version: 6.17.0OS: Ubuntu 24.04.4Device: STM32U3C5CIUxQ

I noticed that STM32CubeMX2 (DEBUG features page) offers only three debug modes: JTAG 4‑pin, JTAG 5‑pin, and Single Wire Trace Asynchronous.In many practical cases, developers use only the SWCLK and SWDIO lines to save pins, so the absence of a simple Serial Wire option (without Trace) seems to be a limitation of the current STM32CubeMX2 release.This option is still available in STM32CubeMX1 when working with similar MCUs, such as the STM32H5 series.Is this understanding correct?

Split from STM32CubeIDE missing “STM32 Project” and CubeMX after fresh installation - that issue was resolved.This is a new issue.The new version 2.1.1 appears pretty useless even after trying to make a project with the separate cubemx. From the IDE you cannot then build the project. It just sits there. I would hope that the IDE is at at capable of building and compiling the project but it appears that is no longer the case.Did you employ someone from microsoft to break it. It was working perfectly before hand. New->STM Project->.....->build->debug. I will revert back to 1.19 to avoid wasting more time and just use an older CubeMX as that was the only reason I upgraded Please leave working software alone or simply improve it and not break it for no reason

Hello everyone!I am trying to get a custom board based on an STM32WBA5MMG to join my existing ZigBee network. As a first test, I have created a basic project in CubeMX, that configures STM32_WPAN to generate a ZigBee project with one OnOff-Endpoint and sets up USART2 for logging. When I generate a CMake-based project and try to compile it in VSCode with the STM32 extensions installed (without making any changes to what CubeMX generated), I get a bunch of linking errors and the build fails:[build] /Users/dg/Library/Application Support/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/bin/../lib/gcc/arm-none-eabi/14.3.1/../../../../arm-none-eabi/bin/ld: warning: /Users/dg/Library/Application Support/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/bin/../lib/gcc/arm-none-eabi/14.3.1/thumb/v8-m.main+fp/hard/crtn.o: missing .note.GNU-stack section implies executable stack [build] /Users/dg/Library/Application Support/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/bin/../lib/gcc/arm-non

I am trying to download the windows version of the IDE but I can't get it to work. Either the download button doesn't do anything or it's just not there. I've tried with different email accounts, different web browsers, different networks but that didn't do it. I've looked on here and it was suggested to disable browser extensions like ad-blockers and such and I've disabled all of them and still nothing. I would appreciate any help.

I am having debugging issues with STM32CubeIDE. the processor is STM32F030F4Px and I am using a knock off ST-Link V2. It seem that no matter what I configure I get the same error. There also is a check GDB server version error in the IDE window. Open On-Chip Debugger 0.12.0-00017-gb153daa14 (2023-02-03-14:58)   Licensed under GNU GPL v2   Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : STLINK V2J41S7 (API v2) VID:PID 0483:3748 Info : Target voltage: 3.240714 Info : clock speed 4000 kHz Info : stlink_dap_op_connect(connect) Info : SWD DPIDR 0x0bb11477 Info : [STM32F030F4Px.cpu] Cortex-M0 r0p0 processor detected Info : [STM32F030F4Px.cpu] target has 4 breakpoints, 2 watchpoints Info : starting gdb server for STM32F030F4Px.cpu on 3333 Info : Listening on port 3333 for gdb connections Info : accepting 'gdb' connection on tcp/3333 Info : device id = 0x10006444 Info : flash size = 32 KiB Warn : GDB connection 1 on target