Solved

Hello, I have been having a ton of trouble setting up a simple ADC + DMA on the new STM32N6 Nucleo board. I have confirmed that my adc is sampling by looking into the data register of my ADC. However, the only way I got the HPDMA to write in my adc buffer was through DTCM as I followed the reccomendation of this topic, in order to avoid the hassle with S and NS domains. However I wish to sample at 2.5 MSPS and through DWT and the Cplt_Callback of the HPDMA I found that my data actually came through at 1.44MSPS. The ADCs of this STM are rated for 5MSPS.Can anyone help me make it so that I can sample at the desired rate and actually get a hold on that data at the desired rate. Also if you know of a better fix than cranking the CID to 11 I’d happily take it. Thanks, Lorenzo

The top line is S4 then there is a QR Code and then 513. I think it to be one of the iNEMO Inertial Modules but I don’t know how to go about checking which one. I don’t know the dimension of the package  

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.

I am a long-time STM32CubeMX user (7+ years). I ran into an issue with STM32CubeMX recently while modifying an existing configuration for an STM32L4 project. This is a usability issue.In the NVIC configuration page, there are two tabs, one labeled "NVIC", the other labelled "Code Generation". In the NVIC tab there is a column labelled "Enabled". The issue is with the word "Enabled" -- it has a clear meaning with regard to interrupts. I wanted the interrupt handler created, but I wanted the code generated with the interrupt disabled. I made the mistake of disabling "Enabled" in the NVIC tab, initially ignoring the "Code Generation" tab. The result was that the interrupt handlers, along with my user code, was removed from the stm32l4xx_it.c file. (I had it in source control, so nothing was lost.)"Enabled" on the NVIC tab means that the interrupt is used and a candidate for code generation. The selection I wanted is on the "Code Generation" tab labelled "Generate Enable in Init". The word

missing --start-group around WBA2_LinkLayer_BLE_Full_lib.EnvironmentSTM32CubeMX version: 6.17.0STM32CubeWBA firmware package: 1.9.0Target device: STM32WBA25CG (NUCLEO-48 board)Toolchain: GNU Tools for STM32 14.3.1+st.2 (arm-none-eabi-gcc/ld)Build system: CMake (toolchain selected via "CMake" in CubeMX project settings)Host OS: Windows 11Steps to reproduceCreate a new STM32CubeMX project for STM32WBA25 (NUCLEO board).Enable BLE (peripheral role, BLE_Full stack).In Project Manager → Toolchain/IDE, select CMake.Generate code.Build with the generated CMakeLists (e.g. cube-cmake --build build/Debug).Expected Build links cleanly.Actual Link fails with:ld.exe: stm32wba_ble_stack_full.a(le_ctrl.o): in function `LECTRL_LL_Init': le_ctrl.c:(.text.LECTRL_LL_Init+0xa): undefined reference to `ll_ble_events_init' ld.exe: (ll_ble_events_init): Unknown destination type (ARM/Thumb) in stm32wba_ble_stack_full.a(le_ctrl.o) le_ctrl.c:(.text.LECTRL_LL_Init+0xa): dangerous relocation: unsuppor

Hello EveryoneI am using CubeMX 6.17.0 and Embedded Software Package STM32H5 1.6.0:Is there a control missing to setup "Trigger Output (TRGO) Parameters?  In comparison to e.g. Tim15:   

Hello,I just downloaded STMCubeIDE 2.1.1 to generate a simple project for a Nucleo-C562RE board.I am not using CubeMX2 (for various reason, that is not the point).The default empty project generated for STM32C562RE by the IDE has only 1 SRAM element with a size of 64K, instead of 2 SRAM elements of 64K each.FLASH size is correct though.Out of curiosity, if ST were to push a fix for this kind of bug, would it be a new IDE release ? or could it be a STM32C5 pack update only ?

Hello, I'm trying to create a project with custom model via STM32 Cube AI studio, which uses STedge Core AI v. 3.0.0. Validation is performed on STM32N6570-DK. I'm getting following error:E200(ValidationError): TARGET: Unable to bind the ST.AI runtime with "network" c-model: [] E801(HwIOError): Invalid firmware - COM7:115200 When running same command from command line I see that progress goes to 74,8 % and then stucks until error is displayed.See attached failed report for details. 

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

