STM32CubeMX (MCUs)

I enabled this option to activate the virtual COM port for debug reasons: It is a CMake Project to be opened in VS-CodeEnabling the Virtual Com Port in CubeMX results in this error in VS Code:Crawling in the files, I found that the stm32h5xx_nucleo_conf.h the USE_BSP_COM_FEATURE is not enabled.Enabling this manually will result in many more errors:Generating the code again will reset the USE_BSP_COM_FEATURE to 0.Did I forget or overlook something?

Hi, I am using the STM32G0B1CBTx on the STM32CubeMX and setting the I2C1 for SMBus-two-wire-Interface. I want to disable the timeouts but I noticed that when I do so, the clock timeout enable (bit 15 of I2C_TIMEOUTR register) is still high. Looking at the generated timeout value to be written in the register (0x0000830D), it shows that indeed, the STM32CubeMX is enabling the timeout even though I selected Disable. Below is a screenshoot showing this. Is this a bug in MX ?  

Hello,I am using STM32H730ZBT6 with STM32 CubeMX V6.12.1 (I am not using the newest version because of the problem related in topic Downgrade STM32CubeProgrammer in STM32CubeIDE. I dont' know exactly if CubeMX would reproduce the problem, but for the case...) and I have detected 2 problems in code generation:1. Eventhough I am using peripheral SDMMC2 the code generated in file "fx_stm32_sd_driver_glue.c" is prepared for SDMMC1. Here a code portion as example: extern SD_HandleTypeDef hsd1; #if (FX_STM32_SD_INIT == 1) extern void MX_SDMMC1_SD_Init(void); #endif 2. If the option "Generate peripheral initialization as a pair of '.c/.h' files per peripheral", some erros ocur because "fx_stm32_sd_driver_glue.c" file doen't know where to find functions and instances, and is necesary to include "sdmmc.h" file. A part of those twoo problems, in functions "void HAL_SD_TxCpltCallback(SD_HandleTypeDef *hsd)" and "void HAL_SD_RxCpltCallback(SD_HandleTypeDef *hsd)" hsd is not used, so

Moved from MPUs forum; STM32F072 is an MCU - not an MPU.Hi,I've just started a new project for a STM32F072 chip using STM32CubeIDE 1.17.0.When adding FreeRTOS support to my project, the program hangs soon after osKernelStart() is called.I had hard time finding the culprit.The problem is that the SysTick_Handler() present in cmsis_os2.c is not used (It is surrounded with #if defined(SysTick) /  #endif).Because os this, the default handler is called (infinite while loop).I've worked around this problem by copying the SysTick_Handler() function in my code. But this problem should be fixed in the STM32CubeIDE code generator.Best regards,Nicolas

I get this error in downloading files in side stm32cubemx:error downloading the following files: crdb_full.zip

The new CMake generation is great! It's very tastefully done (toochain file, presets, simple CMakeLists.txt, etc).My request: I want to add some additional compiler flags (like `-Wconversion`) to my project.In the top CMakeLists.txt I did:```cmaketarget_compile_options(${CMAKE_PROJECT_NAME} PRIVATE"-Wconversion")```The problem is that it applies to the HAL as well, generating an endless stream of errors.I could create a new cmake target for my own functions, but I wish the generated CMake template would support this out of the box.  Regards,Gabriel

Hi,We are working on a board with the STM32H7S7Z8J6 in a BG144 package. We use cubemx to create the correct pinout for this part, but we see the datasheet has different pinout then the CubeMX tool. Is this a bug in CubeMX?   

I made a change to my project (using an STM32H7S3L8 part), saved the results, and a few days later tried to reload the project, but got a "Not a valid ioc file" error message.  Here is the output of the log file:```2025-02-17 10:59:38,352 [FATAL] ProjectFactory:568 - Exception caughtjava.lang.NumberFormatException: For input string: ""at java.lang.NumberFormatException.forInputString(NumberFormatException.java:67) ~[?:?]at java.lang.Long.parseLong(Long.java:719) ~[?:?]at java.lang.Long.valueOf(Long.java:1157) ~[?:?]at com.st.microxplorer.mcu.memorymap.MemInfoExtractor$ETHInfoExtractor.onETHEnable(MemInfoExtractor.java:4561) ~[STM32CubeMX:?]at com.st.microxplorer.mcu.memorymap.MemInfoExtractor.completInit(MemInfoExtractor.java:252) ~[STM32CubeMX:?]at com.st.microxplorer.mcu.memorymap.MemoryMapService.MMTActivated(MemoryMapService.java:1259) ~[STM32CubeMX:?]at com.st.microxplorer.mcu.memorymap.MemoryMapService.loadConfigV3(MemoryMapService.java:2578) ~[STM32CubeMX:?]at com.st.microx

Good morning, I recently created a project using an STM32F469NI - disco (2Mb flash, 320 KB Sram) board. Firstly, I created a project with the board default configuration, add the peripherals and labeled some pins. Later, I added Touch GFX as a software pack to create a simple screen conformed by an image and a text area. The problem comes when I try to compile the project, it does not fit the memory. C:/Z-Eneko/STM32CubeIDE_1.13.2/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.1.0.202410251130/tools/bin/../lib/gcc/arm-none-eabi/12.3.1/../../../../arm-none-eabi/bin/ld.exe: SPI_PROJECT_0.elf section `ExtFlashSection' will not fit in region `FLASH'C:/Z-Eneko/STM32CubeIDE_1.13.2/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.1.0.202410251130/tools/bin/../lib/gcc/arm-none-eabi/12.3.1/../../../../arm-none-eabi/bin/ld.exe: SPI_PROJECT_0.elf section `TouchGFX_Framebuffer' w

Despite referring to the STM32F0 label (can't this forum have a simple one labeled as a general problem for STM32CubeMX???) the problem exists for ALL situations and MCU's where you simply start working with the STM32CubeMX.Since several years ago, some colleagues on this form (and myself for 1-2 months) continue to report a completely stupid mess in the stm32CubeMX that makes it completely useless (again I attach a picture of today's nonsense and that completely prevented me simply from doing my work at the University - I'm sick of it!) No one at TS has (apparently) spent even a minute trying to solve such a stupid problem. For now (and against my will) I will migrate to NXP MCUs, which at least the configuration software works! As soon as someone at ST fixes the problem (which drags on for years!) please let me know.

Posted on October 29, 2017 at 01:12Hi all,I would like to report a bug of CubeMX.I did generated simple project for STM32F103VEx.  Project if fairly simple just uses USB in CDC mode.I did generate similar project for same processor but only SPI3 using shared pins PB3 and PB4 with JTAG.Each time while I did generated those projects CubeMX forces to distable whole debug communication JTAG +SWDby adding line    /**DISABLE: JTAG-DP Disabled and SW-DP Disabled      */   __HAL_AFIO_REMAP_SWJ_DISABLE();While SWD could be turned on since it does not conflicts with any of those peripherals. STM32 have options to disable only JTAG or either distable only NRJST pin in JTAG. Why CubeMX forces to kill all of the debug communication ?Simple project attached. Example file located in testCDC/stm32f1xx_hal_msp.c function void HAL_MspInit(void)https://community.st.com/tags♯/?tags=stm32%20cube%20mx https://community.st.com/tags♯/?tags=stm32f103%20usb https://

Hello,When generating code via CubeMX, the main code does not contain the configuration for the GPIO pins I need to be using.I have checked other solutions and seen that the pins need to be assigned to the core (in this case it would be the M3). The option to do this doesn't seem to be available; is there any hidden menus I need to be looking for? Thanks

CubeMX under Monterey seems to now think that all of my ioc files are read-only and not valid project files.Also, when I <File><Load Project> no files or directories show up in my Documents directory. This all worked before I updated to Monterey.

I have a STM32F469I-DISCO board. It seems that I am unable to change the GPIO Pull-up/Pull-down Mode for a timer. I have tried to do it both in the CubeMX interface, and I have also looked through the HAL methods and attributes. I don't think it's an option. Does anyone happen to know why? 

I'm using STM323H755ZIT6 NUCLEO board, STM32CubeMX 6.13.0 and STM32CubeIDE 1.17.0.In my scenario, I created a project in STM32CubeMX 6.13.0 and generated the project. After that, I opened this project in STM32CubeIDE 1.17.0 and added paths for external folders in Paths and Symbols. Later, I edited the .IOC file in STM32CubeMX and tried to regenerate the project, but an error popup appeared.ERROR POPUPAfter this popup, I clicked the OK button, and STM32CubeMX showed 'Project Successfully Generated.' However, when I tried to build the project in STM32CubeIDE, it failed to build, and errors appeared, such as:D:/NAVANEETHAN/CoffeeMaker/DisplayControl/Project/DisplayControl/CM7/Core/Src/main.c:116: undefined reference to `HAL_Init'D:/NAVANEETHAN/InstalledSoftwares/STM32CubeIDE_1.17.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.1.0.202410251130/tools/bin/../lib/gcc/arm-none-eabi/12.3.1/../../../../arm-none-eabi/bin/ld.exe: A total of

Hey guys,Why are the "SYS" settings simultaneously unavailable for Boot and Application? There may be a reason, but it's somewhat unclear.   Thank you, and as always:"Always be yourself unless you can be a pirate. Then always be a pirate." 

Hello,I'm trying to install the latest version of cubemx on my widows machine and I'm always getting an error "File execution returned 1" Failed to execute com.st.stm32cube.ide.common.services.mx.jar-1.17.0-rc1.jar. This happens on step 6/14 of overall installation progress. I click ok and the installation finishes. After this the cubemx does nothing when I try starting the application. I've updated to the latest version of Java without any success.Any help would be greatly appreciated!

I have created a project for the STM32H747I-DISCO and have deadlocked the MCU twice. a BIG thanks to ST for not having ANY warning about this. The DISCO board comes configured to default to SMPS mode. The project I created, without any warnings, defaulted to LDO mode. I corrected the problem using the process described in UM2411, section 5.2.3 only to go right back into the deadlock condition when downloading code.I now know that I must set the power mode to SMPS but I cannot find this setting in CubeMX. I am using CubeIDE v1.17.0. Where is the power settings for LDO and SMPS?????

I tried this board but i get some problem about interrupt.I "writed" only 1 function ( void EXTI0_1_IRQHandler(void) ) the other code has been autmaticaley generate from Cube.The goal is : for any change of state of PA0, pulse_count++.The problem is the function "EXTI0_1_IRQHandler(void)" doesn't work it means no interrupt it obtains when the singnal on PA0 chages.. On PA0 there is a square waveform. The uart is died, only because the interrupt doesn't work. I tested the uart and works fine. I cheched hardware problem it seems everything works fine.Here the code #ifdef __cplusplus extern "C" { #endif #include "main.h" #include <stdio.h> #include <string.h> #include "stm32c0xx_hal.h" #include "stm32c0xx_hal_gpio.h" #include "stm32c0xx_hal_tim.h" #ifdef __cplusplus } #endif volatile uint16_t pulse_count = 0; UART_HandleTypeDef huart2; void SystemClock_Config(void); static void MX_GPIO_Init(void); static void MX_USART2_UART_Init(void); int m

Cube MX: After RTC configuration with "activate clock source" and running the Cube generated Code  the RTC wont start.TheCube MX generated code  is missing to set the RTCAPBEN Bit in the RCC->APB3ENR Register.I found out that the  "stm32h5xx_hal_rtc.c"  hal  driver  doesnt work correct.:The driver states:   "Call the function HAL_RCCEx_PeriphCLKConfig with RCC_PERIPHCLK_RTC forPeriphClockSelection and select RTCClockSelection (LSE, LSI or HSEdiv32)(+) Enable RTC Clock using the __HAL_RCC_RTC_ENABLE() function."This is called by the Cube output but this doesnt set the RCC Clock bit for the RTC to "1" . It stays "0"Workaround:   Set the RTCAPBEN Bit   in   RCC->APB3ENR  manualy. Regards Henry 

I'm new to STM32CubeMX and have difficulties finding out how to map all OCTOSPIM_P2 signals to Port G. I can manually map some signals to Port G (CS, IO[7:4], DQS), but can't figure out how to map the rest.  Any help most welcome!

I recently updated my version of CubeMX from 6.12.1 to 6.13.0. It is now unable to open my .ioc for a specific STM32H563VI project. When I try to migrate, it loads the IOC, then gives an error saying it is "Not a valid ioc file".If I try to continue using the old version, it gets stuck on unzipping a file (DB.6.0.121.tar.bz2) for a few minutes, then silently stops.If I uninstall and go back to CubeMX 6.12.1 it can open it no problem, but that doesn't seem like a good solution.I have tried reinstalling CubeMX 6.13.0 from the website directly, checking for updates and relevant software packages.I am able to open previous projects that use the same MCU, so it seems it may be due to some specific configuration used. I have tried modifying the working project to include the same features as the non-working one, but it has not prevented it from loading. I tested opening an older project which used the NUCLEO-H563ZI. This older project also gives an "Not a valid ioc file" error, whe

Dear board, Whenever I create a Trust-zone enabled stm32 project for an stm32h573xx microcontroller using cube ide or cube mx, upon code generation I get the warning:"The provisioning scripts are only supported for DK boards (Or custom boards with the same flash and same pin mapping.     Are you sure to have this kind of board?"The microcontroller I am using does not have a corresponding evaluation board ( STM32H573VIT6T ), so i would either like to know:Is this warning relevant?what are the consequences of using the generated provisioning scripts?What corrections should I manualy enter to support the used microcontroller? To reproduce this behaviorOpen CUBEIDE and create a new stm32 projectSelect Trust zone enabled, uncheck secure project generation.Select the STM32H573VIT6T microcontrollerIn the CUBEMX interface go to Project tab and setup the Secure Boot path adding stIrot, stuRot and secure manager to boot the non-secure application.save and generate the code, t

Hello everyone,I have successfully set up and run a C-based AI model on my local development environment using the X-CUBE-AI libraries and a Makefile. The setup involves compiling and executing the model on my local CPU, and I am getting the expected output.Here is a brief overview of my current setup:Development Environment: Windows with a MinGW-W64 toolchain.Project Structure:A makefile to compile the project.Source files including main.c, and generated model files located in the model directory.X-CUBE-AI libraries located in the cubeai_lib_XX directory.Now, I am looking to deploy and run this model on my target hardware, which is an STM32 microcontroller. However, I am unsure about the steps needed to transition from running the model on my local CPU to executing it on the target hardware. Unfortunately, I could not find much documentation on this process.Could anyone provide guidance or resources on:How to set up the environment for cross-compilat

Using STM32 CubeMX ver 6.9.2, if you start a new project using STM32F469I-DISCO board and choose Yes to set all peripherals to their default settings, TIM6 comes up disabled/gray. Why is that? Instead of pinout view, choosing system view, only shows TIM1 in use.Second question on DAC. If DAC output 1 or 2 is enabled, NVIC settings shows TIM6 global interrupt, DAC1 and DAC2 underrun interrupt is automatically enabled & no way to disable it. When testing, even before HAL_init() completes, TIM6_DAC_IRQHandler starts going off. Why is that & how to stop it?