The problem is that you set the time via rtems_clock_set() in Init().
The you wait via rtems_task_wake_after(5s in ticks). With a
rtems_task_wake_after(n) you wait to the n-th next tick, thus your wait
interval is slightly less than 5s in most cases.
On 18/01/16 00:19, Joel Sherrill wrote:
Hi
With the recent clock changes, I am noticing that on some BSPs
ticker is reporting times 4, 9, 14, ... instead of 5, 10, 15.
It looks like the time is 4.9999999 when it should simply be 5 so
ticker just reports 4.
Given this is a visible change in behavior, I would like to know
what causes it and how it can be resolved?
Thanks.
--joel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
