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 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@rtems.org > http://lists.rtems.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
