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

[Pedro]

Hi Marte Myrvold ,

After a long wait still no answer. Any suggestion to solve the problem?

Thanks and kind regards.

[Marte Myrvold]

Hi Pedro,

I have asked the developers for an update.

Best regards,
Marte

[Marte Myrvold]

Hi Pedro,

I got an update now.

The developers have not been able to figure out what the issue is yet, but they are still working on it.

Common for the reports of this issue is a fairly high port number. To rule out any issues with the port selection mechanism, can you try hardcoding the port number to the standard JLink GDB port?

To do so you need to bind a custom launch configuration to the debug button by clicking the cogwheel on the right hand side of the action:

Then, in the generated launch configuration, you need to add the following fields right after the config field:

"serverAddress": ":2331",
"serverArgs": "-if swd -device ${device} -select usb=${snr} -speed 12000 -port 2331 -singlerun -nogui -halt -noir -silent -rtos ${rtosPlugin}"

Best regards,
Marte

[Pedro]

Hi Marte,

I followed your instructions but unfortunately got same error

[Marte Myrvold]

Hi,

Thank you for testing.

The developers have some further questions as well.

• Do you have any other issues communicating with the device, or is it only when trying to debug you are seeing an issue?
• Is the device connected to the computer through an USB hub?
• Can you confirm that no other processes are trying to communicate with the device? E.g. if nRF Connect for Desktop or similar is running in the background.

Best regards,
Marte

[Pedro]

Hi Marte,

Marte Myrvold said:

Do you have any other issues communicating with the device, or is it only when trying to debug you are seeing an issue?

It's only when trying to debug. I can flash the device without problems.

Marte Myrvold said:

Is the device connected to the computer through an USB hub?

I've tried though an USB hub and directly to PC.

Marte Myrvold said:

Can you confirm that no other processes are trying to communicate with the device? E.g. if nRF Connect for Desktop or similar is running in the background.

Just vscode is open.

Thanks for your support!

Kind regards,

Pedro.

[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