1. Delta between 1.11.0 and 1.11.2
| ID |
Summary
|
| 140972 |
STM32CubeIDE installations were corrupted when using the Eclipse Marketplace, the Toolchain Manager, and downloading OpenSTLinux packages. This patch v1.11.2 fixes this issue.
|
| 140569 |
With STM32CubeIDE v1.11.0, some code about the FreeRTOS™ support was removed for the STM32F4. This patch v1.11.2 fixes this issue.
|
2. Fixed issues
| ID |
Summary
|
73456
74149
107232
138057
|
Fixed issue with SFR view – incorrect values during search and filters will show child nodes.
|
| 85064 |
Some macOS® versions report installation image corruption or that the image cannot be opened because the developer cannot be verified. The work-around is to execute the following command:
xattr -c /Applications/STM32CubeIDE.app
|
| 123405 |
Fixed issue with SWV bandwidth performance with ST-LINK GDB server.
|
| 124770 |
There are multiple CM0+ pre-compiled stacks with different memory size requirements. It is consequently up to the user to update the linker script to reflect the memory split between the CM4 and CM0+ core.
|
| 130208 |
Fixed issues with selecting text in Linker script editor and solved dark theme issues.
|
| 131836 |
ST-LINK GDB server can now abort debug launch when STM32CubeProgrammer fails to perform the flash download.
|
| 134020 |
RAM linker script for STM32H7B0xB device has only 128K RAM.
|
| 134147 |
ST-LINK GDB server dead-lock in persistent mode after a few GDB-client connections.
|
| 134674 |
The Build Analyzer "Memory Regions"-tab has an error in the "End Address" column.
|
| 135591 |
OpenOCD – Shared ST-LINK option persistent when switching script generation method.
|
| 136427 |
Fixed the issue with SWV ITM Console going black.
|
3. Known issues
The known issues are split into general, 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.
|
| 109764 |
FreeRTOS™ kernel-aware debugging: Full stack traces off all tasks do not work if configUSE_PORT_OPTIMISED_TASK_SELECTION 1
|
| 115928 |
Editing live expressions while target is running does not work with SEGGER J-Link.
|
| 124062 |
GCC-10 is more strict with respect to declaration of global variables in header files. Read the GCC-10 porting guide.
|
| 133183 |
STM32CubeIDE cannot debug using FreeRTOS aware with J-LINK.
Work-arounds, if: Reset strategy == Connect under reset, requires Initialization commands:
info threads
info threads
thread 2
Work-arounds, if: Reset strategy == None (attach mode), requires Initialization commands:
info threads
info threads
thread 2
stepi
|
3.2. OS-specific issues
3.2.1. Linux®
| ID |
Summary
|
| 139617 |
The CAD view in the ioc-editor may not render. A restart of STM32CubeIDE is required. |
3.3. Target-specific issues
3.3.1. 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.
|
3.3.2. 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.
|