nRF Connect (Mac v. 2.4.0) can't scan

[Rob Lewis]

Just installed Mac v. 2.4.0 of nRF Connect, and the "Start Scan" button is disabled. Here's the log:

2018-07-05T13:43:15.834Z INFO Application data folder: /Users/rob/Library/Application Support/nrfconnect/pc-nrfconnect-ble
2018-07-05T13:43:15.987Z DEBUG App pc-nrfconnect-ble v2.2.0 official
2018-07-05T13:43:15.987Z DEBUG App path: /Users/rob/.nrfconnect-apps/node_modules/pc-nrfconnect-ble
2018-07-05T13:43:15.987Z DEBUG nRFConnect 2.4.0 is supported by the app (^2.4.0)
2018-07-05T13:43:15.987Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar
2018-07-05T13:43:15.987Z DEBUG HomeDir: /Users/rob
2018-07-05T13:43:15.987Z DEBUG TmpDir: /var/folders/hh/xsjc40cx0k19q4k8hfcck0hh0000gn/T/
2018-07-05T13:43:16.005Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port
2018-07-05T13:43:16.006Z VERBOSE Could not fetch serial number for serial port at /dev/tty.RobsiPhone-WirelessiAP
2018-07-05T13:43:16.006Z ERROR Error while probing devices: Error occured when get serial numbers. Errorcode: CouldNotOpenDLL (0x7)
Lowlevel error: JLINKARM_DLL_NOT_FOUND (ffffff9c)

System is a 2015 MacBook Pro with macOS 10.13.5.

My understanding is that "DLL" is a Windows term, not appropriate for Mac.

[tesc]

Hi,

I recommend version 6.22g because that is the latest version known to work flawlessly with nRF Command Line Tools. (There were some issues there lately, with the newest J-Link drivers.)

When you have installed the J-Link Software and Documentation Pack nRF Connect should work. If you are still seeing problems with it, please provide the logs and full description of what you do and what version of the J-Link driver you are currently using.

Regards,
Terje

[Rob Lewis]

Sorry, still doesn't work after installing 6.22g and removing the newer version. I launch nRF Connect, then click the Launch Bluetooth Low Energy button. The "Start scan" button is still grayed out/disabled. I verified that the Mac's Bluetooth is on.

The log is different this time: instead of complaining about a DLL it now complains about serial numbers for serial ports(?)

2018-07-09T17:23:39.238Z INFO Application data folder: /Users/rob/Library/Application Support/nrfconnect/pc-nrfconnect-ble
2018-07-09T17:23:39.400Z DEBUG App pc-nrfconnect-ble v2.2.0 official
2018-07-09T17:23:39.400Z DEBUG App path: /Users/rob/.nrfconnect-apps/node_modules/pc-nrfconnect-ble
2018-07-09T17:23:39.400Z DEBUG nRFConnect 2.4.0 is supported by the app (^2.4.0)
2018-07-09T17:23:39.400Z DEBUG nRFConnect path: /Applications/nRF Connect.app/Contents/Resources/app.asar
2018-07-09T17:23:39.400Z DEBUG HomeDir: /Users/rob
2018-07-09T17:23:39.400Z DEBUG TmpDir: /var/folders/hh/xsjc40cx0k19q4k8hfcck0hh0000gn/T/
2018-07-09T17:23:39.418Z VERBOSE Could not fetch serial number for serial port at /dev/tty.Bluetooth-Incoming-Port
2018-07-09T17:23:39.418Z VERBOSE Could not fetch serial number for serial port at /dev/tty.RobsiPhone-WirelessiAP

[tesc]

Hi,

From what I can see that is the same log as previously, just without the Segger J-Link errors.

I do not see any log entries for trying to establish serial port connection to a local device. What device are you using for connectivity, does it list properly in the "Select device" dropdown, and does anything fail if selecting it? nRF Connect for desktop doesn't use BLE hardware on the computer itself, rather it uses an nRF DK or Dongle for providing BLE capabilities.

Regards,
Terje

[Rob Lewis]

Well I guess that's the problem—somehow I missed the fact that external hardware is required! Is there something you recommend for a Mac? This is basically for hobby & independent development so I'm not looking for something expensive.

[Rob Lewis]

Do you know if there is firmware that could be flashed to this device to make it usable as a dongle? I looked for your dongles online and it seems the distributors don't have them in stock. And which of your dongles has the most capability and/or newest architecture? I'm interested in experimenting with Bluetooth Mesh.

[tesc]

Hi,

I am very sorry for the delayed response.

I am afraid I do not have any experience with the device that you mentioned. First and foremost we recommend our own DKs and Dongles, as those are what our firmware is originally made for. Other nRF devices might require modifications to the firmware (depending on what pins they use for UART), J-Link programmers in order to flash the firmware, etc. but that is all dependent on the board in question.

I think it could at least be worth having a look at the nRF52 Dongle, which is intended for exact this purpose of connectivity device.

For nRF development I recommend to use at least one nRF52 DK, as it is supported by our SDKs (including the nRF5 SDK for Mesh) and comes with a J-Link programmer that can be used to program other boards during development. You may of course find other boards out there as well, that better suits your specific needs.

Regards,
Terje