Unable to start debugging

[Tage Korsdal Nielsen]

When starting debug inside VC I get this:

My launch.json looks like this:

{
	"folders": [
		{
			"path": "."
		},
		{
			"path": "../ncs"
		},
		{
			"path": "../lbs"
		}
	],
	"settings": {
		"nrf-connect.applications": [
			"${workspaceFolder}\\bluejay"
		],
		"nrf-connect.toolchain.path": "${nrf-connect.toolchain:2.5.1}",
		"files.associations": {
			"array": "c",
			"string_view": "c",
			"initializer_list": "c"
		},
		"nrf-connect.debugging.bindings": {
			"${workspaceFolder}/bluejay/b_ida0105_project": "Launch b_ida0105_project"
		}
	},
	"launch": {
		"version": "0.2.0",
		"configurations": [
			{
				"type": "nrf-connect",
				"request": "launch",
				"name": "Launch b_ida0105_project",
				"config": "${workspaceFolder}/bluejay/b_ida0105_project",
				"runToEntryPoint": "main"
			},
			{
				"type": "nrf-connect",
				"request": "launch",
				"name": "Launch b_ida0105_wp2_no_secure",
				"config": "${workspaceFolder}/bluejay/b_ida0105_wp2_no_secure",
				"runToEntryPoint": "main"
			}
		]
	}
}

I use nRF v2.5.1.

Segger j-link base.

Debug works on the nRF eval/DK boards.

I can run "west debug" and debug in gdb.

Programming works fine in all cases.

[Tage Korsdal Nielsen]

After uninstall/install of nRF VS extensions I now get this:

[Elfving]

Hello Tage,

Debug works on the nRF eval/DK boards.

So you are using an external programmer, like a JLink Commander or similar? Did this used to work for you in the past?

This reminds me a lot of this previous case of mine. What I suggested to him (and what I assumed the issue was related to) was the debugger being connected incorrectly. Though if you both are seeing this issue maybe there is something wrong with the newer version of the VSC extension.

Regards,

Elfving

[Tage Korsdal Nielsen]

Hello Elfving,

Yes I am using this external "j-link BASE" black box from Segger.

I am tasked with moving us to V2.5.1.

I have a colleague still working on V2.3.0 - and it works for him. 

So yes - it looks a lot like the case you linked.

I will try to debug a nRF52DK_52832 board with the Segger j-link box and update here.

Thank you.

Rgds Tage

[Elfving]

Tage Korsdal Nielsen said:

I will try to debug a nRF52DK_52832 board with the Segger j-link box and update here.

Great, let me know if that works.

Tage Korsdal Nielsen said:

I have a colleague still working on V2.3.0 - and it works for him. 

Could one of you also try doing it with the other SDK just to be sure that its related to the SDK, and not the environment/HW?

Regards

Elfving

[Tage Korsdal Nielsen]

Debugging a nRF52DK_52832 board with the Segger j-link box works!

Debugging my target from VC/nRF extension fails for me on bot NCS v2.3.0 and v2.5.1.

Rgds

Tage

[Tage Korsdal Nielsen]

I tried starting debugging while having windows dbgview running.

It seems jlinkgdbserver is started with a target SWD speed of 12000kHz:

MS_MIDebug: 1: (124) Starting: "C:\Program Files\SEGGER\JLink\JLinkGDBServerCL.exe" -if swd -device nRF52832_xxAA -select usb=50123743 -speed 12000 -port 49330 -singlerun -nogui -halt -noir -silent -rtos c:/Users/tnielsen/.vscode/extensions/nordic-semiconductor.nrf-connect-2023.11.301-win32-x64/debug/jlink/x64/zephyr_rtos.dll

This is too fast for my target setup -  I tried starting jlink with 12000kHz and the target could not connect.

How do I change that?

Rgds Tage

[Tage Korsdal Nielsen]

Added this to configurations in launch.json:

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

Now it works!

rgds Tage