<?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>New rules of UICR.CLENR0 for SOFTDEVICE V8.00?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/7375/new-rules-of-uicr-clenr0-for-softdevice-v8-00</link><description>Hi,
I updated to softdevice 8.00 recently, and found something different with softdevice 6.00. 
 When trying to program the new softdevice hex to the chip using nrfgo studio v 1.15, it fails. But using the &amp;quot;flash_softdevice&amp;quot; target of Keil project is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 Jul 2015 12:01:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/7375/new-rules-of-uicr-clenr0-for-softdevice-v8-00" /><item><title>RE: New rules of UICR.CLENR0 for SOFTDEVICE V8.00?</title><link>https://devzone.nordicsemi.com/thread/26201?ContentTypeID=1</link><pubDate>Tue, 21 Jul 2015 12:01:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5ac49f3e-c7c5-45d3-be19-ffb97ffaf8a9</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;xc0903, ff this answer helped you then please click the ✓ to the left of the answer so that others can come and look here.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: New rules of UICR.CLENR0 for SOFTDEVICE V8.00?</title><link>https://devzone.nordicsemi.com/thread/26200?ContentTypeID=1</link><pubDate>Sat, 27 Jun 2015 01:58:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf67a919-4a3d-43af-a4b8-297913d7702b</guid><dc:creator>xc0903</dc:creator><description>&lt;p&gt;Thanks for your explanation. It&amp;#39;s late because visiting here is slow in China. Best wishes!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: New rules of UICR.CLENR0 for SOFTDEVICE V8.00?</title><link>https://devzone.nordicsemi.com/thread/26199?ContentTypeID=1</link><pubDate>Mon, 01 Jun 2015 18:40:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2037df6b-5afd-4b31-915a-cac3bec2cc1b</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Softdevice does not write to UICR.CLENR0 by default now. I think this has changed in 7.x.
This means that by default softdevice is not protected and readback is not enabled. As you have noticed, softdevice size is located inside a structure located at memory address 0X3000.
Application can write to UICR.CLENR0 if it wants to protect softdevice and make few peripherals restricted to application.&lt;/p&gt;
&lt;p&gt;The reason for not writing to CLENR0 register now is to allow softdevice upgrades by DFU which could be larger in size than set in CLENR0 register. But once this register is written, it cannot be changed in DFU, because DFU will not be able to erase UICR registers as it only erase pages, never does an eraseall.
I probably have confused you, please ask anything if you need more clarifications.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>