STM32CubeIDE (MCUs)

Morning all,I'm really having some issues getting the latest CubeIDE (1.18.1) to work.This problem started when I was trying out some different processors for a new product (a CPU upgrade) - everytime I selected the new CPU and attempted to start a new project, I was told that it was missing an XML file and that no new project could be started without it.After trying/retrying several times with searches for the XML file turning up nothing - I came to the conclusion that I needed a re-install of the tools as this would give me the XML file I needed for the new board.I downloaded and installed the latest 1.18.1. Everytime I started CubeIDE, I would get a popup window after the splash screen  saying this or that log would hold the details of what was going wrong. Reading the log file showed that there was no swt-win32 in the java library path. The path listed in the log is pointing to a .DLL, which exists at the location given.Assuming I had an old java install, I got and installed t

STM32CubeIDE 1.9.0 has been working fine, until tonite. I started it and after it asked which workspace it acted like it was loading but never went anywhere. I killed it, removed the .lock file and restarted and the same thing except it's now exiting. The .ide.log has this:2022-06-15 23:57:26,297 [INFO] PluginManager:213 - loadIPPluginJar : add gic 2022-06-15 23:57:26,301 [INFO] IPUIPlugin:75 - create IPUIPlugin 2022-06-15 23:57:26,301 [INFO] PluginManager:213 - loadIPPluginJar : add openamp 2022-06-15 23:57:26,624 [FATAL] Updater:297 - Updater called before beeing initialized 2022-06-15 23:57:26,784 [FATAL] Updater:297 - Updater called before beeing initialized 2022-06-15 23:57:26,795 [INFO] DbMcusAds:47 - JSON generation date=Thu Sep 30 02:55:09 EDT 2021 (1632984909247) 2022-06-15 23:57:26,795 [FATAL] Updater:297 - Updater called before beeing initialized... and it just keeps going. I tried re-installing but it just says "Nothing to install", prolly because it is installed.OS is Debi

Good evening,I’m reaching out to ask if anyone might be familiar with a solution to a hard fault issue we’re currently encountering.Here is the situation:We are using a custom-designed board that incorporates an STM32H7 microcontroller and external Flash memory from Winbond. All source code is stored in the external Flash. The code itself is relatively simple and primarily handles UART communication.While debugging with CubeIDE, we frequently encounter hard faults when using the Live Expression feature. The fault appears to be an alignment error.The debugger connection is via SWD using ST-Link. Interestingly, when debugging via JTAG using SEGGER’s J-Link, the hard fault does not occur—even when using Live Expression. However, in this case, the console displays a message saying “cannot read register map.”This leads me to believe that the occurrence of hard faults may be influenced by the debugging interface (SWD vs. JTAG).I would greatly appreciate it if anyone could share insights into

Bug Report: CubeMX Code Generation Error - Incorrect DMA Link in HAL_XSPI_MspInit Function Environment The software environment is STM32CubeIDEVersion: 1.19.0 Build: 25607_20250703_0907 (UTC)and the FW used is STM32CubeH7RS Firmware Package V1.2.0 / 05-February-2025. Problem Description When CubeMX generates theHAL_XSPI_MspInitfunction, it incorrectly linkshandle_HPDMA1_Channel0, which is the transmit (TX) DMA channel, to the receive (RX) pointerhdmarxof the XSPI handle. This causes manually modified code to be overwritten with the incorrect code every time the.iocfile is saved and the code is regenerated.Incorrectly Generated Code:__HAL_LINKDMA(hxspi, hdmarx, handle_HPDMA1_Channel0);Correct Code:__HAL_LINKDMA(hxspi, hdmatx, handle_HPDMA1_Channel0);Cause There is an error in the CubeMX code generation logic that incorrectly links the TX DMA channel to the RX pointer within theHAL_XSPI_MspInitfunction. Solution UtilizeUSER CODEblocks to protect manual

I'm trying to get semihosting to work under STM32CubeIDE with ST-LINK(OpenOCD) debugging.After being able to connect to the target (an STM32H503), I cannot step over the function initialise_monitor_handles()  (see source code). A lot of traps occur but I can't get into the real code to debug. (the lines in the main.c while loop).Bear with me but the code looks a bit like swiss cheese. Tried various reads, scanf etc. But at the moment I cannot get across the "initialise_monitor_handles();" call.

