Join discussions in the Product Forums. Ask questions, learn from your peers, and share insights on ST solutions to accelerate your design journey.
Most recent activity
🚀 StellarStudio 9.2 — Release NotesStellarStudio 9.2.0 version is officially published. (Windows, macOS, Linux) based on Eclipse 2026-03 and CDT 12.4.0 with standalone tools (Java 21).🧰 Standalone ToolsRequires Adoptium Java 21. Available for Windows, Linux, macOS.Tool Supported Device Families StellarStudio Pinmap Configurator ⬅ G3 added in 9.2 SR5E1, SR6P3, SR6P3E, SR6P6, SR6P7, SR6G7, SR6G6, SR6G3 StellarStudio NoC Configurator ⬅ P3E added in 9.2 SR6G6, SR6P3, SR6P3E, SR6G7, SR6P6, SR6P7 StellarStudio Clocktree Configurator ⬅ G3 added in 9.2 SR5E1, SR6P3, SR6P3E, SR6P6, SR6P7, SR6G7, SR6G6, SR6G3 StellarStudio Power Consumption Configurator ⬅ P3E added in 9.2 SR5E1, SR6G6, SR6P3E ✨ What's New in This ReleaseSR5E1 public device🔵 FIX — Multicore debug with StellarLink / OpenOCD 🔵 FIX — Wrong symbol recognition in IDE when defined in MakefileSR6 restricted devices (On demand, contact our sales office)SR6 common🔴 REMOVE — Removal of SR6P7G7 MCU from the tool (the oth
Hi fellow developers, Welcome to the new STM32CubeCLI topic! This is the place to ask questions, report issues and share ideas about STM32CubeCLI. What is STM32CubeCLI? STM32CubeCLI lets developers and DevOps engineers find, download, install, update and run ST tools (bundles) with one cube command: GCC, CMake, Ninja, STM32CubeProgrammer, ST-LINK GDB server and more. It runs on Windows, Linux and macOS. Tool versions can be pinned per project, so your laptop, your teammates and your CI runner all use the same tools.If you use STM32CubeIDE for VS Code or STM32CubeMX2, you are already using STM32CubeCLI. It installs and updates their tools behind the scenes. Get startedDevNews introduction article: https://community.st.com/stm32-software-tools-165/introducing-stm32cubecli-your-stm32-toolchain-from-the-command-line-168704 Documentation (growing): https://dev.st.com/stm32cube-docs/stm32cubecli/latest/en/index.htmlIn a project with pinned tools:cube bundle install --projectcube cmake --pres
Pleased to announce that the new release 3.11.0 of STM32CubeIDE is online FeaturesProject Creation Modes: Two distinct modes for project creation are supported, offering flexibility in development workflows: STM32CubeMX Projects: Supports project creation with integrated CMake, enabling streamlined configuration and management. Empty Projects: Allows for the creation of bare projects with CMake, providing a clean slate for custom development. Cube Discovery Process: Project import step, designed to allow STM32 developers to easily move legacy CMake code bases into STM32CubeIDE for Visual Studio Code and configure the tooling properly. Edit & Compile Tools: The following edit and compiler tools part of the package: clangd indexing: Helps developers navigate, write, understand, and improve C/C++ code. Microsoft CMake Tools: Provides developer a full-featured, convenient, and powerful workflow for CMake-based projects in Visual Studio Code. Build Analyzer: A new build analyzer ha
Dear STM32 Community, We believe that the example projects provided for the STM32Cube embedded software are a valuable resource when developing projects. We would like to better understand how developers use these examples in their workflow and explore ways to improve them. Therefore, we have a few questions we would like to ask: From where do you obtain the examples, and why? Are you working with the examples through the STM32Cube MCU packages, the STM32CubeMX Example Selector, or through GitHub? Is there a particular reason you prefer one channel over the others? How do you use the examples in your work with STM32 embedded software? Do you use the examples to learn how to use a driver or a feature, as reference code for implementation, and/or for debugging? What is working well, and what can we do to improve the examples and/or your experience working with them? You can either reply directly in this thread or feel free to send me a private message. &nb
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 docum
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
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 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 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 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
We wish to always improve our documentation. The best reviews and critics always come from the people that read it, so we would like to use this post to collect your thoughts and feedbacks. Please share what you like, dislike, what you think is missing, etc ... /The TouchGFX team
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
When creating a UI project, you may need widgets that are not part of the TouchGFX library. To create your own graphical element, the TouchGFX team suggests using the Custom Container approach. Since TouchGFX 4.20 it is possible to export and import Custom Containers into different projects. The TouchGFX team is working on developing new custom containers that could be useful for our own projects. You will find them under this post. The first widget is a keyboard. We hope that the idea will please you and that it will be useful for your projects ;)! We invite you to do the same. In the guide attached you will learn how to create your own widgets and how to export them. We wish to create a space where the community can find and share custom widgets. To keep this space a good place for collaboration between all of us, we invite you to share your project in a zip format which includes you widget (.tpkg) and a short document explaining your widget. Your post needs
We are pleased to announce that STM32CubeProgrammer 2.22 is available What is new in 2.22: Support for the STM32U3 microcontrollers with 2 Mbytes of flash memory: 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 RDP regression with password SFI through debug and bootloader interfaces (USB and UART) Support for STM32C5 series microcontrollers: 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 Register viewer Firmware encryption/signing RDP regression with password Support for STM32WBA2xxx microcontrollers: Inter
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.
Dear MCSDK users, The full MCSDK documentation is embedded in the Motor Control Workbench tool. Refer to Workbench tool > About > Documentations > Documentation.This document provides: Introduction: Includes startup guide links for MCSDK, HSO feature, MC Workbench and Pilot tools. User manual: Description of Motor Control features, algorithms, reported errors and procedures to address them. Motor control firmware files, functions, and data. You can also access the HTML documentation at the following location:file:///C:/_your_install_folder_/MC_SDK_x.y.z/Documentation/html/index.html Motor Control wiki page with FAQ page for MCSDK versions prior to MCSDK6.x
Dear MCSDK users, MCSDK version 6.4.0 is now available: Download It here. This version of the new Motor Control SDK 6 series (X-CUBE-MCDSK) provides mainly FOC and 6Step improvements, here are the main changes for this version: Motor Control Features: Common: Regular conversion manager (RCM) component has been modified to reduce memory footprint and to meet the requirement of synchronizing ADC conversions "regular" and "injected". 6Step: Increased 6Step firmware architecture efficiency and reduced FLASH and RAM Memory footprint Added Initial Position Detection and On-The-Fly Startup features. Added Software Current Sensing Monitoring mode supported for series STM32C0xx/F0xx/F3xx/G0xx/G4xx. FOC: New Maximum Modulation Index (MMI) computation compatible for all sensor-less or sensor algorithms. Mitigated speed overshoot during startup. Added ICS (Isolate Current Sensors) support for profiler for F3, G4, F4, F7, and L4. Added the ability to switch to/from primary to aux
When installing some StellarStudio plugins http://*.srxstudio.org , you can meet the issue : sun.security.validator.ValidatorException: PKIX path building failed It is typical IT Issue :face_screaming_in_fear: in each corporate company. “"Path building" refers to the process of verifying a chain of certificates from a specific certificate up to a root CA (Certificate Authority) certificate. If this process fails, it means that the application could not construct a trusted path from the server's certificate to a root CA.” IMPORTANT : The customer needs to install their own root certificate in JRE StellarStudio keystore Typically this keystore is at c:\StellarStudio-5.0\eclipse\jre\\lib\security\cacerts. The keytool that is used to access the keystore is typically installed with the JRE and ready to use. Run the standard keytool to import the certificate, from c:\StellarStudio-5.0\eclipse\jre\\lib\security\cacerts. c:\StellarStudio-5.0\eclipse\jr
Dear community member, The “Analog and audio” topic is no longer supported on the ST community. The legacy content is available only by the read-only basis. If you have any requests regarding "Analog and audio” topics, check the alternative support channels at ST: Support Home.We apologies in case of any inconvenience. ST community team
The documentation of the Board descriptions format is now available on Motor Control Boards Description Wiki page, this documentation is compatible with MCSDK versions from 6.1.2. Board Descriptions are used by the ST motor-control workbench to enable users to configure their motor-control application and produce a software project that implements it following its hardware component features. Wiki Link A new documentation will arrive soon and will detail these features: Current Sensing: three-shunt-raw-currents-differential-internal-opamp-with-external-gain-and-filtered-adc-intput-hwv ICS Phase Voltage sensing feature Driver Protection feature The descVersion property is equal to 4 from version 6.2.0 of the MCSDK and the "contentVersion" property is added. For questions regarding the board manager, please respond under this post. Regards
ST Community highlights – April to June 2026
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