Hi everyone,the update to CubeMX 6.17 seems to introduce a new valid range of the "First RX Descriptor Address" of the Ethernet setup on a NucleoH755 board. This is also the case for the STM32H745.This is the valid range according to the CubeMX field description (there is also a typo for the Parameter Description "Fisrt"):First Rx Descriptor AddressFirst Rx Descriptor Address must be between 0x24000000 and 0x30047fff.Parameter Description:Fisrt Rx Descriptor address must be only in the D2 Domain AHB SRAM. Rx descriptor address must not exceed Max value and must no overlap with Tx descriptor and Rx buffer. These areas must not be cacheable.This contradicts the knowledge base article: How to create a project for STM32H7 with Ethernet and LwIP stack working The reference manual also states that 0x3004000 - 0x3004FFFF should be part of the D2 Domain AHB SRAM3 and hence be part of the intended area. Is this just a bug or do I overlook something?Kind regards

With the attached ioc, CubeMx 6.17.0 freezes when I click on "Generate Code" on macos 14.8.3 . If I start it from the command line I can see this error in the console:2026-03-09 17:20:52,902 [INFO] UtilMem:75 - End SaveConfig() Used Memory: 550133736 Bytes (1459617792)2026-03-09 17:20:52,976 [INFO] UtilMem:75 - End SaveConfig() Used Memory: 580273760 Bytes (1459617792)2026-03-09 17:20:53,182 [INFO] ProjectBuilder:603 - [PM] Start Project Generation Thread2026-03-09 17:20:53,207 [INFO] IPsOverviews:2785 - set Specific Code input for plugin: RCC2026-03-09 17:20:53,207 [INFO] IPsOverviews:2785 - set Specific Code input for plugin: I2C2026-03-09 17:20:53,207 [INFO] IPsOverviews:2785 - set Specific Code input for plugin: I2C2026-03-09 17:20:53,207 [INFO] IPsOverviews:2785 - set Specific Code input for plugin: USART2026-03-09 17:20:53,207 [INFO] IPsOverviews:2785 - set Specific Code input for plugin: MEMORYMAP2026-03-09 17:20:53,207 [INFO] IPsOverviews:2785 - set Specific Code input for plug

Hello, I was going through the schematic of STM32U5G9J-DK1 where I came across the unused LDO (U19) for generating 1.8 V on this board. I wanted to know the significance of this LDO and what were the reasons to keep it unpopulated?Also, can I expect to see an improvement in the driving capability of this rail in case I wish to populate U19 with TPS76301? If yes, which orderable part no. of the same would be recommended?

  Hi everyone,I think STM32CubeMX is generating an incorrect configuration for STM32L071.In CubeMX → System Core → SYS → System power supply,I selected Power Regulator = SMPS (instead of LDO) and generated the project.After code generation, I get build errors because CubeMX inserts code that does not exist for this device / HAL package:In stm32l0xx_hal_msp.c, I see references like: HAL_PWREx_ConfigSupply(...) PWR_SMPS_SUPPLY But for STM32L0 / my CubeL0 HAL, these are not definedMy version is :

When choosing SmartCard mode for USART, parameter Parity is automatically set to Even. However generated code in usart.c, does not has:hsmartcard1.Init.Parity = SMARTCARD_PARITY_EVEN;Only when I manually reselect that in GUI, the parity will be set in the generated code.I am using Nucleo-G0B1RE.

Hello,I have been trying to configure the ethernet RMII with PTP synchro on cube MX. The idea is to link the PPS signal to trigger the timer. I can't manage to get the remap to be done to the ETH_PTP_PPS as is not displayed in the dropdown. According to the same cube mx that option should appear. On a side note when I enable the RMII_PTP_syncro I also loose all the config information of ethernet which i find rather strange. Do any of you have any suggestions on what's the proper way of configuring this? Is this even possible or is just a bug of the prompt that implies is possible? Thanks in advance ;)

Hello,  Began learning STM32 MCUs with my Nucleo-H753ZI board and I think I found a bug. The IO configurator on CubeIDE thinks user LED2 is on PB7 and is blue coloured. I'll paste the code it generates below. But in fact, the user manual UM2407 says user LED2 is on PE1 and is yellow coloured, which is indeed correct. Generated code from CubeIDE for Nucleo-H753ZI:#define LED2_PIN GPIO_PIN_7 #define LED2_GPIO_PORT GPIOB Appears to be a bug that should be fixed in the BSP.

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.  

