Implementation of an RTC on nrf52832 - drift issueshttps://devzone.nordicsemi.com/f/nordic-q-a/66507/implementation-of-an-rtc-on-nrf52832---drift-issuesHi-- I tried to implement an internally managed RTC using the app timer library, but came to find the error on that is too much for an RTC (~25 min lost over a few days). I started trying to find other alternatives, and came across this github repoen-USTelligent Community 13Tue, 29 Sep 2020 15:28:23 GMTRE: Implementation of an RTC on nrf52832 - drift issueshttps://devzone.nordicsemi.com/thread/272118?ContentTypeID=1Tue, 29 Sep 2020 15:28:23 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a86d73bb-0eb6-4b14-8029-0d38571f2df5rsoc16<p>Misery breeds company! Yeah, the actual issue was I switched everything over to RTC2, but I masked the register compare wrong (RTC2 was already enabled in the config header file). Once I fixed that error, I was good to go</p><div style="clear:both;"></div>RE: Implementation of an RTC on nrf52832 - drift issueshttps://devzone.nordicsemi.com/thread/272117?ContentTypeID=1Tue, 29 Sep 2020 15:25:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:945e34c2-419b-4ab9-86d4-66a995d21200Ivan Herrera<p>No worries. Believe it or not but I was also looking at the calendar example today to figure out a way to keep track of time without app_timer, hence I knew why you were having trouble :)&nbsp;</p><div style="clear:both;"></div>RE: Implementation of an RTC on nrf52832 - drift issueshttps://devzone.nordicsemi.com/thread/272116?ContentTypeID=1Tue, 29 Sep 2020 15:23:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4bd11f04-bc94-4969-8ffe-2623a470cd23rsoc16<p>Sike, never mind. Just got it. another stupid error. Sorry! Appreciate the quick help.</p><div style="clear:both;"></div>RE: Implementation of an RTC on nrf52832 - drift issueshttps://devzone.nordicsemi.com/thread/272115?ContentTypeID=1Tue, 29 Sep 2020 15:22:09 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8c64e56c-8841-4584-b396-e905b64eb7e8Ivan Herrera<p>Have you enabled RTC2 in sdk_config.h?&nbsp;</p><div style="clear:both;"></div>RE: Implementation of an RTC on nrf52832 - drift issueshttps://devzone.nordicsemi.com/thread/272112?ContentTypeID=1Tue, 29 Sep 2020 15:21:11 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e116de44-596c-4a53-b62f-7c3a636ac070rsoc16<p>Ah, im an idiot. Thanks, I swapped the defines for&nbsp;</p> <p>#define CAL_RTC NRF_RTC0<br />#define CAL_RTC_IRQn RTC0_IRQn<br />#define CAL_RTC_IRQHandler RTC0_IRQHandler</p> <p>to</p> <p>#define CAL_RTC NRF_RTC2<br />#define CAL_RTC_IRQn RTC2_IRQn<br />#define CAL_RTC_IRQHandler RTC2_IRQHandler</p> <p></p> <p>I still am having issues getting the callback going in the example after doing this. Is there something extra I need to do?</p><div style="clear:both;"></div>RE: Implementation of an RTC on nrf52832 - drift issueshttps://devzone.nordicsemi.com/thread/272110?ContentTypeID=1Tue, 29 Sep 2020 15:09:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2a0a62ad-55e3-473b-b37c-1ab594d5b141Ivan Herrera[quote userid="90073" url="~/f/nordic-q-a/66507/implementation-of-an-rtc-on-nrf52832---drift-issues"] Does the calendar implementation conflict with the use of a soft device? Is there any way around it if it does?[/quote] <p></p> <p>In the README of that example it is stated that this example does not support the softdevice. You can also see that it uses RTC0, which is used by the SoftDevice, so using these together will create issues for sure. RTC1 (if not using app_timer) and RTC2 should be free to use though.</p><div style="clear:both;"></div>