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 interr
On Mon, Dec 28, 2015 at 4:11 PM, Martin Galvan
wrote:
> 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 pr
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
On Mon, Dec 28, 2015 at 12:14 PM, Martin Galvan <
martin.gal...@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 ti
