Any known issues using J-Link Lite or with nRF52810?

[rich_l]

Development Environment: Segger Embedded Studio 4.16

Debugger:  Segger J-Link Lite/ Segger J-Link Pro

Debugging a custom nRF52810 board using SWD interface.

I am experiencing sporadic issues running the j-Link debugger to debug code on the nRF52810 through SES (I.e. Target->ConnectJLink or Debug->Go).  The issue randomly occurs (more times than not it occurs) and I get the following error:

I've tried doing this running SES on different operating systems (Mac OS and Windows) as well as tried different J-Link devices, USB cables etc.  I've tried power cycling the target hardware and disconnecting/reconnecting the USB cable from the J-Link and sometimes the problem goes away for a short time (meaning I am able to connect and debug code) but soon returns again.

I was wondering if anyone else out there is having similar issues debugging on the nRF52810?

[awneil]

rich_l said:

anyone else out there is having similar issues debugging on the nRF52810?

No.

As far as the debug connection is concerned, it's just another Cortex-M4.

[Sigurd]

If you have long SWD wires, then you could try to decrease the SWD clock frequency, and see if that improves anything. (In SES, you can do this under project options -> Debug-> J-Link)

[rich_l]

Thanks Sigurd.  I have found the issue and turns out to be intermittent hardware.