I'm using STM32f407 board with Cubeide. When load new code, I want to work code after pressing reset button.How can I set it in STM32CubeIde.Thank's

I got this (since I have multiple STLINKs attached):Where do I specify the serial number in the command line (of the gdb server) ?

I am writing some firmware for a device with an alpha-numeric display. The display language must be changable. For most languages, this means using characters outside the A-Z range. UTF-8 covers most of the necessary characters.In the project properties, I found this setting, and naively thought that the UTF-8 selection included the actual compiler:Well, obviously not, as it is GCC that needs to know that the character set is to be UTF-8. The codesprintf(pString, "Français");is translated tosprintf(pString, "Français"); (It might not be super-visible, but the ç in Français is a c with a cedilla, which has the UTF-8 code 0xE7.)I tried using the flags -finput-charset=utf-8 and -fexec-charset=utf-8 in an attempt to tweak GCC to use UTF-8 for strings and characters, but that didn't make a difference. Also, I have a hunch that these flags only work for C++, but I'm not sure.Is what I'm trying to do even possible?I do have the option to replace ç with \xE7, but with

I'm using the STM32G474RE with STM32CubeIDE - Version: 1.19.0, and I encountered a strange issue. I'm not sure whether to call it an error, as it doesn't technically throw any errors—but it's unusual.When I create a new project and open the .ioc configuration, the NVIC section (which usually shows 7-8 entries for code generation) is completely empty. This behavior seems abnormal, and I'm unsure what's causing it.Could someone please help me understand what's going on or how to resolve this?

I'm trying out semihosting with openocd in STM32CubeIDE.  For this purpose I added the call initialise_monitor_handles(); in main.c as the second call after HAL_Init(); I have STLINK(gdb server) configured. The program goes into that call (initialise_monitor_handles) but never returns. Trying OpenOCD gives another error:Open On-Chip Debugger 0.12.0+dev-00623-g0ba753ca7 (2025-04-30-14:20) [https://github.com/STMicroelectronics/OpenOCD] Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : STLINK V2J46M33 (API v2) VID:PID 0483:374B Info : Target voltage: 3.224068 Info : Unable to match requested speed 8000 kHz, using 4000 kHz Info : Unable to match requested speed 8000 kHz, using 4000 kHz Info : clock speed 4000 kHz Info : stlink_dap_op_connect(connect) Info : SWD DPIDR 0x6ba02477 Info : [STM32H503CBTx.ap0] Examination

Hello,I am experiencing a consistent connection issue with my development setup:Hardware/Software Configuration:MCU: STM32 (exact model: STM32G474VET6)Debugger: STLINK-V3IDE: STM32CubeIDEProgrammer: STM32CubeProgrammerOperating System: WindowTarget board : Custom boardart of custom board schematics : Problem Description:When connecting my STLINK-V3 to STM32CubeIDE, the IDE fails to detect or connect to the target device. It typically shows error messages like “No ST-LINK detected” or “No target found.”However, when I use STM32CubeProgrammer, the STLINK-V3 is detected and connects to my target MCU without any issues. All programming and memory read functions work perfectly.While many boards face connection issues with STLINK-V3 in STM32CubeIDE, some boards succeed to be connected.Questions:Has anyone experienced similar issues where STM32CubeIDE fails but CubeProgrammer succeeds with STLINK-V3?Are there recent changes in CubeIDE or driver packages that could explain this?Any additi

Hi everyone,I am a little desperate due to my problem in debugging my programs on my newly purchased STM32N6570-DK discovery board. I am running all the software on my Macbook Pro 2024 with M4 Max processor with macOS Sequoia 15.6.1.I have been using STM32 Cube IDE version 1.19 and have successfully managed to debug a binary. It was the classic blink example. It seems to be working fine in the Cube IDE but not when I am trying to setup a debug target in my CLion environment. I have been comparing all of the parameters to the debugger between Cube IDE and CLion and tried using exact same. I have also tried using the separate CLT package for the programmer and debugger from ST.It always results in a timeout and releasing debugger with a disconnection and the following message:Error in initializing ST-LINK device.Reason: Target not halted.GDB Server stopped, exit code 9Anyone having ideas?

