<?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>issuing eraseuicr from openocd</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115684/issuing-eraseuicr-from-openocd</link><description>On Seeed Xiao nRF52840, I&amp;#39;m attempting to use reset (P0.18) as GPIO in a Zephyr (ZMK) app. 
 
 I&amp;#39;ve set 
 ``` 
 
 &amp;amp;uicr { 
 /delete-property/ gpio-as-nreset; 
 nfct-pins-as-gpios; 
 }; 
 ``` 
 in my overlay, and I need to erase the UICR. I do not have</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 31 Oct 2024 00:32:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115684/issuing-eraseuicr-from-openocd" /><item><title>RE: issuing eraseuicr from openocd</title><link>https://devzone.nordicsemi.com/thread/508601?ContentTypeID=1</link><pubDate>Thu, 31 Oct 2024 00:32:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4583d72e-fa91-4c26-a721-2a0f636ddb0b</guid><dc:creator>wlp</dc:creator><description>&lt;p&gt;Thanks Vidar. Please feel free to close this issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: issuing eraseuicr from openocd</title><link>https://devzone.nordicsemi.com/thread/508458?ContentTypeID=1</link><pubDate>Wed, 30 Oct 2024 07:48:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8b997d7-092f-49ac-9b4c-b10f87193f50</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Unfortunately, I&amp;#39;m not familiar with this project, but in our SDK examples, the application address will automatically default to 0x0 if the build does not include any bootloaders. It will likely be easier to test different configurations if you do a local install.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: issuing eraseuicr from openocd</title><link>https://devzone.nordicsemi.com/thread/508428?ContentTypeID=1</link><pubDate>Tue, 29 Oct 2024 18:38:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:71a2c346-391c-4161-a4f4-ffbfd9c9957d</guid><dc:creator>wlp</dc:creator><description>&lt;p&gt;Thanks so much for the reply. I did not change the application start address. I&amp;#39;m not sure how to do so in the zmk GitHub action I&amp;#39;ve been using to build... I may have to do a local install&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: issuing eraseuicr from openocd</title><link>https://devzone.nordicsemi.com/thread/507123?ContentTypeID=1</link><pubDate>Mon, 21 Oct 2024 11:59:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b57eb71c-0f45-4a48-8ab2-5daaa5e5e134</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="wlp"]from the Nordic website, it seems that eraseuicr is not a part of the ap register? Is it possible to set this in some other way?&amp;nbsp;[/quote]
&lt;p&gt;Correct, it is not a part of the AP registers.&amp;nbsp;If you want to only erase the UICR,&amp;nbsp;you need to write to the NVMC registers, first NVMC.CONFIG to enable erase, then NVMC.ERASEUICR to start the UICR erase. Performing the ERASEALL through the control access port (&lt;span&gt;nrf52.dap apreg 1 0x04 0x01`)&amp;nbsp;&lt;/span&gt;will erase both the FLASH and UICR.&lt;/p&gt;
[quote user="wlp"]I believe the application has been built correctly as when I flash a boatloader and then the application from the same build in uf2 format, it works as expected.[/quote]
&lt;p&gt;Did you change the application&amp;#39;s start address to 0x0 when programming it without the bootloader?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: issuing eraseuicr from openocd</title><link>https://devzone.nordicsemi.com/thread/507032?ContentTypeID=1</link><pubDate>Mon, 21 Oct 2024 02:31:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8e782249-43be-4800-bcc5-c471f304d57f</guid><dc:creator>wlp</dc:creator><description>&lt;p&gt;Upon examination of the Debug and Trace section of the&amp;nbsp;nRF52840 Product Specification&lt;br /&gt; from the Nordic website, it seems that eraseuicr is not a part of the ap register? Is it possible to set this in some other way?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I ran&amp;nbsp;&lt;span&gt;`nrf52.dap apreg 1 0x04 0x01`, and then flashed the application without a boot loader, but the application doesn&amp;#39;t seem to boot, despite flashing verifying as successful in both hex and bin formats. I believe the application has been built correctly as when I flash a boatloader and then the application from the same build in uf2 format, it works as expected.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>