STM32CubeMX (MCUs)

We are migrating to a custom board and controller. Looking at the IOC generated by the Motor Control Workbench, there are some mystery variables that show up in the timer and we cannot track down where they are defined. See the attached snapshot and highlighted areas.Where are these defined? What is HTMIN?

MCU used : STM32H753ZITx LQFP144CubeMx version : 6.13.0Situtation: I have a IOC file with some configurations on ADC1, like "Left Bit Shift" set to "4 bits shift" and "Conversion Data Management" to "DMA One Shot Mode".Those modifications are not translated into the generation ADC init in main.cI need to edit this by myself by callingADC_REG_InitStruct.DataTransferMode = LL_ADC_REG_DMA_TRANSFER_LIMITED;ADC_InitStruct.LeftBitShift = LL_ADC_LEFT_BIT_SHIFT_4;

I found the following issues when generating code for an SAI peripheral using CubeMX6.14.0 for the STM32H73IIKx board. These issues are also present in 6.14.1 and 6.15.0. They are not present in 6.13.0.1. Displayed Real Audio Frequency in CubeMXTwo sub-issues:When a specific Audio Frequency is selected, the displayed Real Audio Frequency seems to be equal to the read audio frequency for a clock divider of 0, regardless of the Audio Frequency Selected.WhenUser set Master Clock Divider value is selected for Audio Frequency, the displayed Real Audio Frequency is 0.These issues are shown in the attached Real Audio Frequency.jpg.2. OVERSAMPING constants are used for the NoDivider field in the generated codee.g.&

Setup:STM32CubeMX Version v6.14.0SMT32Cube FW_G4 V1.16.0Problem Description:When enabling RegisterCallback for EXTI Interrupts, the generated code still calls a predefined interrupt callback  for EXTI interrupts and does not call the registered callback function./** * @brief Handle EXTI interrupt request. * @PAram GPIO_Pin Specifies the port pin connected to corresponding EXTI line. * @retval None */ void HAL_GPIO_EXTI_IRQHandler(uint16_t GPIO_Pin) { /* EXTI line interrupt detected */ if (__HAL_GPIO_EXTI_GET_IT(GPIO_Pin) != 0x00u) { __HAL_GPIO_EXTI_CLEAR_IT(GPIO_Pin); HAL_GPIO_EXTI_Callback(GPIO_Pin); } } /** * @brief EXTI line detection callback. * @PAram GPIO_Pin: Specifies the port pin connected to corresponding EXTI line. * @retval None */ __weak vo

Hello ST team,I’m using an STM32F723 microcontroller with USB HS (High Speed) in Communication Device Class (CDC) mode.Everything worked perfectly using:STM32CubeMX v6.10.0STM32Cube FW_F7 v1.17.1However, after migrating the project to:STM32CubeMX v6.13.0STM32Cube FW_F7 v1.17.4the USB HS initialization fails due to what appears to be a missing clock enable definition and configuration in the generated code.Observed behaviorIn the generated usbd_conf.c file, inside:void HAL_PCD_MspInit(PCD_HandleTypeDef* pcdHandle)Previously (working version) CubeMX generated:/*

I'd like to report one issue with DMA Linked List editor. I need to do PSSI reception with GPDMA using linked list on STM32H7R3L8H6H. CubeMX is version v6.15.0 and CubeIDE is v1.19.0.Based on reference manual (RM) and AN5593, the GPDMA ports 0 and 1 are both AHB ports, with port 0 being capable of direct access to APB peripherals. However, Linked list editor in CubeMX displays port options with wrong names:I guess it follows HPDMA port naming. Maybe it should avoid naming at all or decide it based on the DMA channel option in the List editor.It looks like a minor issue, but I happened

In Docs & Resources dialog, we have every docs except the datasheet.The only way to read datasheet is the icon during device selection, once the project is created there is no more link to datasheet.  

I have a project with the STM32H753IIT6 with 9 free pins on it all of them labeled and many peripherals configured. I want to migrate to STM32H7R3I8T6 which I understand is the same family of MCU, it should be possible. I followed the steps in How to switch from one STM32 to another using STM3... - STMicroelectronics Communityand after selecting the document from where to import I get the "Project is successfully imported. Import RCC : PASS" dialog, but all the configuration remains in default state, nothing has changed. I also tried to create a new project with the same MCU as before (STM32H753IIT6) and it was really imported; all pins are there.Also tried to create a new project with the STM32H753IIT6, assign a few pins, save it and imp

Hi,I'm configuring the CubeMX for an application with 5 capacitive sensors.I used G1_IO1 and G1_IO2 for two sensors, and G1_IO3 for the sampling capacitor of G1. The other three sensors are on G4_IO1, G4_IO2 and G4_IO3, with the sampling capacitor on G4_IO4.The active shield is configured on G3_IO2 with the sampling cap on G3_IO3.I would like to define banks to sample G1_IO1 at the same time as G4_IO1 (and shield), and G1_IO2 with G4_IO2 (and shield). The third bank will be a single channel (G4_IO3).I was actually able to set it in the tsl_user.h as#define CHANNEL_0_IO_MSK (TSC_GROUP1_IO1)#define CHANNEL_0_GRP_MSK (TSC_GROUP1)#define CHANNEL_0_SRC (TSC_GROUP1_IDX) /* Index in source register (TSC->IOGXCR[]) */#define CHANNEL_0_DEST (0) /* Index in destination result array */#define CHANNEL_1_IO_MSK (TSC_GROUP1_IO2)#define CHANNEL_1_GRP_MSK (TSC_GROUP1)#define CHANNEL_1_SRC (TSC_GROUP1_IDX)#define CH

