<?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>The issue where protect is automatically enabled every time the firmware is written</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116478/the-issue-where-protect-is-automatically-enabled-every-time-the-firmware-is-written</link><description>Hello, 
 I have a question regarding a recent issue. 
 I&amp;#39;m currently developing with the nRF52840 IC or EVM, and I&amp;#39;m facing a problem. Whenever I write firmware to the flash, it seems that the read-protect mode is automatically enabled. This makes development</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 26 Nov 2024 17:13:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116478/the-issue-where-protect-is-automatically-enabled-every-time-the-firmware-is-written" /><item><title>RE: The issue where protect is automatically enabled every time the firmware is written</title><link>https://devzone.nordicsemi.com/thread/512206?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 17:13:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c9212d55-99aa-46ea-adbf-a2670987f00b</guid><dc:creator>naya</dc:creator><description>&lt;p&gt;Thank you very much for answering my inquiry!&lt;/p&gt;
&lt;div id="__endic_crx__"&gt;
&lt;div class="css-diqpy0"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The issue where protect is automatically enabled every time the firmware is written</title><link>https://devzone.nordicsemi.com/thread/512101?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 12:38:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ecc0a9b1-ec08-4be8-8dc1-30d9bbfb128d</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;For the nRF 5 SDK, to disable the access port protection for debugging, follow these steps:&lt;/p&gt;
&lt;p&gt;a. Run&amp;nbsp;nrfjprog --recover -f nrf52&lt;/p&gt;
&lt;p&gt;b. Compile your code without the ENABLE_APPROTECT define.&lt;/p&gt;
&lt;p&gt;c. Write HwDisabled (0x5A) to UICR.APPROTECT. This can be done in your code.&lt;/p&gt;
&lt;p&gt;d. Flash the compiled code and perform any reset to run the code. The programmed code will open the access port by writing to APPROTECT.DISABLE during start-up.&lt;/p&gt;
&lt;p&gt;If you want to keep the debug interface open across power cycles, you need to add code at the beginning of your application to disable APPROTECT. Here&amp;#39;s an example of how to do this:&lt;br /&gt;NRF_APPROTECT-&amp;gt;DISABLE = APPROTECT_DISABLE_DISABLE_SwDisable;&lt;/p&gt;
&lt;p&gt;By implementing these steps, you should be able to keep the debug interface open and avoid having to perform recovery mode every time you flash new firmware.&lt;/p&gt;
&lt;p&gt;How to correctly disable APPPROTECT is also detailed in the following ticket:&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/116408/unresponsive-device-when-flashing-after-disabling-appprotect"&gt;Unresponsive device when flashing after disabling APPPROTECT&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Swathy&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The issue where protect is automatically enabled every time the firmware is written</title><link>https://devzone.nordicsemi.com/thread/511368?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2024 16:59:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5f3c8630-b58c-4ce1-bb8d-711a71adc490</guid><dc:creator>naya</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Thank you very much for reviewing the issue. We are also using the nRF Connect SDK, so it will likely be helpful for future use with the 52840. However, the current issue is occurring in a project that uses the nRF52 SDK, version 17.02. I would greatly appreciate it if you could guide me once again on how to resolve this issue within this SDK. Your assistance would be highly appreciated.&lt;/p&gt;
&lt;p&gt;Thank you in advance!&lt;/p&gt;
&lt;div id="__endic_crx__"&gt;
&lt;div class="css-diqpy0"&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The issue where protect is automatically enabled every time the firmware is written</title><link>https://devzone.nordicsemi.com/thread/511286?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2024 12:48:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d8a071be-ebcd-4389-a3c4-accee0b2e913</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The nRF52840 Rev 3 has APPROTECT enabled by default after every reset or power cycle. This is a security feature designed to protect the device from unauthorized access.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I assume you are using the nRF Connect SDK..&amp;nbsp;In your project configuration, add the following Kconfig option to disable APPROTECT:&lt;br /&gt;CONFIG_NRF_APPROTECT_LOCK=n&lt;/p&gt;
&lt;p&gt;This configuration will ensure that the firmware doesn&amp;#39;t lock the access port on boot:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/security/ap_protect.html#enabling_software_ap-protect_with_confignrfapprotectlock"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/security/ap_protect.html#enabling_software_ap-protect_with_confignrfapprotectlock&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Swathy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>