<?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>Boot loop during secure DFU upgrade with S140 from SDK 14.2.0 to SDK 15.0.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34164/boot-loop-during-secure-dfu-upgrade-with-s140-from-sdk-14-2-0-to-sdk-15-0-0</link><description>I&amp;#39;m in the process of migrating from SDK 14.2.0 S140 5.0.0-2.alpha to SDK 15.0.0 with S140 6.0.0 on an nRF5280 based custom board. 
 It should be possible to do a secure DFU upgrade of BL+SD+APP by creating a zip package containing all these items. The</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 09 May 2018 11:10:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34164/boot-loop-during-secure-dfu-upgrade-with-s140-from-sdk-14-2-0-to-sdk-15-0-0" /><item><title>RE: Boot loop during secure DFU upgrade with S140 from SDK 14.2.0 to SDK 15.0.0</title><link>https://devzone.nordicsemi.com/thread/131483?ContentTypeID=1</link><pubDate>Wed, 09 May 2018 11:10:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:25c3c776-9775-4036-b52b-132632de96df</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;According to the release notes, s140_nrf52840_5.0.0-2.alpha uses MBR version 2.1.0, which has the following limitation:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The SV-calls sd_mbr_command_vector_table_base_set() and sd_mbr_command_copy_bl() are not supported&lt;br /&gt;(DRGN-8197). Using these calls leads to undefined behavior.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;What that means in practice is that bootloader update is not possible from the s140 5.0.0-2.alpha SoftDevice, as it leads to the behavior that you are experiencing. Since the MBR is not updated on SoftDevice update, the only option to fix this issue is to program MBR version 2.3.0, where the issue has been resolved, using a programmer. Preferably by using s140 version 6.0.0.&lt;/p&gt;
&lt;p&gt;The issue only applies to alpha releases of the s140 SoftDevice, and was fixed prior to release of the (qualified) s140 v6.0.0 release which is the first production quality SoftDevice for the nRF52840.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>