<?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>Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/30600/preventing-reprogramming-an-nrf52832</link><description>I can see that we can use APPROTECT to disable reading of the flash. 
 This seems to be reversible using: nrfjprog -f NRF52 --recover, which will erase the flash and allow reprogramming. 
 This protects the original code from being discovered but does</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 23 Feb 2018 04:11:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/30600/preventing-reprogramming-an-nrf52832" /><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121746?ContentTypeID=1</link><pubDate>Fri, 23 Feb 2018 04:11:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:00353b7d-35a2-4f99-9f33-b66ac6535974</guid><dc:creator>karthikeyan</dc:creator><description>&lt;p&gt;thanks edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121701?ContentTypeID=1</link><pubDate>Thu, 22 Feb 2018 15:26:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cf470fc8-3f6d-4079-a043-9071a846305a</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Well. If the SWDIO and SWCLK are shorted to GND, there is no way to program it. The only way to program it then would be through a bootloader, but this would have to be programmed in before the chip is soldered to the pcb, or at least before the SWDIO and SWCLK are grounded.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121531?ContentTypeID=1</link><pubDate>Wed, 21 Feb 2018 14:04:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d58a5653-3bd1-45a1-90da-3c58f55b1336</guid><dc:creator>Matt</dc:creator><description>&lt;p&gt;If folks are desperate to reprogram your chip they&amp;#39;ll always find a &amp;quot;way&amp;quot;. You have to think system protection then i.e. how would the &amp;quot;other&amp;quot; side verify the identity of your chip.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121465?ContentTypeID=1</link><pubDate>Wed, 21 Feb 2018 06:31:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2f6d23f-f536-43b6-8913-24d46ffbfefe</guid><dc:creator>karthikeyan</dc:creator><description>&lt;p&gt;hi edwin,&lt;/p&gt;
&lt;p&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;similar question to me. but i am programming the chip after soldering in my custom pcb. so after that how can i give protection. i need suggestion from hardware not in software.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121265?ContentTypeID=1</link><pubDate>Mon, 19 Feb 2018 13:43:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:18c5560a-b0f4-4536-b777-3bf2efbec1dd</guid><dc:creator>Matt</dc:creator><description>&lt;p&gt;The Decepticons are working on it... any &amp;quot;Transformer 6&amp;quot; fans here? :)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121257?ContentTypeID=1</link><pubDate>Mon, 19 Feb 2018 13:18:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1e056a35-3b57-4a1c-b855-0fd6853d05be</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;There is no way in software to prevent an erase and reprogramming of the nRF if they have physical access to the programming pins of the nRF, but as you say, there is readback protection, to prevent them from reading the .hex file programmed to the chip.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;What you could do, is to pre-program the chip, before soldering it on to the PCB. Then, on the PCB, you can ground the SWDIO and SWDCLK. This will make it impossible to program the chip unless you desolder the chip. In my opinion, if someone is able to desolder the chip, they might as well change the entire PCB with their own chip and firmware.&lt;/p&gt;
&lt;p&gt;BR,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121165?ContentTypeID=1</link><pubDate>Sun, 18 Feb 2018 02:08:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbefdc9f-584b-4cec-b2dd-0216f57177cd</guid><dc:creator>Matt</dc:creator><description>&lt;p&gt;Do you have control on the other end (eg. the GAP central / GATT client)? If you do then at least you can add some identify verification on the other end to identify the malicious app.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121159?ContentTypeID=1</link><pubDate>Sat, 17 Feb 2018 19:36:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a59086a0-51fb-44e2-8120-b0d059b8b1e5</guid><dc:creator>SRA</dc:creator><description>&lt;p&gt;Yea, and it doesn&amp;rsquo;t actually work that well. Plus the serial bootloader stays on and can&amp;rsquo;t be turned off.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121157?ContentTypeID=1</link><pubDate>Sat, 17 Feb 2018 16:33:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d694579f-4be6-4c10-92b3-af1950872194</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;NXP LPC176x has a &amp;quot;magic&amp;quot; value in flash that can disable both ROM bootloader and JTAG/SWD. The chip is locked for good unless there is a way to erase/flash in the customers firmware.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Preventing reprogramming an nrf52832</title><link>https://devzone.nordicsemi.com/thread/121156?ContentTypeID=1</link><pubDate>Sat, 17 Feb 2018 15:22:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0261ef49-f41e-41d3-bcd3-1999c9c556ae</guid><dc:creator>SRA</dc:creator><description>&lt;p&gt;I can&amp;rsquo;t think of any. Almost all cortex M parts that &amp;ldquo;disable JTAG/SW&amp;rdquo; do so for debug read/write commands but you could still recover/reset the chip with an erase. I have yet to see a Cortex M part with a lifecycle implementation.&lt;/p&gt;
&lt;p&gt;Are you just being overly concerned about your physical device that could surely be cloned?&lt;/p&gt;
&lt;p&gt;if I was tasked to do this, I guess I would program the firmware off the board, then solder the chip on to a board with internally shorted SW pins. That way the only access to program would DFU or desolder.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>