<?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 SDK2.1.1 DFU Serial Host Question</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38992/mesh-sdk2-1-1-dfu-serial-host-question</link><description>I was able to follow the &amp;quot;quick start&amp;quot; guide for Mesh DFU and got things working with 3 nodes. 
 1 node (the serial host hooked to the PC) was programmed with: 
 
 bin/softdevice/s140_nrf52_6.0.0_softdevice.hex bin/bootloader/gccarmemb/mesh_bootloader_gccarmemb_nrf52840_xxAA</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Oct 2018 13:26:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38992/mesh-sdk2-1-1-dfu-serial-host-question" /><item><title>RE: Mesh SDK2.1.1 DFU Serial Host Question</title><link>https://devzone.nordicsemi.com/thread/151256?ContentTypeID=1</link><pubDate>Tue, 02 Oct 2018 13:26:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dafbc66b-5699-4225-8e9a-8c40858b6617</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;Q1: Yes, using the application ID to distinguish between different type of firmware on different devices is the recommended solution.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q2: Yes, that sounds like the way to go.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Q3: No, not that I am aware of.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards&lt;br /&gt;Bjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>