Ask questions and find answers on STM32 microcontrollers software development tools.
Most recent activity
We are pleased to announce that the minor version 6.18.1 of STM32CubeMX is available.What is new in 6.18.1:This release addresses and resolves the issues outlined below:Download error for crdb.zip during update STM32CubeMX displays a download error pop-up during data updates. Note : This issue is resolved for 6.18.1 and later versions. For the earlier versions customers may refer to the following workaround already shared in the community:Workaround for file download error: crdb.zip (Problem during download) | Community Error occurred while importing .ioc file created with STM32CubeMX older than 6.18.0 The “Continue and Migrate” features are not working properly for projects with PCC configured. Issue when setting clock to 240Mhz in STM32H743 and STM32H753 STM32CubeMX prevents the user from selecting 240 MHz, displaying the message: “240 MHz maximum frequency must be <= 225 MHz.” Fixed issues in 6.18.1:Refer to the STM32CubeMX online docu
Pleased to announce that the new release 3.10.0 of STM32CubeIDE is online FeaturesAdded internationalization support. [Build analyzer] Added binary (.elf) file processing to improve build analysis results to a level comparable with STM32CubeIDE for Eclipse [Build analyzer] Added support for Zephyr build artifacts. [Documentation] Added support to export the User Guide as a PDF or zipped HTML file. Added Command-Line Interface (CLI) support for empty project creation. Added core selection for empty project creation on multicore target devices.Chores [STLink GDB server launch] Enabled the live watch feature by default. Updated CMake directives for the empty project creation process to align with the STM32CubeMX2 user experience. Updated CMake directives for the STM32CubeIDE to Eclipse project conversion process to align with the STM32CubeMX2 user experience. [Build analyzer] Improved hyperlinks to source code by excluding static nodes from the rendering. Improved information about enabl
An issue has been identified in STM32CubeIDE 1.19.0 and earlier versions where a download error pop-up may appear during data updates. This issue does not prevent STM32CubeIDE from functioning properly. To continue: click OK twice. STM32CubeIDE should then operate normally. Optional workaround If this pop-up impacts your workflow, you can disable the Auto-Refresh feature: Go to Window → Preferences In the search field, type Firmware Updater Select: Offline Mode No Auto-Refresh at Application start Notes If Auto-Refresh is disabled, STM32CubeIDE will use the local cube-finder-db.zip file and will not automatically retrieve updates. Manual update If needed, you can manually update the data via: Help → STM32Cube Updates → Check for Target Selector Device Database Updates
Dear ST Community members, At the moment, STM32CubeMX2 uses the latest packs available on the public server.A script is available for a specific use case if you prefer not to start a project with the most recently published pack version.This script can be used when a project needs to be created or maintained with the STM32C5 v2.0.0 packs, instead of the most recent version available.If this matches your situation, feel free to use the script as an alternative.Where to get the script: check How to start with previous versions of HAL2 For more details on how to use it, please check the README. If you have any feedback, please don’t hesitate to share it with us in the: STM32CubeMX2 (MCUs) - STMicroelectronics Community The STM32CubeMX2 Team
An issue has been identified in which STM32CubeMX displays a download error pop-up during data updates. This issue does not prevent STM32CubeMX from working properly. To continue: Click OK twice. After these steps, STM32CubeMX can operate normally. If this pop-up affects your workflow, disable the Auto-Refresh feature: In Help → Connection and Updates, select No Auto- Refresh at Application start. Please note that if Auto-Refresh is disabled, STM32CubeMX uses the local cube-finder-db.zip file and does not retrieve updates automatically. If needed, manually update the data: Help → Refresh Data A fix is in progress in a future version.
We’re happy to announce that STM32CubeMX2 v1.1.0 has been released and is now available. This release includes updates and improvements aimed at enhancing the user experience and supporting your development workflow with STM32. What’s new Enhanced installation support for multiple STM32CubeMX2 versions, including linked IOC2 files and a pinned icon on the Windows taskbar Added Expand All and Collapse All functions in software configuration panels Added confirmation dialog boxes for selected actions Added options to export the pinout as CSV from a menu: without alternate functions or with alternate functions Added pin labels that can be used from configuration panels Improved command-line interface (CLI) capabilities for software configuration Added a pack version compatibility check Added end-user guidance to run Pack update steps in the correct order, with a focus on device family pack (DFP) and hardware abstraction layer (HAL) packs Increased pin name visibility in the pinout view to
We are pleased to announce that STM32CubeCLT 1.22.0 release is now available What is new in 1.22.0: Updated to align with STM32CubeIDE v2.2.0 Updated STM32CubeProgrammer to version 2.23.0 Updated ST-LINK GDB server to version 7.14.0 Updated JRE™ to version 21.0.10+7 Updated STARM-Clang to version 21.1.1+st.7 Updated Ninja to version 1.13.2 Updated CMake to version 4.3.1 Added support for make 4.4.1_st_20260330-0700 Main fixed issues in 1.22.0:Refer to the following Link here Know problems and limitations in 1.22.0: Refer to the following Link here How to get STM32CubeCLT 1.22.0: Download STM32CubeCLT 1.22.0 from here
We are pleased to announce that STM32CubeIDE 2.2.0 release is now available. What is new in 2.2.0: Added support for: STM32H5 microprocessors to the STM32H5 series STM3U3 series microprocessors to the STM32U3 series STM32V8 series Added support for new boards: NUCLEO-H553ZG NUCLEO-U345RC-Q, NUCLEO-U366RE-Q, STM32U366E-DK NUCLEO-V873XJ, and STM32V873J-DK Updated the target Platform to Eclipse 2025-12 and CDT™ 12.3.0 Added Multidrop support for debugging: STLINK-GDB server OpenOCD Segger J-Link Updated CMake to version 4.3.1 STARM-CLANG to version 21.1.1+st.7 Added support for OpenSTLinux 6.2.1 CMake static library template Ubuntu 26.04 and Fedora 44 Dependencies versions updates: Eclipse® 2025-12 and CDT™ version 12.3.0 Bundled JRE™: Adoptium® Temurin® 21.0.10+7 with JavaFX 21.0.10 ST-LINK GDB Server 7.14.0 supporting ST-LINK/V2 and STLINK-V3 SEGGER J-Link GDB Server V9.42 STM32CubeProgrammer v2.23.0 Open On-Chip Debugg
We are pleased to announce that STM32CubeProgrammer 2.23 is availableWhat is new in 2.23:AI Assistant : Sidekick is now accessible from STM32CubeProgrammer, with a dedicated access button at the top. Native Raspberry Pi support for the Linux Arm 64-bit command-line interface (CLI) package.You must choose Linux ARM in the download widgetReadable File Paths Launch After Install Online documentation. Support for STM32H543/553 devices: Internal memory programming through debug and bootloader interfaces Option bytes programming through debug and bootloader interfaces OTP programming through debug and bootloader interfaces Core register programming through debug interfaces Automatic mode Serial Wire Viewer Register viewer Firmware encryption/signing OBkey generation/provisioning Certificate generation Debug authentication SFI through debug interfaces Support for STM32U335/345 devices: Internal memory programming through debug and bootloader interfaces Option bytes programming th
Dear STM32CubeProgrammer Community, I hope you are all doing well. Over the past months, you may have received an email from me, either through the STM32CubeProgrammer survey or on other topics like CSAT or Raspberry Pi support. First, I would like to thank you a lot for all your contributions and feedback, we highly appreciate them, your voice matters ! We’re currently working on improving STM32CubeProgrammer’s usability and would like to 1. reduce the number of repetitive / low added value actions you have to perform, and 2. provide you with clearer error messages. We need your contributions to address priority scenarios. Could you please share in the comments which improvements, use cases, or automated actions you would like to see in the tool to make your daily work easier ? This includes typical errors you often get that you think the tool could prevent or handle automatically, as well as any “why do I have to do this myself every time?” situation you e
Hello The version 1.12.0 of STM32CubeMonitor is available on st.com : https://www.st.com/en/development-tools/stm32cubemonitor.html What are the main changes in this version ? Node-RED® updated to version 4.1.3. STM32 devices list updated. Software dependencies updated ( Electron, Chromium, nodeJS) The release note is available on ST.com : rn0119-stm32cubemonitor-release-v1120-stmicroelectronics.pdf Do not hesitate to create new posts if you have any question. The STM32CubeMonitor team.
Hello A new release of STM32CubeMonitor-RF is available on st.com. Click on "Get latest" to download the version 2.19.0. What are the main changes in this version ? Alignment with STM32CubeWB firmware 1.24.0. Alignment with STM32CubeWBA firmware 1.8.0. Alignment with STM32CubeWB0 firmware 1.4.0. Upgrade of Java® runtime version from 21.0.4 to 21.0.8 Upgrade supported OpenThread version to 1.4.0 API 511 Bug fix Changes details can be found in the release note RN104 and User manual UM2288 Note that whatever STM32CubeWB0 firmware 1.3.0 or 1.4.0 used, displayed version is 1.2.0 without futher impact on the tool behavior. Do not hesitate to create new posts if you have any question. The STM32CubeMonitor-RF team.
After generating a CMAKE project using STM32CubeMX2 v1.1.1 followed by setting compiler options to “treat warnings as errors” (-Werror) and enable strict standards-conformance (-Wpedantic) in the root CMakeLists.txt file, I am errors in, mx_def.h. Though this post shows the workaround:What is the recommended C Standard that STM32C5 project should follow? If the generated code stated “gnu11” but yet uses “gnu23”, shouldn’t the generator use the latter instead (see solution)? And, what are the dangers of doing so? Error Message:error: ISO C restricts enumerator values to range of 'int' before C23 Full Error message:[build] C:/PathTo/ProjectName/source/App/generated/hal/mx_def.h:32:38: error: ISO C restricts enumerator values to range of 'int' before C23 [-Werror=pedantic][build] 32 | SYSTEM_OK = 0xEAEAEAEAU, /* System initialization successfully */[build] | ^~~~~~~~~~~[build] C:/PathTo/ProjectName/source
I am having an issue with .ioc file association on macOS when using STM32CubeIDE 2.2 together with the standalone STM32CubeMX.The .ioc file does not seem to be properly registered with macOS.For example, in Finder, .ioc files are shown as unknown files rather than as STM32CubeMX project files.More importantly, when I open an .ioc file from STM32CubeIDE, STM32CubeMX is launched, but it stays on the welcome screen instead of opening the selected .ioc project.The behavior is roughly:STM32CubeIDE ↓STM32CubeMX launches ↓CubeMX stays on the welcome screen ↓project.ioc is not opened I've made some checks. macOS does not appear to assign a normal, application-specific UTI to the .ioc file.For example:mdls -name kMDItemContentType -name kMDItemContentTypeTree project.iocreturns:kMDItemContentType = "dyn.ah62d4rv4ge80w55d"kMDItemContentTypeTree = ( "public.item", "dyn.ah62d4rv4ge80w55d", "public.data")I also checked the application bundle:plutil -p /Applications/STM32
Hi, I have a custom product/board that has an embedded STM32L433. The STM32 is powered with an external battery. It is also connect through USB to a COM board that runs Windows. The COM controls the boot0 and reset pins of the STM32 which allows me to update the chip using CubeProgrammer API. I created a custom application in C# that worked fine until I tried to activate RDP level 1. Since I cannot do a POR, I implemented the activation of RDP in the STM32 software using the enter standby mode method. When I try to update with the RDP already active, I use the connectDfuBootloader2 method with rdu = true. This properly downgrade RDP from level 1 to level 0 and I am able to update the STM32 using the downloadFile method afterward. The issue is that after downloading the new software, the STM32 gets stuck in bootloader. The only way to get it unstuck is to call another time the connectDfuBootloader2 with rdu = true. This does not downgrade the RDP level, it only restarts the STM32 which
When building in STM32CubeIDE 2.1.1, and targeting an STM32F303K8,Project properties C/C++ Build Settings MCU GCC Compiler Miscellaneous Near the bottom, observe a checkbox for -mtune=cortex-a35.This option really does have effect in the gcc command line, and that really does significantly alter the compiled machine code.But… why is this allowed in the UI? Why would this tuning option appear specifically for the A35, when the STM32F303K8 is an M4? By default, the makefile does correctly add -mcpu=cortex-m4.
I’ve been using STM32CubeIDE, STM32CubeMX, STM32CubeProgrammer, and STM32CubeMonitor on a Mac currently running macOS 26.6.When I run env or export in Terminal (which uses Zsh by default), I find these two STM32-related environment variables.STM32CubeMX_PATH=/Applications/STM32CubeMX.app/Contents/ResourcesSTM32_PRG_PATH=/Applications/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/Resources/binExamined Zsh dotfiles in my home folder and found the following two *export*s in ~/.zshrc that set them.export STM32CubeMX_PATH=/Applications/STM32CubeMX.app/Contents/Resourcesexport STM32_PRG_PATH=/Applications/STM32CubeProgrammer/STM32CubeProgrammer.app/Contents/Resources/binWhich apps have added these; CubeMX, CubeProg, or perhaps the respective plugins from CubeIDE? What is their intended purpose, and in particular, which other STM32Cube tools rely on them? Also, do the apps add these every time on launch or only once during installation?
I discovered this issue while trying to program the Riverdi SM-RVT50HQSNWC01 using the STM32UG59. I spent days trying to figure out why the Riverdi demo in TouchGFX 4.26.1 was failing to program the external flash. It always failed when trying to erase external flash. This was with Programmer version 2.23.0. Even with the GUI version, I found that after connecting to the board, the first read of external flash would fail. Sometimes immediately, sometimes after a minute or so. I discovered that the second read performed immediately after the failure would work. Once I suffered through the first failure, I was able to read and program the external flash with no problem. I was ready to give up on the Riverdi board when I decided to try a different system. On this second system, I was able to create a demo from the Riverdi template, built it and program the board from TouchGFX 4.26.1. Same version as the failing system. I then noticed that the STM32CubeProgrammer on the second s
I made a project using CubeMX and imported it to CubeIDE. When I clicked Run → Debug, following message appeared, “The selection cannot be launched, and there are no recent launches.” I used CubeIDE version 1 before, and I could debug a program. What is wrong?
OK, thank you it is so easy to omit.Could you please help me with another issue on usbx: Default value for “CoreStack Device/Host” is “enable” but there is warning in red: The component “USBX/CoreSystem” must be selected alongside either “USBX/UX Host CoreStack” or “USBX/UX Device CoreStack” Core Sytem is selected as you can see. Or is it referencing to some other component?
I'm using a Macbook Air M5. I downloaded the STM32CubeIDE 2.2.0 macOS (Apple Native) version to my computer. After importing my projects, I tried to debug. It connects to the ST-Link and performs the necessary operations. Then, when debugging is ready, I start the debug and get this error: GdbSession, Lost target connection, Exiting... GdbSession, Lost target connection, Exiting... I checked the permissions on my Mac and updated the STM Link version. Also, when I install the Mac (Apple Native) version of STM32CubeProgrammer, I can program the same board using the ST-Link. The port is visible. And interestingly, when I open the same project on my Windows computer, I can debug it without any problems using the same ST-Link.Any advice on how to resolve this issue so I can debug directly from STM32CubeIDE would be greatly appreciated!Thanks in advance for your help.Best regards,
Hello everyone,I am experiencing an issue with STM32CubeMX version 6.18.0 right after a fresh installation. The software is unable to connect to the server to download repositories or updates.Here are the details of my situation:Network Environment: I am using my office Wi-Fi, which does not use a proxy server. Other applications connect to the internet without issues. Error Message: I keep getting a "Problem during server connection" error. Troubleshooting Done: I have already gone into the Connection Settings and tried changing the proxy settings to "No Proxy" as well as "System Proxy", but neither option resolved the issue. Since there is no proxy on our network, I am unsure what is blocking STM32CubeMX from reaching the server. Has anyone encountered this with version 6.18.0, or does anyone know which specific ports or URLs need to be whitelisted in our office firewall?Any help or guidance would be greatly appreciated. Thank you!
Hello,I am currently working on an AI project on the STM32N6570-DK using STM32Cube AI Studio and STM32CubeIDE.I followed the official STM32N6 AI deployment tutorial and generated both projects:FSBL AppliThe AI files generated by STM32Cube AI Studio were copied into the project and the project builds successfully without errors.The application is downloaded correctly to the board and the verification step is successful. However, when the debugger tries to start the execution, the target immediately stops responding.The console shows:Download verified successfullyError in executing 'cont' commandTarget is not responding, retrying...I also get a message indicating a break at an address outside of the application code.At this point I am not sure if:the application is entering a HardFault very early during startup, there is an issue with the FSBL configuration, there is a problem with the linker script or the AI memory sections, or if I missed a configuration step in the STM32N6 deployment
Hi,I'm bringing up a USB MSC device on an STM32U385CGT6 with the USBX middleware in standalone mode. Everything comes from CubeMX 6.18.0 with STM32Cube FW_U3 V1.4.0 (USBX 6.4.0): USB_DRD_FS in device mode, USBX Core System + UX Device CoreStack + UX Device Controller + UX Device MSC.While comparing the generated code and some example applications (NUCLEO-U385RG-Q Ux_Device_HID_Standalone) it looks there is a regression in the generated HAL_PCD_MspInit. While the version from the example application enables Vdd USB, this is missing from the currently generated version of HAL_PCD_MspInit causing the peripheral to remain powered down. As a fix HAL_PWREx_EnableVddUSB(); can be called in the user code section at the bottom of HAL_PCD_MspInit. Best Regards, Cecil
I have an older v1.0.0 installation that works fine, but the newer v1.1.1 freezes up on launch and does not respond to mouse or keyboard input. 2026-08-14T09:04:40.380Z [Error] Could not initialize contribution TypeError: Cannot read properties of undefined (reading 'onChanged') at g.initializeEventWatchers (file:///home/user/.local/share/STMicroelectronics/STM32CubeMX2_1.1.1/resources/stm32cubemx-application/1.1.1/dist/resources/app/lib/frontend/bundle.js:92134:94886) at g.initialize (file:///home/user/.local/share/STMicroelectronics/STM32CubeMX2_1.1.1/resources/stm32cubemx-application/1.1.1/dist/resources/app/lib/frontend/bundle.js:92134:94735) at file:///home/user/.local/share/STMicroelectronics/STM32CubeMX2_1.1.1/resources/stm32cubemx-application/1.1.1/dist/resources/app/lib/frontend/bundle.js:92524:49789 at r.startAsync (file:///home/user/.local/share/STMicroelectronics/STM32CubeMX2_1.1.1/resources/stm32cubemx-application/1.1.1/dist/resources/app/lib/frontend/bundle.js
ST Community highlights – April to June 2026
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.