1 Delta between 1.13.1 and 1.13.2
|159274 - 159633 - 158868 - 159757
|Alignment with STM32CubeMX 6.9.2
|Same embedded STM32CubeIDE user guide revision (UM2609) as the one on the product web page.
|Headless mode build failures fixed.
|Compilation error on printf function fixed.
2 Delta between 1.13.0 and 1.13.1
|Alignment with STM32CubeMX 6.9.1
|With STM32CubeIDE v1.13.0, If you downoald the latest version of X-CUBE-FREERTOS then load a project and compile it will throw compilation errors. This patch v1.13.1 fixes this issue.
3 Fixed issues
|Static stack analyzer do not pick up all functions.
|STM32Cube Project for board STM32MP157F-DK2 failed to write memory and failed to find where with STM32Cube-FW_MP1-V1.6.0.
|Fix debugging in the NS zone when the product status is TZ-Closed for the STM32H5 with a limitation (see chapter Limitations).
|After programming a device CubeIDE opens every time a new tab with startup file and give focus on that tab.
|Failed to launch Debug session with no existing debug configurations mapped to the project for Windows11.
|Software breakpoint not working in ST-Link GDB server.
|CubeIDE does not launch with Linux Fedora.
|Failure to install hardware breakpoints.
|Segmentation fault in STM32CubeIDE Linux build.
|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.
set breakpoint always-inserted on
set breakpoint always-inserted off
For the "Reset & Restart" button to work:
- Add the same script
- Select "None" as the type.
|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.
|In certain cases, we may encounter a post-construction generation problem which results as follows.
1. If you want to deactivated firmware signing after build
a. Untick Sign binary in STM32CubeMX.
b. Generate Code.
c. Edit STM32CubeIDE properties and manually remove the “Postbuild” command: This is the workaround for the limitation.
2. After previous changes, if you can enable again the signature.
a. Tick Sign binary in STM32CubeMX.
b. Generate code.
5 Known issues
The known issues are split into general, OS-specific, and target-specific issues.
5.1 General issues
|Having a space or non-ASCII character in the project/workspace path or installation path is not fully supported.
|Some STM32CubeMX pop-up dialogs are not opened in front of the STM32CubeIDE workbench on all OS's.
|Hierarchical projects cannot be imported with the option Copy into workspace.
|Hierarchical projects cannot be renamed.
|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.
|FreeRTOS™ kernel-aware debugging: Full stack traces off all tasks do not work if configUSE_PORT_OPTIMISED_TASK_SELECTION 1
|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.
|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:
|Could not rebuild a Non secure project when switch between Project Structure.
5.2 OS-specific issues
|The CAD view in the ioc-editor may not render. A restart of STM32CubeIDE is required.
|Unable to install CubeIDE on Fedora 37.
5.3 Target-specific issues
|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.
|ST-LINK GDB server reports being suspended on address: 0x05F0001 when debugging STM32H7 dual-core devices and the core under debug goes to sleep.
|OpenOCD does not support debugging STM32H7 dual-core devices when the core under debug goes to sleep.
|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.
|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.
|First connection to target sometimes fails, next connections are OK. This impact Cortex-M debug in production mode and Linux deployment and user space debug.