Disable bootloader GAP address change

[Mateusz]

Hi,

Depending on how the nRF5 SDK is configured, the BLE address may change once in the bootloader (it's incremented). This happens in the gap_address_change() function. I do not want to enable bonds (NRF_DFU_BLE_REQUIRES_BONDS), but I do want to keep the address the same. I could simply remove the logic that increments the digit, but what are the caveats with this? I assume a mobile device that has been previously paired will fail to establish a connection. This should be harmless though. Any other potential issues?

Thank you.

[Vidar Berg]

Hi,

The reason for the address change is to avoid potential problems with caching as mentioned here: "Buttonless Secure DFU Service without bonds". If you don't do the address change, then you have to make sure you have the service changed characteristic is present in both the bootloader and application's attribute table and that bonding is not supported in the app.

You can read more about the attribute caching rules in in vol.3, part G, section 2.5.2 of the Bluetooth core specification.

Best regards,

Vidar