<?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>Mesh DFU over BLE by using nRF52840 DK boards</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/37309/mesh-dfu-over-ble-by-using-nrf52840-dk-boards</link><description>Hi Nordic team, 
 I have 2 nRF52840 DK boards. 
 
 I followed the steps mentioned in the below link, I am able to Transfer the DFU archive over serial with nrfutil(LED keeps blinking on the DFU performed board). http://infocenter.nordicsemi.com/index</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 12 Aug 2018 20:19:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/37309/mesh-dfu-over-ble-by-using-nrf52840-dk-boards" /><item><title>RE: Mesh DFU over BLE by using nRF52840 DK boards</title><link>https://devzone.nordicsemi.com/thread/143824?ContentTypeID=1</link><pubDate>Sun, 12 Aug 2018 20:19:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f63138e-804b-449d-893c-5ec50e9081e3</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Hi Prasanna,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q1: The serial bootloader will automatically start transferring firmware image to the other mesh nodes over BLE after it has received the firmware image over the serial interface. This is stated in the &lt;a title="DFU quick start guide" href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v2.1.1/md_doc_getting_started_dfu_quick_start.html?cp=4_1_0_3_2"&gt;DFU quick start guide&lt;/a&gt;.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q2: The mesh node will print&amp;nbsp;DFU END! in the log output when DFU has finished.&lt;/p&gt;
&lt;p&gt;Q3: The Bluetooth Mesh is a flooding mesh, i.e. no connections are made.&amp;nbsp; The mesh nodes listen for incoming advertisement packets and then forward these to the other nodes within range. If a mesh node is outside the range of the other mesh nodes when DFU is performed and then joins the mesh at a later point, then it will automatically detect that its firmware version is outdated and will request the mesh to resend the new firmware.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Bjørn&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>