STM32CubeMX (MCUs)

Hi all,I'm using STM32Cube IDE (version 1.13.1, build 17479_20230728_0839 ) to manage my company project based on a STM32U5 MCU.More specifically, I'm using linked list feature (for playing audio with SAI + DMA transfer) and I have noticed what appears to me as a bug in auto-generated code.Basically, I have created through CubeMx one list named SAIQueue, with one node named NodeTx and the auto-generated initialization code is the following:  /** * @brief DMA Linked-list SAIQueue configuration * @PAram None * @retval None */ HAL_StatusTypeDef MX_SAIQueue_Config(void) { HAL_StatusTypeDef ret = HAL_OK; /* DMA node configuration declaration */ DMA_NodeConfTypeDef pNodeConfig; /* Set node configuration ################################################*/ pNodeConfig.NodeType = DMA_GPDMA_LINEAR_NODE; pNodeConfig.Init.Req

1. Issues with Headless Execution and CLI CommandsGUI Opens with CLI Flags: Certain CLI flags designed for automation still launch the AWT/Swing GUI components, which causes failures in headless environments (like Docker containers or typical Linux servers).Specific Example: The -P flag (Package Manager) throws a java.awt.AWTError: Can't connect to X11 window server error because it requires a display.Expected Behavior: All package management and code generation functions should have a truly headless (no GUI dependencies) CLI option that works universally in server environments.Lack of Clear CLI Documentation: Documen

When attempting to initialize a single GPIO EXTI as disabled, the generated code still enables the interrupt. I did notice that if I uncheck all of the EXTI lines, then none of them are enabled in the generated code. So it seems it's all or nothing. Is this the expected behavior?Thanks,FrankThis:Generates: /* EXTI interrupt init*/ HAL_NVIC_SetPriority(EXTI0_IRQn, 5, 0); HAL_NVIC_EnableIRQ(EXTI0_IRQn);   HAL_NVIC_SetPriority(EXTI2_IRQn, 6, 0); HAL_NVIC_EnableIRQ(EXTI2_IRQn);   HAL_NVIC_SetPriority(EXTI3_IRQn, 6, 0); HAL_NVIC_EnableIRQ(EXTI3_IRQn);   HAL_NVIC_SetPriority(EXTI4_IRQn, 6, 0); HAL_NVIC_EnableIRQ(EXTI4_IRQn);

Hi, Is there anyway to generate codes in such way that we can customize our sub-project paths? E.g. Instead of having project/core/src, we have project/src... etc? Thanks in advance!

Hi,I'm using CubeMX 6.16.0 with the EWARM setting.When I click "Generate Code," it creates the IAR project with the default name "project.eww."I open the project with IAR and save it with a new name.Then I click the "Generate Code" button on CubeMX, and it regenerates the workspace name, again as "project.eww."Is it possible to set the IAR project name from CubeMX to something other than "project.eww"?Thanks

After (auto) migration the .ioc file to the actual CubeMX 6.15.0, the Dual Quad SPI mode got changed to Octo SPI mode and there seems to be no way to get back to Dual Quad SPI mode, since the mode selection entry "Dual-Quad SPI" is not shown as mode selection entry.After taking a closer look, I found out, that the Dual-Quad SPI mode is avail only for the OCTOSPI2 device, whereas the Dual-quad SPI option is not avail for the OCTOSPI1 device (tested with a "clean" configuration). Since my hardware was doing fine with Dual-quad SPI mode on OCTOSPI1 device there seems to be no reason for removing the Dual quad SPI mode from OCTOSPI1.I think, this behaviour is not intended ? Actually I found no workaround for this problem except for manually changing the auto-generated code so it would be nice to have that issue fixed. Even if changing the .ioc file manually the Dual Quad SPI mode option is removed on next load into the MX GUI again. Best regrads, Heino

Hello ST team and community,I am working with STM32H755 and noticed a potential bug in the code generated by STM32CubeMX when handling the RCC_FLAG_D2CKRDY check during system initialization. CubeMX produces two variants of the loop:while((__HAL_RCC_GET_FLAG(RCC_FLAG_D2CKRDY) != RESET) && (timeout-- > 0)); if (timeout < 0) { Error_Handler(); }andwhile((__HAL_RCC_GET_FLAG(RCC_FLAG_D2CKRDY) == RESET) && (timeout-- > 0)); if (timeout < 0) { Error_Handler(); }Issue observedThe loop condition uses (timeout-- > 0).This means the loop exits when timeout reaches 0, but never decrements below zero.As a result, the check if (ti

Hi,in the latest cube (6.15) the STM32H573LI is not available, I can't start a project on this MCU.why is that? is there going to be a fix soon?

The new version of CubeMx (6.15.0) nags me about enabling SMPS mode, and I would like to, but the tool seemingly does not have the capability to do so.Under PWR->Low Power there's a checkbox for "Power Savings Mode" which other forum posts led me to believe would need to be enabled. I have found two things about this checkbox. 1.) It is already enabled and 2.) You cannot disable it.Then, under "System Core" -> RCC ->Parameter Settings, there's a "Supply Source" parameter. It has only a "PWR_LDO_SUPPLY" option, and cannot be changed to any other value.Am I missing something here, or is the tool broken? 

Hello, I get the same error recently on 1.19.0 for my STM32U385RGTxQ. The only option available in Power Supply source is PWR_LDO_SUPPLY

From Cube 1.19.0, i keep getting the "For the best power consumption figure, enable SMPS" and although the Nucleo-U385RG-Q board uses a Q variant, I'm not able to switch to SMPS from CubeMX.

Hello,I am trying to understand the memory allocation for the FDCAN, I am using a nucleo H723ZG.With the latest CubeIDE 1.18.1 I seem to be able to configure 32 TX Buffers and 32 TX FIFOs:However the message RAM mapping in AN5348 - Rev 5 shows that there are only a maximum on 32 for both Buffers and FIFOs:

As alread reported a while ago, strange things happen when entering an expression in CubeMX for Prescaler and/or Autoreload. If, for example, 72-1 is entered for Prescaler and 6667-1 for Autoreload, the following code will be generated:STM32CubeMX: TIM Prescaler, Period bug   TIM_InitStruct.Prescaler = 72-LL_TIM_IC_FILTER_FDIV1_N2; ... TIM_InitStruct.Autoreload = 6667-LL_TIM_IC_FILTER_FDIV1_N2; LL_TIM_IC_FILTER_FDIV1_N2 does not make any sense here.Depending on the exact values, the Timer will be initialized with some different settings than desired.With simple constants (without calculations) the generated code will be correct.In contrast to the previous post, in my case the MCU was a STM32F303.CubeMX is Version: 6.15.0-RC7,&nbs

I created default project with FreeRTOS in STM32CubeMx for the board Nucleo-H563ZI. Nothing more added.Hard Fault is invoked at vRestoreContexOfFirstTask.I was looking for the solution in Copilot and Perplexity but without success. Only I can say it's probably no problem with stack overflow.Jan

Hi! I have a problem. I faced with a problem of USB middleware initialization as a virtual port in CubeMX. After code generation USB init initializes in main.c within of one of task FREERTOS. If I initialize USB only as connectivity USB init replaces right. How to resolve it? Here details is: /* USER CODE END Header_start_task_can_handler */ void start_task_can_handler(void *argument) { /* init code for USB_DEVICE */ MX_USB_DEVICE_Init(); /* USER CODE BEGIN 5 */ app_start_task_can_handler(argument); /* Infinite loop */ for(;;) { osDelay(1); } /* USER CODE END 5 */ }

I would like to use USBX to make a CDC ECM USB device, but in STM32CubeMX, there is no option for CDC ECM or RNDIS in the USBX device class menu: The STM32U545RE on the other hand has options for CDC ECM and RNDIS:  Does STM32U385 support CDC ECM and RND

When "Activating clock source" is ticked in RTC module, my MCU doesn't start up if I reset it from RST button. But as soon as I switch the RCC clock source to LSE external 32.768khz crystal and change RTC Clock Mux to LSE, it works without a hitch. Is this by design or there may be a bug?

As mentioned, in order to rule out the interference from the existing project, I created a new blank project. However, it still didn't work. This issue was not present in the previous version 6.13.As shown in the above picture, I have disabled spi1 but still cannot enable the quad spi mode of spi2. Please provide a solution as soon as possible, or please inform me how to roll back my project version to 6.14 or earlier. The project is urgent. Thank you.@

Hello everybody,Problem: I start a new project from scratch in CubeMX version 6.15.0 with STM32H7A3VG. First thing I do is to try to chose OCTOSPI1, Mode Quad-SPI. But it does not work. It's greyed out and I get the message:"Quad SPI disabled: Quad-SPI Mode is already activated".Same thing if I try to chose OCTOSPI2, Mode Quad-SPI.Same thing in STMCubeIDE 1.19.CubeMX version 6.14 allowed me to chose Quad-SPI.Do I miss something ? Is it a bug ?RegardsVmanne

How to start with FileX using CubeMX?In CubeMX I enabled ThreadX and FileX with the default configuration, increased ThreadX "memory pool size" to 2k and  enabled "Generate Init Code" for both.In app_azure_rtos.c, tx_application_define() function MX_FileX_Init() fails - tx_byte_allocate() returns error code 16. According to docs that means TX_NO_MEMORY "Service was unable to allocate a block of memory within the specified time to wait.".I get this error even when I substantially increase ThreadX "memory pool size" to 64k.Without FileX enabled ThreadX works - I created a timer which nicely blinks the onboard LED.I know FileX does not really require ThreadX, but I need it for other purposes.This is

When trying to setup MBedTLS through CubeMX for the NUCLEO-H755ZI-Q, CubeMX does not give the option to select LWIP as the TCP/IP stack in the MBEDTLS "Version and modes" configuration tab. The only options given are "None" and "User defined". Additionally, for the "RNG dependency", the only options are "SW RNG(no entropy)" and "Custom RNG(Custom entropy)". It does not detect that I have enabled hardware level RNG. If I try setting up a project for NUCLEO-H745ZI-Q, I have the same issue. I tried setting up the project so the Ethernet stack was on the M7 only, the M4 only, and both the M7 and M4 and none of these variations made a difference.However, if I try setting up a project for any single core F4 or H7 variant, like the NUCLEO-H753ZI, I am able to select LWIP and HW RNG(ST entropy). In fact, when I enable MbedTLS, they are auto selected. Please see the attached screenshots.   This is the order always followed: Enable Ethernet RMII

 If I enable USB host and TouchGFX without OS I get the following generated code: /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */ MX_USB_HOST_Process(); MX_TouchGFX_Process(); /* USER CODE BEGIN 3 */ } /* USER CODE END 3 */As you can see MX_TouchGFX_Process() isn't indented properly.I want this: /* USER CODE BEGIN WHILE */ while (1) { /* USER CODE END WHILE */ MX_USB_HOST_Process(); MX_TouchGFX_Process(); /* USER CODE BEGIN 3 */ } /* USER CODE END 3 */ 

I have just purchased the STM32N6570-DK kit and have been able to successfully load and run the demo binaries. However when I have tried to generate a simple application like the LED Blink project I have been able to successfully get it running in the Cube IDE debug mode but once I load the .bin file into the external flash it will not run.I have followed the online tutorials by  B.Montanari as well as read all the available documentation but nothing seems to be working.I have signed the fsbl.bin file to create a fsbl-trusted.bin file and programmed the external flash at 0x7000 0000 exactly as outlined in the tutorials but no luck. The code definitely runs on the kit in the Cube IDE debug mode so I am obviously missing some vital key setup when it comes to loading it from flash but I am unable to figure out what it is.I understand how the BOOT pro

Dear community,we're using a Makefile Project with STM32H5xx and NetX Duo using the LAN8742When the code is generated, CubeMX is adding the line:.../STM32Cube/Repository/STM32Cube_FW_H5_V1.1.1/Drivers/BSP/Components/lan8742/lan8742.c \twice to the Makefile which leads to multiple definition errors in Compile. The line has to be removed by Hand afterwards. I think this is malicous behaviour here.Best RegardsPascal 

When I create a new GPIO port configured as OUTPUT in STM32CubeMX, the pin definitely exists on my board. However, after I click Generate Code, the new pin configuration does not appear in main.c (for example, I don’t see the initialization code for that pin in MX_GPIO_Init()).Why does this happen? I tried to investigate but couldn't find the reason.My STM32CubeIDE version is 1.19.0.The MCU I am using is STM32G071RBT3, and the specific pin I am trying to add is GPIOD pin 3 — but I also don’t see any other newly added pins in the generated code. None of the new GPIO ports appear after code generation. THANKS