RE: How to make RTC0 worked in repeated mode?

anusha — Sat, 08 Feb 2020 18:30:23 GMT

Thanks for the suggestions. I tried the task overflow approach since this is the interrupt I will be using and it is working.

RE: How to make RTC0 worked in repeated mode?

hmolesworth — Thu, 06 Feb 2020 17:38:20 GMT

The counter clear operation on the nRF52832 RTC doesn't generate a separate interrupt; and there are 2 other options. If this is the only interrupt used on the timer, you can trigger an overflow, which after 16 RTC ticks will behave as a counter clear and generate an interrupt if enabled.

// Cane use timer overflow trigger as pseudo clear, overflows 16 ticks later
  pRTC->TASKS_TRIGOVRFLW;     // Set COUNTER to 0xFFFFF0

If you have more than 1 interrupt in the RTC, then that not may be usable, in which case you can move the CC register forward on each interrupt to the next required value. There are two ways of doing this, read the current counter and add the offset to that or (preferably) add the offset directly to the CC register. The latter option has proved somewhat troublesome on occasion, but worth a try. The former risks losing accuracy as so many cycles are required to read the counter value. The sample code uses direct low-level registers to make clear what is going on; you can translate that the Nordic drivers if preferred.

//  Frequency fRTC [kHz] = 32.768 / (PRESCALER + 1 )
//  24-bit counter so overflows from 0xFFFFFF to 0x000000, prescaler is 12-bit range 0-4095
#define RTC_CRYSTAL_FREQUENCY   32768ul // Hz
#define TIMER_PRESCALER             0   // (32768Hz/(PRESCALER+1)) -> 32.768KHz or 30.517us tick when prescaler is 0
#define MSECS_PER_TICK             10   // Slower ticks means less power but also less accuracy, so choose a balance
#define TIMER_TICK  ((RTC_CRYSTAL_FREQUENCY*MSECS_PER_TICK)/1000) // Assumes 30.517 us basic crystal tick but adjusts automatically

void RTC0_IRQHandler(void)
{
   NRF_RTC_Type * pRTC = NRF_RTC0;
   // COUNTER and COMPARE[n] registers are all 24-bit. It seems an intermediate sampled
   // value must be used as pRTC->CC[1] += N; does not work for some reason, maybe requires
   // so many cycles to read back
   uint32_t CountValue = pRTC->COUNTER;
#if 0
   // TICK is interrupt every Prescaler overflow (if enabled)
   if (pRTC->EVENTS_TICK == 1)
   {
      // 32.768kHz for 8-bit overflow with divisor set to 0 (ie /1) is 30.52 uSeconds
      pRTC->EVENTS_TICK = 0;
   }
   // OVRFLW is interrupt every RTC Counter overflow (if enabled)
   if (pRTC->EVENTS_OVRFLW == 1)
   {
      // 32.768kHz for 24-bit overflow with divisor set to 0 (ie /1) is 512 seconds
      pRTC->EVENTS_OVRFLW = 0;
   }
   // Unused, 1,2,3
   if (pRTC->EVENTS_COMPARE[1] == 1)
   {
      pRTC->EVENTS_COMPARE[1] = 0;
   }
#endif
   if (pRTC->EVENTS_COMPARE[0] == 1)
   {
      pRTC->EVENTS_COMPARE[0] = 0;
      // Data Synchronization Barrier: completes when all explicit memory accesses before
      // last instruction completes to avoid spurious interrupt
      __DSB();
      // TIMER_TICK compare value, will generate next EVENTS_COMPARE[1]
      pRTC->CC[1] = CountValue + TIMER_TICK;
      // Update generic System Timer or whatever here
      // blahblah
   }
}

The preferred approach:

//  Frequency fRTC [kHz] = 32.768 / (PRESCALER + 1 )
//  24-bit counter so overflows from 0xFFFFFF to 0x000000, prescaler is 12-bit range 0-4095
#define RTC_CRYSTAL_FREQUENCY   32768ul // Hz
#define TIMER_PRESCALER             0   // (32768Hz/(PRESCALER+1)) -> 32.768KHz or 30.517us tick when prescaler is 0
#define MSECS_PER_TICK             10   // Slower ticks means less power but also less accuracy, so choose a balance
#define TIMER_TICK  ((RTC_CRYSTAL_FREQUENCY*MSECS_PER_TICK)/1000) // Assumes 30.517 us basic crystal tick but adjusts automatically

void RTC0_IRQHandler(void)
{
   NRF_RTC_Type * pRTC = NRF_RTC0;
   // COUNTER and COMPARE[n] registers are all 24-bit
   if (pRTC->EVENTS_COMPARE[0] == 1)
   {
      pRTC->EVENTS_COMPARE[0] = 0;
      // Data Synchronization Barrier: completes when all explicit memory accesses before
      // last instruction completes to avoid spurious interrupt
      __DSB();
       // TIMER_TICK compare value, will generate next EVENTS_COMPARE[1]
      pRTC->CC[1] += TIMER_TICK;
      // Update generic System Timer or whatever here
      // blahblah
   }
}

RE: How to make RTC0 worked in repeated mode?

anusha — Thu, 06 Feb 2020 14:19:44 GMT

Also added the following line in rtc_handler():

nrf_drv_rtc_enable(&rtc);

but it still did not help.

RE: How to make RTC0 worked in repeated mode?

haakonsh — Thu, 06 Feb 2020 14:16:53 GMT

you need to CLEAR the counter by triggering the TASKS_CLEAR, either by calling nrfx_rtc_counter_clear or by connecting the EVENTS_COMPARE[0] to the clear task by using a PPI channel.

If you use the PPI channel you will get free-running timer independent of the CPU.

Also note that the SoftDevice requires the use of the RTC0 peripheral, RTC1 and 2 is available to the application.