<?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/"><channel><title>Working with the nRF52 Series&amp;#39; improved APPROTECT</title><link>/nordic/nordic-blog/b/blog/posts/working-with-the-nrf52-series-improved-approtect</link><description>New revisions of nRF52805 (revision 2, build codes Bx0) , nRF52810 (revision 3, build codes Ex0) , nrf52811 (revision 2, build codes Bx0) , nRF52820 (revision 3, build codes Dx0) , nRF52833 (revision 2, build codes Bx0) , nRF52832 (revision 3, build codes</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><item><title>RE: Working with the nRF52 Series&amp;#39; improved APPROTECT</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/working-with-the-nrf52-series-improved-approtect</link><pubDate>Fri, 26 May 2023 19:01:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d8b0027-a1f3-43fb-91bf-da213867a7ea</guid><dc:creator>J.P. Hutchins</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;Generally, I&amp;#39;d like security like&lt;br /&gt;&lt;br /&gt;1) Enabling a secure immutable bootloader (locking that flash region), signing/encrypting updates, etc&lt;br /&gt;2) Locking debug port access&lt;br /&gt;&lt;br /&gt;What concerns me, is that it seems like the debug port access lock can be undone by erasing all flash through CTRL-AP.&amp;nbsp; Is there a way to lock the debug port access and make it impossible to gain access again?&lt;br /&gt;&lt;br /&gt;Technically I would prefer something like requiring a key to unlock the DAP but if that&amp;#39;s not possible then I&amp;#39;d like to know if it&amp;#39;s possible to lock the DAP &lt;span&gt;irrevocably.&lt;/span&gt;&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1422&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Working with the nRF52 Series&amp;#39; improved APPROTECT</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/working-with-the-nrf52-series-improved-approtect</link><pubDate>Tue, 21 Feb 2023 12:02:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d8b0027-a1f3-43fb-91bf-da213867a7ea</guid><dc:creator>Tomasz</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;I have a project with SDK 15.2 and would like to upgrade the protection possible with the new release of silicon but&amp;nbsp;&lt;br /&gt;possibly avoid interfering with the app code and keep build environment the same for the app the same as it was.&amp;nbsp;&lt;br /&gt;As the bootloader is the very 1st bit of code to run, and I can update it independently, isn&amp;#39;t that the only part needs to be rebuilt with the latest MDK?&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1422&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Working with the nRF52 Series&amp;#39; improved APPROTECT</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/working-with-the-nrf52-series-improved-approtect</link><pubDate>Wed, 12 Oct 2022 12:09:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d8b0027-a1f3-43fb-91bf-da213867a7ea</guid><dc:creator>abhay_kr</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Thanks for sharing&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1422&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Working with the nRF52 Series&amp;#39; improved APPROTECT</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/working-with-the-nrf52-series-improved-approtect</link><pubDate>Thu, 05 May 2022 15:07:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d8b0027-a1f3-43fb-91bf-da213867a7ea</guid><dc:creator>toastedowl</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;I have been using NRF52832 Rev 2 and I&amp;#39;m trying to move to Rev 3.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m using SEGGER Embedded Studio on a MAC.&amp;nbsp; I&amp;#39;m using NRF5 SDK version&amp;nbsp;nRF5_SDK_17.1.0.&amp;nbsp; I downloaded nrf_mdk_8_46_0_gcc_nordiclicense and copied all of those files into the&amp;nbsp;nRF5_SDK_17.1.0_ddde560\modules\nrfx\mdk directory, overwriting what was there.&lt;/p&gt;
&lt;p&gt;I have 2 projects: an application and dfu/secure_booloader and I have added ENABLE_APPROTECT to the&amp;nbsp;preprocessor definitions.&lt;/p&gt;
&lt;p&gt;When I use nrfjprog, I get 0xFFFFFFFF&lt;/p&gt;
&lt;p&gt;1) nrfjprog --recover&lt;/p&gt;
&lt;p&gt;2)&amp;nbsp;nrfjprog --memrd 0x10001208&lt;/p&gt;
&lt;p&gt;RESULT: 0xFFFFFFFF&lt;/p&gt;
&lt;p&gt;I am doing this on a Rev 2 while waiting for my Rev 3&amp;#39;s.&amp;nbsp; Is this expected and will the behavior be different if I do the same thing on a rev 3?&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1422&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Working with the nRF52 Series&amp;#39; improved APPROTECT</title><link>https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/working-with-the-nrf52-series-improved-approtect</link><pubDate>Tue, 15 Mar 2022 21:22:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2d8b0027-a1f3-43fb-91bf-da213867a7ea</guid><dc:creator>Jay Tyzzer</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Excellent read. Thanks Daniel!!&lt;/p&gt;&lt;img src="https://devzone.nordicsemi.com/aggbug?PostID=1422&amp;AppID=4&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>