Motorola MPC5200 User Manual

Page 17

Advertising
background image

KwikNet MPC5200 FEC Device Driver

KADAK

11

The base vector for the block of interrupt vectors within the AMX Vector Table is
specified by you in your AMX Target Configuration Module. Use the AMX
Configuration Manager to edit your Target Parameter File and enter your definitions on
the

Exceptions

property page. Note that a

Warning

will always be displayed indicating that

the three MPC5200 exceptions share a common, overlapping region of the AMX Vector
Table. The warning can be safely ignored.

The MPC5200 FEC device driver provides support for two interrupt sources: the FEC
channel and the BestComm FEC subsystem. Each of these interrupt sources is assigned
to a specific vector in the AMX Vector Table.

If the "

First vector number

" for the external interrupt exception is 0, then the AMX vector

number for the FEC interrupt will be 41=0+41.

If the "

First vector number

" for the critical interrupt exception is 0, then the AMX vector

number for the BestComm FEC interrupt will be 71=0+68+3 where 68 is the offset of the
16 AMX vectors reserved for the BestComm DMA Engine and 3 is the BestComm task
number of the BestComm Ethernet RX task.

These AMX vector numbers are used as the

KwikNet

IRQ Identifiers in the device driver

parameters specified in the data sheet in Appendix A.

Advertising