https://devzone.nordicsemi.com/f/nordic-q-a/38255/custom-bd-address-mac-in-secure-bootloader-with-bondsI&#39;ve created this function static void set_bd_addr(void) { ret_code_t ret_code; ble_gap_addr_t gap_addr; gap_addr.addr_id_peer = 0; gap_addr.addr_type = BLE_GAP_ADDR_TYPE_PUBLIC; // Get BD address from UICR memory uint8_t* ptr = (uint8_t*)&amp;NRF_UICRen-USTelligent Community 13Thu, 06 Sep 2018 13:26:11 GMThttps://devzone.nordicsemi.com/thread/147602?ContentTypeID=1Thu, 06 Sep 2018 13:26:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7cbf4373-2c85-42ad-9c38-eef8eb34e083vist<p>Thank you for the quick reply, I decided to make a copy of nrf_dfu_ble.c and use that in order to not mess up the sdk files. I put the set_bd_addr function at the end of gap_params_init and it seems to work well.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/147589?ContentTypeID=1Thu, 06 Sep 2018 12:35:18 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5c93a62f-14d7-44a7-a94a-45e2a549b39fVidar Berg<p>Hi,</p> <p>Most of the softdevice APIs can only be used after the softdevice has been enabled. It is the BLE transport layer that enables the softdevice in the bootloader. I would suggest to change the address in nrf_dfu_ble.c::gap_params_init().&nbsp;</p><div style="clear:both;"></div>