nRF Connect for Desktop macOS Error while setting up device xyzzy: No serial port available for device with serial number xyzzy

RE: nRF Connect for Desktop macOS Error while setting up device xyzzy: No serial port available for device with serial number xyzzy

panchoy — Mon, 22 Jul 2019 18:00:18 GMT

Great. Thanks for the clarification. I was just curious and I was exploring various possibilities. Now, I know what the possibilities (and the limitations) are for each of the pieces.

I appreciate all of your comments.

RE: nRF Connect for Desktop macOS Error while setting up device xyzzy: No serial port available for device with serial number xyzzy

Stian Røed Hafskjold — Mon, 22 Jul 2019 11:52:22 GMT

Hi, I'm not sure what you are trying to accomplish. The "Bluetooth Low Energy" app inside nRF Connect is a BLE central application that uses nRF devices as hardware. It flashes the nRF with a connectivity firmware and communicates over UART. So you need a UART connection between the PC and the nRF device. It's only supported by Nordic development boards: https://infocenter.nordicsemi.com/topic/ug_nrfconnect_ble/UG/nRF_Connect_BLE/nRF_Connect_intro.html?cp=6_3_0

If you want to use the "Programmer" app in nRF connect to flash the custom board, there's currently limited support for external JLinks, so I would recommend you to use the nrfjprog command line tool instead: http://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Command-Line-Tools/Download#infotabs

If you want to use "nRF connect Bluetooth Low Energy" central application to test the BLE connection to your custom board (as you are doing with nRF Connect running on your cellphone), you will need a separate Nordic development board connected to your PC running the nRF Connect central application. And then you can connect to your custom board over BLE.

RE: nRF Connect for Desktop macOS Error while setting up device xyzzy: No serial port available for device with serial number xyzzy

panchoy — Fri, 19 Jul 2019 21:57:43 GMT

Both the native (host) macOS Mojave and the virtual (guest) VMWare Windows 7 see the J-Link and the nRF52 just fine via the USB port (at different times, of course, at one time connected to the Mac and at another time connected to Windows 7).

Please see the screen shots and please note the serial version of the J-Link v.10.10, which has its VCOM port enabled.

I use Segger Embedded Studio on macOS to work with the nRF52 through the J-Link without any problem,.

For some reason, nRF Connect for Desktop macOS seems to be the only app that doesn't like this setup. Please see the lasts screen shot. It would be great to find out what the reason is.

Please note the error reported by nRF Connect for Desktop:

Cannot read property 'toLowerCase'.

1. Where does this property reside?

2. Who manages this property and who decides whether it's readable or not?

3. Why can't nRF Connect for Desktop "read" this property?

4. Does this property even exist (but it's somehow unreadable) or is it totally missing (and therefore without any hope of being read at all)?

Thanks.

RE: nRF Connect for Desktop macOS Error while setting up device xyzzy: No serial port available for device with serial number xyzzy

Bjørn Kvaale — Fri, 19 Jul 2019 08:31:10 GMT

Have you tried with a different USB port or a different computer? It may be that the COM port on your J-Link is deactivated maybe. Take a look at this link for more info regarding this.

RE: nRF Connect for Desktop macOS Error while setting up device xyzzy: No serial port available for device with serial number xyzzy

panchoy — Tue, 16 Jul 2019 23:19:16 GMT

This is a custom board with the NRF52832_xxAA_REV1 certified by Rigado.

I don't have one of your Dev Kits.

I'm using a J-Link Plus 9.3.

Your mobile nRF Connect sees it perfectly via BLE.

Thanks.

RE: nRF Connect for Desktop macOS Error while setting up device xyzzy: No serial port available for device with serial number xyzzy

Bjørn Kvaale — Tue, 16 Jul 2019 13:06:12 GMT

This is a custom board, I'm guessing? What J-Link device are you currently using? Do you get the same issue if you use one of our Dev Kits?