GDB error when trying to launch debugger

[Pedro]

Hi,

I'm developing using vscode and Nordic pluggin, Windows 10 OS. When I try to launch debugger, I get the following message:

"Unable to start debugging. Unexpected GDB output from command "-target-select-extended-remote 127.0.0.1:63241". Remote communication error. Target disconnected.: No such file or directory."

The launch configuration is the default:

	"launch": {
		"version": "0.2.0",
		"configurations": [
			{
				"type": "nrf-connect",
				"request": "launch",
				"name": "Launch build",
				"config": "${workspaceFolder}/build",
				"runToEntryPoint": "main"
			}
		]
	}

How can I make it run?

Thanks in advance,

Pedro.

[Marte Myrvold]

Hi Pedro,

Are you trying to debug a DK or a custom board? Is the device directly connected to the computer with an USB cable, or are you using an external debugger?

Please provide support information from the VS Code extension:

1. Open the command palette (Ctrl + Shift + P or View > Command Palette).
2. Write "nRF Connect: Generate support information" and press enter.
3. Copy the entire support information output.
4. Upload it here using Insert > Code or upload a .txt file with Insert > Image/video/file.

Make sure to remove confidential information you do not want to be shared in a public case.

Best regards,
Marte

[Pedro]

Hi Marte,

Thanks for your help. I've attached the generated support information.

support information.zip

[Oguzhan Turk]

This didn't solve my problem either.

[Pedro]

Hi Marte! Any update?

[Pedro]

Just in the case it helps, only once, this message appeared. But it never appeared again.

[Marte Myrvold]

Hi,

No update from the developers. They have not been able to reproduce the issue, which makes it hard to figure out what the issue is.

Best regards,
Marte

[Elith]

We are having the same issue, but only with our J-link Compact Plus - our J-link Pro works fine.

I have tried numerous things - what might have worked is to include the localhost address above changing it to:

"serverAddress": "127.0.0.1:2331",

And the speed I changed to 4000 instead. And I opened up the ports 2331-2333 on localhost in Windows 11 for everything, but it seems to be redundant because another J-link server rule was already there opening up all ports.

It seems to me that this is some kind of race-condition between opening up the J-link server through VSC and then connecting to it. Hence, VSC opens up J-link server, but before J-link server/programmer is ready, VSC tries to connect and hence the error of "no such file". Is it possible to somehow include a delay after opening op the J-link server when using the launch.json?

Or to just connect to an already running J-link server instance instead of opening up a new instance automatically?

EDIT: I forgot to say that I disabled IPv6 on the network interfaces. Have not checked if this actually did anything.