<?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>Why I couldn&amp;#39;t wirte RBPCONF register via JLinkExe?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10122/why-i-couldn-t-wirte-rbpconf-register-via-jlinkexe</link><description>I found I couln&amp;#39;t write RBPCONF register via JLinkExe on Mac (everytime i wrote the value just remains) but only through nrfgo with option &amp;quot;Lock entire chip from readback&amp;quot; selected on PC. I conjecture it&amp;#39;s on the concern of security. 
 But I&amp;#39;m just curious</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 07 Nov 2015 05:08:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10122/why-i-couldn-t-wirte-rbpconf-register-via-jlinkexe" /><item><title>RE: Why I couldn't wirte RBPCONF register via JLinkExe?</title><link>https://devzone.nordicsemi.com/thread/37545?ContentTypeID=1</link><pubDate>Sat, 07 Nov 2015 05:08:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:499adc14-40a8-49e8-9b95-237361da81fb</guid><dc:creator>joc</dc:creator><description>&lt;p&gt;Thanks for your answer!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why I couldn't wirte RBPCONF register via JLinkExe?</title><link>https://devzone.nordicsemi.com/thread/37544?ContentTypeID=1</link><pubDate>Sat, 07 Nov 2015 05:03:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11468e44-c056-4c30-a798-c859ff73f092</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Yes that&amp;#39;s the whole point of readback protection. If you were able to un-set it again, it wouldn&amp;#39;t be protected. You have to erase the whole chip to remove it. This is all in the manual.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why I couldn't wirte RBPCONF register via JLinkExe?</title><link>https://devzone.nordicsemi.com/thread/37543?ContentTypeID=1</link><pubDate>Sat, 07 Nov 2015 05:02:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:17e3d319-16ff-4be4-b011-c94a9a34b564</guid><dc:creator>joc</dc:creator><description>&lt;p&gt;Yes, after I write config register with write enabled, I could write the RBPCONF register! Thanks for your help! But I couldn&amp;#39;t write RBPCONF agiain meaning unlock the readback protection after the first write, is it reasonable ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Why I couldn't wirte RBPCONF register via JLinkExe?</title><link>https://devzone.nordicsemi.com/thread/37542?ContentTypeID=1</link><pubDate>Sat, 07 Nov 2015 01:27:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24bb2693-dda5-4734-b9a5-562564c55c98</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Did you enable writing to flash before trying to write the RBPCONF value? Try that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>