https://devzone.nordicsemi.com/f/nordic-q-a/11449/bt-address-vs-deviceaddrHi, There is a difference of one digit in BT address and DEVICEADDR. Could anybody explain this? I know in the last byte we have to add C0, but what about the frst byte? Why is it different?en-USTelligent Community 13Thu, 21 Jan 2016 12:45:54 GMThttps://devzone.nordicsemi.com/thread/43189?ContentTypeID=1Thu, 21 Jan 2016 12:45:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d4c224a6-8792-41d1-b8d3-86224c091573Hung Bui<p>Hi Sergey,</p> <p>Then it&#39;s normal. In the bootloader we change address by +1 so that the address of the bootloader would not be identical with the application. This is to avoid ATT table caching issue we have on the phone. So that it won&#39;t update the ATT table when we switch to bootloader mode.</p> <p>If you don&#39;t want this, you can of course remove that part of code inside dfu_transport_update_start() in dfu_transport_ble.c so that the address is not modified.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/43188?ContentTypeID=1Thu, 21 Jan 2016 10:10:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2bdab566-efd9-459b-b109-8038d90983e6Sergy<p>Im using BLE DFU Bootloader from SDK10 without any change to it, so this is what i get from advertising in bootloader, not in app.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/43187?ContentTypeID=1Thu, 21 Jan 2016 09:52:42 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9add541d-ad79-447d-b94f-3a352b8548a6Hung Bui<p>Hi Sergey,</p> <p>This is strange. Are you sure there is no manual address change in the application code ?</p> <p>Could you try again with a stock example in the SDK ?</p><div style="clear:both;"></div>