<?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>RTC interrupt does not wake up nRF52</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/14861/rtc-interrupt-does-not-wake-up-nrf52</link><description>I am having issues waking up nRF52 with s132 using the RTC interrupt. The same code is used on nRF51 with s130 and does not show this behavior. 
 The RTC is configured and the interrupts are fired and handled as expected every 10ms. The Softdefice is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 06 Jul 2016 14:14:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/14861/rtc-interrupt-does-not-wake-up-nrf52" /><item><title>RE: RTC interrupt does not wake up nRF52</title><link>https://devzone.nordicsemi.com/thread/56716?ContentTypeID=1</link><pubDate>Wed, 06 Jul 2016 14:14:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1fc4c8ab-673f-4c40-a734-760347e51cdf</guid><dc:creator>Stefan Birnir Sverrisson</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;It is also possible to configure the RTC on nRF52 with help of the nrf_drv_rtc driver. There is an &lt;a href="https://github.com/NordicSemiconductor/nRF52-ADC-examples/blob/master/saadc_low_power/main.c"&gt;example here&lt;/a&gt;, the saadc_low_power, that uses the nrf_drv_rtc driver and the RTC interrupt, which is working properly. Look at the rtc_config and rtc_handler functions in the example. When looking at the driver functions, I don&amp;#39;t quickly see any specific nRF52 code there.   So I would recommend to use the driver, or otherwise mimic what the driver does in order to have this working.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RTC interrupt does not wake up nRF52</title><link>https://devzone.nordicsemi.com/thread/56715?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2016 14:03:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:433627d9-8b74-4556-ac62-0eb071e08d78</guid><dc:creator>vik</dc:creator><description>&lt;p&gt;The IRQ handler for the RTC interrupt:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;void RTC1_IRQHandler (void)
{
    gu64_timerTicks += NRF_RTC1-&amp;gt;COUNTER;
    NRF_RTC1-&amp;gt;TASKS_CLEAR = 1;
    NRF_RTC1-&amp;gt;EVENTS_COMPARE[0] = 0;

    if ( sd_nvic_ClearPendingIRQ (RTC1_IRQn) != NRF_SUCCESS)
    {
        NVIC_ClearPendingIRQ (RTC1_IRQn);
    }
}
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The IRQ priority is defined this way for backward compatibility:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;#define NRF_APP_PRIORITY_LOW (APP_IRQ_PRIORITY_LOW)
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Lookin into app_util_Platform.h the priority of APP_IRQ_PRIORITY_LOW for nRF51 is 3 and for nRF52 it is 6. I also tried to set the IRQ priortiy for nRF52 to 3, but it did not solve the problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RTC interrupt does not wake up nRF52</title><link>https://devzone.nordicsemi.com/thread/56714?ContentTypeID=1</link><pubDate>Thu, 30 Jun 2016 12:55:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d22ed6d4-94a7-4d4c-870c-1170b50a24fc</guid><dc:creator>Anders Strand</dc:creator><description>&lt;p&gt;Can you post the code snippet where you handle the RTC1_IRQn interrupts? What is the numerical value of NRF_APP_PRIORITY_LOW? The priority levels have changed between nRF51 and 52&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>