<?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>DFU-OTA SDK11 to SDK15</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/39883/dfu-ota-sdk11-to-sdk15</link><description>Hello 
 I&amp;#39;m wondering if it is possible to upgrade over-the-air from SDK11 to SDK15. 
 I know already that using the example bootloader from SDK11 will not work because the secured bootloader of SDK15 is bigger (24kB for SDK15 vs 16kB for SDK11) 
 Therefore</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 26 Oct 2018 11:41:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/39883/dfu-ota-sdk11-to-sdk15" /><item><title>RE: DFU-OTA SDK11 to SDK15</title><link>https://devzone.nordicsemi.com/thread/154665?ContentTypeID=1</link><pubDate>Fri, 26 Oct 2018 11:41:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6b945daf-310d-4bbe-bcdd-7bd6242d1c2f</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We need to know more about the errors you are getting in order to suggest a solution, but it should be possible to do this upgrade. As you are changing the major version of the SoftDevice, you have to update the bootloader and SoftDevice together in a single DFU image. That should not be a problem, provided you take the following into account (which it seems you might have done):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;If you have already adjusted for the increased bootloader size, then that should be OK, but typically i assume units in the field does not have this adjustment? If not, then you can rewrite the UICR to contain a new bootloader start address using a special legacy bootloader (which would then be an intermediate step). &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/18199/dfu---updating-from-legacy-sdk-v11-0-0-bootloader-to-secure-sdk-v12-x-0-bootloader/70272#70272"&gt;This post&lt;/a&gt; describes it in detail.&lt;/li&gt;
&lt;li&gt;If you update to a bootloader from a SDK version &amp;lt; 15.0.0 and use a SoftDevice with a different size, you will get a failure due to the &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/27862/update-sd-bl-app-from-sdk-v13-to-v14-via-dfu-fails/109831#109831"&gt;bootloader not handling a change in SoftDevice size&lt;/a&gt; (and thus application start address). That is not a problem with SDK 15, though, so it should not affect you.&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>