Is svdPath still supported in cppdbg now that the microsoft vscode-embedded-tools extension is deprecated?

[jsnowy]

With the deprecation of the Embedded Tools extension (https://github.com/microsoft/vscode-embedded-tools), does this mean the cppdbg no longer supports embedded debugging? Even though the svdPath parameter is still allowed in "type": "cppdbg".

[Bob Brown (bobbrow)]

We haven't changed anything in cppdbg to block this scenario and don't plan to. I think we just aren't supporting that extension any longer. Garrett Campbell (@gcampbell-msft) might have more information.

[Garrett Campbell (gcampbell-msft)]

jsnowy Thanks for the question, Bob Brown (@bobbrow) you are correct.

While the svdPath is still allowed, specifically as it relates to the Embedded Tools extension, it is not supported. However, I wouldn't say that this means that the cppdbg no longer supported embedded debugging, only that the svdPath no longer does anything for the now removed extension.

Utilizing cppdbg with tools like OpenOcd and other launch structures should remain unchanged.

[jsnowy]

Bob Brown (@bobbrow) Garrett Campbell (@gcampbell-msft) Hi there! Thanks a lot for your replies.
I’m now trying to use Peripheral Viewer extension with the cppdbg to extract the svdPath property. Everything works fine except the "WriteMemory" function. I already know cppdbg does not support this feature for now, but it is still usable overall.