STM32CubeMX (MCUs)

I tried to install CubeMx 6.17.0  i get following errorHow do i resolve? 

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

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?

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,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

Hi,I am trying to migrate a STM32F767ZGT6 based project to STM32H743ZGT6. According to AN4936, they should be pin to pin compatible. When I manually compared the each pin, and assigned the state of each PIN as used in STM32F767ZGT6 to STM32H743ZGT6, they seem indeed to be P2P compatible too. But If I try to list PIN compatible MCUs in STM32CubeMx, as of the latest v6.17.0, STM32H743ZGT6 is not listed. Please see the screenshot below:Am I missing something? Or this is a bug in CubeMX? I just don't want to throw 100s of $ down the sink. I attached my IOC file to see if anyone can reproduce my problem.Thanks.

I am running the pre-compiled "object Detection" files on the STM32N6570-DK and am in the process of trying to generate my own STM32CubeMX setup project for the fsbl.I am having difficulty setting up the numerous options for the DCMIPP for this project and have read a lot of the recommended documentation but there does not seem to be any specific details for interfacing to the MB1854 camera module on this kit.From what I can figure out the "Object Detection" demo uses pipe1 for the display and pipe2 for the NPU processing but I am lost as to what settings to use for DCMIPP in STM32CubeMX.I need to know what pipe formats, data types etc are needed for each of the pipe1 and pipe2 settingsCan anyone please help me with this?

CubeMX Project Manager has a bug, where when I accidentally cleared the "Project Location" field and moved the cursor away CubeMX complains that project location cannot have special characters and cannot be empty. But this popup does not go away and gives you no chance to correct your mistake. Screenshot attached. Host OS: Ubuntu 24.04.4 CubeMX version: 6.15.0  Edit: Turns out there was a new version of CubeMX (6.17.0) where this problem disappears. You click 4-5 times on OK and the dialog disappears. Should I delete the question in this case?

I use  GPU2D on STM32U599Z .On CubeMX, I  checked Activate check box  GPU2D  at "Pinout & Configuration".and  I saw " Project Manager > Advanced Settings" There is not GPU2D In Register Callback Groupe. However , The Generated code stm32u5xx_hal_conf.h have  "  #define USE_HAL_GPU2D_REGISTER_CALLBACKS 0U /* GPU2D register callback disabled */How to set this setting? 

(Moved to a separate thread from  Do you need a fast slave interface with high throughput? This is for you.)MCUFinder does not consider PSSI if I do not overlook something.

Hi,I use cubemx to generate code for STM32CubeIDE, compile is OK, but the initial process run fail with HAL_Delay function, the HAL_GetTick() always return 0 so the program blocked here. attached is my .ioc file, any anyone help for thie issue?

