nRF connect programmer fails to get serial numbers for nRF52840

[TimBG]

The device communicates okay with JLINK commander v7.00a although at the beginning it always says "Connecting to J-Link via USB...Out of sync , resynchronizing...
J-Link communication resynchronized" before moving on. Not sure if this is related..

nRF connect is version 3.61 Below is a copy of the log from nRF connect programmer:

2021-05-05T15:01:59.380Z INFO Application data folder: C:\Users\tlechman\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2021-05-05T15:01:59.452Z DEBUG App pc-nrfconnect-programmer v1.4.8 official
2021-05-05T15:01:59.452Z DEBUG App path: C:\Users\tlechman\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2021-05-05T15:01:59.452Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-05-05T15:01:59.452Z DEBUG nRFConnect path: C:\Users\tlechman\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-05-05T15:01:59.452Z DEBUG HomeDir: C:\Users\tlechman
2021-05-05T15:01:59.452Z DEBUG TmpDir: C:\Users\tlechman\AppData\Local\Temp
2021-05-05T15:01:59.488Z INFO Using nrfjprog library 10.12.1, pc-nrfjprog-js 1.7.6
2021-05-05T15:02:02.187Z INFO Using nrfjprog to communicate with target
2021-05-05T15:02:13.192Z ERROR Error while probing devices: Error occured when get serial numbers. Errorcode: Could not execute the function due to too many calls in line (0xe)

2021-05-05T15:02:13.193Z INFO Target device closed.
2021-05-05T15:03:23.856Z INFO Using J-Link Software version 7.0
2021-05-05T15:04:35.522Z INFO Segger serial:  601003234
2021-05-05T15:04:35.523Z INFO Segger speed:  2000  kHz
2021-05-05T15:04:35.523Z INFO Segger version:  J-Link V11 compiled Apr 13 2021 17:20:05
2021-05-05T15:04:35.524Z INFO Core probed: 601003234
2021-05-05T15:04:35.524Z INFO Core RAM: 256KiB
2021-05-05T15:04:35.524Z INFO Core ROM: 1024KiB in pages of 4KiB
2021-05-05T15:05:09.335Z INFO Model: NRF52840_xxAA_REV2.
2021-05-05T15:06:26.140Z INFO Core0: Reading device non-volatile memory. This may take a few seconds.
2021-05-05T15:07:23.448Z INFO Core0: UICR has been read. Click read button to read full non-volatile memory.

[TimBG]

Seems like this is a weird interaction with Parallels desktop for mac preventing the windows side of my computer from communicating to the jtag.. It might be related to power save features from Parallels? The issue only occurs if my laptop is unplugged. That is solution enough for me for now but if someone knows more about what parallels is doing that would be greatly appreciated.