<?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>nRF52 Constantly Waking From WFE()</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/28565/nrf52-constantly-waking-from-wfe</link><description>I&amp;#39;m trying to put the nRF52 into sleep by using the following code in a loop: 
 __WFE();
 __SEV();
 __WFE(); 
 
 But I see current consumption at around 5mA still, and when I debug I notice it the processor is constantly returning from WFE. How can</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Dec 2017 14:10:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/28565/nrf52-constantly-waking-from-wfe" /><item><title>RE: nRF52 Constantly Waking From WFE()</title><link>https://devzone.nordicsemi.com/thread/113180?ContentTypeID=1</link><pubDate>Wed, 20 Dec 2017 14:10:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:20bbce43-e1cc-4e51-aa15-71de20a4d96c</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;If this is the only thing you do in main (while(true) __WFE();__SEV();__WFE();)as you show in your other case, it is highly likely that this is a hw problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 Constantly Waking From WFE()</title><link>https://devzone.nordicsemi.com/thread/113179?ContentTypeID=1</link><pubDate>Thu, 14 Dec 2017 20:39:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e3aca28-5b46-4fda-b9d9-49b60611b5ff</guid><dc:creator>phipi</dc:creator><description>&lt;p&gt;This is with a custom design. I&amp;#39;m starting to think it&amp;#39;s a hardware issue because I&amp;#39;m seeing the high current even with a basic firmware that only does the WFE(), SEV() instructions and nothing else.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve started a new question for that but I&amp;#39;d still be curious if there is a way to determine what the source of the wake interrupt was.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 Constantly Waking From WFE()</title><link>https://devzone.nordicsemi.com/thread/113178?ContentTypeID=1</link><pubDate>Thu, 14 Dec 2017 20:30:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9cdd60b1-f95c-4e4d-bec3-eea62ad04e0a</guid><dc:creator>WestCoastDaz</dc:creator><description>&lt;p&gt;Is this the DK or a custom design?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 Constantly Waking From WFE()</title><link>https://devzone.nordicsemi.com/thread/113177?ContentTypeID=1</link><pubDate>Thu, 14 Dec 2017 20:25:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a580234-8a66-4045-82d7-8e18b829351b</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;The debugger should draw around 1.2 mA (if i remember correctly). What HW peripherals are you using?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 Constantly Waking From WFE()</title><link>https://devzone.nordicsemi.com/thread/113176?ContentTypeID=1</link><pubDate>Thu, 14 Dec 2017 16:44:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b67a0205-dba2-49e8-a77b-3ccfc88bb2c0</guid><dc:creator>phipi</dc:creator><description>&lt;p&gt;Thanks, that makes sense. However, I&amp;#39;m seeing 5mA of current on reset with no debugger connected. What&amp;#39;s the proper way to debug this issue then?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 Constantly Waking From WFE()</title><link>https://devzone.nordicsemi.com/thread/113175?ContentTypeID=1</link><pubDate>Wed, 13 Dec 2017 22:34:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a1670aa4-62a4-4753-b0cf-45e061745509</guid><dc:creator>WestCoastDaz</dc:creator><description>&lt;p&gt;Spizzak,&lt;/p&gt;
&lt;p&gt;The CPU can&amp;#39;t truely enter sleep when debuggin since the debug hardware is sill active.  It&amp;#39;s best to remove the debugger from your target for quiescent current measurements.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>