STM32 MCUs Software development tools

Hi,every time I download the code from CubeIDE into the micro, a seemingly random file (every time a different one) opens up in the editor. More specifically it opens in the split editor area that is active when I press Run (i.e. left window or right window in the editor screenshot below).Furthermore it opens only system/library source and header files like stm32l4xx_ll_adc.h, stm32l4xx_hal_tim_ex.c and stm32l4xx_hal_gpio.c and not the source files I created.Any idea why and how to prevent it from doing that?Thank you 

Hello Community, I have tried to configure TIM8 in CubeMX (Version 6.15.0) with device STM32N645B0 (VFGBA198). But TIM8 is not available in the Timers Group. All other timers are displayed, only TIM8 is missing. Also trying to activate TIM8 over the pin directly does not work. Any ideas? Best regards Thomas

Hi, im using stm32h745bit6 MCU, when im pressing reset button only M7 core is reseting and M4 core is stucking in an reset handler itself, what to do an reset. since if a use system reset also same only.can u someone suggest what to do for this reset handler issues.  regards,srinath

I am using Keil MDK Pro ver 5.38, Compiler ver 6.19, Middleware 8.0.0 (Also tried lower and upper versions). I am using STM32F746NGH6 MCU . I generated a USB FS Host only code in CubeMX. Exported to keil. Compiled the code and got zero errors and zero warningsHowever, after adding RTX5 and middleware components to keil project, the error of MX_Device.h file not found. Ther is no clear solution for this problem on unternet anywhere. Why STM32CubeMX is not generating this file? What is the way forward? 

Hi I am trying to configure a project in Vs code.1) Created/Generated a project using STM32CubeMX.2) in vs code extensions added3) by using open folder latest created project loaded4) on pop-up Debug option selected5) Then when it comes to device selection unable to find STM32H7 Series, eval board numbers in the list.Note : STMCUFinder path, cubemx paths configured . please check below images  

Split from https://community.st.com/t5/stm32-mcus-boards-and-hardware/st-link-contolled-by-python/td-p/677553Could you please give an update on this?I just ran "help python" within arm-none-eabi-gdb (IDE version 1.17.0) and got:(gdb) help python python, py Evaluate a Python command. Python scripting is not supported in this copy of GDB. This command is only a placeholder.It would be nice to know if this will be implemented at some point.My use case is similar to the OP - collection of target execution history within a unit test environment. I current have a Python script that controls the GDB server and runs the client with a command file, but it would be easier to use Python directly.Edited to correct IDE version.

Not sure if this belongs in STM32CubeMX or STM32CubeIDE for VSCode.I have a CMake project generated from CubeMX.When I build within VSCode IDE with the STM32 Extension I get several nocent warnings I would like to eliminate.Some of these are deep in the HAL and/or the generated code produced by CubeMX.ex:warning: declaration of 'hrtc' shadows a global declaration warning: cast increases required alignment of target type [-Wcast-align] etc... I tried several modifications to my top level CMakeLists.txt suggested by AI to suppress these warnings but NONE work.I know this line:include("cmake/gcc-arm-none-eabi.cmake")brings in all the gcc compile options but I don't want to modify this file as it gets regenerated every time I do a CubeMX "GENERATE CODE". Things I have tried are:set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-shadow") target_compile_options(my_target PRIVATE -Wno-shadow) set(MCU_GCC_FLAGS "${MCU_GCC_FLAGS} -Wno-shadow") add_compile_options(${MCU_GCC_FLAGS}) add_compile_o

Running on UbuntuSTM32CubeIDEVersion: 1.13.2Build: 18220_20230914_1601 (UTC).Fresh installation but just getting blank page saying "Target selection: STM32 target or STM32Cube example selection is required".I've:1. Checked for target selector device database updates2. Checked for Embedded Software Packages Updates3. Managed Embedded Software Packages and installed latest package for STMG0Rebooted etc, but still getting this message and can't get past.PS: STM32CubeIDE runs fine on Windows 11 connected to target board (Nucleo-64 G071RB)

HiRecently, when I import an LWIP example project from MDK to CubeIDE, I get the following note message::     "note: the message above does not take linker garbage collection into account"I have 2 questions against these notes:1. Do these notes have any negative affects on generatiing correct binary of the project ?2. If they don't have any negative affects, then how to avoid these annoying messages ?ThanksChao

Is there any way to automatically build the toolchain, even though the standard library is no longer recommended?

