Compiler/CC2540: pairing fails when iOS is peripheral and CC2540 acts as central

The snapshot is attached here.

Hi,

What iOS device are you using? Can you provide detail regarding how to reproduce this from our end?

I have tried use simpleBLECentral with modified gapbond parameters to those you are using, however, I can't seem to get it to fail.
I tested it with iPhone 7 and use lightblue to create virtual peripheral on the iPhone.

According to the log, the error code reason 0x08 indicates the failure is due to Unspecified Reason. The problem is likely in the iOS device but I can't say for sure until we reproduce this here.

Hi Christin,

Thanks for your reply. 

We have tested it using iPhone 5s and iPhone 7 running iOS 11.3. It advertises 1 service including 2 characteristics. We have implemented using CBPeripheralManager as recommended by Apple:

https://developer.apple.com/library/content/documentation/NetworkingInternetWeb/Conceptual/CoreBluetooth_concepts/PerformingCommonPeripheralRoleTasks/PerformingCommonPeripheralRoleTasks.html

Indeed, we are using this library to implement BLE interfaces:

Meanwhile, we will also try to reproduce the scenario using the SimpleBLECentral and LightBlue as you did. Is SimpleBLECentral project supposed to work with CC2540EMK-USB Dongle with no changes? I am not able to use it!

Thanks

Hi,

I was using smartRF05 with CC2541EM instead, since the BLE STACK is the same, I just took what I have now and started working on it.

You will need some modification in order to have simpleBLECentral connects to your light blue especially if you are using the USB dongle.

But you can just use your simple_central to connect with virtual peripheral made from light blue. What we are trying to see is that pairing failure, so I don't think it's important to make it discover your service.

BTW, can you attach the whole sniffer file (.psd file). That might give us more clue.

Hi,

Attached, please find the sniffer data. I did the test with a virtual peripheral on LightBlue and I've got the same error. 

According to my understanding, the iPhone will request/force authentication upon discovery of encrypted services/characteristics. Am I right? As you can see in the Sniffer data, there are some message exchange related to pairing at the beginning and some more when I start the service discovery. This is where I received the pairing failure. If I do not start service discovery, iPhone will drop the connection. I noticed that if I enable the Battery service notification the iPhone will keep the connection.

In SimpleBLECentral, it seems bonding is not done. So, it won't support auto re-connection.

Thanks

Sniffer_ios.psd

Here's another sniffer data where I do not start the service discovery. There are almost the same messages exchanged. There is a termination message from S->M at the very end due to not discovering the services.

Sniffer_ios_nodiscovery.psd

Hi,

Can you share your virtual LightBlue configuration? I would like to reproduce it here.

BTW, can you share the sniffer log of your original problem as well?

Thanks!

Sorry for my late reply. The first sniffer log I shared with you was from the original problem. I couldn't find any way to share the LightBlue configuration with you. Please let me know how I can do that.

Thanks

Can you write down how you configure the lightblue (what service did you include)?
Also the snifferlog, I would like to have the whole .psd file instead of screenshot

Hi,

Is your issue solved? If not, can you provide step by step guide for me to reproduce using lightblue?