Long timer expires immediately

RE: Long timer expires immediately

Heidi — Fri, 27 Dec 2019 07:51:26 GMT

Hi again, you could try to do something like what was done here, instead of delaying x ms you delay max_timeout_length, and then keep doing this until the sum of delays has become x.

Best regards,

Heidi

RE: Long timer expires immediately

Krzysztof Chruscinski — Fri, 20 Dec 2019 05:29:44 GMT

Hi,

there is an ongoing work in zephyr to improve timeout API and eventually use 64 bit timeout values: https://github.com/zephyrproject-rtos/zephyr/issues/21305. That will fix this issue. For the workaround, i would just suggest building another layer on top of the timer which will fragment longer timeouts.

RE: Long timer expires immediately

Heidi — Thu, 19 Dec 2019 14:47:10 GMT

Okay, thank you for the information.

I will ask around but since it's the holidays here in Norway we are very low on staff. Worst case you will hear back during the beginning of week 2.

Best regards,

Heidi

RE: Long timer expires immediately

jlangballeswift — Thu, 19 Dec 2019 14:34:58 GMT

What I'm actually trying to accomplish is having multiple software timers to monitor the health of my different threads. I declare them as an array at compile-time and initialize them later at runtime.

static struct k_timer timers[NUM_MODULES];

...

for (int i = 0; i < NUM_MODULES; ++i)
{
    // Do init for each timer
}

The example I posted is just a stripped down version of this basically

RE: Long timer expires immediately

Heidi — Thu, 19 Dec 2019 14:21:19 GMT

Hi again! Can I ask why you don't want to do it the way you presented in your first example - which you said worked as expected?

RE: Long timer expires immediately

Heidi — Wed, 18 Dec 2019 16:17:57 GMT

Hi! So sorry about that, I misread your post.

I will get back to you with an answer tomorrow.

RE: Long timer expires immediately

jlangballeswift — Wed, 18 Dec 2019 16:11:15 GMT

Hi Heidi,

I am using the nRF9160 though...

RE: Long timer expires immediately

Heidi — Wed, 18 Dec 2019 15:35:01 GMT

Hi!

I'm sorry but as of now, DevZone does not provide support for Zephyr with nRF52840, only nRF9160.

Nordic Semiconductor is part of the Zephyr Project and contributes with misc. components/software, but we do not give support for Zephyr running on nRF52840.

Thanks for your understanding.

Best regards,

Heidi

RE: Long timer expires immediately

jlangballeswift — Tue, 17 Dec 2019 15:51:46 GMT

I posted in the Zephyr slack channel and was linked to this issue. https://github.com/zephyrproject-rtos/zephyr/issues/19075 It looks related but is there some way I can work around this?

After digging into the source a bit, it looks like this may affect all time values from the device's clock, including k_uptime_get(). z_clock_elapsed is implemented as a signed 32 bit integer which would overflow after ~18 hours with the ticks/seconds conversion.