Identifying specific user from the whitelis

RE: Identifying specific user from the whitelis

Hung Bui — Tue, 01 Sep 2015 08:58:54 GMT

@GT: Please open a new question. But before that, please do a search for pstorage example. With that search, I found this: https://devzone.nordicsemi.com/question/15271/how-can-i-write-10kb-of-data-to-internal-flash/?answer=17300#post-id-17300

You should test first to store and restore some simple dummy data to make sure pstorage works properly before you try with IRK.

RE: Identifying specific user from the whitelis

GT — Mon, 31 Aug 2015 14:13:00 GMT

There is almost no progress. I am still trying to store the IRK with the persistent storage manager. Unfortunately it does not work. I am wondering if I should describe the problem here and eventually this question will result in solution for solving this particular problem, or to open a new question. Hung, what would be your advice?

RE: Identifying specific user from the whitelis

GT — Fri, 28 Aug 2015 12:47:00 GMT

So far it looks like the approach for using the IRK as a reference will work. After minor modifications on the device manager I can get the IRK for a particular central from it. However, now I am having troubles storing it, but this is another topic... I will post the progress here.

RE: Identifying specific user from the whitelis

GT — Fri, 21 Aug 2015 12:15:37 GMT

Thank you for your input Hung. I will try to investigate and implement the first solution and I will report my progress next week.

RE: Identifying specific user from the whitelis

Hung Bui — Fri, 21 Aug 2015 08:33:47 GMT

Hi GT,

I think the simplest way is to store to flash either the IRK (if central uses private resolvable address) or the static address (if central uses static address) to flash. And you can check if the device connected is the admin device or not at the BLE_GAP_EVT_CONNECTED event. Beside the irk_match, you can also find the peer_addr of the central.

Other solution is to check if it's the first device to bond in the bond database, but it's more complicated and require the device to re-bond before you can have the master's ediv to look for the master and then check if it's the first master device or not.