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
must always have
> a lower priority.
Particularly, we'd like to know what would happen if we set the ticker
interrupt priority to the same as the rest.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
On Mon, Dec 28, 2015 at 3:26 PM, Joel Sherrill wrote:
> A couple of odd guesses. If there are non-RTEMS interrupts, they must
> be the highest priority.
Precisely, I'd like to know why the ticker interrupt must always have
a lower priority.
> My other guess would be that the interrupt vectoring
s 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. I
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 defi
