STM32CUBE RTOS STATE NOT RUNNING

[istery]

I used the STM32CUBE FOR VSCODE preview version and enabled FreeRTOS in STM32CUBEMX. However, during the debugging process, the STM32CUBE RTOS STATE is empty and does not display any content, even when the program is paused.

[Florent V · Accepted solution]

Hi Istery,

To enable the RTOS state view during debugging, you need to add the "serverRtos" attribute to your debug configuration. For example, for FreeRTOS:

"serverRtos": {
    "enabled": true,
    "port": "60000",
    "driver": "freertos"
},

BR,

/Flo

[istery]

Thank you for your response! It really worked! However, now the Task name cannot be displayed directly under the Tasks label; it needs to be expanded to be visible. Is there a solution to this problem?

[Florent V]

No, for now, the nodes need to be expanded to see the task name.
But thanks for the feedback; we are adding this to our roadmap.

KR,

/Flo

[NMartin]

I had to change the port to 61234 instead of the suggested 60000. Where can I find documentation on this?

Best,

Nate

[LaurentL]

That's strange, and if you try again with 60000, is it still failing ?

61234 is the default port of STLink gdb server.

Are you using an STLink or Segger JLink ?

Can you show your launch json file.

Can you show the "DEBUG CONSOLE" log ?

With the default launch as this one :

            "serverRtos": {

                "enabled": true,

                "port": "60000",

                "driver": "freertos"

            },

You should see these traces if using an STLink :

...

RTOS proxy: Connecting to GDB server 127.0.0.1 on port 61234 ... RTOS proxy: Connected

Listen for GDB connection on port: 60000 ... Debugger connected

...

connected to remote target localhost:60000

...

Rgds,

Laurent

[NMartin]

Working configuration

I opened the project on another computer and changed the port back to 60000... Which also works now. 

Now that I think about it, I was using a different STlink that had been abused (carried back and fourth in a backpack) and was seeing a few connection issues. Next time I do some development on that computer I will try changing the port with a better treated STlink. 

[LaurentL]

OK, next time you try this board, check that jumpers have not been lost and update the STLink Firmware to be sure to have the latest.

Cheers,

Laurent