The problem in the beaglebone bsp interrupt server resides in the way
bsp_interrupt_dispatch handles the interrupts.
bsp_interrupt_dispatch disables the interrupt vector, dispatches the
handler for the vector and then it enables the interrupt vector. Meanwhile,
the irq server disables the interrupt
Actually, it seems like the issue is what Ragunath described here:
https://lists.rtems.org/pipermail/devel/2015-May/011419.html
It looks like the Beagle bsp_interrupt_dispatch function isn't
designed to work with the interrupt server task. From what I saw, this
is the only board where bsp_interru
Since you run the server task at priority 1, if it does not work
correctly then it can be causing a non-responsive system.
Do you reach the USB1HostIntHandler function? What does it do?
-Gedare
On Fri, Jul 10, 2015 at 5:33 PM, Martin Galvan
wrote:
> Hi everyone! I'm currently trying to use an i
Hi everyone! I'm currently trying to use an interrupt server task for
handling USB interrupts on the Beaglebone Black. Here's the code I'm
using:
rtems_interrupt_server_initialize(1, 1500, RTEMS_TIMESLICE | RTEMS_PREEMPT,
RTEMS_DEFAULT_ATTRIBUTES, NULL);
rtems_interrupt_server_handler_install
Hi everyone! I'm currently trying to use an interrupt server task for
handling USB interrupts on the Beaglebone Black. Here's the code I'm
using:
rtems_interrupt_server_initialize(1, 1500, RTEMS_TIMESLICE | RTEMS_PREEMPT,
RTEMS_DEFAULT_ATTRIBUTES, NULL);
rtems_interrupt_server_handler_install
