RTC test issue

RE: RTC test issue

Einar Thorsrud — Thu, 01 Oct 2020 07:05:15 GMT

Hi JK,

[quote user="jawadk"]the second value have to be equal to the first value + 32768. but that is nor accurate, what is the tolerance ? +-tolerance ?[/quote]

There are several factors here. First of all, the accuracy of your 32.768 kHz clock source. If you are using a 32.768 kHz crystal, then the accuracy is whatever is specified for the crystal. If using the internal RC, the accuracy is ±500 ppm if calibrated. Uncalibrated the accuracy is ±5 %. See electrical specification for the LFRC for details. If not calibrated, Secondly, there may be a delay when you sample the clock (getting RTC_val1 and RTC_val2). The latter should not matter on average though, if you do it the same way, but depending on how you do it you could see some jitter. (There could theoretically also be an issue with the reference clock you are using to measure 1 second).

Einar

RE: RTC test issue

jawadk — Thu, 01 Oct 2020 05:06:18 GMT

This is not about the wrap around.

Lets say that the RTC didn't wrap around.

I am getting the first RTC value, then delay for 1 second and then get second RTC value.

the second value have to be equal to the first value + 32768. but that is nor accurate, what is the tolerance ? +-tolerance ?

RE: RTC test issue

Einar Thorsrud — Mon, 18 May 2020 11:48:02 GMT

Hi JK,

It does not look like you handle that the RTC wraps around? If not, then it is expected that your test fails sometimes, when the RTC wraps around between you sampling RTC_val1 and RTC_val2.

Einar