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
From: Tim Cussins
The DHCP code in rtems uses an unchanging transaction id (xid) in the dhcp
discover and request
packets.
It is possible (and in fact has been observed) that DHCP servers may issue
multiple OFFER packets
in response to multiple REQUEST packets from the same device.
The second
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
