<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DFU Device Address Changes</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6900/dfu-device-address-changes</link><description>When my Nordic device is running my custom BLE application I notice that the device address is 0xC4318DBD687C. When device is running the bootloader service the device address becomes 0xC4318DBD687D. I am not changing the address of the device during</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Oct 2019 08:32:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6900/dfu-device-address-changes" /><item><title>RE: DFU Device Address Changes</title><link>https://devzone.nordicsemi.com/thread/213567?ContentTypeID=1</link><pubDate>Mon, 07 Oct 2019 08:32:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a26a77fa-7b8d-48d6-8fc2-ab9477d2fbd9</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Elias: Please create a new case with more information on what you want to know. This case is 4 years old.&amp;nbsp;&lt;br /&gt;The device address is random so the address +1 is also at the same level of randomness.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU Device Address Changes</title><link>https://devzone.nordicsemi.com/thread/213558?ContentTypeID=1</link><pubDate>Mon, 07 Oct 2019 08:00:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:69216fae-f4c0-42f3-aae7-7539157a83e4</guid><dc:creator>Elias L&amp;#246;we</dc:creator><description>&lt;p&gt;Can it happen that some device in DFU mode witll have the same address with any regular Nordic device?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU Device Address Changes</title><link>https://devzone.nordicsemi.com/thread/24331?ContentTypeID=1</link><pubDate>Wed, 07 Oct 2015 20:48:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:efd3fab3-4b4d-46e7-8550-7f5bffeeb134</guid><dc:creator>Jordan Archer</dc:creator><description>&lt;p&gt;So that code wasn&amp;#39;t in the 7.0 SDK.  But it works.  Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU Device Address Changes</title><link>https://devzone.nordicsemi.com/thread/24330?ContentTypeID=1</link><pubDate>Tue, 06 Oct 2015 08:53:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5391e050-2f11-44d7-a7bb-64e1318f4b57</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@ Jordan: If you use SDK v9.0 you can find this code:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;ble_gap_addr_t addr;

        err_code = sd_ble_gap_address_get(&amp;amp;addr);
        APP_ERROR_CHECK(err_code);

        // Increase the BLE address by one when advertising openly.
        addr.addr[0] += 1;

        err_code = sd_ble_gap_address_set(BLE_GAP_ADDR_CYCLE_MODE_NONE, &amp;amp;addr);
        APP_ERROR_CHECK(err_code);
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;From line 1065 to 1074 in dfu_transport_ble.c&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU Device Address Changes</title><link>https://devzone.nordicsemi.com/thread/24329?ContentTypeID=1</link><pubDate>Mon, 05 Oct 2015 19:56:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:228df7f0-319a-48e1-8fc0-bdbbdf186c9d</guid><dc:creator>Jordan Archer</dc:creator><description>&lt;p&gt;I don&amp;#39;t see where in dfu_transport_update_start you change the address.  How does this happen?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: DFU Device Address Changes</title><link>https://devzone.nordicsemi.com/thread/24328?ContentTypeID=1</link><pubDate>Wed, 06 May 2015 10:51:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c083cff-118f-4582-b015-cd095f02351b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Lucas: By design our Bootloader will use a different address from the default address in FICR (FICR address + 1) if there is no bond information shared. Please have  a look at dfu_transport_update_start() in dfu_transport_ble.c&lt;/p&gt;
&lt;p&gt;The reason we do that is to solve the issue that the central device (phones, tablets) may try to use the bond information it has before with the normal application to encrypt the link. If we don&amp;#39;t have shared bondinformation, we won&amp;#39;t be able to follow the encrypted link when in bootloader mode.
So we change the address and will be recognize as a new device from the phone and can avoid the above issue.&lt;/p&gt;
&lt;p&gt;EDIT: It&amp;#39;s not only when there is bond information share but also when a central address is shared, the address will not change. It only changes when the bootloader started up from booting (no bond information or address shared)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>