<?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>About nrfjprog resets..</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/47892/about-nrfjprog-resets</link><description>Hi, we have faced with the same issue as many nRF52 users, debug interface (DIF) will stay active after flashing and high (~3mA) continuous current remains, Power cycle will fix the situation. BUT this is not possible in production where batteries are</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 29 May 2019 15:03:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/47892/about-nrfjprog-resets" /><item><title>RE: About nrfjprog resets..</title><link>https://devzone.nordicsemi.com/thread/189948?ContentTypeID=1</link><pubDate>Wed, 29 May 2019 15:03:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:42435163-4328-485c-b860-122a8b77e78b</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;&amp;quot;&lt;span&gt;I did change our flashing script so that there will be&amp;nbsp;&lt;/span&gt;&lt;em&gt;&lt;strong&gt;reset&lt;/strong&gt;&lt;/em&gt;&lt;span&gt;&amp;nbsp;instead of&amp;nbsp;&lt;/span&gt;&lt;em&gt;&lt;strong&gt;pinreset&lt;/strong&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/em&gt;&lt;span&gt;in the end of the file --&amp;gt; no extra current anymore.&amp;quot; -&amp;nbsp;&lt;/span&gt;It sounds like you&amp;#39;ve already done it correctly.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About nrfjprog resets..</title><link>https://devzone.nordicsemi.com/thread/189925?ContentTypeID=1</link><pubDate>Wed, 29 May 2019 14:21:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6ba5c62c-6188-49a7-993a-9941a30b9b57</guid><dc:creator>kmalmiv16</dc:creator><description>&lt;p&gt;Hi Haakansh, and thanks for your quick response.&lt;/p&gt;
&lt;p&gt;Do you have any recommedations? How should we implement the flashing to avoid to end up to high current. This seems to be very popular topic, but most of the threads are quite old already.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: About nrfjprog resets..</title><link>https://devzone.nordicsemi.com/thread/189893?ContentTypeID=1</link><pubDate>Wed, 29 May 2019 13:09:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09f3fa2c-a0ce-4c91-a567-886d689fcb10</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;A reset will disable the Debug Access Port and thereby removing the excess current consumption. If you try to connect to the device via SWD after a reset the DAP will be enabled again and the excess current consumption will also follow.&amp;nbsp;You must, therefore,&amp;nbsp;make sure that a reset is the last thing you do during production programming.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>