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.

  • The new API is already released for S120 and the peripheral in S130 alpha, but will also be present in the S110 8.x.x series. I do not know the release dates, but it should come with proper and updated SDK examples. The only difference for your peripheral would be to lookup the LTK based on a master-prodivded ediv/rand combo. You are not required to update to the newest versions unless you need features from them. (If you are interested in the timelines and features, please contact our Sales department).

Reply
  • The new API is already released for S120 and the peripheral in S130 alpha, but will also be present in the S110 8.x.x series. I do not know the release dates, but it should come with proper and updated SDK examples. The only difference for your peripheral would be to lookup the LTK based on a master-prodivded ediv/rand combo. You are not required to update to the newest versions unless you need features from them. (If you are interested in the timelines and features, please contact our Sales department).

Children
No Data
Related