<?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>Question about DFU on Mesh SDK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/61227/question-about-dfu-on-mesh-sdk</link><description>Hi, teams. 
 I am trying to implement DFU functionality on mesh node devices. 
 Currently, I am using Mesh SDK 4.1.0 and have read DFU-related documents, but still something is not clear. 
 
 Doing DFU via nRFConnect for Mobile in mesh device is not possible</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 25 May 2020 15:26:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/61227/question-about-dfu-on-mesh-sdk" /><item><title>RE: Question about DFU on Mesh SDK</title><link>https://devzone.nordicsemi.com/thread/251550?ContentTypeID=1</link><pubDate>Mon, 25 May 2020 15:26:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6751393f-ba95-437e-9f6f-6d3d12ce4c07</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;1. The devices need to decide themselves if they want to receive the firmware update when they come in, they do this by calling either nrf_mesh_dfu_request(accepting the update), nrf_mesh_dfu_relay(just relaying), or do nothing(just ignore). They can do every thing on each of the NRF_MESH_EVT_DFU_FIRMWARE_OUTDATED and NRF_MESH_EVT_DFU_REQ_RELAY events, but the latter comes for FWIDs that do not match the one that already are on the device.&lt;/p&gt;
&lt;p&gt;2. Yes, that is correct.&lt;/p&gt;
&lt;p&gt;3. DFU in the LPN-example er for standard BLE DFU, refer to the DFU-example for Mesh DFU.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Question about DFU on Mesh SDK</title><link>https://devzone.nordicsemi.com/thread/251091?ContentTypeID=1</link><pubDate>Thu, 21 May 2020 01:53:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:798b679c-6ebc-4719-9ec1-65cdb566b7ce</guid><dc:creator>choehyunho</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;Still, I cannot fully understand the concept.&lt;/p&gt;
&lt;p&gt;1. Do you mean the whole mesh nodes will try to update firmware if I started DFU with one device? By default, Or with some modification you mentioned - &amp;quot;accept the DFUs, even if they comes in relay request&amp;quot;?&lt;/p&gt;
&lt;p&gt;2. What is the exact meaning of &amp;quot;put network index in the firmware ID&amp;quot;? Put some unique ID in --application-id during DFU archive creation with nrfutil?&lt;/p&gt;
&lt;p&gt;3. I found two DFU example in Mesh SDK, dfu example and the one in lpn example. they seems to be quite different approach. Which one should I refer to?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Question about DFU on Mesh SDK</title><link>https://devzone.nordicsemi.com/thread/250637?ContentTypeID=1</link><pubDate>Tue, 19 May 2020 09:06:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ace3db3c-1036-4dec-bdaa-40fba04037a4</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;1. No, they don&amp;#39;t have to be in the same network. Have a look at &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/50115/mesh-dfu-example---provisioning-into-the-mesh-network/200051#200051" rel="noopener noreferrer" target="_blank"&gt;this&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;2. We&lt;span&gt;&amp;nbsp;do not have a proper solution for this, but what you can do is to put a network index in the Firmware ID, and just accept DFU with the correct network index. This would not require different firmware in each device, you can accept the DFUs you want, even if they comes in as &amp;quot;relay request&amp;quot;-events.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Question about DFU on Mesh SDK</title><link>https://devzone.nordicsemi.com/thread/250341?ContentTypeID=1</link><pubDate>Mon, 18 May 2020 05:42:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:62e36936-a6ad-406f-b3f2-18cf0bcbcbb0</guid><dc:creator>choehyunho</dc:creator><description>&lt;p&gt;Hi, Mittrinh.&lt;/p&gt;
&lt;p&gt;Thank you for clarification.&lt;/p&gt;
&lt;p&gt;OK, I&amp;#39;ll ask more question about possible scenario in Mesh SDK.&lt;/p&gt;
&lt;p&gt;1. To execute DFU over the air, both devices should be provisioned into the same mesh network, right?&lt;/p&gt;
&lt;p&gt;2. If many devices are already provisioned and deployed, what happened if I try DFU? How can I distinguish specific device?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Question about DFU on Mesh SDK</title><link>https://devzone.nordicsemi.com/thread/250143?ContentTypeID=1</link><pubDate>Fri, 15 May 2020 10:29:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:02128f6b-101d-45e3-922e-f76a365deffb</guid><dc:creator>Mttrinh</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Sorry for late response.&lt;/p&gt;
&lt;p&gt;1. Yes, that is correct. You can&amp;#39;t do Mesh DFU over nRF Connect.&lt;/p&gt;
&lt;p&gt;2. You can&amp;#39;t do Mesh DFU over BLE, there is no solution for this. The serial bootloader is used by default for Mesh DFU.&lt;/p&gt;
&lt;p&gt;3a. Yes, that is correct.&lt;/p&gt;
&lt;p&gt;3b. Both devices must have an application with DFU support and bootloader.&lt;/p&gt;
&lt;p&gt;3c. This is the only method that we have implemented. If you want to do it some other way, you have to implement that yourself.&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>