pc-ble-driver binding

RE: pc-ble-driver binding

FormerMember — Tue, 20 Mar 2018 10:00:59 GMT

I just updated my answer, because my first one was not correct.

RE: pc-ble-driver binding

adrianco — Thu, 15 Mar 2018 14:46:40 GMT

Hi Kristin,

I am using the architecture described a serialized Bluetooth application, not writing a program/project to be downloaded into the nRF52832.

My application is running on a host running Linux and is linking pc-ble-driver library.

It is connected over serial line with the connectivity chip (nRF52832) loaded with the connectivity firmware connectivity_2.0.1_115k2_with_s132_5.0.hex.

In my host application:

-create an adapter with sd_rpc_adapter_create(transport_layer);

-open the adapter with sd_rpc_open(m_ble_adapter.m_adapter, status_handler, ble_evt_dispatch, log_handler);

where the ble_evt_dispatch is the handler for all the ble events.

Everything works fine for my application running on the linux host that inplements a peripheral, i create my custom profile(services), advertise, the central can connect to me and access the services that do not require binding. The only missing piece is doing the binding that is a mandatory requirement for one of our custom service.

Can you please be more specific on where the peer manager module should be added?

Into the pc-ble-driver library and recompile the library?(i am using the latest from github)

Is the connectivity firmware suporting the binding process or must be also updated/recompiled.

Thanks,

Adrian

RE: pc-ble-driver binding

FormerMember — Thu, 15 Mar 2018 13:37:51 GMT

1. Where i can get the keys the peer sent?

The parameters to provide to sd_ble_gap_sec_params_reply() is only struct's for where the keys will be stored. And it should not contain the keys. When passing them to sd_ble_gap_sec_params_reply(), the value can be '0'. The p_sec_keyset struct will contain the generated (and shared) key when the bonding process is finished, upon the event BLE_GAP_EVT_AUTH_STATUS(BLEEvtID.gap_evt_auth_status), see sd_ble_gap_sec_params_reply() documentation.

2. Is that a API to generate own keys?

Yes, the softdevice will generate the keys.

3. Are the keys stored in the connectivity chip and are they "power cycle" safe?

No, the keys are not stored in the connectivity chip. Storing of the keys is something that your application has to take care of.

4. Is the binding possible in the serialized Bluetooth architecture?

Yes, to my knowledge, it should be possible to use bonding, the API for doing so is there.

It can also be useful to have a look at this tread regarding sd_ble_gap_sec_params_reply().