STM32 MCUs

TouchGFX 4.26.1 is now out. Please follow this link to download it.This version is a patch release and includes bugfixes of issues seen on TouchGFX Designer 4.26.1 version, as well as adding support of the new STM32H5F5 and Chrom-ART 2.Please visit our dedicated website for STM32H5 graphics to know more about high performance graphics on our most powerful Cortex-M33 MCU. Release details: Release date: March 2nd, 2026 New TouchGFX Designer Features Allow selecting a CMakeLists.txt file as the project file without requiring a STM32CubeMX .ioc file. Bugfixes in TouchGFX Designer Fix caching issue when changing text configurations and re-generating code. Fix outdated timestamp on files when importing a GUI. Fix faulty code generation when a Shape widget has two identical end points. Fix faulty code generation when a Shape widget uses an "interaction ended" callback. New TouchGFX Generator Features Support for STM32H5F5/E5 and STM32H5F4/E4 series with the

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

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

This project tests the STM32C5's XSPI capability to drive QSPI display using the NUCLEO-C5A3ZG M.2/SerialMem connector. GitHub - stm32-hotspot/STM32C5-M2-Serial-Mem-QSPI-Display · GitHub 

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

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

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 2.1.1 of STM32CubeIDE is available. What is new in 2.1.1: This release covers the topics listed below: SEGGER J-Link GDB server updated to 9.24 to fix an issue with the Live Expression view during the debug session Cmake updated to 3.30.8 to support "QUOTE" expression Main fixed issues in 2.1.1: Refer to the STM32 microcontroller wiki at: https://wiki.st.com/stm32mcu/wiki/STM32CubeIDE:STM32CubeIDE_errata_2.1.x Known problems and limitations in 2.1.1: Refer to the STM32 microcontroller wiki at: https://wiki.st.com/stm32mcu/wiki/STM32CubeIDE:STM32CubeIDE_errata_2.1.x How to get STM32CubeIDE 2.1.1: Under this link Or update your current installation of STM32CubeIDE using: Help > Check for updates (The in-tool update does not allow updating the drivers and STLINK server tool. Full installation is required for this to be done).

Dear community we are pleased to announce the new release of STM32CubeIDE for VSCode Breaking Changes Complete architecture redesign: The tool architecture has been split into three major building blocks with the purpose of creating a flexible, maintainable and updatable platform consisting of the following blocks: GUI, CLI tools and STM32 device support. GUI: The platform's single extension has been transformed into an extension pack, offering a more modular, updatable and flexible setup. CLI tools: A new bundle manager is enabling VS Code to download required CLI tools. This replaces the all-in-one STM32CubeCLT package. The bundle manager will provide developers flexibility, updatability and re-producibility in terms of CLI tooling. STM32 device support: The STM32 device support is decoupled from VS Code and sourced via CMSIS-PACK DFPs. Developers can now start using a new MCU without having to install a new STM32CubeCLT package.

We are pleased to announce that STM32CubeCLT 1.21.0 release is available. What is new in 1.21.0: Maintenance of the previous version: Updated in accordance with STM32CubeIDE v2.1.0 Update of Clang/LLVM toolchain Update of GCC to GCC 14 Update of STM32CubeProgrammer to version 2.22.0 Update of ST-LINK GDB server to version 7.13.0 Update of JRE™ to version 21.0.9+10 Update of STARM-Clang to version 21.1.1 Support for Apple® Silicon with ARM64 architecture Main fixed issues in 1.21.0: No fixed issue to report.  Know problems and limitations in 1.21.0: The user must specify the path of STM32CubeProgrammer/bin as argument when executing STLINK_gdbserver as shown in the example below: ST-LINK_gdbserver.exe -cp /c/ST/STM32CubeCLT/STM32CubeCLT/STM32CubeProgrammer/bin How to get STM32CubeCLT 1.21.0: Under this link    