Downloaded the update of STM32CubeMX 6.17.0 to install the ARM version on my M4 MacBook Air with macOS Tahoe.  The issue is that it installs an Intel version and not an ARM version.  I uninstalled version 6.16 before installing this updated version.The installer file was SetupSTM32CubeMX-6.17.0-Mac-ARM.app.tar downloaded from the STM32CubeMX download page.The next macOS version after Tahoe will not support Intel apps and was expecting an Apple Silicon version as per the download!What is up with this?

Hello,I am using a STM32MP257 (Karo SOM), RGMII connected to a DP83869 (100Mbps fiber mode).This is working well until I start the LVDS screen on my board.The screen is powered with 2 regulators :  Backlight (16V/360mA, dedicated boost) Logic (2.7V/500mA, dedicated buck)The DP83869 is powered with 3 regulators :1.1V (dedicated buck) 2.5V (dedicated LDO) 3.3V (shared buck also powering the MP2 SOM)Below is the behavior in different configurations:Screen unplugged => fiber link OK Screen plugged => fiber link KO hot-unplugging the screen makes the link working instantly Screen unplugged, flat cable present, with 100ohm R at the end of the LVDS signals => OK Screen unplugged,  With no current on the BL / logic DC/DC converter => OK Sinking 300mA on the BL => KO Removing the sink current makes the link working instantly Sinking 300mA on the logic => KO Removing the sink current makes the link working instantly Probing power rails with a scope show clean signals,

MCU: STM32H563VITx Stm32CubeMX version: 6.14.0 HAL Driver version: 1.5.0 When I enable EDATA option bytes in CubeMX, it generates the following code: void MX_FLASH_Init(void) { /* USER CODE BEGIN FLASH_Init 0 */ /* USER CODE END FLASH_Init 0 */ FLASH_OBProgramInitTypeDef pOBInit = {0}; /* USER CODE BEGIN FLASH_Init 1 */ /* USER CODE END FLASH_Init 1 */ if (HAL_FLASH_Unlock() != HAL_OK) { Error_Handler(); } /* Option Bytes settings */ if (HAL_FLASH_OB_Unlock() != HAL_OK) { Error_Handler(); } pOBInit.OptionType = OPTIONBYTE_EDATA; pOBInit.Banks = FLASH_BANK_2; pOBInit.EDATASize = 2; if (HAL_FLASHEx_OBProgram(&pOBInit) != HAL_OK) { Error_Handler(); } if (HAL_FLASH_OB_Lock() != HAL_OK) { Error_Handler(); } if (HAL_FLASH_Lock() != HAL_OK) { Error_Handler(); } /* Launch Option Bytes Loading */ /*HAL_FLASH_OB_Launch(); */ /* USER CODE BEGIN FLASH_Init 2 */ /* USER CODE END FLASH_Init 2 */ }​ The function does not launch

Cross selector displays operation frequency of STM32H743II as 400MHz, but it should be 480MHz. I've refreshed all data and databases but the result is the same. Is there a known solution for this issue? 

I'm trying to configure DMA in Memory-to-Peripheral mode for the STM32WB09KE, specifically to transfer data from memory to a Timer channel (TIM2_CH3 for Addressable LED's). However, in STM32CubeMX, I cannot see the expected DMA options under the DMA Settings tab for my Timer.    

Cube MX v6.17.0 and even previous version v6.16.1 have a problem generating SystemIsolation_Config for STM32N6.I made a test IOC file. There are 3 SECURE checkboxes checked in RIF -> RIF Aware IPs -> EXTI1:Line 13 for  EXTI13Line 17 for RTC secure-wakeupLine 62 for Wake-up PIN3Screenshot: Generated SystemIsolation_Config(void) in main.c of FSBL contains: /* set up EXTI configuration */ /* EXTI13 line */ HAL_EXTI_ConfigLineAttributes(13,EXTI_LINE_SEC|EXTI_LINE_NPRIV); /* RTC secure wake-up line */ HAL_EXTI_ConfigLineAttributes(17,EXTI_LINE_SEC|EXTI_LINE_NPRIV); /* Wake-up_PIN3 line */ HAL_EXTI_ConfigLineAttributes(62,EXTI_LINE_SEC|EXTI_LINE_NPRIV);These calls fail in this assert in stm32n6xx_hal_exti.c: assert_param(IS_EXTI_LINE(ExtiLine));Full assert is turned on in IOC so it lands in assert_failed.The assert condition check macro is very messy, but it appears like it expects type and register mask with it so I added them (based on table 138. EXTI line connec

在使用最新版本的CubeMX 6.17.0 配置STM32G474QETx系列的HRTIM时，Dead Time明明没有启用，但是显示TA2的置位输出源无法配置。