Moved to CubeMX forum as this is about the CubeMX functionality - even though it's within CubeIDE.hello everyone. I'm trying to code my H7 chip. In the .ioc shen I try to generate code I take this error. (I'm using CubeIDE 1.19.0) then I turn back and look at my Clock configuration, only this HSI button has a issue.  and ı dont know how to fix this and is there any problem with the HSI usage. also the other of all the clock config is :I couldtn find same problem in the forum. or a solution. 

Description:In STM32U083 series, when multiple UART/LPUART instances share the same NVIC interrupt vector (e.g., `USART3_LPUART1_IRQn`), STM32CubeMX incorrectly generates `HAL_UART_IRQHandler` for all instances, even if one of them is configured in IrDA mode.This leads to a compilation error because:1. The handle for the IrDA instance is generated as IRDA_HandleTypeDef hirdax; (correct).2. However, in stm32u0xx_it.c, it attempts to call HAL_UART_IRQHandler(&huartx); using an undefined huartx handle.Environment:STM32CubeMX Version: 6.17.0OS: Ubuntu 24.04 LTSMCU: STM32U083RCTxFirmware Package: STM32Cube FW_U0 V1.3.0 Steps to Reproduce:1. Create a new project for STM32U083RCTx.2. Configure USART3 mode as IrDA.3. Configure LPUART1 mode as Asynchronous.4. In the NVIC Settings tab, enable the interrupt for "USART3 + LPUART1 global interrupt".5. Generate the code.6. Check `stm32u0xx_it.c`.Actual Result:The generated ISR code looks like this:/** * @brief This function handles US

Hi Everyone,I need your help.I use STM32H573VIT but I can't FATFS in CUBEMX.I checked FILEX, SD interface. But CUBEIDE say fatfs.h : No such file or directory. Please help me out..Thanks,kadekade 

Hello.I created a project for the STM32F769I-DISCO board using CubeMX.I am trying to follow an LVGL example, but the example uses BSP-based libraries, and they are not working in my project. After checking, I found that there is no BSP included anywhere in the generated project.From what I understand, when selecting a board in CubeMX, the BSP should normally be included automatically. However, in my case, it is not.I tried downloading the STM32F769I-DISCO BSP from GitHub and manually copying it into the Drivers folder. However, this caused many build errors, possibly due to missing dependencies or incomplete integration, so I reverted those changes.Could you please advise how to properly include or enable BSP for this board when using CubeMX?Thank you.

In STM32CubeMX v6.17.0, in the left side of the Pinout & Configuration panel, if the mouse cursor is within a table that lists peripherals, the scroll wheel doesn't do anything. I expect it to scroll the window. You need to move it outside of the table but still within the bounds of the "Categories" tab in order to scroll up and down. This is super annoying because it means you have to have the cursor on the far left or far right of this window otherwise a table will appear when scrolling and the mouse wheel will stop working.In the screenshot, having the cursor anywhere in the red box will stop it from scrolling. I expect it to scroll the green scrollbar. 

I'm using a STM32F407VG (actually a disc-1 board). I've set I2S2 in full-duplex master mode and generating the MCLK out on PC6 for an external slave codec. So far so good.Now i want to set SDIO interface in full-duplex 4-bits mode but CubeMX throws a warning about a partial conflict with I2S master clock out. Frankly i have no clue about it, can i safely ignore the warning? 

I created a motion_fx for stm32h562 from CubeMx. The auto generated motion_fx.h file does call (line 135)size_t MotionFX_GetStateSize(void);​But the code does miss the include #include <stddef.h>Which results in the following error:unknown type name 'size_t' motion_fx.h ./Middlewares/ST/STM32_MotionFX_Library/Inc line 135 C/C++ Problem 

Hi,In STM32CubeIDE/MX versions 1.19 and 6.15, I configured HRTIM, and it worked fine without any errors in CubeMX. I have updated STM32CubeIDE/MX to versions 2.1.1 and 6.16.1, and I have noticed the error messages shown in the pictures below.The dead time is not used, but when set Output 2 state MX displays the message "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources". The project operates like before the update, but it is not possible to add new Set Sources (I can only change the number of Set Sources to zero). How to understand this behaviour?Krzysztof  

In a recent release (not sure which one) the option to select USER_PHY was added to the platform settings under LWIP.I need to implement a different PHY for a LAN9374. It is basically identical to the LAN8742. The only issue is that the LAN8742 init code fails unless modified slightly. If I select LAN8742 and modify the file I can get it working but as expected every time I regenerate the project the modifications get overwritten. Where is the documentation on how to implement a USER_PHY?

STM32G491Code generator generate wrong order of calls for SPI initialization for LL driver: LL_DMAMUX_SetSyncRequestNb  calls after LL_DMAMUX_EnableSync

 Hello,I am encountering an issue with the ST example projects "BLE_p2pServer" and "BLE_DataThroughput_Server" for the NUCLEO-WBA65RI board.After generating the code using STM32CubeMX (version 6.17), the project does not include all the required source files. As a result, the compilation fails immediately, even before making any modifications to the code.I enabled the option:"Generate peripheral initialization as a pair of '.c/.h' files per peripheral".The main issue is that the following file is missing:"stm32wbaxx_ll_utils.c" .It seems that some HAL/LL driver files are not being generated or included properly in the project.Could you please advise on:Whether this is a known issue with STM32CubeMX 6.17?If there is an additional step required to include all necessary driver files?Or if a specific configuration is needed for these BLE examples?Thank you in advance for your help.Best regards,Pierre A

The list of #include in the main.c file is lost when regerating stm32cubemx with new GPIO config :Previous : /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2026 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS. * ****************************************************************************** */ /* USER CODE END Header */ /* Includes ------------------------------------------------------------------*/ #include "main.h" #include "string.h" #include "exti.h" #include "embedrt_debug.h" #include <stdio.h> #include <stdbool.h>After regeneration with mx: /* USER CO

When I click this button, my mouse keeps spinning but the program does not open, and there is no error message. I tried using Refresh Data, but it had no effect.

Hi ST Support Team,I am using MXCube for STM32U5A5VJ. I have enabled the RTC, and cube generates the following Init Function. In this way, everytime I restart the controller, the RTC date is gonna be overwritten. In practice, I would like to have the bracket at line 9 down in line 21. Thank you for your support.Best Regards, Gianmarco Cerutti void MX_RTC_Init(void) { ... /** Initialize RTC and set the Time and Date */ if(LL_RTC_BKP_GetRegister(RTC,LL_RTC_BKP_DR0) != 0x32F2){ LL_RTC_BKP_SetRegister(RTC,LL_RTC_BKP_DR0,0x32F2); } RTC_TimeStruct.Hours = 0x0; RTC_TimeStruct.Minutes = 0x0; RTC_TimeStruct.Seconds = 0x0; LL_RTC_TIME_Init(RTC, LL_RTC_FORMAT_BCD, &RTC_TimeStruct); RTC_DateStruct.WeekDay = LL_RTC_WEEKDAY_MONDAY; RTC_DateStruct.Month = LL_RTC_MONTH_FEBRUARY; RTC_DateStruct.Day = 0x11; RTC_DateStruct.Year = 0x25; LL_RTC_DATE_Init(RTC, LL_RTC_FORMAT_BCD, &RTC_DateStruct); ... }