Meizu M2 IRK not resolved

RE: Meizu M2 IRK not resolved

Hung Bui — Mon, 03 Apr 2017 09:02:50 GMT

Good to know Valer. Sorry that I didn't spot that at the beginning. We have seen devices that did the same thing. My suggestion is to ignore the IRK exchange when the public address is used when doing Connect Request.

RE: Meizu M2 IRK not resolved

Valer_I — Fri, 31 Mar 2017 11:52:25 GMT

I changed the filter policy and now receive BLE_GAP_EVT_SCAN_REQ_REPORT. The Meizu's scan address type is Private Non-Resolvable... So IRK provided during the bonding procedure is useless.

RE: Meizu M2 IRK not resolved

Hung Bui — Fri, 31 Mar 2017 11:00:46 GMT

Hi Valer,

I'm suspecting that the IRK may not match the address, causing the nRF5 to ignore the scan request and connect request. If you turn off whitelist mode (or only whitelist Connect request, not scan request) do you see the difference ?

We have some code here that you can use to test if the IRK and the address is matched or not. Could you please try ?

RE: Meizu M2 IRK not resolved

Valer_I — Fri, 31 Mar 2017 09:35:30 GMT

Original question updated.

RE: Meizu M2 IRK not resolved

Hung Bui — Fri, 31 Mar 2017 08:53:17 GMT

The IRK is generated by the phone. So it is possible that the IRK can contains lots of zero depends on the algorithm used to generate it.

I would suggest you to capture a sniffer trace, then we can clearly see which IRK is exchanged and what happens when they re-connect.