<?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>About DFU code start address register between SDK15.3 and SDK16</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/54391/about-dfu-code-start-address-register-between-sdk15-3-and-sdk16</link><description>HI, 
 I find that the DFU code start address regsiter is different between SDK15.3 and SDK16 
 SDK15.3 
 MemorySegment name=&amp;quot;uicr_bootloader_start_address&amp;quot; start=&amp;quot;0x00000FF8&amp;quot; size=&amp;quot;0x4&amp;quot; 
 MemorySegment name=&amp;quot;uicr_mbr_params_page&amp;quot; start=&amp;quot;0x00000FFC&amp;quot; size</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 15 Nov 2019 13:43:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/54391/about-dfu-code-start-address-register-between-sdk15-3-and-sdk16" /><item><title>RE: About DFU code start address register between SDK15.3 and SDK16</title><link>https://devzone.nordicsemi.com/thread/220324?ContentTypeID=1</link><pubDate>Fri, 15 Nov 2019 13:43:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90a179ac-f0ec-4832-8790-1798d99d21c8</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Actually, prior to SDK15.3.0 (SDK... -&amp;gt; SDK15.2.0) the &amp;quot;uicr_bootloader_start_address&amp;quot; and &amp;quot;uicr_mbr_params_page&amp;quot; was written in UICR (hence the name), which is in 0x10001014/18. In SDK15.3.0 they tried to move it to the MBR (0x00000FF8/FC), but it caused some issues during the development phase for many developers because&amp;nbsp;some&amp;nbsp;IDEs didn&amp;#39;t handle this correctly. Hence, it was moved back to the UICR. This is not how the startup procedure in the chip decides whether there is a bootloader or not (I think), but this is how the applications check whether there is a bootloader or not.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Despite the changes, the bootloader should always be backwards compatible, so you shouldn&amp;#39;t need to worry about this when developing your application/bootloader.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>