question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error GDB Server: Timeout on v0.4.4 to v0.4.5 for JLink debugging

See original GitHub issue

I recently updated my cortex-debug version and had the error “Failed to launch undefined GDB Server: Timeout”. I traced the issue starting at v0.4.5. Here are my launch.json settings:

"configurations": [
        {
            "name": "Cortex Debug",
            "cwd": "${workspaceRoot}",
            "executable": "./BUILD/test.elf",
            "request": "launch",
            "type": "cortex-debug",
            "servertype": "jlink",
            "device": "RSL10",
            "interface": "swd",
            "svdFile": "../../rsl10.svd",
            "preLaunchTask": "${defaultBuildTask}"
        }
    ]

I have the JLink server and arm gdb path set in settings.json and confirmed they’re correct. The only thing that breaks the project is updating from 0.4.4 to 0.4.5.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:5

github_iconTop GitHub Comments

2reactions
rodrigobrochadocommented, Oct 11, 2021

It is JLinkGDBServerCLExe (not JLinkGDBServerExeCL) rigth @cwillforeal ? I can confirmt that it works with "serverpath": "JLinkGDBServerCLExe", on v0.4.7.

Now I saw that this information was added on the above mentioned wiki some days ago (and the CL part just got bold).

If it was kind of a “breaking change” shouldn’t it be on the change log? Anyway, problem seems to be solved, thanks @cwillforeal @haneefdm

1reaction
cwillforealcommented, Oct 11, 2021

My issue was solved by specifying JLinkGDBServerExeCL. Seems like the old version worked with the non CL jlink server but CL is required now. Hope that helps!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error GDB Server: Timeout on v0.4.4 to v0.4.5 for JLink ...
I recently updated my cortex-debug version and had the error "Failed to launch undefined GDB Server: Timeout". I traced the issue starting at...
Read more >
Failed to launch OpenOCD GDB Server: Timeout. · Issue #81
VSCode gives me the following error when I try to run the debugger: Failed to launch OpenOCD GDB Server: Timeout.
Read more >
timeout parameter to JLinkGDBServer seems not working - ...
Hi, I've tried specifying a timeout on connection to GDBServer, but it seems to be ignoring it, always exists with after 1-3 secs...
Read more >
Eclipse JTAG Debugging the ESP32 with a SEGGER J-Link
Eclipse with GDB is a great tool helping me to understand the code execution on the ESP32. It requires a JTAG debug probe...
Read more >
[ISSUE] Failed to launch OpenOCD GDB Server: Timeout
[ISSUE] Particle: Flash for debug fails and puts device in error state. Also related to Failed to launch OpenOCD GDB. Server: Timeout.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found