Known limitations ¶
Limitations ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-3618 |
To start debugging in the NS zone when product status is TZ-Closed for STM32H5 using ST-Link GDBServer, add this in Run Commands:
For
Reset & Restart: add the same script and select
|
|
TIDEC1-3756 |
Post-build commands can be restored by either applying code generation or changing the default behavior of Restore Defaults. |
|
TIDEC1-3805 |
On STM32H745 Cortex-M4 dual-core projects, the predefined breakpoint is kept but not caught on run. |
|
TIDEC1-3929 |
From GCC11, build errors may occur for:
|
|
TIDEC1-4297 |
For STM32CubeMP13 bare-metal + Azure
®
RTOS ThreadX, add a
|
|
TIDEC1-4465 |
Enum storage size is minimized by the toolchain to the declared value range. |
|
TIDEC1-4585 |
STM32CubeIDE cannot auto-build after IP configuration changes. Flash size must be increased manually when needed. |
|
TIDEC1-5161 / TIDEC1-5973 |
Connect under reset is not supported on STM32WB05/WB09/WL30/WL31/WL33. A hardware reset pulse is used instead. |
|
TIDEC1-5220 |
For Cortex-M55 (for example STM32N6), GCC12 and earlier may warn with
|
|
TIDEC1-5757 |
Importing STM32CubeMX projects into STM32CubeIDE on macOS/Ubuntu may show a pop-up or fail. |
|
TIDEC1-5975 |
On STM32WBA65I-DK, incremental flashing is not supported for external flash; legacy mode is used. |
|
TIDEC1-6327 |
With OpenOCD on STM32H7S78-DK and NUCLEO-H7S3L8, memory read failures may occur, but debugging remains possible. |
|
TIDEC1-6338 / 6339 / 6341 / 6344 / 6347 |
With GCC14, some examples may show errors/warnings for STM32G0/H5/H7/H7RS/N6/WB/WB0/WBA/WL/WL3. Workaround: set GCC13.3.rel1 as default in Window > Preferences > STM32Cube > Toolchain manager. |
|
TIDEC1-6311 |
For CMake projects, changing generator/build system may require Clean Project before rebuild. |
|
TIDEC1-6318 |
CMake projects are not supported for MPx products. |
|
TIDEC1-6658 |
Prebuild/postbuild scripts may use BusyBox tools (for example
|
|
TIDEC1-6733 |
For Cortex-M0/M0+/M33/M55, core reset mode is not supported in STM32CubeIDE debug configuration. |
General issues ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-353 |
Having a space or a non-ASCII character in the project/workspace/installation path is not fully supported. |
|
TIDEC1-846 |
Hierarchical projects cannot be imported with Copy into workspace. |
|
TIDEC1-866 |
Hierarchical projects cannot be renamed. |
|
TIDEC1-1081 |
To debug an STM32CubeIDE Makefile project: right-click project -> Properties -> C/C++ Build -> MCU settings -> select requested MCU -> Apply. |
|
TIDEC1-2004 |
Restart configuration works only for flash projects, not RAM projects. Manual workaround: in Restart configuration, set program counter to ResetHandler in RAM (example:
|
|
TIDEC1-3120 |
Editing live expressions while target is running does not work with SEGGER J-Link. |
|
TIDEC1-3120 / TIDEC1-3929 |
GCC-10 is stricter regarding global variable declarations in headers. Read GCC-10 porting guide; warnings/errors may occur. |
|
TIDEC1-3483 |
STM32CubeIDE cannot debug with FreeRTOS-aware debugging using J-LINK. Initialization commands workaround:
|
|
TIDEC1-4051 |
Missing string table in Build Analyzer when displaying byte size of
|
|
TIDEC1-4094 |
Issues detected when updating from 1.9.0 to 1.13.1. Recommended: reinstall 1.13.1 from scratch and reuse old workspace. |
|
TIDEC1-4175 |
After programming in Run mode, STM32CubeIDE opens/focuses startup file tab every time. |
|
TIDEC1-4420 |
embOS compile failure due to missing stack variable. Add linker section defining
|
|
TIDEC1-4883 |
Restore-default build configuration removes build commands. |
|
TIDEC1-5170 |
Exported ZIP project can fail when imported in another workspace. Workaround: Import -> Projects from Folder or Archive. |
|
TIDEC1-5194 |
Reset chip/restart debug session does not work as expected on Nucleo-N657X0-Q. Workaround: add
|
|
TIDEC1-5405 |
In 1.17.0, HEX files are not generated automatically. Add post-build command:
|
|
TIDEC1-5441 |
GCC 12.3 compilation error in 1.14.1. Workaround: download/load GCC12 locally (name
|
|
TIDEC1-5853 |
GCC fallthrough attributes can be flagged as errors. |
|
TIDEC1-6256 |
For CMake projects, add
|
|
TIDEC1-6267 |
Debug may fail with
|
|
TIDEC1-6293 |
Multi-context CMake import outputs multiple ELF files. User must select the intended ELF at debug launch. |
|
TIDEC1-6295 |
With GCC14, startup assembly may be malformed. Add:
|
|
TIDEC1-6311 |
After importing some STM32CubeMX projects, changing CMake generator then reconfigure can cause unexpected build completion/failure. |
|
TIDEC1-6335 |
On Ubuntu 22.04/macOS 15, opening
|
|
TIDEC1-6351 |
With LLVM, Static Stack Analyzer may be empty unless
|
|
TIDEC1-6882 |
Some regenerated STM32CubeWBA example files may show warning icons. Remove warning-marked extra files before build. |
|
TIDEC1-6909 |
On first launch after fresh install on macOS 15+, allow local network access popup for TCP/debug operations. |
|
TIDEC1-6960 |
SWV output may not appear for some CMake projects. Manually set core clock in debug configuration to initial STM32CubeMX value. |
|
TIDEC1-7059 |
Updating from older versions may fail when installed under system paths (for example
|
|
TIDEC1-7121 |
For STM32U3 (256 KB flash), debug via ST-Link GDB server is not yet available; use OpenOCD probe. |
|
TIDEC1-7144 |
For STM32CubeWL3 v1.5.0 apps on STM32WL33CC, OpenOCD flashing/debugging may fail in v2.1.1+; ST-Link GDB server works. |
|
TIDEC1-7260 |
On Windows with the Hungarian keyboard layout, pressing AltGr+B in the editor may trigger Disable All Breakpoints instead of inserting
|
|
TIDEC1-7408 |
CubeIDE may fail to start when OpenText UFT One sets the
|
|
TIDEC1-7437 |
The -ftls-model option is not effective with GCC 14 and earlier and is only partially supported with GCC 15. Full TLS support is expected with GCC 16. |
|
TIDEC1-7617 |
In STM32CubeIDE 1.19.0 and later, a subsequent NUCLEO-L432KC debug launch with the ST-LINK GDB server may fail when option bytes select the PH3/BOOT0 pin for BOOT0 (
Workaround: In STM32CubeProgrammer’s
Option Bytes
panel, disable
|
STM32CubeCLT issues ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-6104 |
For macOS install, no paths for
Workaround:
|
Target-specific issues ¶
STM32H7 ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-1160 |
Serial Wire Viewer configuration is not reset for STM32H7 devices on next launch if terminated with record active when using ST-LINK GDB server. |
|
TIDEC1-1484 |
ST-LINK GDB server reports suspended at address
|
|
TIDEC1-1596 |
OpenOCD does not support debugging STM32H7 dual-core devices when the core under debug goes to sleep. |
|
TIDEC1-4615 |
For H7RS project on Ubuntu with ExtMemLoader context configured, postbuild commands cannot be passed successfully when STM32CubeIDE is installed with sudo. Workarounds:
|
|
TIDEC1-5713 |
While using GCC13 in STM32CubeIDE 1.17.0 or 1.18.0, errors or warnings can occur when importing some projects. GCC12 is recommended in this scenario. |
|
TIDEC1-6274 |
Debugging code running from external flash on STM32H7S78-DK may fail with software breakpoints, causing
|
STM32L0 ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-5487 |
Errors appear when building imported project
Workaround: add
|
STM32MP1 ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-1187 |
Debugging in production mode requires a network connection. If STM32CubeIDE uses a network proxy, add the STM32MP1 board IP address to the Proxy bypass list. |
|
TIDEC1-1188 |
Synchronization check between launch configuration IP address and target IP address does not abort launch when they mismatch. |
|
TIDEC1-5941 |
For STM32MP135F-DK (Bare Metal), when enabling FreeRTOS CMSIS_V2, assign RAM alias to
Workaround:
|
STM32MP2 ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-7655 |
Existing MP2x TF-M projects may fail to debug in Production Mode if their linker scripts contain outdated memory region values. Update the linker script to match the CubeMX-generated memory regions. |
STM32N6 ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-5220 |
GCC12 and earlier versions detect warnings with
Workaround:
|
|
TIDEC1-5776 |
When using
|
|
TIDEC1-5778 |
To read data in external memory map mode for STM32N6, use Memory View with Hex rendering: open the three-dot menu, then Table rendering preferences, and switch from Automatic to Manual. |
|
TIDEC1-5864 |
If the Application context contains any breakpoint (even disabled), debug session does not start. Workaround:
|
STM32WB0 ¶
|
ID |
Summary |
|---|---|
|
TIDEC1-4786 |
A false error can be detected in some BLE applications that include binary libraries.
Typical messages:
Workaround: use linker option
|
|
TIDEC1-4887 |
An error seems to appear once the ThreadX option is activated for WB05/WB07/WB09. |
|
TIDEC1-5161 |
For STM32WB0x devices, Connect Under Reset is not supported. |