<?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>BLE Mesh DFU Issue with dfu_no_serial Example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/54832/ble-mesh-dfu-issue-with-dfu_no_serial-example</link><description>When I use dfu_nrf52832_xxAA_s132_6.1.1.hex, it works all devices updated with blink code as described in dfu_quick_start.md But without any provisioning Process, why? And in 3 out of 5 devices I upload dfu_no_serial_nrf52832_xxAA_s132_6.1.1.hex generated</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 28 Nov 2019 05:29:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/54832/ble-mesh-dfu-issue-with-dfu_no_serial-example" /><item><title>RE: BLE Mesh DFU Issue with dfu_no_serial Example</title><link>https://devzone.nordicsemi.com/thread/222503?ContentTypeID=1</link><pubDate>Thu, 28 Nov 2019 05:29:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:efe3232c-9902-4ff7-b5ed-1a3da8b3db2a</guid><dc:creator>bivay</dc:creator><description>&lt;p&gt;Issue Solved by resetting all module before upload code.&lt;br /&gt;Thank You&lt;br /&gt;Bivay&lt;/p&gt;
&lt;div style="bottom:0px;font-weight:400;left:0px;right:0px;top:0px;" id="mouseposition-extension-element-full-container"&gt;
&lt;div style="background:rgba(255, 255, 255, 0.7);color:#000000;cursor:default;display:none;font-family:&amp;#39;Helvetica Neue&amp;#39;, Helvetica, Arial, sans-serif;font-size:12px;height:0px;position:absolute;width:0px;" id="mouseposition-extension-element-rect-display"&gt;
&lt;pre style="background-color:rgba(255, 255, 255, 0.7);color:#000000;text-align:center;"&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;pre style="background:#ffffff;border-color:#222222 black #333333;border-radius:3px;border-style:solid;border-width:1px;color:#222222;cursor:default;display:none;font-family:&amp;#39;Helvetica Neue&amp;#39;, Helvetica, Arial, sans-serif;font-size:12px;line-height:14px;padding:3px;position:absolute;" id="mouseposition-extension-element-coordinate-display"&gt;&lt;/pre&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh DFU Issue with dfu_no_serial Example</title><link>https://devzone.nordicsemi.com/thread/222500?ContentTypeID=1</link><pubDate>Thu, 28 Nov 2019 04:49:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:54a06044-5309-42a2-bdce-701ef1c9c8b2</guid><dc:creator>bivay</dc:creator><description>&lt;p&gt;Ok, I will go to take log and check function&amp;nbsp; &lt;span&gt;fw_updated_event_is_for_me()&amp;nbsp;&amp;nbsp;&lt;/span&gt;of it.&lt;br /&gt;&lt;br /&gt;Firmware ID is same &amp;amp; Application version is greater than installed in all.&lt;br /&gt;&lt;br /&gt;Thank You&lt;/p&gt;
&lt;p&gt;Bivay&lt;/p&gt;
&lt;div style="bottom:0px;font-weight:400;left:0px;right:0px;top:0px;" id="mouseposition-extension-element-full-container"&gt;
&lt;div style="background:rgba(255, 255, 255, 0.7);color:#000000;cursor:default;display:none;font-family:&amp;#39;Helvetica Neue&amp;#39;, Helvetica, Arial, sans-serif;font-size:12px;height:0px;position:absolute;width:0px;" id="mouseposition-extension-element-rect-display"&gt;
&lt;pre style="background-color:rgba(255, 255, 255, 0.7);color:#000000;text-align:center;"&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;pre style="background:#ffffff;border-color:#222222 black #333333;border-radius:3px;border-style:solid;border-width:1px;color:#222222;cursor:default;display:none;font-family:&amp;#39;Helvetica Neue&amp;#39;, Helvetica, Arial, sans-serif;font-size:12px;line-height:14px;padding:3px;position:absolute;" id="mouseposition-extension-element-coordinate-display"&gt;&lt;/pre&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh DFU Issue with dfu_no_serial Example</title><link>https://devzone.nordicsemi.com/thread/222375?ContentTypeID=1</link><pubDate>Wed, 27 Nov 2019 13:46:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4525e672-c975-4814-832f-98a28f6ec28c</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;It&amp;#39;s correct, as you can see in the code, the main difference is just the initialization of the serial interface.&amp;nbsp;Could you take the log of the non-serial node when doing DFU ?&amp;nbsp;&lt;br /&gt;Please make sure the application firmware ID in the&amp;nbsp;device page of all nodes are the same. In addition the application version of the current firmware should be smaller than the application version of the new firmware. Check the&amp;nbsp;fw_updated_event_is_for_me() and see if it returns true.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh DFU Issue with dfu_no_serial Example</title><link>https://devzone.nordicsemi.com/thread/222209?ContentTypeID=1</link><pubDate>Wed, 27 Nov 2019 05:25:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd2a1ecf-c56f-475e-8fbc-1e04464e6cde</guid><dc:creator>bivay</dc:creator><description>&lt;p&gt;Please correct me if I am wrong,&lt;/p&gt;
&lt;p&gt;DFU with Serial and DFU without Serial, differences between these two are DFU with Serial can take Firmware update command from Serial interference, and DFU without Serial can&amp;#39;t.&lt;br /&gt;&lt;br /&gt;I also tried complying from source code, but result is same.&lt;/p&gt;
&lt;div style="bottom:0px;font-weight:400;left:0px;right:0px;top:0px;" id="mouseposition-extension-element-full-container"&gt;
&lt;div style="background:rgba(255, 255, 255, 0.7);color:#000000;cursor:default;display:none;font-family:&amp;#39;Helvetica Neue&amp;#39;, Helvetica, Arial, sans-serif;font-size:12px;height:0px;position:absolute;width:0px;" id="mouseposition-extension-element-rect-display"&gt;
&lt;pre style="background-color:rgba(255, 255, 255, 0.7);color:#000000;text-align:center;"&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;pre style="background:#ffffff;border-color:#222222 black #333333;border-radius:3px;border-style:solid;border-width:1px;color:#222222;cursor:default;display:none;font-family:&amp;#39;Helvetica Neue&amp;#39;, Helvetica, Arial, sans-serif;font-size:12px;line-height:14px;padding:3px;position:absolute;" id="mouseposition-extension-element-coordinate-display"&gt;&lt;/pre&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Mesh DFU Issue with dfu_no_serial Example</title><link>https://devzone.nordicsemi.com/thread/222177?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2019 17:36:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b6d82abd-88e3-43a9-8662-d6961e74211e</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Bivay,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;By theory they should all works, both the one with&amp;nbsp;&lt;span&gt;dfu_nrf52832_xxAA_s132_6.1.1.hex and the one with&amp;nbsp;dfu_no_serial_nrf52832_xxAA_s132_6.1.1.hex.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I&amp;#39;m not sure what would go wrong here. Could you try to compile the file from the code, instead of using the precompiled hex file ?&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The reason why you can do DFU without doing provisioning is that our Mesh DFU using broadcast mesh instead of Bluetooth mesh to do DFU. In broadcast mesh there is no encryption and no provisioning needed.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;If you want to implement DFU in your application, please have a look at the dfu example. It&amp;#39;s pretty simple, just include the DFU file and&amp;nbsp;include a mesh event handler as in the dfu example (mesh_evt_handler) .&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>