STM32CubeMX (MCUs)

It has been verified that the installations of STM32CubeMX, STM32CubeIDE, and STM32CubeProgrammer are completed successfully and operate normally under standard conditions; however, when STM32CubeAI is installed, a critical issue arises in which STM32CubeMX no longer functions properly, specifically preventing the creation of new projects. This behavior was reproduced on two different computers, with identical results observed in both cases. Additional tests were conducted in which all programs were uninstalled and then reinstalled without STM32CubeAI, resulting in normal operation; subsequently, when all programs were reinstalled including STM32CubeAI, the issue reappeared, and finally, upon uninstalling only STM32CubeAI, STM32CubeMX returned to normal operation. This strongly suggests the existence of a direct conflict between STM32CubeAI and STM32CubeMX, and therefore guidance is requested to resolve this issue or to confirm whether it is a known bug, as well as any possible solutio

When configuring the LEDs for the STM32H573I-DK using the STM32CubeMX it generated code which initializes the LED pins as PushPull (rather than OpenDrain).Lookign at the schematics of the STM32H573I-DK it seems to be not "the best option".Would you agree that OpenDrain (GPIO_MODE_OUTPUT_OD) is the better option here, rather than PushPull (GPIO_MODE_OUTPUT_PP)? /** * @brief Configures LED on GPIO. * @PAram Led LED to be configured. * This parameter can be one of the following values: * @arg LED1 * @arg LED2 * @arg LED3 * @arg LED4 * @retval BSP status */ int32_t BSP_LED_Init(Led_TypeDef Led) { int32_t ret = BSP_ERROR_NONE; GPIO_InitTypeDef gpio_init_structure; if ((Led != LED1) && (Led != LED2) && (Led != LED3) && (Led != LED4)) { ret = BSP_ERROR_WRONG_PARAM; } else { switch (Led) { case LED2: /* Enable the LED2 GPIO clock */ LED2_GPIO_CLK_ENABLE(); break; case LED3: /* Enable the LED3 GPIO clock */ LED3_GPIO_CLK_ENABLE()

I'm running Bazzite (Fedora 43) and tried to install STM32CubeMX on a Fedora distrobox and was met with some issues.First, the installer is unable use /bin/chmod, this is fixed by switching out the installer's `jre\bin` directory for OpenJDK.Second, if you run as a normal user it fails with:com.izforge.izpack.api.exception.IzPackException: An error occured in java.lang.Thread.run() at Thread.java:1583 in com.izforge.izpack.installer.unpacker.UnpackerBase.run() at UnpackerBase.java:241 in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at UnpackerBase.java:319 Caused by: com.izforge.izpack.api.exception.InstallerException: File execution failed in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at UnpackerBase.java:299 in com.izforge.izpack.installer.unpacker.UnpackerBase.unpack() at UnpackerBase.java:483 in com.izforge.izpack.installer.unpacker.UnpackerBase.executeFiles() at UnpackerBase.java:959This is fixed by running the installer via sudo.This is what I did

Hello all, I need to use some FFT functions. I have installed the CMSIS-DSP 1.16.2 and CMSIS 6.3 core as it was required from  CMSIS-DSP. Surprisingly, CubeMX did only a part of its job, namely it did not copy source files and did not add proper include paths to the project so I have to do it myself. But after this there is still a bunch of unresolved references, namely arm_cfft_sR_f32_lenxxx and twiddleCoef_rfft_xxx. I have looked all sources in the CubeMX H7 pack version 1.13.0 I use through but could not find these sources. With best regards,Dmitry 

  I have tried using STM32CubeMX 6.17.0 to generate an STM32F429 DISC1 project.The generated project opened in STM32CubeIDE could not be compiled unless I add <root folder> in Project -> Properties -> C/C++ General -> Path and Symbols, the source location tab.I don't know how this happen. It's disturbing to modify project settings each time after modifying the CubeMX and generating the project.It's probably that should happened after I add some source folders to the projects. 

I am experiencing an issue in STM32CubeMX where all peripheral Configuration panels stay empty, while the Mode panels and System Core → Parameters render correctly.What I have already tried:Starting CubeMX standalone (not via CubeIDE)Creating a completely new empty projectDeleting the .stm32cubemx folderDeleting and rebuilding the entire STM32Cube\RepositoryReinstalling CubeMXForcing JavaFX software rendering (-Dprism.order=sw)Setting Windows display scaling to 100%Enabling/disabling GPU accelerationVerifying that the bundled JRE is complete (java.exe + jvm.dll present)In all cases, every peripheral Configuration section remains empty, while Mode sections work normally.It appears that the JavaFX UI for peripheral configuration does not initialize, but without any error message.Has anyone seen this before, or is there a way to force or debug the JavaFX UI subsystem in CubeMX?Thank you in advance.Kind regards, Cornelis Dekker (Netherlands)

I am using STM32C071FBP6N MCU TSSOP 20 pin package for one of our project.I am observing Pin_20 is muxed with lot of other pins like PB3/PB4/PB5/PB6. if i select PB3 as GPIO_Output using STM32CubeMx and generated a code. If i try to toggle the pin but its not working at all, none of the peripheral on that pin for PB3 is working. But if i select PB6 as GPIO_Output i can able to toggle or modify.This issue is not only with Pin_20, same with Pin_1 also which shares with PB7/PB8, only PB7 is working.I have tried with multiple chips what could be wrong in this scenario??

Hello,The latest version of STM32CubeMX no longer lists x-cube-spn5 as an available package.Could someone help me how to use a X-Nucleo-IHM05A1 expansion board with the latest tools please? 

When I clicked the "Access to MCU Selector" button, the interface did not respond. The pointer just kept rotating to indicate loading. However, when I clicked the "Access to Board Selector" button at this time, the selection interface could be opened.On the board selection interface, when I clicked the MCU/MPU Selector interface, it still showed the situation where the pointer was rotating and indicating a loading process, and I did not enter the MCU selection interface. 

Software Versions: - STM32CubeMX: 6.15.0 - MCU: STM32G474QET6 - Firmware Package: STM32G4xx HAL Library V1.6.1 Bug Description: CubeMX 6.15.0 generates incorrect HRTIM deadtime prescaler macro definitions. These macros do NOT match the register bit definitions described in the STM32G4 reference manual (RM0440). This is a code generation bug in CubeMX, not a HAL library issue.  Old Correct Macros (Previous Version): #define HRTIM_TIMDEADTIME_PRESCALERRATIO_MUL8 (0x00000000U) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_MUL4 (HRTIM_DTR_DTPRSC_0) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_MUL2 (HRTIM_DTR_DTPRSC_1) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV1 (HRTIM_DTR_DTPRSC_1 | HRTIM_DTR_DTPRSC_0) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV2 (HRTIM_DTR_DTPRSC_2) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV4 (HRTIM_DTR_DTPRSC_2 | HRTIM_DTR_DTPRSC_0) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV8 (HRTIM_DTR_DTPRSC_2 | HRTIM_DTR_DTPRSC_1) #define HRTIM_TIMDEADTIME_PRESCALERRATIO_DIV16 (HRT

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?

After updating CubeMX to version 6.16.2, we are seeing HRtimer E and F problems which cause our product to fail.  Reverting back to 6.15 and regenerating the code allows our device to work.  I believe the issue is due to the change in the code database version: MxDb.Version=DB.6.0.161 but I can't be sure as the new version of cubeMX forces values into the HRtimer E and F configurations.Hoping for commiseration and resolution!ThanksRauk

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

In STM32CubeMX, here is the orientation for a chip with a red dot marking pin 1 at the top left when text reads from left to right.In real life, here is the orientation for a chip with a red dot marking pin 1. As far as I'm aware, all STM32 chips are oriented like this, with pin 1 at the bottom left when text reads from left to right. Why is the text rotated 90 degrees differently? Is this intentional? If there is a reasonable explanation, I'm interested in hearing it. It seems to only add confusion. Wouldn't it make more sense if the default orientation (or at least the text orientation) to match between the two? In STM32CubeMX, you can rotate the part for convenience. This is useful. However, the text also rotates, so if you put pin 1 in the bottom left like in reality, the text is now rotated. (This is the same story in STM32CubeMX2.) 

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.

Hi everyone,the update to CubeMX 6.17 seems to introduce a new valid range of the "First RX Descriptor Address" of the Ethernet setup on a NucleoH755 board. This is also the case for the STM32H745.This is the valid range according to the CubeMX field description (there is also a typo for the Parameter Description "Fisrt"):First Rx Descriptor AddressFirst Rx Descriptor Address must be between 0x24000000 and 0x30047fff.Parameter Description:Fisrt Rx Descriptor address must be only in the D2 Domain AHB SRAM. Rx descriptor address must not exceed Max value and must no overlap with Tx descriptor and Rx buffer. These areas must not be cacheable.This contradicts the knowledge base article: How to create a project for STM32H7 with Ethernet and LwIP stack working The reference manual also states that 0x3004000 - 0x3004FFFF should be part of the D2 Domain AHB SRAM3 and hence be part of the intended area. Is this just a bug or do I overlook something?Kind regards

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.