• State Verified Answer
  • Replies 9 replies
  • Subscribers 63 subscribers
  • Views 2821 views
  • Users 0 members are here
Attachments (3) Download All
Nordic Case Info
  • Case ID: 254321
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

There are connectivity problems with MacBook Pro and nRF52840 DK with running examples

RAlexeev

I can not connect to nRF52840 DK with running Bluetooth: Peripheral HIDS keyboard example from macOS. And also with some other examples which I tried, but I chose this one just for describing the problem. In the case of the example Bluetooth: Peripheral HIDs I got a window on macOS to type 6-digit passkey and it'd connected. I tried both nRF Connect SDK 1.3.0 and master branch. Both Android devices and Linux laptop could connect and bond with nRF52840 DK with running the same example, but not MacBook Pro.
Firstly, most of the time MacBook Pro shows address instead of a device name.

Then I try to connect MacBook Pro to nRF52840 DK and it looks like connected, but round progress bar icon on the right side from Bluetooth address spins all the time.


Fullscreen connected_log.txt Download 
Connected 38:f9:d3:ea:48:5c (public)

And there's not pairing stage after it. And after a while, this device disappears from the list of devices completely, but there's nothing new in UART log from nRF52840 DK.



When I turn off Bluetooth on MacBook Pro then I see disconnection log from nRF52840 DK.

Fullscreen disconnected_log.txt Download 
Disconnected from 38:f9:d3:ea:48:5c (public) (reason 19)

There's neither a stage of pairing nor a numeric comparison on MacBook Pro and nRF52840 unlike other Android devices, with whom MacBook Pro does pairing and there's the numeric comparison, but after several seconds it also becomes disconnected for some unknown reasons.

I want to ask you whether you have faced the same problems with connecting and pairing from macOS to nRF52840 DK or not. And how to handle them.

  • 0

    Hello, 

    My apologies for the late reply. I have not been able to look into your case but will do so tomorrow (Tuesday). I'm sorry for the inconvenience. 

    Kind regards,
    Øyvind

  • 0

    Hi!

    I will look into this issue. Apologies for the delay. 

    Could you state which version of MacOS you use? And if possible, could you test with an iOS device and another Mac? 

    I will attempt to reproduce and look into the problem here.

    Best regards,
    Carl Richard

  • 0 in reply to Carl Richard

    Thanks for your response! Unfortunately, now I haven't got any other Apple devices to test Bluetooth connection with them. But I can send to you my Mac system configuration:

    Fullscreen macOS_info.txt Download 
    System Software Overview:

  System Version:	macOS 10.15.6 (19G73)
  Kernel Version:	Darwin 19.6.0
  Boot Volume:	Macintosh HD
  Boot Mode:	Normal
  Computer Name:	CAB-WSM-0001172
  Username:	xxxxxxxxxx (xxxxxxxxxx)
  Secure Virtual Memory:	Enabled
  System Integrity Protection:	Enabled


Hardware Overview:

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro15,1
  Processor Name:	8-Core Intel Core i9
  Processor Speed:	2,3 GHz
  Number of Processors:	1
  Total Number of Cores:	8
  L2 Cache (per Core):	256 KB
  L3 Cache:	16 MB
  Hyper-Threading Technology:	Enabled
  Memory:	16 GB
  Boot ROM Version:	1037.147.1.0.0 (iBridge: 17.16.16065.0.0,0)
  Serial Number (system):	XXXXXXXXXXXX
  Hardware UUID:	XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
  Activation Lock Status:	Disabled


  Apple Bluetooth Software Version:	7.0.6f7
  Hardware, Features and Settings:
  Address:	38-F9-D3-EA-48-5C
  Bluetooth Low Energy Supported:	Yes
  Handoff Supported:	Yes
  Instant Hot Spot Supported:	Yes
  Manufacturer:	Broadcom
  Transport:	UART
  Chipset:	4364B0
  Firmware Version:	v87 c4409
  Bluetooth Power:	Off
  Auto Seek Pointing:	On
  Remote wake:	On
  Vendor ID:	0x05AC
  Product ID:	0x007B
  Bluetooth Core Spec:	5.0 (0x9)
  HCI Revision:	0x1139
  LMP Version:	5.0 (0x9)
  LMP Subversion:	0x2057
  Auto Seek Keyboard:	On

    If you need any other info to reproduce errors, let me know.

  • 0 in reply to RAlexeev

    Hello, again!

    I think we've managed to pinpoint the issue.

    In short: It seems to be a problem with the NCS HID keyboard example, as it does not require encryption to work. However, the mac does, but it does not request it. Hence, the nRF52 thinks it is connected while the mac rejects all commands.

    We will look further into the issue tomorrow.

    Best regards,
    Carl Richard

  • 0 in reply to Carl Richard

    Thanks for your answer! It's great that you figured out an error. Should I fix NCS HID keyboard example somehow to provide encryption? And could you point me out how to do it?

Related