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