STM32CubeIDE (MCUs)

I would like to move the project from:C:\ST\STM32Cube_FW_WB_V1.24.0\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_HeartRateFreeRTOSto:C:\Projects\Myprojectso that I can make modifications at will and not worry about corrupting the original code. At the same time, I want all the libraries, etc. to fall under the same directory as the new code will eventually be submitted to version control.How can I do this?Note: All my other projects under the C:\Projects directory were started with CubeMX and all seem to do as I want.

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?

STM32CubeIDE v2.2 has left all of our code in question. We need guidance with the CMake since we no longer have any helper dialogs of the old IDE to create a project within the new framework that matches the old IDE. list of helpful guidesNo HAL is neededa CMSIS and DFP environment for the selected processorCMake snippets that allow us to create and include legacy library code (adjusted for new processor)methods to control code optimization for code sections and filesdirectory structure methodsbasic commands to show what size of code we just compiled and output formats ie .hexWe believe this would be a great tutorial to ease the transition. I’m sure I have missed many other features of the old environment that you will quickly attend to.Any guidance that doesn’t require 200 hours of head banging appreciated. Glenn

I'm in debug mode in STM32CubeIDE.On the SFRs tab in the upper right corner, I want to enable UART4 and check the register status.But I only see UART-related items: LPUART/USART1/USART2/USART3.Why can't I find UART4?My MCU is an STM32C551RCT6.I'm very certain this IC has UART4

Hello,we’are using CubeIDE (1.19 so far) and STM32H750B-DK boards for our several University courses. We have quite big repositories with working projects (mostly based on CubeMX generated .ioc and code) that can be edited, regenerated, debugged flawlessly in 1.19.Is it possible to import those projects in V2 and regenerate code and .ioc files in new v2 environment as it was possible before?I’ve heard that users have problems with migration of these types of projects - is this true? If there are problems, what to do in this situation? Will this ever be solved? Thanks,regards,Robert.   

Hello ST Community,I am following the tutorial "How to deploy an AI model on STM32N6 – Neural-ART":https://dev.st.com/edge-ai-docs/general/latest/en/docs/tutorials/how-to-deploy-ai-model-stm32n6-neural-art.htmlI successfully completed all the steps, but when building the application in STM32CubeIDE, I get the following linker error: arm-none-eabi-gcc -o "Test_inference_model_Appli.elf" @"objects.list" -l:NetworkRuntime1201_CM55_GCC.a -mcpu=cortex-m55 -T"C:\Users\ROMAINC\Test_inference_model\STM32CubeIDE\Appli\STM32N657X0HXQ_ROMxspi2.ld" --specs=nosys.specs -Wl,-Map="Test_inference_model_Appli.map" -Wl,--gc-sections -static -Wl,--cmse-implib -Wl,--out-implib=./secure_nsclib.o -L../Middlewares/ST/AI/Lib --specs=nano.specs -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -Wl,--start-group -lc -lm -Wl,--end-groupC:/ST/STM32CubeIDE_2.1.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.14.3.rel1.win32_1.0.100.202602081740/tools/bin/../lib/gcc/arm-none-eabi/14.3.1/../..

I open up CubeIDE, select a workspace, click “Import projects”  the project explorer tab (excuse the typo)  There is project there, But nothing appears in the Project Explorer,  

Hi,I have project for STM32F405 created manually. Project is using fixed GCC 4.92014q4.After updating STM32CubeIDE to version 1.14.0 i got warnings shown below.Compiler option "Cyclomatic Complexity" is disabled.File "subdir.mk" contains this rule:# Each subdirectory must supply rules for building sources it contributes Src/%.o Src/%.su Src/%.cyclo: ../Src/%.c Src/subdir.mk How to remove this warnings?

 Is it possible to make the command line and description for pre-build and post-build steps larger? It’s a nightmare working with them as they are.I know you can call a script file, but it would still be nice to see more than just a single line.

STEVAL-FCU001V2について、ST社のサイトからダウンロードしたプロジェクトをStm32CUBEIDEで開き、以下の修正を実施。修正1ヘッダーファイル：rc.hについて、REMOCON_BLEからREMOCON_PWMにモード変更。 #define REMOCON_PWM // 外部リモコンRX 4チャンネルPWM修正2 \stsw-fcu001\STSW-FCU001\STEVAL-FCU001V2\Core\SrcにあるSysmem.Cについて、ソースコードに書かれていたcaddt_tが、廃止されたtypedefであった為、void *に変更。上記修正後にBuild ALLを行ったが以下のメッセージが出る。重大なエラー:custom_motion_sensors.h:そのようなファイルまたはディレクトリはありません。custom_motion_sensors.hはフロクトジェ内の別フォルダに、存在しているのでパスまで指定してもう一度Build ALLを試しましたが、結果は同じで、ヘッダファイルのインクルードは結局出来ませんでした。

Hi ST Community,I’m working with an STM32N6 project and I am facing a build issue after generating a project with STM32CubeMX.The project generates successfully and the driver folder is present, but when I open it in STM32CubeIDE and build, I get many linker errors related to missing HAL functions.I checked the STM32N6xx  HAL driver folder, and I do not see the HAL source files  It looks like the generated CubeIDE project is not adding the HAL driver  files into the build.My setup:STM32CubeIDE: 2.2.0 STM32CubeMx: 6.18.0Can you please advise if there is any additional setting required to avoid this issue ?  or if this is a CubeMX generation issue?

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

