RTC1 Initialisation with soft device

RE: RTC1 Initialisation with soft device

RK — Thu, 31 Mar 2016 13:33:17 GMT

@Anders - might be good to put that (use of RTC) in the SDK notes for the FreeRTOS port, the notes for the other RTOS port says it uses RTC1, but I don't think the FreeRTOS one does, or perhaps I totally missed it.

The only reason I asked about the IRQ priority - well apart from that being the error code - is that during the switch from nRF51 to nRF52, and the removal of the old APP_PRIORITY macros, there was more than once I ended up with a hard-coded '1' for an IRQ priority in code intended for both platforms. That's high on the nRF51, but on the nRF52 it's a softdevice-used value. Since it's in the config file and that's subject to being edited a lot, actually checking the value being used seemed like a good idea.

RE: RTC1 Initialisation with soft device

Anders Strand — Thu, 31 Mar 2016 10:47:46 GMT

The freertos in our SDK uses RTC1 as a tick clock. From portmacro_cmsis.h line 120:

/* RTC register */
#define portNRF_RTC_REG        NRF_RTC1

By using the RTC instead of Systick, we can implement tickless idle mode.

Are you using the freertos port provided in our SDK, or have you made your own port?

@RK, in my config the i have the following definition of RTC2_CONFIG_IRQ_PRIORITY: APP_IRQ_PRIORITY_LOW =_PRIO_APP_LOW = 6

RE: RTC1 Initialisation with soft device

RK — Wed, 30 Mar 2016 03:30:36 GMT

.. actually looking at the nRF52 FreeRTOS port I'm not entirely sure what it does use as a timer source. The notes don't say, it does define the portable systick macro as RTC1 as the nrf51 port does but without following all the includes I can't work out whether it manages to use systick after all. I don't quite see how it does, as Systick doesn't tick when the processor sleeps, which means there's nothing to wake tasks.

RE: RTC1 Initialisation with soft device

RK — Wed, 30 Mar 2016 02:51:24 GMT

Systick won't work - not if you sleep the chip at all, you should use one of the nRF52 ports if you want FreeRTOS to work properly.

What is the numerical value of the IRQ priority, what actual number are you using? I keep asking you this, I can't see your nrf_drv_config.h file.

Similarly what priorities has the RTOS set for other peripherals, if it's set Systick to a high interrupt priority - that won't work either. I suggest dumping the contents of the NVIC enabled and priority registers just before the softdevice enable call and finding what's enabled and what priorities they have. The error message is pretty clear - one of your interrupt priorities at least is wrong, you just need to look at them all and find out which one.

RE: RTC1 Initialisation with soft device

Krishna — Wed, 30 Mar 2016 02:20:58 GMT

Sorry SysTick, I am using nrF52.

RTC2_CONFIG_IRQ_PRIORITY has low priority. It defined in nrf_drv_config.h

RE: RTC1 Initialisation with soft device

RK — Wed, 30 Mar 2016 00:22:07 GMT

What do you mean by 'SystemCore Clock'? Do you mean SysTick? Which chip are you using, nRF51 or nRF52? Systick doesn't tick when the device sleeps so that won't work, the RTOS ports for nRF5x use RTC1 because nRF51 doesn't have Systick and nRF52 does but it's not usable as an always-on timer.

RTC2_CONFIG_IRQ_PRIORITY is a define, what have you defined it as?

RE: RTC1 Initialisation with soft device

Krishna — Tue, 29 Mar 2016 18:39:36 GMT

We are using FreeRTOS, BLESTACK and RTC.

FreeRTOS uses SystemCore Clock,RTC0 is blocked by the Soft-device.

We are trying to use RTC1/RTC2 for tick events. When we try to enable the tick event for RTC1 or RTC2 we are getting below shown error. Below Error was displayed by enabling DEBUG.

ID=4097 pc=121272 info=2048,

I am assigning RTC2_CONFIG_IRQ_PRIORITY

RE: RTC1 Initialisation with soft device

Anders Strand — Tue, 29 Mar 2016 10:58:59 GMT

What RK said. See this

RE: RTC1 Initialisation with soft device

Krishna — Sat, 26 Mar 2016 13:44:40 GMT

const nrf_drv_rtc_t rtc = NRF_DRV_RTC_INSTANCE(2);

nrf_drv_rtc_config_t p_config;

p_config.interrupt_priority = RTC2_CONFIG_IRQ_PRIORITY; 
p_config.prescaler = 32; 
p_config.reliable = false; 
p_config.tick_latency = RTC_US_TO_TICKS(NRF_MAXIMUM_LATENCY_US, CONCAT_3(RTC, 2, _CONFIG_FREQUENCY));

err_code = nrf_drv_rtc_init(&rtc, &p_config, rtc0_event_handler);

I am assigning RTC2_CONFIG_IRQ_PRIORITY

RE: RTC1 Initialisation with soft device

RK — Sat, 26 Mar 2016 00:32:50 GMT

So what interrupt priority have you set for RTC1? If you haven't set it explicitly then it's zero and zero isn't available to you with the softdevice. The error message tells you exactly that.

RE: RTC1 Initialisation with soft device

RK — Fri, 25 Mar 2016 00:05:39 GMT

Usual questions. 'Controller reset' usually means you're in the app error handler, are you, put a breakpoint in and find out - then see which system function returned an error.

And post some code