nrf51 as central iOS as peripheral pairing

RE: nrf51 as central iOS as peripheral pairing

Vitaliy — Fri, 07 Aug 2015 15:55:51 GMT

Please edit this answer and add that comment from the other thread how to edit this project to make it work, if someone will download this version

RE: nrf51 as central iOS as peripheral pairing

Vitaliy — Tue, 04 Aug 2015 11:36:09 GMT

Thanks, Petter. I created a separate question there: devzone.nordicsemi.com/.../

RE: nrf51 as central iOS as peripheral pairing

Petter Myhre — Fri, 31 Jul 2015 07:37:12 GMT

Please see my updated answer.

RE: nrf51 as central iOS as peripheral pairing

Petter Myhre — Wed, 29 Jul 2015 15:40:24 GMT

If you have other specific questions I would appreciate if you could add them separately, and add a reference to this question if it is relevant.

RE: nrf51 as central iOS as peripheral pairing

Petter Myhre — Wed, 29 Jul 2015 15:37:40 GMT

Ok. We sell hardware; you can run whatever application you want on it. Our SDK doesn't support everything and anything. Section 7 in the licence agreement for the SDK may be of interest.

I said I would try to look into this some more, so I could give you a more detailed description of the problem/problems. We haven't implemented this, so we haven't tested it. Yes, the Device Manager Peripheral library supports IRK, and the problem or part of the problem may be solved by examining it. I'm trying to help you, but the question you asked is very general, so I gave you general information on how to implement pairing and bonding on a central, together with information about an issue that I'm aware of, if the peripheral is an iOS device.

RE: nrf51 as central iOS as peripheral pairing

Vitaliy — Wed, 29 Jul 2015 14:24:26 GMT

We bought 1000 units of this modules and we "suggest" that it's sdk works. Is there any detailed description of this problem to understand what should we change in sdk to solve this problem?
It' looks like it implemented in Device Manager Peripheral library. Should we use it as a start or this problem has the other reason?

It looks like device manager not implements correctly "GAP Central Bonding: Passkey Entry (Peripheral display) or OOB MSC" sequence chart, is that true? I don't see any information to recognize real iOS address (identity key)

RE: nrf51 as central iOS as peripheral pairing

Petter Myhre — Wed, 29 Jul 2015 14:14:00 GMT

Yes. You can make your own "device manager central" or modify the library. It is just given as a suggestion on how to handle pairing and bonding.

RE: nrf51 as central iOS as peripheral pairing

Vitaliy — Wed, 29 Jul 2015 14:10:15 GMT

Is there any way to do it not "out of the box'?

RE: nrf51 as central iOS as peripheral pairing

Petter Myhre — Wed, 29 Jul 2015 14:06:54 GMT

Unfortunately, no.

RE: nrf51 as central iOS as peripheral pairing

Vitaliy — Wed, 29 Jul 2015 13:58:40 GMT

Thanks, does this problem (IRK) resolved in sdk v9.0.0?

RE: nrf51 as central iOS as peripheral pairing

Petter Myhre — Wed, 29 Jul 2015 13:44:23 GMT

There are some information. We have central examples in our SDK, like ble_app_hrs_c. We have message sequence charts that describe most of the procedures. See this. For central applications we have a device manager central library to handle pairing and bonding.

Unfortunately, this library will not work out of the box with iOS, since it uses IRK. Please see this. I try to look into this some more, but this is the answer I have for you at this point.

Edit 30.07.2015: I modified the ble_app_hrs_c example and the device manager central library. It seems to be working with peripherals that use random resolvable address.

If there are no bonds it will scan and connect normally, if there are any bonds, it will scan and connect with whitelisting using the addresses and IRKs for the bonded devices.

If a connection to a previously bonded IRK device is made, the device manager will use the IRK to identify the correct bond. Then it will not pair again, but just encrypt the link using the previously shared LTK.

Here is my project, it is given as is, and with limited testing. You can find the changes I made by searching for pemy. I used SoftDevice S120 2.1.0 and SDK 9.0.0. Unzip the project to \examples\ble_central.

Edit 07.08.2015: There was a bug in the project. Here is the project with a fix.

Be sure to use the device manager central library included in the folder. The project in \pca10028\s120\arm5_no_packs uses it, but for example the project in \pca10031\s130\arm5_no_packs doesn't. Just remove the library and add the one included in the folder instead.