bonding & Whitelisting & deepsleep

RE: bonding & Whitelisting & deepsleep

FormerMember — Thu, 31 Mar 2016 06:51:20 GMT

In SDK 11, the example ble_app_gls uses the peer_manager module to store the bonding information, I would recommend you to take a look at it.

There is no direct way for the nRF5 device to get to know that the phone has deleted the pairing information. One way to notify the nRF5 device is to use a button push or similar.

RE: bonding & Whitelisting & deepsleep

Mohamed O.Abouzeid — Tue, 29 Mar 2016 03:53:19 GMT

which one of them, can you tell me any of them, I tried ble_App_hrs _dfu, it didn't include the peer manager on its inclusion list even !!

RE: bonding & Whitelisting & deepsleep

RK — Tue, 29 Mar 2016 02:02:24 GMT

use any of the examples in the SDK - the bond manager and the peer manager both write bonding information to flash. Every single example in the SDK which bonds, which is quite a few of them, reconnects after restart

RE: bonding & Whitelisting & deepsleep

Mohamed O.Abouzeid — Tue, 29 Mar 2016 01:59:48 GMT

that's doesn't happen with me, do you have an example of your operation so as I can figure out the problem?

RE: bonding & Whitelisting & deepsleep

RK — Tue, 29 Mar 2016 01:15:00 GMT

so it does a reset - yes I know that - but your bonding information should be stored in flash so you can read it back when you restart.

RE: bonding & Whitelisting & deepsleep

Mohamed O.Abouzeid — Mon, 28 Mar 2016 16:10:31 GMT

@RK The sd_power_system_off function do a reset when wake up, this is the only sleep mode which responds only to the wake up signal. And any other event doesn't cause a wake up, if u have an example for that, would u mind give it to me????

RE: bonding & Whitelisting & deepsleep

RK — Mon, 28 Mar 2016 15:55:12 GMT

Going into deep sleep, or off mode, does not erase memory, I don't know where you get that idea from. Bonding (with any of the Nordic supplied libraries or indeed any code which makes sense) writes bond information to flash and reloads it.