Re: [OpenOCD-user] problem with openocd 0.12.0

[Laurent <lau...@pr...>]

> That suggests that the issue is one of misconfiguration of the VSCode debug launcher rather than any issue with OpenOCD (0.12.0 versus 0.10.0) per se? What is the JSON for your 0.10.0 and 0.12.0 configurations?

You're probably right, but I'm using the same configuration for openocd 10 and openocd 12. I've only changed the path, and I check the path, the path is good.

Here is the json used in vscode:

{
"version": "0.2.0",
"configurations": [
{
"name": "DEBUG-MCU",
"type": "cppdbg",
"request": "launch",
"program": "/path/to/executable.elf",
"setupCommands": [
{
"text": "target remote localhost:3333",
},
{
"text": "file /path/to/executable.elf",
},
{
"text": "monitor reset halt",
}
],
"customLaunchSetupCommands": [
{
"text": "monitor reset init",
}
],
"launchCompleteCommand": "exec-continue",
"MIMode": "gdb",
"targetArchitecture": "ARM",
"cwd": "${workspaceRoot}",
"miDebuggerServerAddress": "127.0.0.1:3333",
"debugServerArgs": "-f board/stm3241g_eval_stlink.cfg",
"serverLaunchTimeout": 20000,
"serverStarted": "Info\\ :\\ [\\w\\d\\.]*:\\ hardware",
"filterStderr": true,
"filterStdout": true,
"externalConsole": true,
"logging": {
"natvisDiagnostics": true,
"traceResponse": true,
"moduleLoad": true,
"trace": true,
"engineLogging": true,
"programOutput": true,
"exceptions": true
},
"stopAtEntry": true,
"miDebuggerPath": "/usr/local/bin/arm-none-eabi-gdb",
"debugServerPath": "/usr/local/Cellar/open-ocd/0.12.0_1/bin/openocd"
}
]}

>