nRF Connect for Desktop reports "Connect a Nordic development kit"

[Christopher Hunt]

Hi there,

Having just migrated from an x86 Mac to an M1 Mac, I'm now having difficulty getting the programmer app of nRF Connect for Desktop to detect a device. When I attempt to, it asks me to "Connect a Nordic development kit" to your computer. I've got a number of these installed at /opt/nordic. Here's what is reported in the log window:

18:19:18.153

Failed to get the library versions: JLINKARM_DLL_COULD_NOT_BE_OPENED

18:19:18.346

Application data folder: /Users/huntc/Library/Application Support/nrfconnect/pc-nrfconnect-programmer

18:19:20.205

Error while probing devices: EnumerateWorker json error

Any ideas? I've installed nrfjprog and jlink. I can also flash to my device via other means, so the device is indeed there.

Thanks!

[Marte Myrvold]

Hi,

Do you have any JLink debuggers connected to your computer that are not connected to another device, or any unused JLink devices connected? We have had reports of similar issues, and the developers found that this was often caused by unused JLink devices connected to the computer. There will be a new release with a fix for this, but until then the solution suggested by the developers is to disconnect all other JLink devices. If this does not solve the issue, please let me know.

Best regards,

Marte

[Christopher Hunt]

Thanks for the reply. I don’t have any other JLink debuggers connected. 

[erickcinco]

I am experiencing the same behavior. Was running nRF Connect for Desktop BLE v3.0.0 just fine up until this morning.

A reboot of my computer sorted things out.

[Christopher Hunt]

Unfortunately rebooting doesn’t solve my issue. 

[Marte Myrvold]

Hi,

We have just released v3.9.0 of nRF Connect for Desktop, which includes fixes to make enumeration more robust and increase the timeout when enumeration takes a long time. The version is not on the download page yet, but you can update to it directly in the app, and you can find the release and release notes here nRF Connect for Desktop releases.

The developers have also found that the JLink version that is bundled with the latest version of nRF Command Line Tools causes errors in nRF Connect for Desktop. They are working on a fix for this as well, but a temporary workaround is to downgrade JLink to a known working version, v6.88a, from https://www.segger.com/downloads/jlink.

Best regards,

Marte