Support for SWO in the 3.x.x VScode extension?

[jostlowe]

Hi!

Is there support for enable and view SWO output in the STM32 VScode 3.x.x. extension using ST-LINKV3?

For now, this is the only feature that would keep us from moving away from the old eclipse-based platform.

If there is no SWO support: Is it on the roadmap?

[unsigned_char_array]

Many years ago I got SWO working on a custom tool chain for VSCode using the cortex-debug extension. I haven't tried the ST extension in years, so I don't know if they support it directly. But there is no technical reason why it shouldn't work.

[jostlowe]

Thanks for the quick reply.

I got SWO to work using the cortex-debug extension a while back, but with the 3.x.x releases ST seem to have shifted away from cortex-debug (which i believe was used on the 2.x.x releases?) and towards a more proprietary platform using the STM32Cube Debug Generic GDB Server and STM32Cube Debug Core plugins. 

I was curious to know the status of SWO on the new platform

[jostlowe]

I guess it would be sufficient to pass some values to the --swd, --swo-port, --cpu-clock, and --swo-clock-div flags when the ST-Link GDB server launches, e.g. trough the launch.json file, so that the SWO data is exposed by the GDB server on a TCP port