<?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>OTA DFU s110 to s130 with UICR.CLENR0 set</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/45153/ota-dfu-s110-to-s130-with-uicr-clenr0-set</link><description>Hi, 
 Please help, I&amp;#39;ve been struggling with this problem for a week and I want to get to the bottom of it. 
 I have production devices in the field based on s110 v7.1.0. The newer firmware uses s130 2.0 and both work independently on the same hardware</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 Mar 2019 14:48:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/45153/ota-dfu-s110-to-s130-with-uicr-clenr0-set" /><item><title>RE: OTA DFU s110 to s130 with UICR.CLENR0 set</title><link>https://devzone.nordicsemi.com/thread/177636?ContentTypeID=1</link><pubDate>Thu, 21 Mar 2019 14:48:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7462328d-6edc-4aba-ac0d-0396fabc8641</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Karim,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As it mentioned in the documentation, and discussed partly &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/13145/s130-v2-soft-device-size-in-future-and-protection"&gt;here&lt;/a&gt;, it&amp;#39;s not possible to update to a softdevice bigger size than the size indicated by CLENR0. The reason is that the part of the softdevice the exceed the CLENR0 won&amp;#39;t be able to access the memory located under CLENR0 address. It&amp;#39;s the hardware protection (please refer to the spec) and you can&amp;#39;t &amp;quot;hack&amp;quot; the MBR to avoid that.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The only workaround is to erase the chip and not write to CLENR0, but then it&amp;#39;s not OTA DFU, unfortunately.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>