Hello,I'm new to Keil and want to port an existing project from STM/FreeRTOS/GNU to Keil toolchain. I've created a project for STM32F4 for Keil MDK using CubeMx V6.15.0.For RTOS, I use RTX5 / CMSIS-RTOS2 API.I get the following compile errorC:/Users/t3.loc.StJo/AppData/Local/Arm/Packs/ARM/CMSIS/6.2.0/CMSIS/RTOS2/Source/os_systick.c(70): error: no member named 'SHPR' in 'SCB_Type'; did you mean 'SHP'? SCB->SHPR[11] = SYSTICK_IRQ_PRIORITY; ^~~~ SHP ../Drivers/CMSIS/Include\core_cm4.h(453): note: 'SHP' declared here __IOM uint8_t SHP[12U]; /*!< Offset: 0x018 (R/W) System Handlers Priority Registers (4-7, 8-11, 12-15) */According to this info Breaking changes in CMSIS-Core 6, there is a version mismatch between the CMSIS-RTOS and the STM

Hi ST Community Team,I previously raised a concern regarding the STM32N657x0H3Q and the NetX Duo Ethernet stack where some driver files are not generated by STM32CubeMX (see original post):"https://community.st.com/t5/stm32cubemx-mcus/stm32n657x0h3q-netxduo-ethernet-some-drivers-files-not-generated/m-p/805201#M32333"This issue is still not resolved, and I haven’t seen any fix or update addressing the problem. It’s blocking development on my end. Could you please look into it.Thank you .

I use my own modified sct file in Keil, and when CubeMX generates project, it overwrites the sct file in the default location.Even ignore the default sct file and chang the Keil sct settings (using a modified sct file stored in a non-default location), CubeMX will reset this setting to the default file when cubemx generates the project. Keil 5.43.1CubeMX 6.15MCU Package F3 1.11.5

I am using the latest MDK-ARM Tool Chain (5.43a), and CubeMX is 6.15. So far, I have used Cubex to generate the initialisation and peripheral codes, middleware, etc., compiling them using KEIL. It is perfect and never seen any issues.I want to use middleware from MDK-ARM instead of Cubex. I followed the manual online at the KEIL/ARM site as well as on ST for RTE and CubeMx Integration. It is not clearly defined; should I run CubeX from the RTE of KEIL, or can CubeMX run independently and create the init code?I get the following errors:Error instantiating RTE componentsError #545: Required input file from generator CubeMX: 'E:/STM32CubeMX/Target_1/GSN_Controller_RevC.cgen.yml' is missingCreating E:GSN_Controller_RevC.Target_1.cbuild-gen.ymlCreating E:/Target_1.cbuild-gen-idx.ymlLaunching CubeMXARM\cmsis-toolbox\bin\cbridge.exe E:\Target_1.cbuild-gen-idx.ymlError: generator 'CubeMX' missing. Install from '

Hello,I was using the STM32CubeMX across various MCUs and wanted to know is there a way to generate a report of the total and unused goios with names? from the current ioc or current project .it should show the GPIOS used and for which peripherals and possibly any warnings for the conflicting GPIOS ?regards,D

Dear ST,This has been reported in other posts before, but I would like to make a clear suggestion.The problem is that IOC file changes are hard to merge in Git (or in other SCM) with diff tools because:Some parameter names use indexing. Inserting something means changes on following lines.Some parameter values are lists of items on a single line. It is painful to merge 1000 characters long line.It is not intuitively clear what some parameters mean. There's no grouping or context. Risk of making bad merge.Therefore I make a suggestion to switch over to a file format that is still human readable, has a hierarchical structure and is source code tools friendly. It would be even better if it is based on some existing widespread format so developers can build their own development tools to parse or create IOC and use it as a SSOT (single source of truth) or as an output from other SSOT system.Two such standards come to my min