I'm trying to program an STM32H503 target attached to STM32CubeIDE through the SWD header of a Nucleo-F411RE. It fails to connect (see log below):Open On-Chip Debugger 0.12.0+dev-00623-g0ba753ca7 (2025-04-30-14:20) [https://github.com/STMicroelectronics/OpenOCD] Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : STLINK V2J46M33 (API v2) VID:PID 0483:374B Info : Target voltage: 3.231434 Info : Unable to match requested speed 8000 kHz, using 4000 kHz Info : Unable to match requested speed 8000 kHz, using 4000 kHz Info : clock speed 4000 kHz Info : stlink_dap_op_connect(connect) Info : SWD DPIDR 0x6ba02477 Info : [STM32H503CBTx.ap0] Examination succeed Info : [STM32H503CBTx.cpu] Cortex-M33 r0p4 processor detected Info : [STM32H503CBTx.cpu] target has 8 breakpoints, 4 watchpoints STM32H503CBTx.cpu in Non-Secure state STM32H503CBTx TrustZone di

I'm trying to run a Debug launch configuration in STM32CubeIDE but I'm getting an error:Console: Open On-Chip Debugger 0.12.0+dev-00623-g0ba753ca7 (2025-04-30-14:20) [https://github.com/STMicroelectronics/OpenOCD]Licensed under GNU GPL v2For bug reports, readhttp://openocd.org/doc/doxygen/bugs.htmlInfo : Listening on port 6666 for tcl connectionsInfo : Listening on port 4444 for telnet connectionsInfo : STLINK V2J46S7 (API v2) VID:PID 0483:3748Info : Target voltage: 2.716832Error: init mode failed (unable to connect to the target)Error message of STM32CubeIDE (1.19.0)  popping up:Error in final launch sequence:Failed to execute MI command:target extended-remote localhost:3333Error message from debugger back end:localhost:3333: Operation timed out.Failed to execute MI command:target extended-remote localhost:3333Error message from debugger back end:localhost:3333: Operation timed out.localhost:3333: Operation timed out.Any ideas what's going wrong? --Christoph

Hello there : )This may be resolved but I cannot find the answer in either Segger's or ST's forum.I have set up a fresh target (NUCLEO-G491RE) via ST-LINK with expected result.When I move SRAM1 -> address 0 it is changed in the memory view.Now, with a J-LINK it never changes, (not after refreshing the memory view either). I have changed the OB to initially put the main FLASH at address 0 (BOOT0 pin will not be valid later).As ST-LINK connects this is confirmed as SYSCFG.MEMRMP is 0x1, and changes to 0x3 correctly.The J-LINK does however starts with 0x0 and changes to 0x3 as expected.In both cases the SYSCFG.CFGR1 changes from 0x0 to 0x7C... before so the RCC does it's work. Any ideas?BTW, the J-LINK Console log does not mention about any of this, no script are involved. 

I'm working on a project to connect multiple stm32-boards using the CAN-bus.So I opened two instances of the ide and connected 2 boards with 2 st-links.When I tried to setup the 2nd st-link for debug, I received an unknown error from the GDB-server.Please help, as I don't want to use multiple computers for that project.RegardsAndreas

HelloI just want to know how to properly uninstall a previous version of the CubeIDE in linux. Do I just delete the folder?

Hello STM32 developers,I use STM32CubeIDE 1.18.1When creating new workspaces, I import my preferences.The colors get right, but the font remain wrong (Consolas)For this to correct, the fastest method seems to copy over.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclipse.ui.workbench.prefsfrom another workspace instead of going through the preferencesIs it possible to add the fonts to be exported and imported in a future release?Or is there another way to do this?

Hi Everyone,I've been working on the N6 kit for a while. Initially, I was able to debug it, albeit with difficulty. However, in my latest attempts, I haven't been able to. I've updated Stlink, the IDE, and CubeProgrammer. I continue to receive the error below. I'm following all the instructions in the Readme. Also, as I mentioned, I've been able to debug it without any problems for about a month. I know that debugging MCUs with external flash drives requires some special considerations. However, when they suddenly stop working after booting, it really makes the development process quite tedious. What should I check? I've eliminated things like the USB cable.BR. Onur  

Hello,I bought a NUCLEO-F401RE and the STEVAL-IOM001V1 evaluation board to experiment with the IO-Link protocol. I’m having trouble importing STSW-IOM001 into my project. According to the documentation, it’s supposed to be opened in SW4STM32, which is an older tool. I’ve followed all the instructions I could find for importing it into STM32CubeIDE, but nothing has worked. Do you have any suggestions?