We are pleased to announce that version 6.17.0 of STM32CubeMX is available. What is new in 6.17.0: Added support for new microcontrollers across the STM32WBA, STM32H5, and STM32U3 series Added support for new boards: NUCLEO-WBA25CE1, NUCLEO-H5E5ZJ, STM32H5F5J-DK, and NUCLEO-U3C5ZI-Q Added the Start From Board feature for NUCLEO-U3C5ZI-Q, NUCLEO-H5E5ZJ, and NUCLEO-WBA25CE1 Added support for new features: PLAY on STM32H5 devices with 4 Megabytes of flash memory HSP on STM32U3 devices with 2 Megabytes of flash memory  STM32CubeMX Notification Service: allows users to subscribe to notifications, updates, or premium content when downloading or installing STM32 software. The subscription to this service is entirely optional and is not mandatory for downloading or installing the software.​ Enhanced the memory management tool for the STM32N6 series Implemented the use of the CMake build generator with STM32MP2 projects Enhanced the build process using CMake

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.

Starting from the release in November 2025, STM32CubeIDE and STM32CubeMX will be available exclusively in their standalone versions. STM32CubeMX will no longer be integrated inside STM32CubeIDE. Instead, the two tools will be interoperable in the same way as with IAR EWARM, Keil MDK-ARM, and STM32Cube for VS Code. The current integration of these two tools may seem compelling in the early prototyping phases of a project. But the integration leads to heavy/poor performance, stability issues across OSes and monolithic updates. It is time for STM32CubeIDE to go back to its roots and focus on Edit / Compile / debug.   What the STM32CubeIDE (2.0) evolution will bring to you:  Greater flexibility in code development thanks to purpose-built, standalone tools.  Updateability: Offering the possibility to use any version of STM32CubeIDE with any version of STM32CubeMX. Separating STM32CubeMX and STM32CubeIDE a

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.

Major change in SigningTool for STM32N6 in STM32CubeProgrammer v2.21.0 This release, we decided to change signing tool behavior to not automatically align the payload to 0x400 with padding bytes, since this is not necessary for other STM32 series. To sign binaries for STM32N6, please take care to add the -align or --align option to the signing tool command, example: >STM32_SigningTool_CLI.exe -bin Project.bin -nk -of 0x80000000 -t fsbl -o Project-trusted.bin -hv 2.3 -dump Project-trusted.bin -align  

  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

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

Please go and visit our wiki pages where you can find a lot of information on our wireless product families (WB, WBA, WL) and the supported protocols: BLE, Zigbee, Thread, Matter, Lora, ... To begin your technical journey, please start from this top page: https://wiki.st.com/stm32mcu/wiki/Category:Connectivity This top page will guide you to the first steps to develop a wireless application using connectivity protocols on ST wireless microcontrollers.   For BLE protocol, please visit: https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_BLE_with_STM32https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_Bluetooth_LE_Audio You can find information on BLE Certification, BLE Features, BLE Mesh, BLE Audio, …   For Zigbee protocol, please visit: https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_Zigbee You can find information on Zigbee certification, Zigbee Features, BLE-Zigbee concurrent mode, …   For Tread protocol, please visit: https://wiki

Dear all, The X-CUBE-MATTER Expansion Package is now available on our official website following this link  MATTER - Matter software expansion for STM32Cube - STMicroelectronics  It is a reference implementation for the demonstration of Matter on STM32. It is ready for prototyping a Matter end-device on a reference development platform. Refer to STMicroelectronics Matter wiki articles at https://wiki.st.com/stm32mcu/wiki/Connectivity:Introduction_to_Matter to get started with matter for the supported STM32 platforms. Kind regards, Ouadi

In order to have a quick response to your forum posts, the best way to ask the question is:- Give the version of the MCSDK used. - Say if the problem concerns a tool (MC Workbench, Motor Pilot, Motor Profiler, etc...) - Provide picture of tools interface when is possible.- Attach the STWB6 file of the project or the JSON of the board when possible.Choose a label for the post ( Motor Pilot MC Workbench, etc...), you can select it to the right of where you write the message.Here is a template that you can reuse:[PN]: Part Number of the products used[VERSION]: Version of MCSDK[TOOL]: Name of tool ( Firmware, MC WB,MC PROFILER, etc..)[DETAILS]:symptom observed or request/question details[EXPECTED BEHAVIOR]:if related to performance then what is the target[HOW TO REPRODUCE]:input, output, steps But before entering a new post, please consider to first check our Motor Control documentation available via Work Bench Tool by clicking on About -> Documentations -> Documentation -> i