bounding with pc-ble-driver

RE: bounding with pc-ble-driver

jpo38 — Mon, 12 Jun 2017 08:00:49 GMT

@HangBui: I see you released v2.0.0 of pc-ble_driver. Is that supposed to support bounding smartly?

RE: bounding with pc-ble-driver

jpo38 — Wed, 13 Jul 2016 13:38:55 GMT

@Hungbui: Done: www.nordicsemi.com/.../30404

RE: bounding with pc-ble-driver

Hung Bui — Wed, 13 Jul 2016 13:31:57 GMT

@jpo: Yes, you can create one but it's the same system as devzone. I talked with the developers, about the request. It doesn't seem we will have something soon as we're focusing on finishing the nRFConnect now.

RE: bounding with pc-ble-driver

jpo38 — Wed, 13 Jul 2016 09:28:14 GMT

@Hungbui: Thanks. Should I create an official support ticket (on nordicsemi.no) for "please add examples" (even if it cannot be covered for next release)?

RE: bounding with pc-ble-driver

Hung Bui — Wed, 13 Jul 2016 08:30:51 GMT

@jpo: I'm sorry that our resource for the pc_ble_driver is not as much as we have on the nRF5 SDK. However, you can also have a look at the nRF_Connect project here.

The project uses the pc_ble_driver_js as the base. It's open source, you can actually find some reference code for your project by looking at the source on github.

Regarding your questions, I would suggest you to create another case to ask. Most of it related to how BLE works. There are some books covered them. I would suggest this and this

RE: bounding with pc-ble-driver

jpo38 — Mon, 11 Jul 2016 17:30:12 GMT

@HangBui: By the way the example should also cover many other questions I'll have next (How to make keys persistent between two sessions? How to know if a device is already bonded upon search process? How to clear all bonding keys on the driver side?...)

RE: bounding with pc-ble-driver

jpo38 — Mon, 11 Jul 2016 17:27:37 GMT

@HangBui: Thanks for the answer. It would be really great if you could consider adding an example for the coming release. This bonding process does not seem to be very obvious and it would really help to have a working example to adapt. I'm already using the driver from github (as I use s130v2). I'll probably try to move to the latest version and try again. Could you provide me a link to the example doing bonding as the central (firmware team members are on vacation....I'm alone to try to work this out ;-)

RE: bounding with pc-ble-driver

Hung Bui — Mon, 11 Jul 2016 14:15:07 GMT

@jpo: Unfortunately we don't have an example. We do have example for central device which handle bonding but it uses devicemanager/peermanager. You may need to look into those example to figure out. In addition, I just checked with the developer, if you are using the pc-ble-driver v0.5 downloaded from our website. Bonding may not work. We had some issue with that.

You may need to use the one on our github. You have two option, either you compile this to get the dll, or you use this and get the dll precompiled by callling "pip install pc-ble-driver-py"

I would suggest you test and make sure things work by directly use S130/S132 as the central(without the driver, you write code on the nRF5 chip) so you know how bonding is handled, after that you can move to the driver.

RE: bounding with pc-ble-driver

jpo38 — Mon, 11 Jul 2016 13:01:05 GMT

@HungBui: See edited question, I'm having a hard time finding the appropriate parameters for sd_ble_gap_authenticate (and it will likely be the same later when I'll have to call sd_ble_gap_sec_params_reply). Could you and/or link me to a working example? I'm surprised there is no example establishing connection with "Nordic Mouse" as there is one for "Nordic HRM".

RE: bounding with pc-ble-driver

jpo38 — Mon, 11 Jul 2016 13:00:40 GMT

@metch: See edited question, I'm having a hard time finding the appropriate parameters for sd_ble_gap_authenticate (and it will likely be the same later when I'll have to call sd_ble_gap_sec_params_reply). Could you and/or link me to a working example? I'm surprised there is no example establishing connection with "Nordic Mouse" as there is one for "Nordic HRM".

RE: bounding with pc-ble-driver

Hung Bui — Fri, 08 Jul 2016 11:38:40 GMT

Thanks metch, @Jpo: Please follow the message sequence chart that metch pointed to.

RE: bounding with pc-ble-driver

jpo38 — Fri, 08 Jul 2016 06:32:26 GMT

Thanks metch

RE: bounding with pc-ble-driver

Christopher — Thu, 07 Jul 2016 21:22:46 GMT

To complete the @hungbui's answer, you should have a look at some sequences diagrams available here: infocenter.nordicsemi.com/index.jsp

For instance, the "GAP Central Bonding: Just Works" sequence chart (for S130 as central device) describes how to use the sd_ble_gap_authenticate function when the connection is established.

RE: bounding with pc-ble-driver

jpo38 — Thu, 07 Jul 2016 17:31:23 GMT

Thanks for the reply, I'll look into that. Should sd_ble_gap_authenticate be called before or after device is connected?

RE: bounding with pc-ble-driver

Hung Bui — Thu, 07 Jul 2016 10:29:14 GMT

Hi jpo38,

To initialize bonding, you do it the same way you do as a central device, please have a look at our device_manager_central.c library.

You need to call sd_ble_gap_authenticate() to initialize bonding, store bonding information (the keys) and then call sd_ble_gap_encrypt() to re-encrypt the link based on the keys you stored.