[riot-notifications] [RIOT] sys/vtimer: Fix two vtimer issues (hwtimer tick conversion). (#2515)

Joakim Gebart notifications at github.com
Mon Jun 1 08:54:07 CEST 2015


I ran this on a test yesterday and also got past the initial problem at one hour. But also got to the same error as @lightblu, there was a lock up at 7696 seconds wall clock time, 7567 hwtimer seconds. I wasn't looking when it happened so it could have been just a problem with the debugger too, I will run another test today and also see if I have the time to refactor the hwtimer driver for Kinetis because I believe the current implementation is losing too many ticks (129 second difference between the wall clock and the timer tick after only 2 hours is not acceptable IMO, almost 1 second per 60 seconds).

This PR fixes a major bug in the vtimer implementation and should be merged independently of the other timer work. The comment by @OlegHahm and me is not crucial, it is better to get this merged and have a working vtimer and do a follow up PR to remove the set_absolute call from vtimer.c.

ACK

---
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/2515#issuecomment-107328777
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20150531/479b8a71/attachment-0001.html>


More information about the notifications mailing list