Edited by a ST moderator to translate the content. Please in next time use English in this community. Thank you for your understanding.   大家好， 我在安装LED时遇到了一个障碍，希望能得到大家的帮助。 · 问题描述：我从官网成功下载了安装包https://www.st.com/zh/development-tools/stm32cubeide.html，但尝试解压时系统提示“无法打开”。 · 我已尝试的步骤：1. 使用不同的解压工具（如 WinRAR 和 7-Zip）进行解压，问题依旧。2. 重新下载了两次压缩包，确保下载过程完整无中断。· 我的环境：操作系统是 Windows 10。 想请教各位： · 有没有朋友遇到过类似的情况？这可能是文件损坏还是环境兼容性问题？· 除了官网，是否有其他可靠的下载渠道或镜像站点？· 或者，是否有跳过解压直接安装的方法？ 任何指点都将对我有巨大帮助！非常感谢！ 标签（建议选择）：安装问题,求助, 文件损坏, Windows   Translation; by Google translator: Hello everyone, I'm running into a problem while installing the LEDs and would appreciate any help. · Problem Description: I successfully downloaded the installation package from the official website (https://www.st.com/zh/development-tools/stm32cubeide.html), but when I try to unzip it, the system prompts "Cannot Open." · Steps I've Tried: 1. Using different decompression tools (such as WinRAR and 7-Zip) to unzip the package, but the problem

I want to use STM32FC091 USART1 for a MODBUS communication on RS485 with DMA. The STM32FC091 USART1 has a full implementation and supports using DMA, receiver timeout interrupt, Modbus communication and driver enable features.I just successfully tested USART1 with DMA on RS485 with my NUCLEO-C092RC. With STM32CubeMX I set USART1 in asynchronous mode and it properly works. But when I try to select Modbus Communication mode for USART1 I get:Driver Enable (DE) for RS485 features is not available. And only a USART1_TX GPIO Setting is available, all the others are not.How to set USART1 for Modbus Communication?  

Hello,I'm using STM32G474QET6 with HSI (16Mhz).When not using DMA - the UART is working.With DMA I'm having 2 issues:When sending 3 bytes, only 2 bytes sends.DMA is not receiving anything (UART Rx) - CNDTR remains 3 and not data is written to the buffer (data.bytes[1]).The 2nd issue is the main issue. That is my UART init func: LL_USART_InitTypeDef usart_init_struct; USART1->CR1 &= ~USART_CR1_UE; // Disable USART 1. // USART 1 clock enable. LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_USART1); usart_init_struct.BaudRate = 19200; usart_init_struct.DataWidth = LL_USART_DATAWIDTH_8B; usart_init_struct.HardwareFlowControl = LL_USART_HWCONTROL_NONE; usart_init_struct.OverSampling = LL_USART_OVERSAMPLING_16; usart_init_struct.Parity = LL_USART_PARITY_EVEN; usart_init_struct.PrescalerValue = LL_USART_PRESCALER_DIV1; usart_init_struct.StopBits = LL_USART_STOPBITS_1; usart_init_struct.TransferDirection = LL_USART_DIRECTION_TX_RX; LL_US

I just bought discovery kit for STM32MP1 and I have connected power and JTAG USB.When I am clicking on connect, I am getting below error. Can you please tell how to connect? 

Not sure if this belongs in CubeMX or STM32 code for VS.I have a CMAKE project generated from CubeMX.When I build within VS Code IDE with the STM32 Extension I get several nocent warnings I would like to eliminate.Some of these are deep in the HAL and/or the generated code produced by CubeMX.ex:warning: declaration of 'hrtc' shadows a global declarationwarning: cast increases required alignment of target type [-Wcast-align]etc.I tried several modifications to my top level CMakeLists.txt suggested by AI to suppress these warnings but NONE work.I know this line:include("cmake/gcc-arm-none-eabi.cmake")brings in all the gcc compile options but I don't want to modify this file as it gets regenerated every time I do a CubeMX "GENERATE CODE" Things I have tried are:set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wno-shadow")target_compile_options(my_target PRIVATE -Wno-shadow)set(MCU_GCC_FLAGS "${MCU_GCC_FLAGS} -Wno-shadow")add_compile_options(${MCU_GCC_FLAGS})add_compile_options(-Wno-shadow)set(CM

Hello. I'm using STM32CubeMX with STM32f777ZI MCU to create a CMAKE project.The generated linker script file (STM32F777XX_FLASH.ld) has a really simple definition of RAM memory regions:/* Specify the memory areas */MEMORY{RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 512KFLASH (rx) : ORIGIN = 0x8000000, LENGTH = 2048K}There is no separation of SRAM1, SRAM2, DTCM and etc. For example - I want to enable cache in SRAM1 and I need to have a proper section definitons. I want to use in my code something like:__attribute__((aligned(sizeof(uint32_t)), section ... and etc.Is it possible to force STM32CubeMX to generate more detailed RAM segmentation for F7 cores?

I created an external flash STLDR file for my board, with STM32H750VB chip and W25Q64 QSPI FLASH. After copying the STLDR file to the cubeprographer directory, it can perform normal external flash read/write and sector erase functions. However, when selecting full chip erase, the cubeprographer prompts me "please select external loader before performing external full chip erase". But I am sure that my code contains the correct int MassErase (void) function, and I used the readelf command in Ubuntu environment to read the STLDR file I created, which also includes the MassErase function. But it seems that this function cannot be correctly detected by the cubeprographer. How can I locate the cause and solve this problem?Wishing you peace

