RE: Bond Manager Issue

Ignacio Lopez — Fri, 15 Nov 2013 13:50:56 GMT

Thanks. Great answer! This is exactly what I see. And yes, I was testing with and iOS device. I tested with the MCP and the master address is not stored as BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE. I will follow your advices.

RE: Bond Manager Issue

Audun — Fri, 15 Nov 2013 12:57:43 GMT

Hi,

there are several issues that can cause this behavior. First of all, I suggest upgrading to the bondmanager found in SDK 4.4.2. Compared to Desktop 2 v1.0.4, this bondmanager release fixes many issues, several of which are related to resolvable addresses (used most notably by iOS).

First off, is the condition (m_masters_db[master_handle].bond.master_addr.addr_type == BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE) true regardless of which Master you are connected to? When connected to for example the Nordic Master Emulator it should be false. Let's assume that you are connecting to an iOS device, in which case it's expected that this is the correct address type.

Resolvable addresses can be changed at any time, and thus it doesn't make sense to use that address for directed advertising. Instead undirected advertising with a whitelist should be used. The Identity Resolve Key (IRK) is put in the whitelist, which makes it possible to recognize the Master even though it has changed its address. The bondmanager will handle IRKs and can be used to generate a whitelist for you (ble_bondmngr_whitelist_get()). Several bugs related to address types and IRK storage has been fixed lately, so again I suggest upgrading to SDK 4.4.2 bondmanager.

The address type can be found in ble_bondmngr.c, m_masters_db[x].bond.master_addr.addr_type. m_masters_db is a RAM struct. The contents of this struct is loaded from flash during bondmanager initialization. You can take a look at the flash storage area to see if there is any data there at all: Open address FLASH_PAGE_BOND (default value 255 in DT2 v1.0.4) * 1024 in the debugger. If this area is all F's (flash erase value), then the data is invalid. If it's not just F's there is probably valid data there, and you can take a closer look at the m_masters_db array during bondmanager initialization.

Hope this helps!