STM32CubeMX (MCUs)

This is the post to split

Another question asked that needs to be split and separated to another thread.

With the recent split of STM32CubeIDE and STM32CubeMX, I'd like to propose a dark mode option be added to STM32CubeMX.In consideration of the competing priorities for STM's software development team, I have two suggestions for how this proposal could be implemented:The first suggestion is the typical route: STM's in-house software development team add the UI theming and inputs to switch between dark and light mode.The second suggestion is less typical: make STM32CubeMX open source and let the larger software community assist with adding dark mode. Perhaps the source could be placed alongside other repositories in STM's current GitHub account....The benefits of adding such an option would be as follows:Consistency with STM32CubeIDE, from which STM32CubeMX was split from (STM32CubeIDE already has a dark mode)Consistency with the vast majority of other software in the industryConsistency with what has become a common user experience across operating systems, browsers, and setups in g

This thread is split from this old discussion @FBL  RCC_USBPHY1REFCLKSOURCE_OTGPHY1 and RCC_USBOTGHS1CLKSOURCE_HSE_DIV2 are missing in generated code I created a simple FSBL application that is jump to the AppliThe Appli is using the same approach (SW solution) like it was implemented inside "Ux_Device_CDC_ACM" example, (it was migrated in to the Appli)Currently, during debug, I am observing the same issue like it was described before (stuck in USB_CoreReset() during checking the "USBx->GRSTCTL & USB_OTG_GRSTCTL_CSRST" )The solution, that you provided, it looks like it does not working anymore by using the latest Cube_FW and generated compilation errors (no defines for the RCC_USBPHY1REFCLKSOURCE_OTGPHY1 and RCC_USBOTGHS1CLKSOURCE_HSE_DIV2).Could you please provide a solution (it would be better to see an example) how to solve this issue base on the latest MXCube and STM32CubeIDE versions. Currently it is : STM32CubeIDE_2.1.1  STM32Cube_FW_N6_V1.3.

HiAccording to the reference manual the high-cycle capable Flash of a STM32H562 is mapped to the address 0x0900_0000 to 0x0901_7FFF. The Memory Management Tool of CubeMX does not allow me to generate a Region in this address range (see Error below). Is this correct or should CubeMX not allow the generation of a memory region in this range? The Flash Option Byte was configured for the use of the high-cycle Flash.As a work around I can of course manually edit the linker script.I use STM32CubeMX Version 6.14 with the Firmware Package V1.5.0 to generate a STM32CubeIDE project on Windows 11.  

There are 4 external events that can be chosen to trigger and reset individual counters of each HRTIM timer unit in STM32H743 MCU. CubeMX shows those events once the Event Configuration is chosen "Enabled" . Yet only Source 1 is active (allowed to be chosen) but the Source 3 that I need to connect internally to the TIM2 TRGO output is inactive (cannot be chosen) . Why? My attempts to use AI got strange results - after searching the STM documents AI concluded that CubeMX is limited , it allows only external on-pin connections and any internal connections must be manually coded in addition to the generated code. If it is so then why does CubeMX show those other options yet does not allow to choose them? Or is there way to activate those options ?Please anybody give me suggestion.Note: the STM32CubeMX is the latest downloaded and installed yesterday. The MCU library pack is also current. 

Hi ST,I’m trying to configure the clocks for the STM32C071GBUx MCU in CubeMX (latest version, 6.17).This MCU has two SPI interfaces, two UARTs, and two I²C peripherals. However, CubeMX only allows me to configure the clock for one UART, one I²C, and no SPI at all.Am I missing something?I’ve attached the complete clock configuration diagram below.

Hello,For one of my project, my goal is to use PTP to synchronise multiple STM32H563 to one host.However, when configuring the ETH Device, I can only enable RMII, as the "RMII_PTP_SYNCHRO" is greyed out.I've read the pop up that tells me to enable TIM2 as a slave with trigger source "ETR1 through Remap", Channel 1 as "Input Capture direct mode from Remap". And both "remap capabilities" are set to "is connected to ETH_PPS".Is there something that I'm missing ?Best regards

 When I click ACCESS TO MCU SELECTOR, the console prints :（I tried uninstalling and reinstalling, but the problem persists）command：jre\bin\java -jar STM32CubeMX.exe -ioutput：2024-10-09 19:44:07,992 [INFO] DbMcus:218 - Found 0 MCUs, 0 are supported2024-10-09 19:44:07,993 [INFO] ApiDb:423 - Load user favorites file C:\Users\PCH/.stm32cubemx/favorites.mcus.txt: 0 item(s)2024-10-09 19:44:07,993 [INFO] ApiDb:427 - User favorites MCUs=[]2024-10-09 19:44:07,993 [INFO] DbMcus:224 - Set 0 / 0 favorites MCUsException in thread "AWT-EventQueue-0" java.lang.NullPointerException: Cannot load from int array because "minMax" is nullat com.st.microxplorer.mcufinder.gui.mcuselector.McuFilterPanel.createControls(McuFilterPanel.java:1476)at com.st.microxplorer.mcufinder.gui.mcuselector.McuFilterPanel.createGUI(McuFilterPanel.java:241)at com.st.microxplorer.mcufinder.gui.selector.FilterPanel.<init>(FilterPanel.java:124)at com.st.microxplorer.mcufinder.gui.mcuselector.McuFilterPanel.<init>

