Unable to start debugging

RE: Unable to start debugging

Elfving — Mon, 05 Feb 2024 12:33:12 GMT

Great!

I am glad you got it working, and thanks for sharing your solution.

Regards,

Elfving

RE: Unable to start debugging

Tage Korsdal Nielsen — Mon, 05 Feb 2024 09:21:17 GMT

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

RE: Unable to start debugging

Tage Korsdal Nielsen — Fri, 02 Feb 2024 11:59:50 GMT

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

RE: Unable to start debugging

Tage Korsdal Nielsen — Fri, 02 Feb 2024 10:57:52 GMT

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

RE: Unable to start debugging

Elfving — Fri, 02 Feb 2024 10:08:21 GMT

[quote user="Tage Korsdal Nielsen"]

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

[/quote]

Great, let me know if that works.

[quote user="Tage Korsdal Nielsen"]

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

[/quote]

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

RE: Unable to start debugging

Tage Korsdal Nielsen — Thu, 01 Feb 2024 14:46:24 GMT

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

RE: Unable to start debugging

Elfving — Thu, 01 Feb 2024 14:34:20 GMT

Hello Tage,

[quote user=""]

Debug works on the nRF eval/DK boards.

[/quote]

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

RE: Unable to start debugging

Tage Korsdal Nielsen — Wed, 31 Jan 2024 15:36:25 GMT

Also, I needed to add this to launch.json:

"gdbPath": "c:/dev/ncs/toolchains/c57af46cb7/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gdb.exe"

Starting JLink GDB server, and arm-zephyr-eabi-gdb.exe worked - starting from inside VS/nRF extension give the error dialog above.

RE: Unable to start debugging

Tage Korsdal Nielsen — Wed, 31 Jan 2024 15:32:18 GMT

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