If you add the Custom Launch Debugger (vMicro > Add Code > Add Custom GDB Debugger (Advanced) )
And replace the contents with the below:
{
// Adafruit NRF52x Hardware Debug + JLink
"serverLaunchTimeout": 5000,
"filterStdout": false,
"filterStderr": true,
"targetArchitecture": "arm",
"stopAtEntry": false,
"externalConsole": false,
"MIMode": "gdb",
"MIDebuggerServerAddress": "$(miDebuggerServerAddress)",
"cwd": "$(buildPath)",
"MIDebuggerPath": e-eabi-gcc\\9-2019q4\\bin\\arm-none-eabi-gdb.exe",
"MIDebuggerArgs": "$(miDebuggerArgs)",
"debugServerPath": "C:\\ProgramData\\vmicro\\tools\\openocd-0.10.0.1\\bin/openocd.exe",
"debugServerArgs": "-d2 -s \"C:\\ProgramData\\vmicro\\tools\\openocd-0.10.0.1/share/openocd/scripts/\" -f \"board/nordic_nrf52_dk.cfg\" -c \"init; reset halt\"",
"setupCommands": [],
"program": "$(program)",
"logging": {
"moduleLoad": false,
"trace": false,
"engineLogging": false,
"programOutput": false,
"exceptions": false,
"traceResponse": false
}
}
Then ensure that the MIDebuggerPath has the user name changed, and if required the rest of the path
(This can be verified with vMicro > Compiler > Show Build Properties Enabled, then perform a build, and search the output for "runtime.tools.arm-none-eabi-gcc.path=")
Once this is saved the debugger should have the tools configured for this NRF52 package and the JLink probe, so try attaching or starting the debugging process....
Let us know if you get any errors when attaching in the Output > Debug Window (or pop ups).