[riot-notifications] [RIOT-OS/RIOT] xtimer: hang on xtimer_spin_until (corner case) (#11149)

vac notifications at github.com
Fri Mar 29 19:57:01 CET 2019


Just found out that it is not possible ready every value of the async timer in sam21d.
If we would read the count register of TC, even in continuous mode, it will result in same value for 6 async (slow) clocks 😢 

If we agree that such platforms exist it makes handling timer functions much more complicated (for example mentioned `xtimer_spin_until` function).

I've tested it with 48MHz DFPLL main clock and 32768Hz xtimer clock.
With the 32768Hz clock, the theoretical resolution should be ~30us but on samd21, when polling count value, the resolution is ~180us... So RIOT xtimer solutions such us `XTIMER_OVERHEAD` handling need to be verified and improved.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/11149#issuecomment-478112352
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190329/381e81f9/attachment-0001.html>


More information about the notifications mailing list