<?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>How to flash examples to Dongle?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/41828/how-to-flash-examples-to-dongle</link><description>I bought a nRF52840 Dongle, to evaluate the use of nRF52840 for ZigBee purposes. 
 I have been able to flash such firmwares as \examples\peripheral\blinky\hex\blinky_pca10056_mbr.hex with the nRF Connect Programmer v1.0.1, however no LED flashing took</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 02 Jan 2019 09:27:32 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/41828/how-to-flash-examples-to-dongle" /><item><title>RE: How to flash examples to Dongle?</title><link>https://devzone.nordicsemi.com/thread/163374?ContentTypeID=1</link><pubDate>Wed, 02 Jan 2019 09:27:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b924dc63-d951-4fc0-8d46-d037c0dafc03</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Michail,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If you want to update an application that doesn&amp;#39;t require the softdevice, you can just use -sd-req 0x00. You don&amp;#39;t need to provide any softdevice hex file. Then you can update the .zip normally.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to flash examples to Dongle?</title><link>https://devzone.nordicsemi.com/thread/162914?ContentTypeID=1</link><pubDate>Sun, 23 Dec 2018 12:03:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:281e9713-14d1-437a-aa86-6290c0434b3f</guid><dc:creator>qm3ster</dc:creator><description>&lt;p&gt;Ok, so the Dongle is actually PCA10059.&lt;br /&gt;PCA10056 also uses the same&amp;nbsp;&lt;span&gt;nRF52840&lt;/span&gt; SoC but is not the dongle.&lt;br /&gt;Hence, I got the blinking working&amp;nbsp;by flashing `&lt;code&gt;\examples\peripheral\blinky\hex\blinky_pca10059_mbr.hex` with&lt;/code&gt;&amp;nbsp;the nRF Connect Programmer graphical app.&lt;br /&gt;This also worked for some other examples, like the BLE hexes that include a SoftDevice.&lt;/p&gt;
&lt;p&gt;But I can&amp;#39;t do the same with the nrfutil, because:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I haven&amp;#39;t been able to make a &amp;quot;dfu package&amp;quot; that doesn&amp;#39;t require any SoftDevice. So if I make one from the blinking example, it demands the soft device be installed. And if I `dfu` it when the requires SoftDevice is available, it just puts the `blinky` `--application` after the SoftDevice, which makes it not work. So, how can I make a `package.zip` that doesn&amp;#39;t require any soft device?&lt;/li&gt;
&lt;li&gt;When doing the same with a BLE example, it puts most of the `hex`&amp;#39;s contents, including a second copy of the SoftDevice, after the existing SoftDevice. Hence, once again the example doesn&amp;#39;t work. How would I make it update just the Application sector from the `hex`?&lt;br /&gt;It is definitely possible, because loading this `hex` in&amp;nbsp; Programmer graphical application shows me the different sectors separately. (But possibly not implemented yet)&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>