Skip to main content
Associate II
September 19, 2026
Question

Debug FreeRTOS with STlink GDB

  • September 19, 2026
  • 0 replies
  • 8 views

I am trying to debug an application running on a Nucleo-F411RE using the VS code STM32 extensions. I am using the onboard debugger with the "STM32Cube: Launch ST-Link GDB Server" debug launch option.

The RTOS proxy is starting, but I get the following errors when it hits the initial break at main.

RTOS proxy: Missing symbol: xQueueRegistry.

Missing symbol: xQueueRegistry.

Missing symbol: pxCurrentTimerList.

{"label":"","value":[{"label":"Version","value":"1.0.0"},{"label":"Driver","value":"freeRTOS"},{"label":"Kernel state","value":"Not started"},{"label":"Data","value":[{"label":"Tasks","value":""}]}]}

Attempt to use a type name as an expression.

Attempting to continue, when it hits my first breakpoint I get:

Breakpoint 2, SPITestTask (pars=0x0) at D:/Users/kecknew/Documents/BowieStage/TMC5041Src/spitest.cpp:16

16 spi.SPISetup(&hspi2);

monitor rtos -m state

Wrapping read detected. Addr: 0xffffffff; Length: 256

Ignoring packet error, continuing...

Where the last line keeps repeating and the debugger becomes unresponsive.

Debug firmware on the board is: V2.J48.M35

Application is a basic FreeRTOS application as generated by CUBE MX with only one thread.

All tools were recently installed so should be up to date.

Debugging works fine if I do not use the RTOS server, but then I lose a lot of useful features.

Is this a bug or am I doing something wrong?