nrf_drv_rtc_tick_enable crash app when using DFU secure bootloader (with buttonless dfu App)

RE: nrf_drv_rtc_tick_enable crash app when using DFU secure bootloader (with buttonless dfu App)

ClementGoobie — Fri, 11 Jan 2019 08:41:18 GMT

I found the solution to my problem :

My deice has 2 RTC : one for the soft device and the other for the app. So 'ill simply use the timers inside the app_timer which use RTC1 to program my date saving and increment.

Thanks for your help Hung

RE: nrf_drv_rtc_tick_enable crash app when using DFU secure bootloader (with buttonless dfu App)

ClementGoobie — Thu, 10 Jan 2019 16:39:42 GMT

Thanks for your reply, I'll give it a try and keep you updated

RE: nrf_drv_rtc_tick_enable crash app when using DFU secure bootloader (with buttonless dfu App)

Hung Bui — Thu, 10 Jan 2019 16:00:48 GMT

I am afraid that on the nRF52810 you can't use drv_rtc at the same time with the app_timer. The chip has only 2 RTC and one is already occupied by the softdevice.

If you just need to keep track of the time, you can think of using the app_timer and have a timer event occurs every 1 sec (or faster if you need)

RE: nrf_drv_rtc_tick_enable crash app when using DFU secure bootloader (with buttonless dfu App)

ClementGoobie — Thu, 10 Jan 2019 15:21:15 GMT

Thanks Hung,

I've already seen your method to debug. But I don't know how to debug with nrfjprog with gcc. I think I should use JLinkExe with gdb ?

For now I have NRF_LOG activated and it prints me on uart the Logs when everything is alright but nothing is printed when nrf_drv_rtc_tick_enable is called in the programm. Even previews prints to this function are not showing up.

Concerning your timer app I didn't seen it before. My final goal is to use rtc low power to keep track of time with a CTS_Client.

Thanks for your help,

Clément

RE: nrf_drv_rtc_tick_enable crash app when using DFU secure bootloader (with buttonless dfu App)

Hung Bui — Thu, 10 Jan 2019 14:29:57 GMT

Hi Clement,

Correct, when the softdevice is enabled the nrf_drv_clock is also initialized. You can find the code inside sd_state_evt_handler() where the clock driver is initialized.

You don't need to call lfclk_config() after the softdevice is enabled.

Could you step into the rtc_config() and check at which line it will crash and which error code ?

You may want to follow this debug guide.

Note that we already have app_timer inside the example and it utilize RTC1