STM32H5 USB Custom HID CubeMX issue.When setting parameter "UX_DEVICE_CLASS_HID_EVENT_BUFFER_LENGTH" to 64 in CubeMX, the corresponding define in the "ux_user.h" file is commented out.Setting this parameter to any other valid value (between 0 and 255, excluding 64) in CubeMX generates an uncommented define.I presume CubeMX is doing this because it assumes the default value from USBX is 64 bytes.In fact a default value is provided by usbx in "ux_device_class_hid.h", but this value is actually 32 bytes.Thus, using out of the box CubeMX generated code when "UX_DEVICE_CLASS_HID_EVENT_BUFFER_LENGTH" set to 64 results in very nasty memory overwrites in the USBX device structures that subsequently result in hard fault.Please update CubeMX to not comment out this define when set to 64.Thank you.    

Hello ST team,I’m developing on a STM32H755BITx dual-core (Cortex-M7 / M4) using STM32CubeIDE and STM32CubeH7 HAL.I have a custom bootloader that starts the user application located at 0x08040000 (M7 app) and 0x08100000 (M4 app).ContextBootloader and application are both generated with STM32CubeIDE.The bootloader runs correctly and can jump to the application.Everything works fine when the application is compiled using STM32CubeH7 v1.12.0.But when I rebuild the exact same application using STM32CubeH7 v1.12.1, the app starts but hangs — no LED toggling, no interrupts, no SysTick activity.ConfigurationMCU: STM32H755BITxIDE: STM32CubeIDE (latest version available)Bootloader base M7: 0x08000000Bootloader base M4: 0x08020000App M7 base: 0x08040000App M4 base: 0x08100000Dual-core synchronized via HSEMPower configuration macro used: USE_PWR_LDO_SUPPLYSymptomsWhen jumping to the app built with v1.12.1:The vector table and MSP are correct (checked with debugger).The app reaches main(), but HAL

 Help me with tcp lwip implemenation

Hello Forum,I've noticed a feature/bug/behaviour in CubeMX 6.15.0 that I'm unsure about so could do with some advice.  I've been configuring an STM32U5A9ZJT 144 pin MCU for a project I'm working on.  This has been an evolutionary process.  To make the point I'll just focus on two peripherals, LPUART1 which has already been configured and I2C3 that I want to add in and configure.I start with LPUART1 configured as follows:Which has pins assigned like this on the MCU:I then enable the previously disabled I2C3 peripheral - there's nothing to say it conflicts with anything.  This results in I2C3 looking like:Having done this CubeMX silently reconfigured the LPUART1 pins.  thus:So the question is: "Is this normal?" If so I've never noticed before. It seems odd to me as I could have had a physical board made with the LPUART1 pins setup in the initial config.  Adding the I2C3 peripheral breaks LPUART1.Any thoughts/advice much appreciated.DD   &

Dear ST Support Team, I hope this message finds you well. I am currently working with the STM32U575ZIT6QU Nucleo board and would like to request a assistance in obtaining a sample bootloader application for this device. Goal is to ensure a successful boot-up sequence where the bootloader initializes correctly and subsequently launches a sample application.To clarify the requirements:We are not using secure boot or image signing; verification is not required for now not needed, but good to haveNeed a basic bootloader that can boot and transition into a sample application reliably.The sample application should demonstrate that the bootloader has successfully handed over control.Could you kindly provide:A reference bootloader project compatible with STM32U575ZIT6QU.A sample application that can be used to validate the bootloader handoff.Any documentation or guidelines that would assist in integrating and testing this setup.Your support in helping us get started with this boot-up

We have received new STM32H755ZI-Q board recently from STM, When we connect try to flash through STMCubeIde ST_link is not detecting and saying target not found. but in device manager the device is showing. below is error snippet Error in final launch sequence: Failed to start GDB server Failed to start GDB server Error in initializing ST-LINK device. Reason: (4) No device found on target.

Hi,The Build Analyzer extension in VSCode consistently crashes when I attempt to open or analyze medium-sized projects. The IDE itself not responsive anymore and the Build Analyzer crash unexpectedly.Steps to Reproduce:Open VS Code STM32Cube Build Analyzer (extension v1.0.2)Load elf file into STM32Cube Build Analyzer Observe the crash extension and freeze IDEExpected Behavior:The Build Analyzer should open and display memory and code size statistics without crashing.Actual Behavior:The Build Analyzer crashes or fails to load, making it unusable for project analysis.Additional Info:No error message is shownIDE logs do not indicate a specific causeIssue is reproducible across multiple similar projectsRegardsUwe

Hi everyone,  can anyone provide total DCMIPP camera interface STM32CubeMX    .ioc file therefore I can create a project and My applications. Please help me to implement the B-CAMS-IMX camera.I also try with BSP drivers that are available in STM32N6570_discovery_bus.c and .h , STM32N6570_discovery.c and .h file but in IMX335.c file I am unable to read device ID properly.So, please provide proper DCMIPP camera interface STM32CubeMX .ioc Thankyou.