<?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>verify low power mode on 51422</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/13122/verify-low-power-mode-on-51422</link><description>Hi, 
 How Can I verify if my CPU has entered Low Power mode?? 
 I have power manage function running in the main loop , but when I put breakpoint on sd_app_evt_wait() or after same function, TASKS_LOWPWR stays to 0x00000000 and DCDCEN also stays to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 13 Apr 2016 08:35:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/13122/verify-low-power-mode-on-51422" /><item><title>RE: verify low power mode on 51422</title><link>https://devzone.nordicsemi.com/thread/50030?ContentTypeID=1</link><pubDate>Wed, 13 Apr 2016 08:35:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e34d3f96-1f6c-4277-9880-f4c6ee1699b1</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;DCDC:&lt;/strong&gt; The way it actually works on nRF51 is that you enable the DCDC manually , but in fact the DCDC is only enabled on radio activity. For activity on other peripherals, the DCDC is not enabled. This is automatically managed by hardware. As soon as you manually enable the DCDC, the DCDC register is set, but what that actually means is that the DCDC is managed by hardware, periodically enabling the DCDC on radio activity.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;TASKS_LOWPWR:&lt;/strong&gt; What sd_app_evt_wait() actually does is to disable the CPU. I think if you put breakpoint on sd_app_evt_wait(), then the sleep command has not been executed yet and the CPU is still active. If you put a breakpoint on the command after sd_app_evt_wait(), the device is already awake again. Also, when you are in debug mode, the high frequency 16MHz clock is always active, which also adds ~1mA to the current consumption of the device.&lt;/p&gt;
&lt;p&gt;You can see if the device is in low power mode by measuring the current consumption. Some more info on this is in the &lt;a href="https://devzone.nordicsemi.com/tutorials/11/"&gt;nRF51 current consumption guide&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>