STM32 MCUs Software development tools

Hi. ST There is an error in the code that is generated by CubeMx when you use 16bit in SPI DMA transfer. Can be solved in the stm32h5xx_hal_msp.c file: /* USER CODE BEGIN SPI4_MspInit 1 */ memcpy(&handle_GPDMA1_Channel1.Init,&NodeConfig.Init, sizeof(NodeConfig.Init)); /* USER CODE END SPI4_MspInit 1 */   maybe ST will look into it? Using:  STM32Cube FW_H5 V1.3.0 STM32CubeMX: 6.12.1 MCU: STM32H573IIKxQ Best regards.  

Hi everyone, I’m new to STM32 development and need some help configuring CLion for working with STM32 microcontrollers. I have installed STM32CubeMX (version 6.13.0) and am trying to generate a project for my STM32F411CEU6 microcontroller. However, I’m encountering an issue where the Eclipse launcher fails to work, and I can’t proceed further. I’m using macOS Sequoia (version 15.2). Could anyone guide me through the process of setting up CLion on macOS to work with STM32? Any advice, steps, or resources would be greatly appreciated! Thanks in advance!

The HSEM option is not found in "System Core" in STM32CubeMX (version 6.15), and the configuration option for HSEM interrupt is only found in NVIC. How to configure HSEM in STM32CubeMX. When I selected the LL library environment, the generated source code did not import the HSEM LL library header file. How to solve these two problems? If it is not possible to configure and import the HSEM related library files into the project file in STM32CubeMX, please let us know.

Hello, I trying to use DMA on USART6, but in handle list USART6 is unavailable:   I ques what there is some CubeMX error because in stm xxx_hal_dma.h file this uart is added to list: #define GPDMA1_REQUEST_USART6_RX 117U /*!< GPDMA1 HW request is USART6_RX */ #define GPDMA1_REQUEST_USART6_TX 118U /*!< GPDMA1 HW request is USART6_TX */  For now I will try to setup manually, but I still on question about this issue ?

Hi,Both Region 1 and Region 2 are configured with ALL READS/WRITES access permissions.The resulting initialization code is as follows: /** Initializes and configures the Region 1 and the memory to be protected */ LL_MPU_ConfigRegion(LL_MPU_REGION_NUMBER1, LL_MPU_INSTRUCTION_ACCESS_ENABLE|LL_MPU_ACCESS_INNER_SHAREABLE, LL_MPU_ATTRIBUTES_NUMBER1, 0x08030000, 0x0807FFE0); LL_MPU_EnableRegion(LL_MPU_REGION_NUMBER1); /** Initializes and configures the Region 2 and the memory to be protected */ LL_MPU_ConfigRegion(LL_MPU_REGION_NUMBER2, LL_MPU_INSTRUCTION_ACCESS_DISABLE|LL_MPU_ACCESS_INNER_SHAREABLE, LL_MPU_ATTRIBUTES_NUMBER0, 0x20010000, 0x20043FE0); LL_MPU_EnableRegion(LL_MPU_REGION_NUMBER2);The second parameter should also include the LL_MPU_REGION_ALL_RW attribute but it is missing.The .ioc configuration file is attached.

I am working with the MDF peripheral and find this to be a great peripheral. However the CubeMX generated code for multiple DMA based filters is not correct.I am using two filters with DMA and CubeMX generates the following descriptors:MDF_HandleTypeDef MdfHandle0;MDF_FilterConfigTypeDef MdfFilterConfig0;MDF_HandleTypeDef MdfHandle1;MDF_FilterConfigTypeDef MdfFilterConfig1;DMA_NodeTypeDef Node_GPDMA1_Channel1;DMA_QListTypeDef List_GPDMA1_Channel1;DMA_HandleTypeDef handle_GPDMA1_Channel1;DMA_NodeTypeDef Node_GPDMA1_Channel0;DMA_QListTypeDef List_GPDMA1_Channel0;DMA_HandleTypeDef handle_GPDMA1_Channel0; When starting the application I found that both MdfHandle0 and MdfHandle1 refer the same DMA handle,  handle_GPDMA1_Channel1. Likewise both handle_GPDMA1_Channel0.Parent and handle_GPDMA1_Channel1.Parent refer the same filter handle,  MdfHandle0.This is caused by generated function HAL_MDF_MspInit which is called when starting a filter using HA

