Solved
STM32CUBE RTOS view not working when debugging running target with just symbolFileName supplied to imagesAndSymbols
STM32CubeIDE for Visual Studio Code v3.8.0
serverRtos fails to recognize symbolFileName when attaching to running target. This causes the rtos viewer to not work properly.
None working setup:
"type": "stlinkgdbtarget",
"request": "launch",
"name": "CM7 master STM32Cube: Launch ST-Link GDB Server",
"origin": "snippet",
"cwd": "${workspaceFolder}/",
"deviceName": "STM32H747BIT6",
"deviceCore": "Cortex-M7",
"serverReset": "None",
"imagesAndSymbols": [
{
//"imageFileName": "${workspaceFolder}/executable.elf",
"symbolFileName": "${workspaceFolder}/executable.elf",
}
],
"serverRtos":
{
"enabled": true,
"port": "60000",
"driver": "freertos",
"driverPort": "ARM_CM7"
},Debug console output:
RTOS proxy: STMicroelectronics RTOS Proxy. Version 0.18.1
Copyright (c) 2026, STMicroelectronics. All rights reserved.
Failed generate debug info
Loading RTOS driver... FreeRTOS
Connecting to GDB server 127.0.0.1 on port 61234 ... RTOS Proxy: readelf: Error: 'undefined': No such file
Waiting for debugger connection...
Working setup but with loading the elf file which is not preferred:
"type": "stlinkgdbtarget",
"request": "launch",
"name": "CM7 master STM32Cube: Launch ST-Link GDB Server",
"origin": "snippet",
"cwd": "${workspaceFolder}/",
"deviceName": "STM32H747BIT6",
"deviceCore": "Cortex-M7",
"serverReset": "Connect under reset",
"runEntry": "main",
"imagesAndSymbols": [
{
"imageFileName": "${workspaceFolder}/executable.elf",
"symbolFileName": "${workspaceFolder}/executable.elf",
}
],
"serverRtos":
{
"enabled": true,
"port": "60000",
"driver": "freertos",
"driverPort": "ARM_CM7"
},