User`s guide

5 Interrupt Support
that board with either two or four ID values, depending on the specific
hardware. W hen calling the hook functions, the xPC Target kernel obtains
thePCIinformationfortheboardandpassesittothehookfunctions.Use
these parameters to help identify the interrupting board.
- For VendorId and DeviceId, enter the IDs you get from the board
manufacturer.
- Many boards do not have SubVendorId and S ubDe viceId values. In
these cas es, insert the value
-1 to prevent The xPC Targ et software
from checking for them.
If you have an ISA board, it does not ha ve a vendor or de vice ID; i n stead,
the generated code will insert the ISA base a ddress in the first base address
entry of the PCI structure. To indicate to the kernel that this is an ISA
board, set
VendorId to -1 and DeviceI d to 1.
If you do n ot need hook functions:
- Set VendorId to -1 and DeviceId to -1.
- Set Fnc and PostHookFcn to 'NULL'.
- Set StartFunction and StopFunction to 'NULL'.
The Async IRQ S ource block will sti ll call the subsystem when an interrupt
occurs.
The following table summarizes your options for this element:
Vend orId DeviceId
Usage
+ID +ID
PCI board
-1 +1
ISA board
-1 -1
Special case: If the driver does no t need hook
functions. The driver can still use the Async IRQ
Source block. As an example, see the source code
for the serial communication driver.
• Enter the names of the interrupt functions. See “Hook Function Prototypes
— Alphabetical List” on page 5-15 for the prototype details.
5-12