Hello,With CubeMX version 6.16.0 and FW package version STM32Cube FW_N6 V1.3.0, the GPIO configuration's are missing from the generated HAL_I3C_MspInit and HAL_I3C_MspDeInit functions in stm32n6xx_hal_msp.c, when I3C is set to application context.Application context stm32n6xx_hal_msp.c/** * @brief I3C MSP Initialization * This function configures the hardware resources used in this example * @PAram hi3c: I3C handle pointer * @retval None */ void HAL_I3C_MspInit(I3C_HandleTypeDef* hi3c) { RCC_PeriphCLKInitTypeDef PeriphClkInitStruct = {0}; if(hi3c->Instance==I3C2) { /* USER CODE BEGIN I3C2_MspInit 0 */ /* USER CODE END I3C2_MspInit 0 */ /** Initializes the peripherals clock */ PeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_I3C2; PeriphClkInitStruct.I3c2ClockSelection = RCC_I3C2CLKSOURCE_CLKP; if (HAL_RCCEx_PeriphCLKConfig(&PeriphClkInitStruct) != HAL_OK) { Error_Handler(); } /* Peripheral clock enable */ __HAL_RCC_I3C

Subject: Linker Error: Multiple definitions of BLE assembly modules when using CubeMX v6.16.1 CMake generator on STM32WB09Environment:MCU: STM32WB09CubeMX Version: 6.16.1Toolchain: CMake / arm-none-eabi-gcc 14.3.1IDE: VS Code with STM32CubeIDE Extension v3.7.0Middleware: STM32_BLE (Bluetooth LE Stack)Description: I am experiencing a linker failure when building a project generated with STM32CubeMX using the CMake toolchain option. While the project compiles and links correctly when using the standard STM32CubeIDE (Eclipse-based) workflow, the CMake-based build in VS Code fails during the linking stage.The linker reports multiple definitions for several symbols located in the BLE Middleware assembly files. It appears that the same source files are being compiled into different targets and then linked together, causing collisions.Key Error Logs:[main] Building folder: C:/Users/reginaldo.lopes/Desktop/ble_test/build/Debug [build] Starting build [driver] NOTE: You are building with preset

Hello ST,FYI - It appears CubeMX was not updated since DP-FPU capability was added to the STM32N6 data sheets.Regards,Dave

I have set XSPI1 to "Hexa SPI" mode. I'm using EXTMEM_MANAGER to manage the memory. I'm unable to select the setting EXTMEM_LINK_CONFIG_16LINE for "Number of memory data lines". Instead there is a info textbox which says "Active only when XSPI enabled in Hexa SPI mode.". The only available option is EXTMEM_LINK_CONFIG_1LINE. This results the EXTMEM_DRIVER_PSRAM_Init function to fail in the Config switch case, as the only options in the switch case are EXTMEM_LINK_CONFIG_16LINE and EXTMEM_LINK_CONFIG_8LINE.If i manually force the Config to be EXTMEM_LINK_CONFIG_16LINE before the switch case, it seems to work.I believe that i should be able to select EXTMEM_LINK_CONFIG_16LINE with MX if my XSPI is configured to Hexa SPI mode.    

CubeMX 6.16.1MacOS 15.7.3STM32F469NIHXMultimedia - DSIHOST - Data and Clock Lanes     -  click,click,clickShow Advanced Parameters - checkHS Transmission fine tuning and LP Transmission fine tuningTransmission Delay on Clock Lane and Transmission Delay on Data LanesThese items refer to 2-bit wide fields in DSI_WPCR1 but CubeMX allows values from 0-10, which would be 3.32-bits wide. By setting the clock transmission delay to, say, 10, the data clock delay gets overwritten as well. Data delay overwrites the low power clock delay, and so on.The actual data range for these items should be [0,3], and HAL_DSI_SetSlewRateAndDelayTuning should probably sanitize the parameter Value before using it.

