<?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>readback register and security</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/886/readback-register-and-security</link><description>On the nRF51822, I see that by programming the readback protect register, one can prevent reading code regions 0 and 1 from the SWD interface. However, if one had access to the SWD interface, a debugger, and the nrfjprog tool, it appears that the UICR</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 15 Nov 2013 11:45:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/886/readback-register-and-security" /><item><title>RE: readback register and security</title><link>https://devzone.nordicsemi.com/thread/4337?ContentTypeID=1</link><pubDate>Fri, 15 Nov 2013 11:45:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:876bc418-0d2b-4199-b7d9-d64196a3cd4f</guid><dc:creator>Ole Morten</dc:creator><description>&lt;p&gt;As far as I know, enabling read-back protection should give the full protection you&amp;#39;re after. The ERASEUICR register is not available on an nRF51822, since it doesn&amp;#39;t have any pre-programmed code, as shown in table 4 in the nRF51822 Reference Manual, and hence there should be no way of getting access to code on an nRF51822 if read-back protection has been set. The only way to disable protection would be to do an erase-all, in which case the protected code would also be gone.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>