STM32CubeMX (MCUs)

New in CubeMX, so read this with "nonexpert" flag set ;)If HSE is used as source for RTC on STM32L072 device, it fails to initialize clock source for RTC.Running RTC with LSI or LSE both work fine, but with HSE it fails, regardless of prescaller setting.I think problem is in HAL_RCCEx_PeriphCLKConfig() function, it fails to set HSE as RTC source because HSE is allready enabled and this block of code fails:   /* Check if user wants to change HSE RTC prescaler whereas HSE is enabled */   temp_reg = (RCC->CR & RCC_CR_RTCPRE);   if ((temp_reg != (PeriphClkInit->RTCClockSelection & RCC_CR_RTCPRE))#if defined (LCD)    || (temp_reg != (PeriphClkInit->LCDClockSelection & RCC_CR_RTCPRE))#endif /* LCD */      )   { /* Check HSE State */     if ((PeriphClkInit->RTCClockSelection & RCC_CSR_RTCSEL) == RCC_CSR_RTCSEL_HSE)   

Hi。A simple yet glaring bug that persists: when you open stm32cubeMX and enter information in the 'Commercial Part Number' field, you'll notice that the letters you type appear twice. For example, if you type 's', the input box shows 'ss'; if you type 't', the input box shows two 't's. -----warmest greetings。

Hello,When a user adds a peripheral (for example I2c),  CubeMx picks some default and/or available pins for the device.It would be really nice if CubeMX can list all the Alternative pins that this peripheral can use.  So by right clicking on "I2C_SCL" in the image above, a popup can appear with a list of possible pins [ PB6 (green) because it is selected, PA0 (possibly yellow) because it is used by another peripheral, and PF6).  Then the user can click on the new pin in the popup list and change the pin number.  In my opinion, this would make pin selection a lot easier.ThanksMatthew

HII just upgraded MX 6.14The SAI configuration panel fail to load, all other configurations panel are available. The existing SAI configuration is not changed but MX. It also report an error before the code generation for SAI not correctly configured. 

STM32Cube IDE 1.18.0fw : STM32Cube_FW_H7RS_V1.2.0brd : NUCLEO-H7S3L8* main issue is :Once project created :  SAI configuration not provided in CubeMX after activation, therefore no setting can be adjusted in this section ( see picture )This problem also appreared after migration from a similar project edited with cube 1.17.0 and implying SAI to 1.18.0  with STM32Cube_FW_H7RS_V1.2.0.*  other issue :- C/C++ indexer errors popups appearing along while creating a new projet from scratch.-> deleting workbench.xmi (as suggested as a workaround in found other post :  https://community.st.com/t5/stm32cubeide-mcus/c-c-indexer-has-encountered-a-problem-1-11-2/td-p/84723 ) file located at : \STM32CubeIDE\workspace_1.18.0\.metadata\.plugins\org.eclipse.e4.workbench-> rebuil index.Thanks for your cooperation in resolving. 

 When DCache is disabled, CubeMX still generates this:#define __DCACHE_PRESENT 1U /*!< CM7 data cache present */If you comment out this line, CubeMX will uncomment it, causing some peripherals to fail.Using 6.14 and the STM32H743 cpu.

When unchecking "Generate Code" for MX_LWIP_Init, the code is still generated anyway. It's very annoying because I have to delete the generated function every time I generate code. Using CubeMX version 6.14.

We are using the STM32WL55CCU6 processor and generating code for two cores. For GPIO it is not possible to specify which core will initialize the GPIO (of course, it is not necessary) but the code and definitions are not generated for any core.STM32CubeIDE Version: 1.18.0ioc file included...

Hello,I am new to the STM32N657x0H3Q MCU and trying to generate code from latest CubeMX with the following peripherals enabled:UARTEthernetDCMIUSBNon-secure region onlyHowever, after generating the code and compiling it in Keli, I am encountering multiple errors. Additionally, CubeMX shows a warning:"  - Generating AppNS project without AppS, compilation errors maybe generated."I am trying to understand why this issue occurs.Is there a strict limitation in this MCU series that requires defining a secure region?If not, how can I properly generate code with only a non-secure region and avoid these errors?Also, I am planning to buy the STM32N6570-DK board for my project.thanks..... 

I'm freezing on the following screen, is there anything I can do?TK

Hello,I am working on a project for the STM32F3348-DISCO board using STM32 IDE 1.18.0.I have created a new project with the following settings:- Target Reference: STM32F3348-DISCO- Firmware Package Name and Version: STM32Cube FW_F3 v1.11.5- Initialize all peripherals with their default Mode ?  Yes STM32CubeMX shows there are multiple conflicts with the default configuration. Do you have any suggestions on how to resolve these issues?

Hi, I dont know the reason of this issue, I just generate code via STM32cubeMX after enabling UART4 and below there is the main program!: But my program cannot neither receive nor transmit any data and stuck in UART_WaitOnFlagUntilTimeout. Help please#include "main.h"/* Private includes ----------------------------------------------------------*//* USER CODE BEGIN Includes *//* USER CODE END Includes *//* Private typedef -----------------------------------------------------------*//* USER CODE BEGIN PTD *//* USER CODE END PTD *//* Private define ------------------------------------------------------------*//* USER CODE BEGIN PD *//* USER CODE END PD *//* Private macro -------------------------------------------------------------*//* USER CODE BEGIN PM *//* USER CODE END PM *//* Private variables ---------------------------------------------------------*/UART_HandleTypeDef huart4;/* USER CODE BEGIN PV */uint8_t data[]="hello world \n";uint8_t data1[10];/* USER CODE END PV *//* Private f

Is there a way to select the dark theme to STM32CubeMX?  

 STM32H7 SeriesI have enabled generation of linker script (need to redefine memory layout).There is no possibility to change  state of checkboxes of both CPU caches if this generation has been enabled.The state of the checkboxes may be on or off, but grayed out.You have to:- disable linker script generator- enable chaches- reenable linker script genSetup of the cache strictly follows the state of the checkboxes. 

Trying to export LQFP144 pinout to Altium CAD models with cubeMX.  But CubeMX is trying add pin #204 #202 #158, etc, on symbol for an L471 micro that doesn't even come in packages  bigger than 144 pins.  Altium chokes on this symbol, I imagine that's because the foot print only has 144pins.See screenshot below.  Will attach .ioc file if possible. 

Title edited to reflect the correct board used. Changed from NUCLEO-H7A3ZI-Q to NUCLEO-H7S3L8.Hi,I’m trying to set up UART communication using UART3 on the NUCLEO-H7A3ZI-Q board. I have the UART3 pins (PD8 and PD9) connected to the ST-Link VCP on this board.Do I need an external USB-UART converter to communicate through other UART pins, or should the onboard ST-Link handle the UART3 communication through VCP?It's showing USART3 is not available. I’m new to this board, so I want to confirm if there’s anything I might be missing in the configuration or connections. Any guidance would be appreciated!Thanksin advance!

I am facing a persistent issue with the Nucleo H755ZI-Q board that is driving me crazy! The issue I am having is : Error: Unable to get core IDError: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug AuthenticationEncountered Error when opening C:\ST\STM32CubeIDE_1.17.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.0.202409170845\tools\bin\STM32_Programmer_CLI.exeError in STM32CubeProgrammer       Here's the setup and steps I've followed:Chip Configuration:Selected STM32H755ZIT6 in STM32CubeMX.Disabled HSE and enabled LSE with a crystal resonator.Set M7 clock to 400 MHz and M4 clock to 200 MHz.Power settings:Supply source: PWR_DIRECT_SMPS_SUPPLY.Power regulator voltage scale: 1.   Peripheral Configuration:I2C1: PB8, PB9.USART1: PB14, PB15.USART2: PA2, PA3.Configured GPIO for onboard LEDs and user switch.  2. Debug Configur

I am having and issue with a STM32H725RGV6.After powering my board, I can see the SMPS output at 1.36V, which I have connected to the VCAP inputs.I can also connect to the µC using the STM32CubeProgrammer.However, after flashing a simple firmware, the SMSP output drops to 0V and I can not connect anymore. I am aware that this can be the result of an improper SMPS configuration (https://community.st.com/t5/stm32-mcus/unable-to-connect-to-stm32h7-devices/ta-p/49296). However, in my (cube generated) project am am callingHAL_PWREx_ConfigSupply(PWR_DIRECT_SMPS_SUPPLY)so this should be correct. Additionally, I tried to upload a program with nothing but an infinite loop in main, and the problem still occurs. When pulling BOOT0 high, the SMSP output becomes 1.36V again and I can connect again. This makes me believe, that everything is set-up correctly hardware-wise. Otherwise, the bootloader would not run. thank you for your help 

Hello,I am now using STM32CubeMX to config STM32G030F6P6, I want to use TIM14 to capture pulse, so I configged to Input Capture direct mode, which is obviously input port, but GPIO setting becomes GPIO output Low. is this a stm32cubeMX bug?please confirm.Thanks@GMA  

I have a project on a H563ZI Nucleo board, and noticed an issue when I enable both the Board Support Package (BSP) options and ThreadX.The MX-generated code in main.c places the BSP initialisation after the call to MX_ThreadX_Init()  - see snippet below.  This means the BSP code is unreachable and the components are not initialised.The workaround is simple (copy the BSP code into the USER CODE 2 section), but it should probably be looked at. Snippet of automatically MX-generated code from main.c: /* USER CODE END 2 */ MX_ThreadX_Init(); /* Initialize leds */BSP_LED_Init(LED_GREEN);BSP_LED_Init(LED_YELLOW);BSP_LED_Init(LED_RED); /* Initialize USER push-button, will be used to trigger an interrupt each time it's pressed.*/BSP_PB_Init(BUTTON_USER, BUTTON_MODE_EXTI); /* Initialize COM1 port (115200, 8 bits (7-bit data + 1 stop bit), no parity */BspCOMInit.BaudRate = 115200;BspCOMInit.WordLength = COM_WORDLENGTH_8B;BspCOMInit.StopBits = COM_STOPBITS_1

Hi,I am using the STM32U5G9VJT6Q and in CubeMX I configured the clock to the full 160MHz for all busses including the core (first screenshot). According to the documentation for 160MHz I need to set 4 Wait States for those speeds and VCORE voltage needs to be in Range 1 (second screenshot).Two questions if someone could please help:1. after setting the clock in MX, where can I check that the wait states have been set correctly (in MX - not programmatically, debug or other ways) ?2. in MX, where do I set the VCORE? If it is set automatically, where can I check that it is set correctly (in MX - not programmatically, debug or other ways)?Thank you :)Ricko   

I am using STM32F7 or STM32H7 to test SDRAM using FMC controller. Initially I could ot se a clock output. Seaching here has got that going. I have tried theSTM32CubeIDE and even set SDRAM bank 2 the same as Bank1 after reading there may be an issue.So far nothing. I stepped through and see a clock being anabled. It is mapped to PG8 on both H7 and F7 but I see not output there. I have tried various HCLK speeds with no joy.I saw a message about needing static void BSP_SDRAM_Initialization_Sequence(SDRAM_HandleTypeDef *hsdram, FMC_SDRAM_CommandTypeDef *Command)but I cannot find a reference to original documentaton so am using it from the github repository.Also what is the 16-bit byte enable, I already have 16bit wide bus enabled. Thanks for help with this... I see it enles extra lines for how it writes but agin I cannot fd documentation about it. just a presentaion saying everything it can do, but not how to do it!What simple thing am I missing? Most other things work through STM32CubeIDE

I'm migrating a project from STM32G431KB to STM32G431CBT6. Both projects were generated using STM32CubeMX and are developed in Keil (MDK ARM), so I only transferred the user code. However when debugging code on the new chip, random breakpoint commands in the disassembly window appear (not the user-defined red dots, but the BKPT mnemonic specifically).It's always first 3 times between _sys_open and _sys_close, then one time between _sys_istty and_sys_seek and another one between _sys_write, _sys_read, then my program runs normally. I tried a full chip wipe, code regeneration, code rebuilds all without any luck. I'm guessing there might be a setting I forgot somewhere that could cause this or a library from CubeMX, but so far I haven't been able to figure out what it could be.The CubeMX software packs I use:Selected features:

Good day all, USBX crashes at line 171 of the file ux_dcd_stm32_initialize_complete.c, as the dcd structure is not initialized at this point. I have tried this on two different MCUs, U575 and H753. In concert, on the H753 the code generator does not generate the call to MX_USBX_Device_Init() and in both cases the call to HAL_PCD_Start() is not generated as well, so this functionality will not work out of the box either. I suppose that I should insert some more calls for initialization, does anyone have idea? Regards,Dmitry

This appears to be loosely related tohttps://community.st.com/t5/stm32cubemx-mcus/warning-during-stm3cubemx-setting-in-usb-host-on-platform/m-p/194919#M8793If I start with Cube IDE:File -> New -> STM32 Project then select NUCLEO-C071RB and then Ux_Host_HID_Standaloneall goes swimmingly well.  However, if I start with CubeMX, then choose the same example I get errors:I can make the Platform Settings error go away by assigning a GPIO to who knows what, per the related post, but I don't want to waste a GPIO and furthermore, I want to make changes to the project that I cannot do using the IDE-only method. Is there some other setting I'm missing in the CubeMX example creation?