IOS-EP2 I/O SERVER MODULE Cyclone II Based FPGA Module
__________________________________________________________________
__________________________________________________________________________
Acromag, Inc. Tel:248-295-0310 Fax:248-624-9234 Email:[email protected] http://www.acromag.com
24
3. Re-enab
le the interrupting channel(s) by writing a “1” to the appropriate
bit(s) in the Interrupt Enable Register.
General Sequence of Events for Processing an Interrupt
1. The IOS-EP20X asserts the Interrupt Request 0 Line (INTREQ0*)
in response to an interrupt condition at one or more inputs.
2. A generated interrupt is recognized by the carrier board and is recorded
in the carrier board‟s Interrupt Pending Register and passed to the PCI bus
by driving interrupt request signal INTA# active.
3. The host processor uses the PCI interrupt to locate an interrupt service
routine to process interrupts from the carrier board.
4. The carrier board interrupt service routine examines the carrier board‟s
Interrupt Pending Register and invokes IOS module interrupt service
routines to service individual IOS modules.
3. The carrier board interrupt service routine accesses the interrupt space of
the IOS module selected to be serviced. Note that the interrupt space
accessed must correspond to the interrupt request signal driven by the IOS
module.
4. The carrier board will assert the INTSEL* signal to the appropriate IOS
module together with (carrier board generated) address bit A1 to select
which interrupt request is being processed (A1 low corresponds to
INTREQ0*; A1 high corresponds to INTREQ1*).
5. The IOS module receives an active INTSEL* signal from the carrier and
supplies its interrupt vector to the host processor during this interrupt
acknowledge cycle. An IOS module designed to release its interrupt request
on acknowledge will release its interrupt request upon receiving an active
INTSEL* signal from the carrier. If the IOS module is designed to release it‟s
interrupt request on register access the interrupt service routine must also
access the required register to clear the interrupt request.
6. If the IOS module interrupt stimulus has been removed and no other IOS
modules have interrupts pending, the interrupt cycle is completed (i.e. the
carrier board negates its interrupt request
INTA#).