Whitelist enabled in rnf51822 , but after restart the firmware unable to connect phone that are added in whitelist

RE: Whitelist enabled in rnf51822 , but after restart the firmware unable to connect phone that are added in whitelist

Vidar Berg — Wed, 21 Feb 2018 08:18:41 GMT

Bonding information also include encryption key (LTK), ediv, and rand, which is needed to encrypt the link when you re-connect, please refer to the MSC I linked to in my previous reply.

I think it would be easier to modify the peer manager/fstorage backend to use ext. flash than it would be to create a custom "peer manager" from scratch.

RE: Whitelist enabled in rnf51822 , but after restart the firmware unable to connect phone that are added in whitelist

NIDHIN K — Wed, 21 Feb 2018 06:17:37 GMT

Only we need to store whitelist.pp_irks, whitelist.irk_count ,whitelist.pp_addrs, whitelist.addr_count these four parameter right??

Or anything else we need to store in memory ??

Because we are passing only these 4 params in this function ble_advertising_whitelist_reply(&whitelist);

After reset occurs i have read back from ext.flash and load these four parameter.

RE: Whitelist enabled in rnf51822 , but after restart the firmware unable to connect phone that are added in whitelist

Vidar Berg — Tue, 20 Feb 2018 13:05:26 GMT

Hi,

It sounds like the whitelist filtering is working as intended, and that the problem may be that the bonding information is lost on the 51 side. Phones will normally send a new bonding request to the peripheral after existing bond information has been cleared.

I would suggest to debug the app and check if it replies with the correct keys after a reset. Message sequence chart for encrypting the link with existing keys can be found here: http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.api.v2.0.1/group___b_l_e___g_a_p___p_e_r_i_p_h___e_n_c___m_s_c.html?cp=3_7_2_1_0_2_1_3_8_5

RE: Whitelist enabled in rnf51822 , but after restart the firmware unable to connect phone that are added in whitelist

NIDHIN K — Tue, 20 Feb 2018 04:26:43 GMT

Yes both data are same before and after reset. i have checked whitelist.pp_irks, whitelist.irk_count data are same after reset also that means memory storage has no any issue. My exact issue is, i think my whitelist is working because i can able to connect only previously bonded phone( cant able to connect any other phone)but problem is i need to delete bond information from phone after reset nrf51822. i used motog5s plus.

RE: Whitelist enabled in rnf51822 , but after restart the firmware unable to connect phone that are added in whitelist

Vidar Berg — Mon, 19 Feb 2018 14:14:35 GMT

Hi,

Have you compared the content of the whitelist before and after reset to ensure that the data is the same? The fact that it fails after a reset indicates that the data may have been retrieved/stored incorrectly on the ext. flash. Do you see the same behavior if you restart whitelist advertising without doing a reset in-between?