Hi,
we have a battery powered application that will spend most time in Deep
Sleep, so a wake-up will trigger a CPU reset with some backup memory
retained.
To conserve energy, the radio interface should only be activated if
there is data to send. In the common case the sensor would just wake up
Hi,
the main change is that it is now offset based instead of absolute.
So instead of `target` and `long_target` you can check the new members
`offset` and `long_offset` for being zero.
They are only set to zero once the timer was either fired or removed.
I also agree that an explicit `is_se
Hi,
with https://github.com/RIOT-OS/RIOT/pull/9530 being merged the API of
xtimer changed a bit. Before, one could check if an xtimer is set by
deactivating the IRQ, checking if its members `target` and `long_target`
were 0 and reactivating the IRQ (as was done in the xtimer-internal
function `_is