Hello, I have configured a project with CubeMX using a NUCLEO-H7S3L8 with an STM32H7S3L8 MCU.Although everything works, I first need to flash the bootloader and then flash the application.A reset is required to start the app.Using the debugger, I confirmed that the app is running from an external flash drive (PC with a 0x9000000 value).I'm missing the "Build All" option, which allows you to build all three projects simultaneously and start the application after flashing without having to press the reset button. I think so.This is the first time I've used a bootflash MCU, and I'm sure I've missed something.I've attached the IOC file, which only shows a blinking yellow LED.Why do I need to reset the board to start the application? Update 1:There's a "Build All" button in the toolbar that performs this task. But it does this for all projects in the workspace.I usually have several projects in one workspace, so I don't need to re-adjust my entire workspace, such as the dark theme, col

How to add a python script to introduce build errors during compilation process when some of the GPIO settings are modified from the below ones. PFB the python scriptimport sys import re # ‌‌ Define the locked GPIO settings here LOCKED_SETTINGS = { # Format: "PinName.Property": "ExpectedValue" "PA0.GPIO_Label": "Button1", "PA0.GPIO_Mode": "GPIO_MODE_INPUT", "PA0.GPIO_PuPd": "GPIO_NOPULL", "PB5.GPIO_Label": "LED1", "PB5.GPIO_Mode": "GPIO_MODE_OUTPUT_PP", "PB5.GPIO_PuPd": "GPIO_NOPULL", "PB5.GPIO_Speed": "GPIO_SPEED_FREQ_LOW", } def check_ioc_file(ioc_path): try: with open(ioc_path, "r", encoding="utf-8") as f: lines = f.readlines() except FileNotFoundError: print(f"‌‌ ERROR: File not found: {ioc_path}") sys.exit(1) errors = [] for key, expected_value in LOCKED_SETTINGS.items(): found = False for line in lines: if line.startswith(key + "="): found = True actual_value = line.strip().split("=")[1] if actual_value != expected_value: errors.append(f"{key} changed! Expected '{expected_value

Hi, I use lasted available library’s and software Cube IDE and stm32f103 mcu. I create clear project with minimum required parameters for use usb MSD or COM, with using USB HAL, So I compile it and connect usb, device recognised and OS propose format it, all works correctly.So the problem: if in settings project optimisation select any type not include “none” after programing device not recognised by OS if I connect it by usb. No meter what optimization level i select. In debug mode initialisation comes without return error, (OS still not recognized usb device)

Initially I downloaded the Debian version of the IDE. Now I am using the generic Linux version. In both versions I could build the project, but in neither one of them could I run the program. I kept getting the error: Could not determine GDB version.I tried to see where is the cross-compiler in use: Project -> Properties -> C/C++ Build -> Environment. Here the PATH variable is different from the system's PATH variable, having the following value:   /opt/st/stm32cubeide_1.17.0/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.linux64_1.1.0.202410170702/tools/bin:/opt/st/stm32cubeide_1.17.0/plugins/com.st.stm32cube.ide.mcu.externaltools.make.linux64_2.2.0.202409170845/tools/bin:/home/daniello92/.local/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin:/home/daniello92/.dotnet/tools:/snap/bin   I supposed that the cross-compiler is taken from the PATH, so I went ahead and

Hello, When using I2S2 with DMA transmit, the auto-generated stm32f7xx_hal_msp.c does not includePeriphClkInitStruct.PeriphClockSelection = RCC_PERIPHCLK_I2S inside HAL_I2S_MspInit().As a result, after calling HAL_I2S_Transmit_DMA() no DMA interrupts/callbacks occur.As a workaround, I manually added the snippet in the user code section. Question:Is this intended (by design) or something wrong with STM32CubeIDE?For an I2S setup, should RCC_PERIPHCLK_I2S be auto-generated at an appropriate place?Or should it be added manually?Also, I may be missing a recommended setting/order, so if there’s an official way to ensure RCC_PERIPHCLK_I2S is applied, I’d appreciate guidance.Environment:    MCU/Board: STM32F767ZI / NUCLEO-F767ZI    STM32CubeIDE: 1.19.0