VScode Debugger fails to launch with custom board

RE: VScode Debugger fails to launch with custom board

Jason — Thu, 15 Dec 2022 12:54:53 GMT

This was caused by a bad wiring harness.

RE: VScode Debugger fails to launch with custom board

Jason — Fri, 02 Dec 2022 11:49:30 GMT

If there's no obvious answer to this then it's no problem. I just thought there might be an easy fix that I didn't know about.

Thanks for your help

RE: VScode Debugger fails to launch with custom board

Jason — Wed, 30 Nov 2022 12:45:08 GMT

Thanks, I'd not seen that info before.

but I don't understand, I have the same launch.json for all of my custom boards, but only 1 has stopped working.

It looks like this

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
    
        {
            "name": "Launch build",
            "type": "nrf-connect",
            "request": "launch",
            "config": "c:\\Vigglab\\Projects\\Doodoody\\BTSender_ClipPair\\NCS_Firmware\\ClipPair\\build",
            "runToEntryPoint": "main"
        }
    ]
}

RE: VScode Debugger fails to launch with custom board

Øivind — Tue, 29 Nov 2022 12:50:00 GMT

Hi, sorry for the late response

If the server address is wrong, you can try setting the GDB server address yourself to the launch.json file:

https://nrfconnect.github.io/vscode-nrf-connect/reference/ui_debug.html#

RE: VScode Debugger fails to launch with custom board

Jason — Thu, 24 Nov 2022 10:45:34 GMT

I forgot to mention that I've already tried "Erase board" and "recover board" from the VScode extension

(and I should also mention that the VScode extensions are simply fantastic and I would have absolutely hated trying to develop without them.)