In CubeMX Version 6.17.0, for STM32G474RET6, HRTIM1, TIMA output2 configuration, set sources is forced to 0 cannot be changed to 1 and it is showing "Set Sources: nothing to set as Dead Time is enabled, Output2 signal is defined based on Output1 Configuration Set Sources" even if Dead time is kept disabled. This issue was not present on previous versions of CubeMX.

Hi, everyone.I'm trying to configure I2S in a STM32H523CET. I'd like to activate MCLK signal, but I can't find how. I'd also like activate external clock input for I2s (AUDIOCLK signal). The CubeMX says:"Audio Clock Input is not available.To enable it, one of the following RCC Mode(s) or IP(s) have to be configured from the Pinout TAb:-EnableExtClockForSAI1"But again, I can't find where to activate that. 

Hi ST, This is just to let you know that STM32CubeMX version 6.17.0 does not generate correct cmake file for the STM32WL33 and this error results in the microntroller not starting up correctly but hangs in function  SystemInit() in system_stm32wl3x.c.   The problems is that the wrong is -mcpu is generated. The problem can be found in the file -> path/to/dir/cmake/gcc-arm-none-eabi.cmake # MCU specific flags set(TARGET_FLAGS "-mcpu=cortex-m4 ") // wrong for the WL33 # MCU specific flags set(TARGET_FLAGS "-mcpu=cortex-m0plus ") // correct for the WL33 Ola

Hello,STM32CubeMX installer on linux doesn't creating desktop entry file.Thanks in advance.

Dear STM expert:     Currently, Iam facing an issue:when using the stm32f030f6p6 chip, I cannot find this chip model when creating new projects in stm32cubeide and stm32cubeMX ,thus it making it impossible to new projects,what this?hope a reply..thanks.

STM32CubeMX v6.17.0While configuring an STM32CubeMX project for an STM32H753 Ethernet project on a NUCLEO-H753ZI, I observed some strange behavior.After enabling memory management, including the checkboxes- Apply Application Regions Settings to Peripherals and- Apply Application Regions Settings to Linker Files,I would have expected the memory regions to be included in the linker description file STM32H753XX_FLASH.ld.Unfortunately, this was not the case.However, since the STM32H753XX_FLASH.ld file had obviously been regenerated, I did not suspect the file handling itself.After several hours of searching, I discovered that if the .ld file is deleted before regeneration, different content is generated.Steps to reproduce this:Open STM32CubeMXFile / New Project… / Board SelectorSelect NUCLEO-H753ZIIn „Board Project Options“ dialog, click button „Unselect All“Set Project Manager / Project / Toolchain / IDE  to CMakeand Default Compiler/Linker to ST Arm ClangFile / Save ProjectGenerate

CubeMX 6.17. When creating a new project for H533RETx or for the corresponding Nucleo-H533, SYSCLK is set at 32 MHz.Not sure whether or not it is intended, but it looks like a trap for a new user, since the MCU datasheet talks about 250 MHz.Instead, example projects for Nucleo-H533 (at least the couple that I've seen) quite reasonably run the MCU at 250 MHz, driven from the crystal present on the board.

Hi: My goal is to perform full-duplex I2S using the STM32F722RET6 part. To achieve this using the pins available on the package it looks like I need to use SAI2 (sub-block B) as the master/TX and SAI1 (sub-block A) as a slave/RX synchronized to SIA2.The configuration of SIA2 in CubeMX works fine.  However, when I attempt to configure the slave side (SAI1-A) the I2S option is greyed out (see below). Can anyone help me to debug this? Many thanks, Bruce.

Hi, I'm working on the STM32H7S7L86H with cube MX 6.17 and cube H7RS 1.3.0I need to use RNG in appli and boot context but it is grayed because it accept only one context. It also block the usage of the hash module.Any idea how to fix this ?Thanks 

Hi All,I have an issue with STM32CubeMX 6.17.0 (Windows 11 + Visual Studio Code)I want to start a STiRoT Full secure project (with DA and encryption) for STM32H573 with FREERTOS.But when I add the freertos software pack, I don't get any configuration options.Open STM32CubeMXStart My project from MCUSelect STM32H573IIK3Q (same as STM32H573I-DK)Enable ICACHE and MPU -> YesWith TrustZoneSoftware packs -> Select Component -> Cortex-M33 Secure -> X-CUBE-FREERTOS 1.5.0 -> CMSIS RTOS2 11.2.0 -> Core : TZ_Secure (I can't select Heap???)No configuration is shownIf I add FREERTOS to non-secure I am able to open configuration optionsI have added my IOC file.Can someone tell me what I'm doing wrong?Thanks!With kind regards,Marty

