Whitelisting example on central and peripheral devices

RE: Whitelisting example on central and peripheral devices

Primož Kralj — Wed, 16 Dec 2015 12:55:09 GMT

What was the problem?

RE: Whitelisting example on central and peripheral devices

Fávero — Wed, 25 Nov 2015 20:25:41 GMT

Just posted! Thanks for the help.

RE: Whitelisting example on central and peripheral devices

run_ar — Wed, 25 Nov 2015 20:03:37 GMT

If you are able to connect to the peripheral with two different centrals I guess you have an issue when populating the whitelist on the peripheral. The easiest for me is if I can debug the complete project (If it's keil), but it could be interesting to see the part where you populate the whitelist and starts advertising.

RE: Whitelisting example on central and peripheral devices

Fávero — Wed, 25 Nov 2015 19:57:39 GMT

Sure, just point out which code section you want to check and from which device (central or peripheral). I'll glady share!

RE: Whitelisting example on central and peripheral devices

run_ar — Wed, 25 Nov 2015 19:50:05 GMT

8.0.0 has the same behavior. If you still have problem with this, maybe you could share your code on mypage so I can take a look at it?

RE: Whitelisting example on central and peripheral devices

Fávero — Wed, 25 Nov 2015 13:37:53 GMT

I'm using SDK 8.0.0.

RE: Whitelisting example on central and peripheral devices

run_ar — Wed, 25 Nov 2015 13:26:24 GMT

hmm, I don't get this. As far as I can see dm_whitelist_create will update the irk_count and addr_count as the whitelist is populated. I'm looking at SDK 10.0.0.

RE: Whitelisting example on central and peripheral devices

Fávero — Tue, 24 Nov 2015 16:10:09 GMT

Ok. Fiddled with the code: Whitelist populated? No. Code runs inside BLE_ADV_EVT_WHITELIST_REQUEST. When checking whitelist, pp_addrs is populated but addr_count is equal to zero. pp_irks is populated but irk_count is not. Central devices use static random address (default).

RE: Whitelisting example on central and peripheral devices

Fávero — Tue, 24 Nov 2015 15:10:06 GMT

Thank you. Could you point where (which function) I could verify?

RE: Whitelisting example on central and peripheral devices

run_ar — Tue, 24 Nov 2015 12:55:46 GMT

Can you check the following. Is the whitelist populated and forwarded to the softdevice? And can yo make sure that you haven't already bonded with both central devices. I assume the central devices uses a static address? if not you could check if you get a IRK match in the connected event.

RE: Whitelisting example on central and peripheral devices

Fávero — Tue, 24 Nov 2015 12:32:04 GMT

Yeah, just tested. Even with _FILTER_BOTH, my peripheral keeps connecting to central B (when central A is off).

RE: Whitelisting example on central and peripheral devices

Fávero — Tue, 24 Nov 2015 12:29:29 GMT

In mode BLE_ADV_MODE_FAST, adv_params.fp = BLE_GAP_ADV_FP_FILTER_CONNREQ. Let me try with the presented option. I'll get back.

RE: Whitelisting example on central and peripheral devices

run_ar — Tue, 24 Nov 2015 12:19:59 GMT

How did you set up fp? This needs to be configured to tell the softdevice what to do when a device that's not in the whitelist sends a connection or scan request. e.g. use BLE_GAP_ADV_FP_FILTER_BOTH.

RE: Whitelisting example on central and peripheral devices

Fávero — Tue, 24 Nov 2015 12:19:09 GMT

So, just to get this right and to verify if whitelist is the right option for me: I want one peripheral to connect to only one central. After 15 seconds, my peripheral goes to sleep (i'm using sleep_mode_enter()), so when it wakes up, it actually resets, resetting the whitelist. Is whitelisting the right option for me? Or is there other way to keep a non-volatile connection?

Let me present an example:

I have 2 centrals, 1 peripheral. Peripheral has whitelist enabled, just like hid keyboard example presents. Both centrals are on. When I turn on my peripheral, it connects to central A. If I turn off central A and keep central B on, peripheral connects to central B. I want to avoid this recconection behavior. I want the peripheral to connect only to central A, even if other centrals are available.

RE: Whitelisting example on central and peripheral devices

run_ar — Tue, 24 Nov 2015 11:52:28 GMT

No, you will have to call dm_whitelist_create to update the whitelist, so you are in control of when this changes. Normally this will be done right before you start advertising.

RE: Whitelisting example on central and peripheral devices

Fávero — Tue, 24 Nov 2015 11:19:14 GMT

Is the whitelist normally volatile? I did some testing, and it turns out volatile (when I turn off and on my peripheral, sometimes it connects to the "wrong" central). Is there a way to make it non-volatile in peripheral?

RE: Whitelisting example on central and peripheral devices

run_ar — Tue, 24 Nov 2015 10:15:20 GMT

For Peripheral you can look at the hid keyboard example. But all you need to do is provide the whitelist to ble_gap_adv_params_t. This is populated using dm_whitelist_create. For central you can look at ble_app_hrs_c.