Nrf52 issue with RTC event running GPIOTE Task

RE: Nrf52 issue with RTC event running GPIOTE Task

Ole Bauck — Mon, 16 Jan 2017 11:47:31 GMT

Is the frequency on the timer 32768 KHz?:

#define RTC2_CONFIG_FREQUENCY    32768

I just tested your code and it works. You know that the pin will only toggle once (before the timer overflows)?

RE: Nrf52 issue with RTC event running GPIOTE Task

Ole Bauck — Mon, 16 Jan 2017 11:39:06 GMT

I was looking at SDK 12 and 13, I see that in SDK 11 it checks if the p_config is NULL.

RE: Nrf52 issue with RTC event running GPIOTE Task

labi — Fri, 13 Jan 2017 15:56:44 GMT

I tried your workaround, but that didn't work either. In nrf_drv_rtc_init() I see that its checking for the NULL parameter in SDK11 (see below). Perhaps you were looking at a different version of nrf_drv_rtc?

ret_code_t nrf_drv_rtc_init(nrf_drv_rtc_t const * const p_instance,
                        nrf_drv_rtc_config_t const * p_config,
                        nrf_drv_rtc_handler_t handler)
{
if (handler)
{
    m_handlers[p_instance->instance_id] = handler;
}
else
{
    return NRF_ERROR_INVALID_PARAM;
}

if (p_config == NULL)
{
    p_config = &m_default_config[p_instance->instance_id];
}

RE: Nrf52 issue with RTC event running GPIOTE Task

Ole Bauck — Fri, 13 Jan 2017 10:23:02 GMT

I see that the documentation says that the p_config parameter can be NULL to use the default config, but in the nrf_drv_rtc_init(..) function it does not seem to check if this is NULL and use the default config in that case. I will mark this as a bug internally.

Can you check if the code works if you use nrf_drv_rtc_config_t config = NRF_DRV_RTC_DEFAULT_CONFIG and pass this as the p_config parameter instead?