STM32CubeMX (MCUs)

Hello:        I am trying to use VS Code. below message will always pop up. With the generated codes I had another set of errors at VS Code.  Error at VS Code I need some guidance.  Regards Simon 

 Hello everyone,I recently encountered an issue after updating the STM32H5 MCU Package from v1.0.1 to v1.3.0. Some peripheral pin assignments have changed, and previously available pin options are no longer configurable.I started my project in 2024 using STM32H5 Series and developed my hardware based on MCU Package v1.0.1. Recently, I needed a simple peripheral modification and accidentally migrated my IOC file to v1.3.0. After doing so, I noticed that some pin assignments had changed.For example, on STM32H563VGTx, in RMII Ethernet mode, the ETH_TXD1 pin was originally assigned to PB13 in v1.0.1, but in v1.3.0, this option is no longer available (it has been removed from the possible pin mappings).I couldn’t find any release notes explaining why these changes were made. If this is a critical update, I would like to understand the reason behind it so I can decide whether I need to update my PCB design accordingly.Has anyone else encountered this issue, or does anyone have insights

A new question moved from this thread to the correct forum board (to be answered by CubeMx team) Hi If STM32U5 has no support for Ethernet why in configurator i can enable the Middleware NetxDuo?  The question start from this point, NetxDuo support, as documented, the LAN8742 component. The STM32U5 can enable NetxDuo. So STM32U5 can be equipped with ethernet port. If this is not true the configurator cannot give the possibility to enable this sw component.  Looking at example present in other MCU as F4/H7 series, the pins used to drive ethernet component are GPIOs the only difference is the presence of interrupt drived from Eth block. but in the code seems, if im not wrong, not used in connection management.   

 MacOS 15.3.1.  CubeIDE 1.18.0. Firmware STM32Cube FW_U5 V1.7.0.I  was tracking down an issue with SD cards on SDMMC2 on an STM32U5G9N not wanting to start.I found that HAL_SD_MspInit calls:__HAL_RCC_SDMMC1_CLK_ENABLE();instead of:__HAL_RCC_SDMMC2_CLK_ENABLE(); 

a picture is worth a 1000 words...Attached is the .ioc file 

Posted on October 17, 2017 at 12:08When using CubeMX, with STM32L476, for setting LSE drive capability other than 'Low Drive' the setting will not be implemented. This is due to the fact that the write access using bit DBP in PWR->CR1 is not set prior to setting RCC->BDCR value.The code generated in SystemClock_Config is:void SystemClock_Config(void){RCC_OscInitTypeDef RCC_OscInitStruct; RCC_ClkInitTypeDef RCC_ClkInitStruct; RCC_PeriphCLKInitTypeDef PeriphClkInit;/**Configure LSE Drive Capability */ __HAL_RCC_LSEDRIVE_CONFIG(RCC_LSEDRIVE_LOW);/**Initializes the CPU, AHB and APB busses clocks */ RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_LSE|RCC_OSCILLATORTYPE_MSI; RCC_OscInitStruct.LSEState = RCC_LSE_ON; RCC_OscInitStruct.MSIState = RCC_MSI_ON;....}where HAL_PWR_EnableBkUpAccess must be executed prior to __HAL_RCC_LSEDRIVE_CONFIG#cubemx #lse

Hi,looking at the screenshot below of CubeMX in the LTDC, the total Width and total Height are non-editable (i.e. auto calculated) but they are one pixel less?For example, for the attached display datasheet:- Horizontal Sync Width (Editable) = 8 pixels- Horizontal Back Porch (Editable) = 7 pixels- Active width (Editable) = 800 pixels- Horizontal Front Porch (Editable) = 6 pixelsSo the total is 821 pixels instead of 820. But CubeMX displays 820 and it is not editable.Did I miss something? Do I need to change some other setting?Thank you :)  

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