https://devzone.nordicsemi.com/f/nordic-q-a/90631/disable-bootloader-gap-address-changeHi, Depending on how the nRF5 SDK is configured, the BLE address may change once in the bootloader (it&#39;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 toen-USTelligent Community 13Wed, 03 Aug 2022 07:31:51 GMThttps://devzone.nordicsemi.com/thread/379806?ContentTypeID=1Wed, 03 Aug 2022 07:31:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:81866b6a-a89f-4426-b3ac-0abce1eecc72Vidar Berg<p>Hi,</p> <p>The reason for the address change is to avoid potential problems with caching as mentioned here: &quot;<span><a title="Buttonless Secure DFU Service without bonds" href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/service_dfu.html?cp=8_1_3_3_5_3#service_buttonless_unbonded">Buttonless Secure DFU Service without bonds</a>&quot;. If you don&#39;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&#39;s attribute table and that bonding is not supported in the app. </span></p> <p><span>You can read more about the attribute caching rules in in vol.3, part G, section 2.5.2 of the Bluetooth core specification.</span></p> <p><span>Best regards,</span></p> <p><span>Vidar</span></p><div style="clear:both;"></div>