Live watch very slow in VSC compared to CubeIDE

[JanusAudio]

I am using Visual Studio Code with the latest "STM32Cube for Visual Studio Code".

I use the default launch.json generated by CubeMX and added this to the config to activate the Cortex Live Watch:

            "liveWatch": {
                "enabled": true,
                "samplesPerSecond": 20
            }

The values in my live watch update really slowly though, around 2 or 3 updates a second. I started CubeIDE with the same project, so exact same code and get very fast updates of my values in the live view there, looks like dozens of updates a second.

Is there any way to setup the cortex debugger or GDB server to get similar performances in Visual Studio Code?

Thanks,

Sebastian

[Nawres GHARBI]

Hi @JanusAudio  

could you paste your live watch here please ? 

[JanusAudio]

Hi @Nawres GHARBI,
thanks for getting back to me! I don't understand: Do you want me to post a video of the live watch? There wouldn't be a lot to see in the Cortex Live Watch window if I just posted a screenshot. Or do you want my complete launch.json?

[Cartu38 OpenDev]

"I use the default launch.json generated by CubeMX". Be aware STM32CubeMX doesn't generate any launch.json but I guess this launch file comes from STM32CubeMX generated project import proces sinto VSCode Thanks STM32 extension.

Such said live watch feature comes in this context Thanks https://marketplace.visualstudio.com/items?itemName=marus25.cortex-debug / https://github.com/Marus/cortex-debug/blob/0074bab85fabbcabc508c734abe16873376ac70a/package.json#L788. This solution is known less efficient than STM32CubeIDE one but has benefit to exist !

PS: If my analysis is right means you're playing with 2.x.y STM32 extension version. Be aware  some new one (pre-release) has been shared https://community.st.com/t5/stm32cube-for-visual-studio-code/new-stm32cube-for-visual-studio-code-extenstion-released-3-4-11/td-p/800040
Such said no live watch support more here just hoping part of plans !

[JanusAudio]

Ok, so the launch.json was probably generated by the STM32 extension. And you are correct: I use version 2.1.1 which is the default on VSCode for Mac. And the extension also depends on Cortex-Debug.

I just thought there might be some setting for this to speed up the live watch to get results similar to CubeIDE.

So hopefully in then final 3.4 release it will be supported and fast.