LEON3 with shared interrupt handlers

[Joel Sherrill]

Yes. Gaisler ported the irq.h framework to leon3. It is the api used on PowerPC, ARM, and x86 where you always need bsp help to vector an interrupt.

In this case, it is layered on top of the simple vectored API that is normally used on the SPARC. But when you have a pic, the bsp must assist and that's what this api provides.

--joel

"Miller, Scott A." <scott.miller at swri.org> wrote:


In our use with the GR712RC LEON3 processor and the Aeroflex-Gaisler provided SpaceWire driver, we’ve run across a roadblock.

The RTEMS driver SpaceWire interrupt triggers as part of the “extended” LEON3 interrupt set.  It initially triggers as interrupt 12, which then triggers RTEMS to read the “Extended Interrupt Register” to decode which interrupt (16..31) actually fired.

In addition to using the SpW driver, we’d also like to have our own interrupt handler for other “extended” interrupts for other peripherals with an extended interrupt from 16..31 (but also initially triggering off interrupt 12).

Is there a way in RTEMS to have multiple interrupt handlers called for the extended interrupt 12?  Both the included GRSPW driver and our own handler?

Thanks in advance.

Scott Miller
Southwest Research Institute

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20131010/08cf89e1/attachment.html>