I’m trying to build the LED example for the P-NUCLEO-WB55.USBDongle.I have included all the necessary include & source paths yet when I try to build it exits with the following, This file does actual exist though,  and its location is in the paths list, What am I missing here?

Hello, When you start STM32CubeIDE with this settings removed : Run/Debug → Launching → General Options → Build (if required) before launching, the debugger couldn’t start, nothing happens, no error in logs.You have to set again this settings, launch debug, then remove again this settings, and now debug can work.Laurent.

  I wrote a Python book, but I am new at STM32. I bought a STM32F407G Discovery Board. And I bought related books. A related book describes the Stm32Cube IDE. But it used version 1.12.1 He started the project with "Fille--New--STM32 Project" . Then the program opens the STM32CubeMX. But the version of my STM32cubeIDE  is 2.11. and there is no "STM32 Projects" in File--New. From where should I  start for a new STM32 project in version 2.11?  And how do I reach to STM32CubeMX window  from STM32CubeIDE 2.11? 

This account only shares restored community content posted by members between May 22 and June 9, 2026, who did not register for the new community.Hello, I am struggling getting my code generated and to compile it..I am working on VirtualBox with Ubuntu OS, and I have downloaded the standard Linux STM32CubeIDE.When creating a project, my mcu ode is not being generated within the files.. I had also installed the STM32CubeMX and was able to select my HW there and I get my code generated properly.. but I cant import it into STM32CubeIDE... if I import, then I cannot Build the code... (picture below)

NUCLEO-V873XJ board bring-up.STM32CubeIDE 2.2.0 includes support for the STM32V8 series devices; however, the NUCLEO-V873XJ board is currently not available within STM32CubeMX board configurations

EDIT: Solved. It seems to just be that one pin that isn’t working. I tried a couple other ones and they work fine.Hello, sorry if this is a silly question, but I'm pretty new to all of this. I've recently picked up Israel Gbati's Bare-Metal Embedded C Programming. It gives a step-by-step walkthrough on how to turn on an LED using pin D12/PA5, but I'm struggling to connect to any of the other pins.I've been trying to connect my LED to pin D0/PA3. My code is below.#define PERIPH_BASE (0x40000000UL)#define AHB1PERIPH_OFFSET (0x00020000UL)#define AHB1PERIPH_BASE (PERIPH_BASE + AHB1PERIPH_OFFSET)#define GPIOA_OFFSET (0x0000UL)#define GPIOA_BASE (AHB1PERIPH_BASE + GPIOA_OFFSET)#define RCC_OFFSET (0x3800UL)#define RCC_BASE (AHB1PERIPH_BASE + RCC_OFFSET)#define AHB1EN_R_OFFSET (0x30UL)#define RCC_AHB1EN_R (*(volatile unsigned int *) (RCC_BASE + AHB1EN_R_OFFSET))#define MODE_R_OFFSET (0x00UL)#define GPIOA_MODE_R

Does anyone know what the productname.xml file in a Cube IDE directory does?<?xml version="1.0" encoding="UTF-8" standalone="no"?><targetDefinitions xmlns="http://openstm32.org/stm32TargetDefinitions" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://openstm32.org/stm32TargetDefinitions stm32TargetDefinitions.xsd">  <board id="xxx">    <name>XXX</name>    <mcuId>stm32f417vgtx</mcuId>    <dbgIF>JTAG</dbgIF>    <dbgDEV>ST-Link</dbgDEV>  </board></targetDefinitions>Mine is dated 2019 so may not be used.I am on Cube IDE 1.14.1. ST32F417/437. Later versions do nothing new and just carry on with the same bugs e.g. the random file opening.

I have created a project for the STM32WL33 several weeks ago, using the DEEPSTOP mode with context restoration provided by ST. Even if there are some pitfalls with this the project worked mostly fine. But after the update to STM32CubeIDE 2.1.0 I get a compilation error:./System/Startup/cpu_context_switch.o(CPUcontextRestore): Unknown destination type (ARM/Thumb) in ./Core/Src/system_stm32wl3x.odangerous relocation: unsupported relocationmake: *** [makefile:89: Euris3-EHKV-WMBus.elf] Error 1I've reverted the version to 2.0.0 and the error is gone.

Above image you can see in toolchain option STM32IDE is disable . also i am facimng issure i =n import examples which stm32 provided for reference . you can also refer my shared video.

I recently purchased a new Windows on ARM laptop—a Snapdragon X2 Elite, to be exact. Like many others, I ran into issues getting the ST-LINK/V2 to work because of driver compatibility. I ended up working on a fix that allows STM32CubeProgrammer to connect to the ST-LINK/V2 using the Windows WinUSB driver. Simply changing the driver to WinUSB isn’t enough—the ST-LINK device interface GUID also needs to be added/updated so that STM32CubeProgrammer can properly detect and communicate with the probe. Updating the ST-LINK/V2 firmware presented another problem. When the ST-LINK enters firmware-update mode, it enumerates as a different USB device. This means the firmware-update/DFU interface also needs to be configured to use WinUSB.With this fix, you can now update the ST-LINK/V2 firmware directly from a Windows on ARM computer. There is no longer a need to connect the ST-LINK/V2 to an Intel/AMD Windows computer just to perform a firmware update. The next issue was STM32CubeIDE. Even though