JLinkGDBServer could not connect to target

RE: JLinkGDBServer could not connect to target

Carl Richard — Tue, 13 Oct 2020 10:27:13 GMT

Hello, again!

No problem! Glad to hear that you've made it work.

I will probably try this out for the nRF5340 myself someday soon. Will update you if I discover a better way.

Best regards,
Carl Richard

RE: JLinkGDBServer could not connect to target

Oliver Batista — Tue, 13 Oct 2020 08:28:36 GMT

Hey Carl, thanks for sharing your configuration. I've managed to make it work by using "cortex-m33" as "device" value. Not sure if this is the best way but at least I got myself some breakpoints.

RE: JLinkGDBServer could not connect to target

Carl Richard — Fri, 09 Oct 2020 12:48:04 GMT

Hello, avlier!

I must speak with the author of that tutorial for some details, but in the meantime you can have a look at a tutorial I've looked at myself earlier. It's a bit old, but it enabled me to debug an nRF9160 using VSCode.

My Cortex Debug configuration is attached below:

{
    // 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": "Debug NCS",
            "cwd": "${workspaceRoot}",
            "executable": "./build/zephyr/zephyr.elf",
            "request": "launch",
            "type": "cortex-debug",
            "serverpath": "C:/Program Files (x86)/SEGGER/JLink/JLinkGDBServerCL.exe",
            "servertype": "jlink",
            "device": "nrf9160_xxAA",
            "interface": "swd",
            "armToolchainPath": "C:/gnuarmemb/bin",
            "ipAddress": null,
            "serialNumber": null
        }
    ]
}

We do not really support debugging solutions outside of SES, but I will do my best to help you.

Best regards,
Carl Richard