<?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>Protect the firmware on the beacon</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/17101/protect-the-firmware-on-the-beacon</link><description>Hello 
 I want to understand how far the firmware that is burnt on to a Hardware is protected. Is it possible to actually read the firmware from a device (if the device has GVDC Pins) and re engineer the HEX file from it? What are the typical safeguards</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 17 Oct 2016 20:28:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/17101/protect-the-firmware-on-the-beacon" /><item><title>RE: Protect the firmware on the beacon</title><link>https://devzone.nordicsemi.com/thread/65595?ContentTypeID=1</link><pubDate>Mon, 17 Oct 2016 20:28:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3761d640-8000-43b7-92c9-23d704eac836</guid><dc:creator>pltv</dc:creator><description>&lt;p&gt;Thanks. But comment from @Wojtek says that it is still possible to dump firmare protect by that register and reverse engineer. Whats the final word on this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Protect the firmware on the beacon</title><link>https://devzone.nordicsemi.com/thread/65594?ContentTypeID=1</link><pubDate>Mon, 17 Oct 2016 12:26:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eddc02eb-f1cf-46b7-837b-c23e5ab0c238</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;After you have successfully programmed your device, you can enable readback protection with the RBPCONF register. You will then have no access to the flash or RAM from the outside. When unlocking the device, the RAM and FLASH will be erased.&lt;/p&gt;
&lt;p&gt;See chapter 8 in &lt;a href="http://infocenter.nordicsemi.com/pdf/nRF51_RM_v3.0.pdf"&gt;the reference manual&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Protect the firmware on the beacon</title><link>https://devzone.nordicsemi.com/thread/65593?ContentTypeID=1</link><pubDate>Mon, 17 Oct 2016 11:54:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f5da8104-f665-4aa2-96d1-8d1e8233546f</guid><dc:creator>Wojtek</dc:creator><description>&lt;p&gt;There is RBPCONF register, you can read about it in reference manual. HOWEVER it does not give you 100% security, as there already is method of dumping firmware protected by that register. But i think this is the only firmware security feature that is implemented in nrf51&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Protect the firmware on the beacon</title><link>https://devzone.nordicsemi.com/thread/65591?ContentTypeID=1</link><pubDate>Mon, 17 Oct 2016 11:48:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0947fa63-38bf-4b60-b79b-0fea8b71acdd</guid><dc:creator>pltv</dc:creator><description>&lt;p&gt;nRF51822 QFAC&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Protect the firmware on the beacon</title><link>https://devzone.nordicsemi.com/thread/65592?ContentTypeID=1</link><pubDate>Mon, 17 Oct 2016 11:47:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:12b55998-2da5-4e15-9951-c2d59d6862cd</guid><dc:creator>Wojtek</dc:creator><description>&lt;p&gt;Which chip are you asking about?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>