Hello, We appear to be experiencing a severe code generation bug with CubeMX. After naming and sizing application regions in the memory management tool, what used to generate a correct linker script now generates bad output.Upon generation the linker script STM32U575XX_FLASH.ld now shows:/* Specify the memory areas */ MEMORY { RAM (rwx) : ORIGIN = 0x20000000, LENGTH = 768K FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K /*start of MX regions Auto-generated By STM32CubeMX*/ RAMBK (rw) : ORIGIN = 0x20000000, LENGTH = 768K RAM4 (rwx) : ORIGIN = 0x20000000, LENGTH = 768K SPIFLASH (rwx) : ORIGIN = 0x08000000, LENGTH = 2048K /*end of MX regions*/ }Given that we cannot downgrade the IOC and have performed more work this is an awkward situation and we will manually manage regions in the meantime. This was not an issue before. Please advise what may be going on. Host: OS X 26.2CubeMX: 6.16.1Target: STM32U575xx  

I am using cubemx to generate a CMAKE project for a NUCLEO_144 based board (NUCLEO_H563).Project generation creates a cmake/stm32cubemx/CmakeLists.txt file that generates a macro define "USE_NUCLEO_144".it also auto creates a stm32h5xx_nucleo_conf.h file that also creates the same define: /** @defgroup STM32H5XX_NUCLEO_CONFIG_Exported_Constants Exported Constants  * @{  *//* Nucleo pin and part number defines */#define USE_NUCLEO_144/* #define USE_NUCLEO_64 */ This creates a duplicate redefinition warning upon build in many places as this header is included throughout my project in many places.This is extremely annoying.I can suppress the warning by adding: #if !defined (USE_NUCLEO_144)#define USE_NUCLEO_144#endif /* USE_NUCLEO_144 */ to the stm32h5xx_nucleo_conf.h filebut of course, this change gets wiped out upon next cubemx code regeneration. It would be so helpful if this guard was included if whatever mechanism you use to generate the _conf.

Dear STMicroelectronics,This is a bug report on the UI for STM32CubeMX 6.16.0 running on Windows 11 Pro 25H2.Please report this internally so that it may be fixed in some future version. Steps to reproduceStart STM32CubeMXFile / New ProjectSelect MCU STM32H563RIT6Click button Start ProjectSelect with TrustZone activated and click OKUnder Categories, expand Middleware and Software PacksFor ThreadX, click the greyed out radio button in column M33NSClick it againExpectedThe popup is readable.ActualAfter the second click, the popup is shown partially obscured by the table and is not readable.If you select the row for ThreadX and click the radio button you can get the popup very much obscured - see attached screenshot.Further infoThe screen resolution doesn't seem to affect the behaviour.I have also reproduced this problem when running the Linux variant of 6.15.0 on Debian bookworm.     Best regards, Jesper 

Split from this thread. Yes, but No!CubeMX V6.16 now allows only exactly 32 TX Buffers ((TX Buffer Nbr + TX Fifo Queue Elmts Nbr) == 32).But less then 32 TX Buffer is allows by the Hardware, and some times, required if You want to maximize the RX Buffers.

Hi everyone,I am attempting to set up the new CubeMX version (6.16.0) inside a Docker container, but I am running into issues.Setup:Base Image: Ubuntu 24.04Target Software: STM32CubeMX 6.16.0Goal: Headless installation (auto-install), since CubeMX is no longer bundled with CubeIDE 2.0.0.The Issue: The headless installation fails. According to the User Manual "UM1718", this mode should still be supported. However, the installation process differs from the manual and aborts with an error. Note: The current manual still uses version 6.11.0 in its examples.What I have tried so far:Verified with v6.11.0: I tested the headless installation with the older version 6.11.0. This works perfectly and follows the manual exactly.Quiet Mode: I tried installing v6.16.0 using the -q operator, but this triggers an error as well.Error Log: I receive the following output/error trace:user:/# ./SetupSTM32CubeMX-6.16.0Check exe path on linuxFullExe path1 is: /SetupSTM32CubeMX-6.16.0Exe path is: /Search java