Hello, I have a simple CubeMX project with the STM32N6 MCU, and I cannot seem to be able to uncheck the FREERTOS option from the FSBL to move it to the Application.  Is there something I am doing wrong? Thank you 

Hi,I'm using STM32H5F5LJHxQ. External HSE Oscillator is 48MHz. RTC clock mux is set to HSE_RTC, divider set to "/48" and the tool shows correctly that RTC clock is 1000kHz (48MHz / 48).During my tests I discovered a wrong RTC time, error ~2%. (1.2 seconds deviation per minute)In the generated function HAL_RTC_MspInit() is see: (49 instead of the expected 48)PeriphClkInitStruct.RTCClockSelection = RCC_RTCCLKSOURCE_HSE_DIV49; If I change the configuration in CubeMX to create a divider of 47, the correct RCC_RTCCLKSOURCE_HSE_DIV47 is generatedIf I change the configuration in CubeMX to create a divider of 49, the correct RCC_RTCCLKSOURCE_HSE_DIV49 is. generated.If I manually set the correct RCC_RTCCLKSOURCE_HSE_DIV48 in the sources, the RTC runs correctly. Regards,Gunnar BohlenHMS Networks 

See attachment, field gets erased every time I re-generate code using STM32 CubeMX.problem seen on versionsSTM32CubeMX version 6.16.1uVuion/Keil version 5.43This has been ongoing for a while so problem does exist on older versions of both.

Hello,   maybe someone can check this,it seems to be incorrectly generated code. In my application for STM32H5xx I want to use ADC3. void HAL_ADC_MspInit(ADC_HandleTypeDef* hadc) { GPIO_InitTypeDef GPIO_InitStruct = {0}; RCC_PeriphCLKInitTypeDef PeriphClkInitStruct = {0}; if(hadc->Instance==ADC3) { ... .../* Peripheral clock enable */ __HAL_RCC_ADC_CLK_ENABLE(); This macro does not enable ADC3. #define __HAL_RCC_ADC_CLK_ENABLE() do { \ __IO uint32_t tmpreg; \ SET_BIT(RCC->AHB2ENR, RCC_AHB2ENR_ADCEN); \ /* Delay after an RCC peripheral clock enabling */ \ tmpreg = READ_BIT(RCC->AHB2ENR, RCC_AHB2ENR_ADCEN); \ UNUSED(tmpreg); \ } while(0) I think something like this is required: #define __HAL_RCC_ADC3_CLK_ENABLE() do { \ __IO uint32_t tmpreg; \ SET_BIT(RCC->AHB2ENR, RCC_AHB2ENR_ADC3EN); \ /* Delay after an RCC peripheral clock enabling */ \ tmpreg = READ_BIT(RCC->AHB2ENR, RCC_AHB2ENR_ADC3EN); \ UNUSED(tmpreg); \ } while(0)  

Hi,  i'm missing something in the configuration of alternate function on STM32C092. I can't get working alternare function on shared pin, interested physical pin are  PIN 1, 15, 20.  Example1: PIN15 only the function on PA8 are working properly, neither (PB0,PB1 or PB2) are working at all with any function even a simple toggle. I'm pretty sure that the Alternate Function property are being generated correctly. Example2: PIN20 Generating a PWM with TIM3_CH1 only works on PB6, if the same timer is passed to PB4 i can't get any output. Same on PIN1 i can get output only on PB7.  There is the HAL_TIM_MspPostInit where PB6 is working as expected but PB1 isn't: void HAL_TIM_MspPostInit(TIM_HandleTypeDef* htim) { GPIO_InitTypeDef GPIO_InitStruct = {0}; if(htim->Instance==TIM3) { /* USER CODE BEGIN TIM3_MspPostInit 0 */ /* USER CODE END TIM3_MspPostInit 0 */ __HAL_RCC_GPIOB_CLK_ENABLE(); /**TIM3 GPIO Configuration PB1 ------> TIM3_CH4 PB6