<?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>Why No firmware to activate?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62127/why-no-firmware-to-activate</link><description>Hello 
 Using PCA10040 dev board, 
 Building with SDK 16, &amp;amp; S112 - using ses 
 Running ..\examples\dfu\secure_bootloader\pca10040_uart_debug 
 
 Using nrfutil to download my package via serial port - all looks good ( package is just app hex file) 
 via</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 12 Jun 2020 07:08:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62127/why-no-firmware-to-activate" /><item><title>RE: Why No firmware to activate?</title><link>https://devzone.nordicsemi.com/thread/254606?ContentTypeID=1</link><pubDate>Fri, 12 Jun 2020 07:08:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c8b6c4e-8a3b-4c64-9fd0-dcc9c6ace9ac</guid><dc:creator>MichaelKilleen</dc:creator><description>&lt;p&gt;Thank you, moved to sample app with ble already included. Updated app with our test code. Building this worked and was also able to upgrade via dfu/boot loader. My previous app was based of sample code with ble support. Not sure what made this work&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why No firmware to activate?</title><link>https://devzone.nordicsemi.com/thread/253584?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 14:40:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aaf975a9-357c-4949-800d-a11aa2c82018</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;MBR should only be used for updating bootloader, and jumping to bootloader on boot, so I do not think the problem is with that one. You may also try to rebuild the bootloader with a clean SDK in case the application-rebuild does not help.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why No firmware to activate?</title><link>https://devzone.nordicsemi.com/thread/253578?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 14:22:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ef2fc1e7-ab26-4a82-9eff-e73396f886b1</guid><dc:creator>MichaelKilleen</dc:creator><description>&lt;p&gt;boot loader has different keys, otherwise no difference, when program boot loader get restart messages (maybe some already captured in RTT viewer), nrfutil gets to 100% - Device programmed&lt;/p&gt;
&lt;p&gt;So possibly messages/errors output not very clear. Going back to build my test app again, may be missed a trick or two in that project. Possibly related to MBR?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why No firmware to activate?</title><link>https://devzone.nordicsemi.com/thread/253573?ContentTypeID=1</link><pubDate>Fri, 05 Jun 2020 14:12:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e18b0a6-e9fb-4b95-9025-758ef0164dcd</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Have you made many changes to the bootloader? It seems that the log shows multiple resets, is that correct, or have you reset the board yourself?&lt;/p&gt;
&lt;p&gt;What is the output from &amp;#39;&lt;span&gt;nrfutil dfu serial&amp;#39; command?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why No firmware to activate?</title><link>https://devzone.nordicsemi.com/thread/253301?ContentTypeID=1</link><pubDate>Thu, 04 Jun 2020 13:06:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ae4cf977-3508-48d3-ab4d-6933348a75c7</guid><dc:creator>MichaelKilleen</dc:creator><description>&lt;p&gt;Hi Lorgen,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks for feedback. Did create and use new private and public keys. The logs message say the that &amp;quot;Image verified&amp;quot;. Do not see message saying something is wrong - should we?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why No firmware to activate?</title><link>https://devzone.nordicsemi.com/thread/253287?ContentTypeID=1</link><pubDate>Thu, 04 Jun 2020 12:28:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7ce85dd1-db0e-4d88-9e5a-4fa3a085aec3</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;pca10040_uart_debug can only be used with the test-images in examples\dfu\secure_dfu_test_images, as it uses the public key for Nordic&amp;#39;s un-published private key. Please make sure you follow the &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v16.0.0/sdk_app_serial_dfu_bootloader.html"&gt;instructions in the documentation&lt;/a&gt; closely, to generate keys, bootloader settings, DFU package, etc.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;br /&gt;Jørgen&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why</title><link>https://devzone.nordicsemi.com/thread/253097?ContentTypeID=1</link><pubDate>Wed, 03 Jun 2020 16:14:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:592bc204-8513-4c81-a020-5367eba7eded</guid><dc:creator>MichaelKilleen</dc:creator><description>&lt;p&gt;Title truncated when posted... should be &amp;quot;Why&amp;nbsp;&lt;span&gt;No firmware to activate&amp;quot; ?&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>