This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

irk_match when having a BLE_GAP_EVT_CONNECTED

Hi all,

I have made my own device manager because the device manager from Nordic is somewhat bloat (in code and resources) and I needed to add a feature, ranking the devices so the less used device is removed when the storage is full and a new devices wants to bond. I was not able to create this feature outside the device manager. Anyway, I want to test the manager and every thing is working well. The only thing I am not able to test is irk. I never see an irk_match. The devices gets identified by means of the address or by means of the diversifier. I find this rather strange be cause the iPhone uses a random address, so it should be identified with an irk. Does anybody knows why I do not get a irk_match in a connect event?

Thanks in advance,

Marcel

Parents
  • Hi,

    You will only get an irk_match if you advertise or connect using a whitelist with IRKs in it (irk_count > 0). As a peripheral, the SoftDevice will resolve all devices trying to connect to or scan it and only respond if there is a hit in the address or IRK whitelists. As a central, the SoftDevice will process all connectable advertisers that use resolvable address types and match them before trying to connect

    If a connection happens due to a match coming from the IRK part of the whitelist, the index to entry which was matched will be present in the irk_match field of the connected event.

  • Ok ,we understand each other than correctly now. The real question was already answered for, but I was curious if I understood correctly how your softdevice works. This was outside the scope of BLE_GAP_EVT_CONNECTED. There lies the misunderstanding between us. Will the new version of the softdevice, which abandon the diversifier and start using the EDIV and RAND, be released shortly? Because I have to change my device manager than and I will release in a couple of weeks.

Reply
  • Ok ,we understand each other than correctly now. The real question was already answered for, but I was curious if I understood correctly how your softdevice works. This was outside the scope of BLE_GAP_EVT_CONNECTED. There lies the misunderstanding between us. Will the new version of the softdevice, which abandon the diversifier and start using the EDIV and RAND, be released shortly? Because I have to change my device manager than and I will release in a couple of weeks.

Children
No Data
Related