1. Limitations
| ID | Summary |
|---|---|
| Authentication issue | If you have encountered an authentication problem while using STM32CubeIDE, don't worry. You simply need to set your connection parameters. For more details see link below: https://community.st.com/t5/stm32-mcus/how-to-set-the-network-connection-parameters-for-stm32cubeide/ta-p/585694 |
| 133183 | Unable to debug using FreeRTOS aware with a J-LINK Ultra+ in STM32CubeIDE 1.10.1 |
| 138771 | To start debugging in the NS zone when the product status is TZ-Closed for the STM32H5 using ST-Link GDBServer, add the following script to "Run Commands" in the debugging configuration.
For the "Reset & Restart" button to work: - Add the same script - Select "None" as the type. |
| 143485 | Post build commands are restored by using one of the following two options :
restore the post-build command by applying a "code generation" change the default behavior of the command "restore Defaults". |
| 146043 | On STM32H745 Cortex-M4 Dual Core projects the pre-defined
breakpoint is maintained but not caught upon run |
| 152549 | From GCC11, the build can be in error with some functions:
_close, fstat, _getpid, _isatty, _kill, _lseek, _open, _read, _write, _gettimeofday It’s due to that a state is define using the system information. The application needs to define a way to track time. |
| 156539 | If the user needs to set a proxy to be authenticated, a check for connection should be done: Windows > Preferences > STM32Cube > Firmware Updater and then Check Connection. |
| 166245 | When using the STM32CubeMP13 bare-metal firmware and activating Azure® RTOS
ThreadX, the STM32CubeIDE linker file must contain the following section to avoid compilation issues:
|
| 171852 | The implemented toolchain is allocating to an enum type only as many bytes as it needs for the declared range of possible values. |
| 174727 | STM32CubeIDE cannot make the project build automatically after having changed the IP configuration, it cannot automatically control this configuration, the user needs to increase Flash size manually when needed depending on his configuration. |
| 189888
213181 |
The “connect under reset” connection mode is not supported on STM32WB05, STM32WB09, STM32WL30, STM32WL31 and STM32WL33 microcontrollers. An “hardware reset pulse” will be applied in order to connect and debug. |
| 192219 | For cortex M55 (like STM32N6), GCC12 and earlier versions detect warning using OFast and O3 optimizations level.
Workaround:
|
| 213261 | For STM32WBA65I-DK, incremental flashing is not supported for external flash, flashing will be done according to the legacy mode. |
| 214243 | For STM32MP135F-DK ,bootloader is not yet functional using OpenSTLinux 6.1.0 |
| 215027 | Regardless of the STM32CubeIDE version, after performing a data refresh, the series filter in the Product Info section under the MCU/MPU finder does not apply the selected criteria to the displayed product list. |
2. Fixed issues
| ID | Summary |
|---|---|
| 178003 | On STM32U5 devices, Live Expression doesn't show the correct variable's value if it is both declared in secure and non-secure projects. |
| 182619 | The TSIZE register size is wrongly set in the SFR view. |
| 196779 | Using "B-WB1M-WPAN1-BLE_HR_p2pServer", an issue will be found in example importing from Example Selector.
Workaround: Import from file system using the menu "File -> Open Porject from file system" |
| 198955 | STM32WB0x and STM32WBA5x products: after importing an STM32Cube wireless applications (BLE, Thread / Zigbee, …), user will get issues during project compilation. |
| 203090 | For STM32WL3x serie it is not possible to use the ST-Link V2 with STM32CubeIDE and STM32CubeProgramer. |
| 203376 | While using the FSBL_XIP example for STM32N657-DK, debug session once restarted might fail. |
| 206830 | OpenSTLinux repository from update site mechanism cannot be installed on MPU empty project, issue related to the detection whether the required soc is MP1 or MP2 to select the right repository to install. |
| 207435 | For STM32WL31 serie, an HardFault_Handler() is detected at stm32wl3x_it.c. |
| 207908 | Compilation errors with board P-L496G-CELL02. |
| 209215 | When using a STM32WB0 device with STM32CubeIDE and "STLink (OpenOCD)" as debug probe, it is not possible to program above address 0x10080000. |
| 209345 | For some STM32U3 devices, the debug session got stuck at MX_GTZC_S_Init(). |
| 209380 | Changing builder settings twice for CMake project can introduce an internal error. |
| 209401 | Using some examples for the STM32N6 devices shows a warning message regarding the Project nature issue. |
| 209843 | Using OpenAMP with STM32H7 microcontrollers generates warnings and it results errors at runtime. |
| 210492 | For STM32N6 microcontrollers, IWDG_IRQHandler misspell in startup file was corrected |
| 211344 | After generating the code for some serie, sometimes a dialog appears with errors. |
| 212318 | Compilation of the AppliNonSecure project fails during the binary trusting process for the ST32N6 serie. |
3. Known issues
The known issues are split into general, STM32CubeCLT, OS-specific, and target-specific issues.
3.1. General issues
| ID | Summary |
|---|---|
| 59435 | Having a space or non-ASCII character in the project/workspace path or installation path is not fully supported. |
| 63624 | Some STM32CubeMX pop-up dialogs are not opened in front of the STM32CubeIDE workbench on all OS's. |
| 68184 | Hierarchical projects cannot be imported with the option Copy into workspace. |
| 68440 | Hierarchical projects cannot be renamed. |
| 89454 | Restart configuration only works for flash memory projects and not for RAM projects. Program Counter register is not set correctly. Manual work-around: In Restart configuration, manually set PC to the ResetHandler() in RAM: set $pc = 0x20000xxx. |
| 115928 | Editing live expressions while target is running does not work with SEGGER J-Link. |
| 124062 152549 | GCC-10 is more strict with respect to declaration of global variables in header files. Read the GCC-10 porting guide, so many warnings and errors result. |
| 133183 | STM32CubeIDE cannot debug using FreeRTOS aware with J-LINK.
Work-arounds, if: Reset strategy == Connect under reset, requires Initialization commands:
Work-arounds, if: Reset strategy == None (attach mode), requires Initialization commands:
|
| 139637 | Creating new STM32Cube project inside STM32CubeIDE is not possible if ioc-editor is point at STM32CubeMX stand-alone |
| 156812 | Missing string table in Build Analyzer while showing the bytes of the size of the ".rodata" section . |
| 159507 | Issues detected when updating STM32CubeIDE version from 1.9.0 to 1.13.1. |
| 162500 | After programming a device in Run mode, STM32CubeIDE opens every time a new tab with startup file and give focus on that tab. |
| 169316 | When building an existing project, using GCC11 or GCC12, a warning should be noticed: “elf has a LOAD segment with RWX permissions”.
This warning highlights a vulnerability, to correct it and secure the data section, we suggest to update the linker files: From this kind of section:
To:
But it’s incompatible with GCC10 and earlier versions. |
| 170279 | Failure to compile embOS due to missing stack variable as a new section defining _stack_start__ and __stack_end__ in linker file need to be added in linker file once it is required by ThreadX. |
| 183033 | The restore default build configuration feature lost the build commands. |
| 189478 | On Ubuntu 22.04 while creating a new STM32 project, STM32CubeIDE stucks at MCU finder step. Issue can be avoided by starting STM32CubeIDE with "wayland" version, or start it with sudo mode. |
| 199067 | In STM32CubeIDE 1.17.0, Hex files are not generated, setting a post build command:
arm-none-eabi-objcopy -O ihex "project_name.elf" "project_name.hex" is required. |
| 197993 | In STM32CubeIDE 1.17.0, MP2 sources are not installable following project import steps, instead all update source need to be deactivated expect OpenSTLinux source first. |
| 200233 | Compilation error when using toolchain GCC 12.3 with CubeIDE 1.14.1.
As Workaround, I proposed to the customer to download GCC12 and load it from local by setting the toolchain
|
| 207337 | After updating the STM32CubeIDE from some versions to the patch 1.18.1 using the update site updater, the GUI of the integrated STM32CubeFinder and STM32CubeMX are the images of the old UI tools.
Workaround: reinstall STM32CubeIDE from the installer on st.com. |
| 209826 | if GCC’s fallthrough attribute are used they will be flagged as error. |
| 212124 | A popup might appear expressing an install error while Firmware installing. If such event occured, popup dialog needs to be closed, and code needs to be regenerate. |
| 212197
212444 |
Add a description: if in target selection static lib option was chosen, build errors will be generated for STM32WBA65I-DK1, B-WBA5M-WPAN NUCLEO-WBA65RI, STM32H745I-DISCO and STM32H747I-DISCO.
Workaround: The following preprocessor definitions must be added: ../../Common/Inc ../../Drivers/STM32H7xx_HAL_Driver/Inc/Legacy ../../Drivers/STM32H7xx_HAL_Driver/Inc |
3.2. STM32CubeCLT issues
| ID | Summary |
|---|---|
| 214938 | For MACOs install, no paths for "CLANG_GCC_CMSIS_COMPILER" and GCC_TOOLCHAIN_ROOT.
Workaround:
|
3.3. OS-specific issues
3.3.1. Linux®
| ID | Summary |
|---|---|
| 139617 | The CAD view in the ioc-editor may not render. A restart of STM32CubeIDE is required. |
| 165338
189478 |
Using Ubunto 22, the target selection doesn’t appear normally without sudo permission.
Workaround: start with sudo permission or start the wayland binary instead of STM32CubeIDE binary. |
| 175176 | Using the generic Linux installer, the libncurses must be installed independently. |
3.4. Target-specific issues
3.4.1. STM32G4
| ID | Summary |
|---|---|
| 194756 | Problem with project creation using STM32G411 with the 1.6.0 firmware.
Workaround: use the version 1.6.1 of the firmware. |
3.4.2. STM32H7
| ID | Summary |
|---|---|
| 73552 | Serial Wire Viewer configuration is not reset for STM32H7 devices on the next launch if it was terminated with record active when using ST-LINK GDB server. |
| 79658 | ST-LINK GDB server reports being suspended on address: 0x05F0001 when debugging STM32H7 dual-core devices and the core under debug goes to sleep. |
| 81763 | OpenOCD does not support debugging STM32H7 dual-core devices when the core under debug goes to sleep. |
| 175966 | H7RS project on Ubuntu with ExtMemLoader context configured: Postbuild commands cannot be passed successfully when STM32CubeIDE is installed with sudo.
Workarounds:
|
| 202605 | For the STM32H7Rx/7Sx microcontrollers in the STM32H7 series and when activating TRACER_EMB, the NONCACHEABLE region size in the linker file need to be increased to fit TRACER buffer.
To add into the section: __RAM_NONCACHEABLEBUFFER_SIZE = 0x400; |
| 206638 | While using GCC13 in STM32CubeIDE 1.17.0 or 1.18.0, errors or warnings can be encountered while importing some projects. GCC12 usage is recommended in this scenario. |
| 207664 | Debug Errors will be encountered while Boot project and application project are both selected for STM32H7S78-DK. |
3.4.3. STM32L0
| ID | Summary |
|---|---|
| 201878 | Errors will appear when building the imported project ADC_DMA_Transfer for NUCLEO-L010RB.
Workaround: syscall.c file needs to be added to the project". |
3.4.4. STM32MP1
| ID | Summary |
|---|---|
| 73895 | Debugging in production mode requires a network connection. If STM32CubeIDE is configured to use a network proxy, then the IP address of the STM32MP1 board needs to be added to the "Proxy bypass" list. |
| 73896 | The synchronization check between the IP-address entered in launch configuration and the IP-address of the target does not abort the launch in case of mismatch. |
| 214243 | For STM32MP135F-DK ,bootloader is not yet functional using OpenSTLinux 6.1.0 |
3.4.5. STM32N6
| ID | Summary |
|---|---|
| 192219 | GCC12 and earlier versions detect warning using OFast and O3 optimizations level.
Workaround:
|
| 208549 | If we use the “XSPI_PSRAM_MemoryMapped” example or any similar application, data stored in the external memory could not be viewed by the memory view in STM32CubeIDE |
| 209390 | When in a debug session, if we jump to the application and need to reset the execution to go back to the FSBL project, the “Reset” button will not works.
Workaround: add a specific command to set the program counter to the beginning of the FSBL code. Under the “Reset Configuration” menu add the set $pc = Reset_Handler command.  |
| 210446 | If the Application context contains any break point even if it is disabled, the debug session will not start.
Workaround: Therefore, any break point needs to be added while debugging and after the execution of this instruction “retr = MapMemory();”. This is why we set the breakpoint at JumpToApplication instead of main in the startup configuration. |
3.4.6. STM32WB
| ID | Summary |
|---|---|
| 211049 | Some project for STM32WB can generate compilation error if the Firmware version used is V1.23.0. |
3.4.7. STM32WB0
| ID | Summary |
|---|---|
| 180379 | A false error could be detected on some BLE applications when is included some binary libraries.
The error should be: “missing .note.GNU-stack section implies executable stack” or “NOTE: This behaviour is deprecated and will be removed in a future version of the linker” Workaround: Use the linker option: -z noexecstack More information: https://lists.gnu.org/archive/html/info-gnu/2022-08/msg00002.html |
| 183143 | An Error seems to be found once the ThreadX Option is activated for WB05/WB07/WB09. |
| 189888 | For STM32WB0x devices the connection Under Reset type is not supported. |
| 198955 | Starting from Example Selector: After importing an STM32Cube wireless applications (BLE, Thread / Zigbee, …), user will get issues during project compilation
Workaround: To resolve this issue, users are advised to regenerate the project. Staring by import: After importing an STM32Cube wireless applications (BLE, Thread / Zigbee, …) of the STM32WB0x products using the menu “File -> Import -> Import Existing STM32CubeMX Configuration File (.ioc)”, or “File -> New -> STM32 Project from an Existing STM32CubeMX Configuration File (.ioc), users will get issues during project compilation. Workaround: To resolve this issue, users are advised to follow these steps:
|
3.4.8. STM32WBA
| ID | Summary |
|---|---|
| 198955 | Starting from Example Selector: After importing an STM32Cube wireless applications (BLE, Thread / Zigbee, …), user will get issues during project compilation
Workaround: To resolve this issue, users are advised to regenerate the project. Staring by import: After importing an STM32Cube wireless applications (BLE, Thread / Zigbee, …) of the STM32WB0x products using the menu “File -> Import -> Import Existing STM32CubeMX Configuration File (.ioc)”, or “File -> New -> STM32 Project from an Existing STM32CubeMX Configuration File (.ioc), users will get issues during project compilation. Workaround: To resolve this issue, users are advised to follow these steps:
|
4. Upgrades
| ID | Summary |
|---|---|
| BusyBox | 1.31.0.st_20240131-1810 |
| Eclipse and CDT | Eclipse 2024-09
CDT 11.6.1 |
| GCC1 binaries | 13.3.rel1.20240926-1715 |
| JRE | Adoptium® Temurin™ 21.0.3_9 and JavaFX 21.0.3 |
| JxBrowser | 7.41.4 |
| Make | 4.4.1_st_20231030-1220 |
| OpenOCD | v0.12.0+dev-00623-g0ba753ca7 |
| RTOS Proxy | 0.17.0 |
| SEGGER J-Link | V8.38 |
| ST-LINKGDBServer | 7.11.0 |
| STLink Server | 2.1.1-2 |
| STM32CubeMX | 6.15.0 |
| STM32CubeProgrammer | 2.20.0 |
If you have any question or request concerning this wiki or if you see some pages with some mistake, you can report them using ST Support Center or ST Community MCU Forum.
All rights reserved (c) 2025 STMicroelectronics