I recently tried to use -noreconnect via the cli on windows and it still attempted to reconnect.I was connected via UART and programming option bytes. Here was the command I used:& "C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe" -c port=COM14 br=115200 -noreconnect -ob ndbank=0x0I see that there was fix put in for linux. Im wondering if the same bug exists on Windows.Thanks,Daniel 

Hello,Our project is based on the STM32WBA65MI, and we have an external flash chip on the board that we use STM32CubeProgrammer w/a custom external loader to program. This worked well with STM32CubeProgrammer v2.20, but when I updated to STM32CubeProgrammer v2.21, suddenly I was unable to connect to the board using the external loader.This happens as soon as I select the external loader andIf I select verbosity level 3, this is what I see:08:50:10:520 : Selected loader: C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX25R6435_STM32WBA65-LEGATO.stldr 08:50:10:520 : Error: Flash loader C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/ExternalLoader/MX25R6435_STM32WBA65-LEGATO.stldr cannot be loaded.Here's the StorageInfo:struct StorageInfo __attribute__((section(".Dev_Info"))) const StorageInfo = { "MX25R6435F_Legato", // Device Name + version number SPI_FLASH, // Device Type 0x00000000, // Device Start Address 0x800000, // D

I want to set the BOR_LEV of H523 to 1. If you have any good ideas, please let me know.

Hi everybody, I'm using a custom PCB which is build upon a STM32L431CBT6 MCU. When connecting to the CUBE Programmer i had this error:Error: Database: There's no active configuration for this device. All the 1 configurations are disabled!Then, i confirmed the issue arose from the DeviceID 0x435 .xml file not having the 128K flash memory settings. What i did is code it myself like this:<!-- JTAG_SWD Interface --> <Interface name="JTAG_SWD"> <Configuration number="0x0"> <!-- 256KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0100"/> </FlashSize> </Configuration> <Configuration number="0x1"> <!-- 128KB--> <FlashSize> <ReadRegister address="0x1FFF75E0" mask="0x0000FFFF" value="0x0080"/> </FlashSize> </Configuration> </Interface> <!-- Bootloader Interface --> <Interface name="Bootloader">

Hi, I am trying to debug my STM32N6570-DK board, i followed the steps listed under 4.1.3 (Debugging the application) in the getting started instruction list (https://www.st.com.cn/resource/en/application_note/an6265-getting-started-with-stm32n6-mcus-in-stm32cubeide-stmicroelectronics.pdf). When i try to debug the application, it starts normally (code uploads to the external memory), but when i click resume to start the program, the debugger loses connection and eventually exits debug mode. The program I am trying to debug was made using TouchGFX, it's configured as an FreeRTOS project. This is the output the debugger gives to me:Starting server with the following options:Persistent Mode : DisabledLogging Level : 1Listen Port Number : 61234Status Refresh Delay : 15sVerbose Mode : DisabledSWD Debug : EnabledInitWhile : EnabledWaiting for debugger connection...Debugger connectedWaiting for debugger connection...Debugger connectedWaiting for debugger connection...Target is not respond

Even I am using the latest CubeProgrammer v2.21.0, it indicates an update available but when I check it, there is no update and the updater log does not update, it cannot update its last update date as well.I know not so important but quite annoying problem, i`d like to mention, 

STM32CubeIDE for VS Code is there a memory window? like MDK Memory window   

Can anyone help to find the error in the code because it is not able to print anything on the console. I have also try to change the pins of UART but then also it is not be to print anything on the console. 

Hi im trying to make up a iot curtain right now and using stm32f411re with nodemcu to connect them to my wifi.i am testing all the sensors and wifi sector separated so non of the sensors are connected to stm32 right now just nodemcu and stm32. so i have tested to make a webpage to have a button to light up ld2 led and when i modified the code like below, the mcu still connected to wifi, gave the IP address to connect, but webpage gives me ERR_CONNECTION_REFUSED how do i solve this problem?