Hi,  When will the announcement in the link below come into effect?  ​​Will there be a version of STM32CubeMX that will generate a project including the LwIP, FreeRTOS, and Filex libraries for    the  STM32H5?  https://community.st.com/t5/developer-news/new-strategic-directions-for-stm32cube/bc-p/804011#M126 Ari

When using USART2 on the C071, CubeMX is generating calls to functions like `HAL_UARTEx_SetTxFifoThreshold` but the USART2 on C071 is a basic UART without FIFO.

Yesterday I've switched from v6.13.0 to v6.14.1 and noticed that the new version changes the way cmake/stm32cubemx/CMakeLists.txt generated. Previously generated CMake list had relative paths like ../../Src/main.c, which works perfectly in both cases when CMakeLists.txt in root directory of project (the one generated by CubeMX) is the top-level CMake list and when it's not. But now (not sure from version 6.14.0 or 6.14.1) paths to files generated by CubeMX become absolute and use CMAKE_SOURCE_DIR variable as prefix directory (e.g. ${CMAKE_SOURCE_DIR}/Src/main.c). The new approach perfectly works when top-level CMake list is the one in project root directory generated by CubeMX, but it fails when used as part of another (non-CubeMX) top-level project, due to broken paths to source files. A few words about my project structure:my_cmake_project/ ├── boards

Issue: ST67W6X_CLI lockup Test Setup:Use the ST67W6X_CLI example provided with the x-cube-st67w61-v1.0.0 software package.Send wifi_sta_connect command to connect.Send several ping commands to verify connection.Keep the connation active.Wait for 5 to 10 minutes then repeat the ping commands. Observation:Fail to respond to atcmd AT reset required to recover.See attached.

Hi ST team, Been trying to build a bare bones MX generated project for the STM32H563ZI using CMake, for both TrustZone and non-TrustZone Projects. Had the same issue on both Ubuntu22.04 and Ubuntu24.04, and am unable to compile any of these projects. When I have TrustZone enabled with both S and NSC projects enabled I get the following error messages:```lachjet@lachjet-Katana-GF76-12UD:~/tzt2/uild$ make[ 6%] Creating directories for 'tzt2_S'[ 12%] No download step for 'tzt2_S'[ 18%] No update step for 'tzt2_S'[ 25%] No patch step for 'tzt2_S'[ 31%] Performing configure step for 'tzt2_S'Build type: Debug-- The C compiler identification is GNU 11.4.0-- The CXX compiler identification is GNU 11.4.0-- Detecting C compiler ABI info-- Detecting C compiler ABI info - done-- Check for working C compiler: /usr/bin/cc - skipped-- Detecting C compile features-- Detecting C c

Hello @STTwo-32.In this new release 6.13.0 I can`t use the internal Voltage Reference in STM32U585. I also don't see the option to select the Internal Voltage Reference in VREFBUF setting. It's very bad(.

Hello,While creating a project for STM32N6 I can’t find the option for hexaspi or octospi for STM32N657B0HxQ . Is there any particular option I have to enable?I am trying to generate the ioc similar to STM32N6570-DK board .I am on 6.15.0 STM32CubeMX. Where is octo and hexaspi option?also which mode I have to enable FSBL + Non Secure/Secure or only Non Secure/SecureBest Regards,D

Hi,APB1 clock can't be enabled if HSI clock is chosen. It says that the driven clock must be 10M<=x<48M, so, without using the PLL it's impossible to get the 10MHz. Things get worse when I try to feed the PLL from the HSI: it says that the PLL should have HSE as an input!

Hi, I am using the following environment:OS: Ubuntu 20.04 LTSSTM32CubeMX: 6.15.0Visual Studio Code: 1.103.2STM32Cube for Visual Studio Code : 3.5.1Board: NUCLEO-H563ZI I found a bug where the STM32H563XX_FLASH.ld file is not generated after generating code.This bug can be reproduced by following the steps below:Create any cubemx project for STM32H563xx.Set "The Toolchain / IDE" to CMake.Click "Generate Code" .After generating code, the files "STM32H563xx_FLASH.ld" and "STM32H563xx_RAM.ld" are generated.However, the CMake build environment requires only STM32H563XX_FLASH.ld. As a result, the CMake build fails an

Hey everyone,I'm currently trying to work with the NUCLEO-U386RG-Q development board.When I try to download the latest available MCU package (1.2.0) via STM32CubeIDE, I only get an error message stating that the requested MCU package is not available. This is obviously incorrect, as I can manually download and install it from the ST website. When I try to install one of the previous releases, the connection is established, but the download is extremely slow for some reason.