auto update of epoch time

RE: auto update of epoch time

Einar Thorsrud — Tue, 11 Jan 2022 12:35:17 GMT

It is not possible. The frequency of the RTC is 32.768 kHz.

RE: auto update of epoch time

Tushar_V — Tue, 11 Jan 2022 12:02:34 GMT

Hi Einar Thorsrud,

In RTC which api can i use to get the value in microsecond

can u please tell me

Regards

Tushar

RE: auto update of epoch time

Einar Thorsrud — Tue, 11 Jan 2022 11:50:49 GMT

Hi Tushar,

There is no timer with that resolution in Zephyr (you could get CPU cycles, but that will most likely not work as I assume you don't intend to let the CPU run always, wasting power(?)).

Moreover, there is no low power clock source that will give you that resolution, so if you want that you will have to use a TIMER peripheral. You would need to handle wrap arounds though (perhaps simplest by using a 64 bit offset that you update whenever it wraps around), and normally when you read the time take the current timer value + the accumulated offset (+ whatever you got from syncing with the phone).

Note that this can never be low power, and there is physically no way to get better resolution than maximum 32.768 kHz with low power, as that is the frequency of the low power oscillator on the hardware. If you need low power (this is a key question!), then the only option to also give you better time resolution is to use an external RTC that can give a compromise between resolution, accuracy and power consumption that fits you requirements.

RE: auto update of epoch time

Tushar_V — Tue, 11 Jan 2022 11:33:34 GMT

Hi Einar Thorsrud,

I am using k_uptime_get() which is giving me values in millisecond in nrf_connect_sdk zephyr

is there any api which gives microsecond

Regards

Tushar

RE: auto update of epoch time

Einar Thorsrud — Fri, 07 Jan 2022 10:28:31 GMT

Hi Tushar,

That is up to you. The only thing you get from the SDK is time as ticks of a counter of some sort (there are many different options here, but it all comes down to the same), and you must relate that to the real time you got from the phone.

RE: auto update of epoch time

Tushar_V — Fri, 07 Jan 2022 09:16:25 GMT

Hi Einar Thorsrud,

timeutil_timegm() and timeutil_timegm64() converts human readable to epoch time but i am passing value from mobile to nrf52840dk is epoch value, so i want an api which gives me epoch value of the current timezone

Regards

Tushar

RE: auto update of epoch time

Einar Thorsrud — Fri, 07 Jan 2022 08:06:54 GMT

Hi Tushar,

I was too quick typing my answer previously. The timeutil_timegm() or timeutil_timegm64() is what you want. This gives you the current "time" and you offset it with the value you got from the same function when you got the actual time from the phone. (You won't get nanosecond resolution in any case, though.)

RE: auto update of epoch time

Tushar_V — Fri, 07 Jan 2022 06:47:36 GMT

Hi,

timeutil_sync_state_update() i have used this api can u please tell me how to give input to this api

Regards

Tushar

RE: auto update of epoch time

Einar Thorsrud — Thu, 06 Jan 2022 10:37:08 GMT

Hi Tushar,

Are you using nRF5 SDK or nRF Connect SDK?

If using nRF5 SDK get the local time at the same time as you get the time from the phone, and calculate the offset. Use that offset subsequently.

If using the nRF Connect DK you have all this done for you, so use the available time utilities I linked to in my previous post (for instance, use timeutil_sync_state_update() when you get the time from the phone).

RE: auto update of epoch time

Tushar_V — Thu, 06 Jan 2022 10:20:26 GMT

Hi Einar Thorsrud,

i want to give an epoch time for example 1641464227 from my mobile to nrf52840dk

then i want the epoch time to increment continuously with time sync

Regards

Tushar

RE: auto update of epoch time

Einar Thorsrud — Thu, 06 Jan 2022 10:13:03 GMT

Hi Tushar,

Which exact resolution do you need? If you really need close to nanosecond resolution, then you will have to use a timer which is based on the HF clock. This is only 16 MHz though, and there are no higher frequency clocks available. Also, this will force the HF clock always on, so your device will not be low power.

If you don't need as high resolution and needs the device to be low power, then it makes more sense to use an RTC based approach. The RTC is 32.768 kHz and the accuracy will be identical to the accuracy of the 32.768 kHz crystal you use on your board.

In the latter case, if using the nRF5 SDK, the simplest way to do this is to use the app_timer library which is almost always used, and change it slightly so that the you can use the get_now() function from outside (see this post). This will then give you an always increasing 64 bit timer value. With this, just compare that with the time you got when you synced with a mobile phone, and you will effectively have the epoch time. If using nRF Connect SDK, you already have support for epoch time.

Einar