nRF Connect displays blank window

[Rob Lewis]

I just received my nRF52840 dongles and am trying to get nRF Connect going (macOS El Capitan).

Installed the J-Link package per instructions, and the nRF Connect 2.6.0 app. So far I've tried the Bluetooth Low Energy and Programmer apps.

When I click 'Select device' in the main window, it shows the ID 'C850B87ED8D6', which I presume is the dongle's MAC address? It is plugged into a USB port on the Mac keyboard (which works fine with, e.g., Arduino devices).

When I click on that device, it displays a small window with some information too quickly for me to read it (I think it may say 'Generic Access' and 'Generic Attribute'), and then opens a large, completely empty window titled 'nRF Connect v2.6.0 - Bluetooth Low Energy'.

If I select 'View | Reload' I get back to the main window. Here I select 'Launch other app' and select 'Programmer'. The log says 'Using nrfjprog library 9.8.1, pc-nrfjprog-js 1.4.1'

If I now select the dongle device, the Device Memory Layout just shows crawling diagonal bars. The pop-down menu shows device information, but Communication Type says 'unknown'.

That's the extent of what I've been able to do.

[Mttrinh]

Hi,

We haven't seen this issue before. Can you provide me with your Mac hardware and the nRF52840 dongle version you are using?

[Rob Lewis]

I didn't know there were different versions of the dongle. Can you tell me how to determine this?

The Mac is a mid-2007 iMac with 6GB RAM, running the El Capitan OS. Old, I know, but works fine. In years of using it I have found one case where software that was advertised to run on any Core 2 CPU actually seems to require the expanded instruction set of a newer Intel device: the Android Emulator that comes with the Android Studio IDE.

[Mttrinh]

You can find the version of the dongle on the label on it. See image attached(version 0.6.0).

Have you tried it with other Mac's to see if it makes any difference? 

[Rob Lewis]

The dongle version is 1.0.0. The software appears to work on a newer Mac, so perhaps it's the instruction set issue (your developers might know). Or it could be something else.

[Mttrinh]

I have forwarded this to the developers. We don't have a fix for this at the moment, so I suggest you to work with a newer Mac while they have a closer look at the issue.