STM32CubeIDE (MCUs)

in default situation, you could not call c++ function in C file.  So the main.c  is not suitable file in C++ project.   if user choose C++ project,the generated main.c ,stm32h7xx_it.c should sufixed with .cpp.

Hi everyone,I’m working with STM32L010K4T6, which is based on the ARM Cortex-M0+ core.I’d like to use FFT (Fast Fourier Transform) functions in my project, preferably within STM32CubeIDE.However, I noticed that the CMSIS-DSP library (which provides FFT functions) seems to have limited or no direct support for the L0 series inside CubeIDE.My questions are:Is it possible to add and use the FFT / CMSIS-DSP library with STM32L0 series MCUs like STM32L010K4T6?If yes, what is the recommended way to integrate it in STM32CubeIDE (manual CMSIS-DSP source import, or any ready package)?Are there any performance or memory constraints I should be aware of when running FFT on Cortex-M0+?Thank you in advance for any guidance!Best regards,Burak

Hi, I tried to build my project but I faced these errors :--------------------------------------------------------------------------------------------------------------------------------------------------C:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/bin/ld.exe: C:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard\libc_nano.a(libc_a-closer.o): in function `_close_r':(.text._close_r+0xc): warning: _close is not implemented and will always failC:/ST/STM32CubeIDE_1.12.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_1.1.0.202305231506/tools/bin/../lib/gcc/arm-none-eabi/11.3.1/../../../../arm-none-eab

I'm trying to track down a memory corruption bug in my code. I can setup a Watchpoint for a specific variable (Expression to watch: *(uint32_t*)0x20024840), and get the debugger to stop at a breakpoint whenever the variable is written to (good!).However, my problem is that 99% of the time, it's a legitimate/intended write, and I'd like it to NOT break at those locations so I can focus on the problem area.I've tried using the "Conditon:" field in the breakpoint property in 3 different ways:1) Ignore breakpoint if at a specific address:  $pc != 0x80201cc2) Ignore the breakpoint if in a specific function:  !$_is_in_function("my_func")3) Ignore the breakpoint if the value being written to the variable is within a range:  *(uint32_t*)0x20024840<3000||*(uint32_t*)0x20024840>4000In all 3 cases, it seems to have no filtering at all. I hit all the breakpoints any time the variable is written to no matter what I write on the "Conditon:" box. Is my syntax wrong? Do I need to

Hello,I’m using an STM32F429I-Discovery board with an MT9M001 camera module, trying to display the camera image on the board’s built-in LCD.However, I found that the following pins conflict between the DCMI and LTDC functions (please correct me if I misread the pin mapping):PA4: DCMI_HSYNC vs LTDC_VSYNCPA6: DCMI_PIXCLK vs LTDC_G2PC7: DCMI_D1 vs LTDC_G6PB8: I2C1_SCL vs LTDC_B6PB9: I2C1_SDA vs LTDC_B7In this situation, what is the typical way to handle such pin conflicts?Would it be necessary to change the board or the camera module?Any advice would be greatly appreciated.Thank you in advance.

Hello,when enabling DMA for a Timer channel in PWM mode, the transfer direction is set to Memory to Peripheral.This s very questionnable.Is it a deliberate choice or a bug?It does not make sense to select Peripheral to Memory for the DMA channel as it is used to wrtie to the device.I fell in the trap several time, wasting time to look up for an issue in my code...Very boring.STM32 device is STM32F429, CubeIDE version 1.19.0 (same problem with all versions since I started using CubeIDE a couple of years before.) 

Post edited by ST moderator to be inline with the community rules for the code sharing. In next time please use </> button to paste your code. Please read this post: How to insert source code. Hello to all, I'm coding a simple project for STM32WL55IC7 MCU, for the NUCLEO-WL55JC2 board. I didn't use the BSP for the board, in other words i didn't select the NUCLEO board option, but I started the project using the MCU. The Project name is STM32WL55IC7_foo. The CubeIDE build the following 3 projects: 1. STM32WL55IC7_foo  2. STM32WL55IC7_foo_CM0PLUS (the code for Cortex M0+ code) 3. STM32WL55IC7_foo_CM4 (the code for Cortex M4 code) When I try to compile the project, while the CM4 core code is compiled without any error, the code for the M0PLUS core issued errors, on the following snippet during the EXTI interrupt initialization: /* EXTI interrupt init*/ HAL_NVIC_SetPriority(EXTI1_0_IRQn, 1, 0); HAL_NVIC_EnableIRQ(EXTI1_0_IRQn); HAL_NVIC_SetPriority(EXTI15_4_IRQn, 1, 0); H

I am trying to flash and debug on CM4 on stm32 H755 ZI-Q board.1. Firstly i tried debugging CM7 , with debug configurations --> Connecting under reset and halt all cores.2. Then i tried debugging CM4, with debug configuration -->None(no reset)3. Also added .elf files in startup while debugging CM7.4. I separately debugged cm7 and then cm4, but got only cm7 prints output.5. So then i tried in other way,I launch the group debug, adding cm4 and cm7 both elf files,, still the cm7 i could able to see prints,, cm4 no prints.. basically, I think cm4 is not able to get up from stop mode.So, provide me solution 1.How to run cm4 independently? If this is not possible,  2. How to run the code written in m4, along with m7 in stm32 h755 zi-q series board.

Hi! I have a board based on STM32U585CIU, and I'm trying to enable a USB CDC on it. The problem is: when I generate a project in CubeMX for MDK-ARM, the code I've attached works fine, USB CDC device is being recognized by PC, and I can see messages via COM port. However, once I generate it for CubeIDE or Makefile, it just goes to hard fault in MX_USBX_Device_Init. Considering it works in Keil uVision, seems like hardware is completely okay, so there is something in the difference between gcc-arm and arm compiler. 

I would like to ask how to program multiple STM32 MCUs connected in a JTAG daisy chain individually, and how to disable automatic program execution after flashing. I would like to achive the following goals simultaneously:Program each STM32 MCU individually while connected in a daisy-chain configuration.Prevent the program from automatically running after the flashing process.In my current setup, I have successfully programmed two STM32L476RG devices individually through a J-Link Base Compact using STM32CubeIDE by configuring the Debug Configuration settings (see the attached image for details).However, after programing, the application code starts running automatically. When using STM32CubeProgrammer, unchecking the "Run after programming" option successfully disables the automatic execution.However, I could not find a way to specify individual targets (e.g., by IR length or other parameters) for daisy-chained devices in STM32CubeProgrammer, either in the GUI or CLI versions

Hello,I downloaded the STM32CUBE-IDE 1.19 for linux RPM today.I use fedora43 on x86. It failed to install:sh-5.3# sudo /bin/shsh-5.3# ./st-stm32cubeide_1.19.0_25607_20250703_0907_amd64.rpm_bundle.shCreating directory makeself_dir_ZeOUueVerifying archive integrity... 100% All good.Uncompressing STM32CubeIDE installer 100% grep: warning: stray \ before /STMicroelectronics Software License AgreementSLA0048 Rev4/March 2018Please indicate your acceptance or NON-acceptance by selecting "I ACCEPT" or "I DO NOT ACCEPT" as indicated below in the media.BY INSTALLING COPYING, DOWNLOADING, ACCESSING OR OTHERWISE USING THIS SOFTWARE PACKAGE OR ANY PART THEREOF (AND THE RELATEDDOCUMENTATION) FROM STMICROELECTRONICS INTERNATIONAL N.V, SWISS BRANCH AND/OR ITS AFFILIATED COMPANIES (STMICROELECTRONICS), THE RECIPIENT, ON BEHALF OF HIMSELF OR HERSELF, OR ON BEHALF OF ANY ENTITY BY WHICH SUCH RECIPIENT IS EMPLOYED AND/OR ENGAGED AGREES TO BE BOUND BY THIS SOFTWARE PACKAGE LICENSE AGREEMENT.Under STMi

Colleagues, I’ve got a nitpick question.Where’s the best place to define USE_FULL_ASSERT ? It can be defined as a preprocessor symbol. Or, it can be #defined in the stm32xxx_hal_conf.h file. Or, is there a setting in the .ioc file?The stm32g4xx_hal_conf.h which STM32cubeIDE had generated for me has this block:/** * @brief Uncomment the line below to expanse the "assert_param" macro in the * HAL drivers code */ /* #define USE_FULL_ASSERT 1U */But it’s not in the the USER CODE block. I’m concerned that the automatic code generator would restore the #define USE_FULL_ASSERT back to the commented out line next time it re-generates stm32g4xx_hal_conf.h .Best regards,- Nick

Hello everyone,I’m planning to buy a Surface Laptop 7 with a Qualcomm processor. I use STM32CubeIDE frequently for my work, and I’m wondering if STM32CubeIDE and the ST-Link driver are compatible with an ARM64-based laptop.Many thanks,

Has there been any confirmation if there are any compatibility issues with running the STM32CubeIDE on the Qualcomm Snapdragon X Series based Windows 11 Hardware?

The debugger is getting stuck on a random line about 350 lines into main(). There is nothing particular about this line of source code except its location, because if I comment out that line it just stops on the next one, and if I add a line it stops earlier. When the debugger is not active, the source runs just fine without stopping in that area. I have deleted all breakpoints and watchpoints. I have set the optimizations to "off". When the debugger is stuck on that line, its status is "running."This is my first time debugging this project after converting from TrueStudio. I may need to switch back if I can't find anything else to try. Any suggestions?

Has anyone had any success getting this to install into STM32CubeIDE?I get the following error Cannot complete the install because one or more required items could not be found. Software being installed: Assist AI 1.0.6.202509261754 (com.github.gradusnikov.eclipse.assistai.feature.group 1.0.6.202509261754) Missing requirement: Assist AI 1.0.6.202509261754 (com.github.gradusnikov.eclipse.plugin.assistai.main 1.0.6.202509261754) requires 'osgi.bundle; org.apache.commons.lang3 3.17.0' but it could not be found Cannot satisfy dependency: From: Assist AI 1.0.6.202509261754 (com.github.gradusnikov.eclipse.assistai.feature.group 1.0.6.202509261754) To: org.eclipse.equinox.p2.iu; com.github.gradusnikov.eclipse.plugin.assistai.main [1.0.6.202509261754,1.0.6.202509261754]I've tried finding the offending org.apache.commons.lang3 (found at maven.apapche.org) and dropping in to my plugins folder but after stopping and restarting CubeIDE the plugin is not listed in the About-Installation Detail

So I'd been merrily using STM32CubeIDE all morning, doing the usual code-download-debug cycle with no problems at all.Then, after some code updates & successful build, it suddenly can't reach the GDB server: STMicroelectronics ST-LINK GDB server. Version 7.4.0Copyright (c) 2023, STMicroelectronics. All rights reserved.Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Number : 61234 Status Refresh Delay : 15s Verbose Mode : Disabled SWD Debug : Enabled InitWhile : EnabledFailed to bind to port 61234, error code -1: No errorFailure starting GDB server: TCP port 61234 not available.Shutting down...Exit. Several people seem to have had this recently; eg,https://community.st.com/t5/stm32cubeide-mcus/cubeide-1-18-cannot-detect-st-link-anymore/m-p/784313?search-action-id=49992011530&search-result-uid=784313https://community.st.com/t5/stm32cubeide-mcus/st-link-error-failed-to-bind-to-port-61235-failure-starting-swv/m-p/784642

I'm using the latest of STM32CubeIDE. to program my STM32H750VBT6 created by WeACT. I've created very simple program that consist of I2C from DS3231 RTC and simple counting with the code below HAL_GPIO_TogglePin(GPIOE, GPIO_PIN_3);statusrtc = HAL_I2C_Mem_Read(&hi2c2, DS3231_ADDRESS, 0x00, 1, get_time, 7, 1000);HAL_Delay(500);count1 = count1+3;HAL_Delay(100); The problem is, the count1 is not counting, but the count goes to statusrtc. I realize the statusrtc give the HAL status (like HAL_BUSY, HAL_TIMEOUT) after the counting is done (>256 because count1 is uint8_t). What actually going on with my device? Or it is the bug of STM32H7 in CubeIDE?    

Hello everyone I am new to the STM boards I had received my board today I had tried the basic LED toggle code and it is working fine but can someone please guide me to see the debug message on the code like I can see the printf statements how can I see those debug messages can someone please help me.

some time when I try to import an existing project in file system into workspace every thing looks to work properly it find the project show the project name in the list but when I clic finish it never show in workspace here my information using 1.19 release of cube ide on a windows 11 host  

Hi, I’m developing a voice-control system on ST’s STEVAL-STWINBX1 evaluation board. I’d like to build on the original “Dual-mode application with STM32Cube.AI and NanoEdge™ AI” by replacing the anomaly-detection function with a binary classifier based on IMP23ABSU microphone data (“xiaobei” vs. “other”). I also plan to replace the original USC model with a 10-class classification model trained on IMP23ABSU microphone data. The intended behavior is: when the MCU recognizes “xiaobei,” it should wake the USC model; otherwise, it should not.My NanoEdge™ AI binary model is already running—when I execute start neai_class, I can see the classification output. However, after “xiaobei” is detected, the USC model fails to wake up and the firmware even falls into HardFault_Handler in some cases. I’m not sure what’s going wrong. Could you please share suggestions? For example, after modifying the USC model parameters, which source files need to be updated so the new model is compatible with t

* board - STM32N6570-DK*  using STM Cube 1.19.0* Example - USBPD_SNK In the example USBPD_SNK it tell you to view the traces like this. * Run CubeMx Monitor and open trace tools I'm guessing this is something inside of STM32Cube ide.  Not STM32CubeMonitoring app* https://www.st.com/en/development-tools/stm32cubemonitor.html So i started the trace's like i normally would in STM32CubeIde but it doesn't seem to show anything in the trace output when i run the application.  They say to use STM32CubeMonitor but when i connect both ends to my computer i don't see any com's to select.   Currently i'm not entirely sure how to enable the traces, so any help would be greatly appreciate. 

While trying to launch a project, I get the following error:'Launching <Project Name>' has encountered a problem.Could not determine GDB version using command: arm-none-eabi-gdb --versionCould not determine GDB version using command: arm-none-eabi-gdb --versionarm-none-eabi-gdb: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory OS: Fedora Linux 42STM32CubeIDE version: 1.19.0 Although libncurses.so.5 is apparently a very old package, I have "ncurses-compat-libs", which should provide compatibility with the required package version. I can find it on /usr/lib/ but not on /usr/lib64/. 

Sometimes it works, sometimes it doesn't.When I try to open the IOC viewer either the IDE freezes or the view isn't rendered properly, as you can see below. This misbehavior breaks my working flow and makes me waste a lot of time. Any ideas?

* board - STM32N6570-DK*  using STM Cube 1.19.0* firmware v1.2.0Test projects* USBPD_SNK/USBPD_SRC So i'm trying to do PD with the STM32N6, but i can't seem to be able to test the example code from ST.  When i run USBPD_SNK, it just doesn't seem to work.  I get a weird no source available issue.  I thought it was because of ThreadX, but i tried VENC_USB and that example worked fine.  The USBPD_SRC also fails to work.  I don't know if this a STMCubeIDE problem or something weird with the specific PD usb examples.