RTEMS behaviour when using rtems_clock_tick incorrectly?

[Leonard Bise]

Hello all,

We're working on a project where we have a RTEMS application which uses the
rtems_clock_tick function to signal that a tick elapsed.
Now I just noticed that in some case the implementation is badly done and
this function can be called two successive times in a very short amount of
time.

This happens because the rtems_clock_tick is called from an IRQ which is
triggered when receiving a synch signal over the MIL-1553 bus. This IRQ in
some error cases can be trigged two times in the lapse of a few
milliseconds.

For debugging purposes and to better understand the problem we have, could
anyone shed some light on what could or would happen to RTEMS scheduling in
case the ticks are very close to each other instead of being called roughly
once per second?

Thanks in advance.

-- 
*
*
*Léonard Bise*
Software Design Engineer
Direct Line +41 (0)32 338 9902

*SYDERAL SA*
Neuenburgstrasse 7
CH-3238 Gals (Switzerland)
Desk Line +41 (0)32 338 9800
Web Site http://www.syderal.ch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20120705/810d7a52/attachment.html>