Ticker interrupt priority

Sebastian Huber sebastian.huber at embedded-brains.de
Mon Jan 4 09:30:06 UTC 2016

On 28/12/15 19:14, Martin Galvan wrote:
> Hi everyone! We're still looking into the issue Marcos described here:
> https://lists.rtems.org/pipermail/devel/2015-December/013216.html
> We noticed the problem seems to go away if we set the ticker interrupt
> priority to be the same as for the other interrupts. While that's not
> a definitive fix, I was wondering if anyone knows why is it necessary
> that the ticker interrupt has a lower priority than the rest.

Its not necessary, but in most cases it is desirable since the system 
tick is not related to a low-latency hardware event.

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.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

More information about the devel mailing list