Ticker interrupt priority

Joel Sherrill joel at rtems.org
Mon Dec 28 18:26:55 UTC 2015

On Mon, Dec 28, 2015 at 12:14 PM, Martin Galvan <
martin.galvan at tallertechnologies.com> 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.
> A couple of odd guesses. If there are non-RTEMS interrupts, they must
be the highest priority.

My other guess would be that the interrupt vectoring code isn't handling
the nesting correctly. Perhaps a dispatch is missed or it doesn't know
it is nested.

> Thanks!
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20151228/750516f9/attachment-0002.html>

More information about the devel mailing list