<?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>After DFU completed new firmware is running but advertised name of new firmware not updated.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/57852/after-dfu-completed-new-firmware-is-running-but-advertised-name-of-new-firmware-not-updated</link><description>Hi 
 The issue is that after a buttonless DFU is completed the new firmware runs as expected but the new advertised name doesn&amp;#39;t change. 
 device name in firmware before DFU p27_5f0181cb63ff 
 device name in firmware after DFU p28_5f0181cb63ff however</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 20 Feb 2020 20:38:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/57852/after-dfu-completed-new-firmware-is-running-but-advertised-name-of-new-firmware-not-updated" /><item><title>RE: After DFU completed new firmware is running but advertised name of new firmware not updated.</title><link>https://devzone.nordicsemi.com/thread/235582?ContentTypeID=1</link><pubDate>Thu, 20 Feb 2020 20:38:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a57f9ab-20ba-492c-91e7-08451daac39a</guid><dc:creator>dm1</dc:creator><description>&lt;p&gt;Ok have tested using nRF Connect on the PC and it operates as expected and the DEVICE_NAME updates correctly. So as you say it looks like an issue with caching on the phone or the application.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I guess if the cached info is held in the phone and cannot be invalidated by the application then it will be hard for you to fix. I am talking about IOS here not Android as I haven&amp;#39;t yet tested android due to lack of a device.&amp;nbsp;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: After DFU completed new firmware is running but advertised name of new firmware not updated.</title><link>https://devzone.nordicsemi.com/thread/234705?ContentTypeID=1</link><pubDate>Mon, 17 Feb 2020 15:20:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fa541f8c-4011-4cbd-b973-0cd89fce1927</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Dml,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We need to verify if the advertising device name is actually not changed or it&amp;#39;s just the phone didn&amp;#39;t update the advertising packet.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please try to turn off and on Bluetooth, on the phone,&amp;nbsp; remove any bond information with the original device.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Also you can use nRF Connect on PC to verify the actual advertising packet.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: After DFU completed new firmware is running but advertised name of new firmware not updated.</title><link>https://devzone.nordicsemi.com/thread/234520?ContentTypeID=1</link><pubDate>Sat, 15 Feb 2020 10:27:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b77a8324-b303-4bb9-9a4d-ff11c53909bb</guid><dc:creator>dm1</dc:creator><description>&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;static void gap_params_init(void)
{
    uint32_t                err_code;
    ble_gap_conn_params_t   gap_conn_params;
    ble_gap_conn_sec_mode_t sec_mode;


    ble_gap_addr_t ble_addr;
    sd_ble_gap_addr_get(&amp;amp;ble_addr);

    sprintf(&amp;amp;strDeviceName[0], &amp;quot;%s_%.2x%.2x%.2x%.2x%.2x%.2x&amp;quot;, &amp;amp;DEVICE_NAME[0], 
        ble_addr.addr[0],
        ble_addr.addr[1],
        ble_addr.addr[2],
        ble_addr.addr[3],
        ble_addr.addr[4],
        ble_addr.addr[5]
    );

    sprintf(&amp;amp;strBleAddress[0], &amp;quot;%.2x:%.2x:%.2x:%.2x:%.2x:%.2x&amp;quot;,  
        ble_addr.addr[0],
        ble_addr.addr[1],
        ble_addr.addr[2],
        ble_addr.addr[3],
        ble_addr.addr[4],
        ble_addr.addr[5]
    );

    
    
    BLE_GAP_CONN_SEC_MODE_SET_OPEN(&amp;amp;sec_mode);


//    device_name_set(); 
    err_code = sd_ble_gap_device_name_set(&amp;amp;sec_mode, (uint8_t *) strDeviceName, strlen(strDeviceName));


//    err_code = sd_ble_gap_device_name_set(&amp;amp;sec_mode,
//                                          (const uint8_t *)strDeviceName,
//                                          strlen(strDeviceName));
    APP_ERROR_CHECK(err_code);

    /* YOUR_JOB: Use an appearance value matching the application&amp;#39;s use case.
       err_code = sd_ble_gap_appearance_set(BLE_APPEARANCE_);
       APP_ERROR_CHECK(err_code); */

    memset(&amp;amp;gap_conn_params, 0, sizeof(gap_conn_params));

    gap_conn_params.min_conn_interval = MIN_CONN_INTERVAL;
    gap_conn_params.max_conn_interval = MAX_CONN_INTERVAL;
    gap_conn_params.slave_latency     = SLAVE_LATENCY;
    gap_conn_params.conn_sup_timeout  = CONN_SUP_TIMEOUT;

    err_code = sd_ble_gap_ppcp_set(&amp;amp;gap_conn_params);
    APP_ERROR_CHECK(err_code);
}&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>