You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HI, Looking for help with vscode launch files in order use a pico debug probe (not a second pico).
I am working on a Ubuntu 22.04 host, have openocd setup and can use gdb-multiarch to debug a blink program on a pico.
When I try to use the launch files provided in pico-examples/ide/vscode vscode complains that:
"type":"cortex-debug",
"please use node type instead", and for these :
"executable": "${command:cmake.launchTargetPath}",
"servertype": "external",
"gdbPath" : "gdb-multiarch",
"gdbTarget": "localhost:3333",
"svdFile": "${env:PICO_SDK_PATH}/src/rp2040/hardware_regs/rp2040.svd",
"runToEntryPoint": "main",
// Work around for stopping at main on restart
"postRestartCommands": [
"break main",
"continue"
]
each of these lines have a key words that are "not allowed". I am obviously missing something that will turn out to be obvious. But I cannot see it.
The text was updated successfully, but these errors were encountered:
HI, Looking for help with vscode launch files in order use a pico debug probe (not a second pico).
I am working on a Ubuntu 22.04 host, have openocd setup and can use gdb-multiarch to debug a blink program on a pico.
When I try to use the launch files provided in pico-examples/ide/vscode vscode complains that:
"please use node type instead", and for these :
"executable": "${command:cmake.launchTargetPath}",
"servertype": "external",
"gdbPath" : "gdb-multiarch",
"gdbTarget": "localhost:3333",
"svdFile": "${env:PICO_SDK_PATH}/src/rp2040/hardware_regs/rp2040.svd",
"runToEntryPoint": "main",
// Work around for stopping at main on restart
"postRestartCommands": [
"break main",
"continue"
]
each of these lines have a key words that are "not allowed". I am obviously missing something that will turn out to be obvious. But I cannot see it.
The text was updated successfully, but these errors were encountered: