<?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>Low power mode and RTC, Timer and PPI</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51949/low-power-mode-and-rtc-timer-and-ppi</link><description>SDK15.3 
 nRF52840 
 S140 v6.1.1 
 
 Q1. I have an RTC compare event connected to a Timer count task over PPI. The Timer is configured in low power counter mode. My question is when I go into low power mode using sd_app_evt_wait(), will the RTC events</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 10 Sep 2019 09:02:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51949/low-power-mode-and-rtc-timer-and-ppi" /><item><title>RE: Low power mode and RTC, Timer and PPI</title><link>https://devzone.nordicsemi.com/thread/208843?ContentTypeID=1</link><pubDate>Tue, 10 Sep 2019 09:02:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc412b4e-034b-4f49-af94-0821166488bc</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;Q1)&lt;br /&gt;&lt;span&gt;sd_app_evt_wait() will put the MCU into SystemON Idle, where the CPU is at sleep but the peripheral sub-system is awake. This means that all peripherals are available, with PPI and EasyDMA. Anything running before you call&amp;nbsp;sd_app_evt_wait() will continue to do so. If a peripheral requires the CPU to run a driver the CPU will be woken up.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;Q2)&lt;br /&gt;Yes, because the PPI system requires the 16MHz clock tree, who&amp;#39;s a division of the HFCLK clock. &amp;#39;Low power mode&amp;#39; means that the HFCLK is turned off/on on-demand, vs &amp;#39;constant latency&amp;#39; where the HFCLK is always on to force a constant latency of the wake-up times of peripherals and CPU.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>