Interrupt Handling; Figure 14-4: Fcan Interrupt Bundling Of V850E/Ca2 - NEC V850E/CA2 JUPITER Preliminary User's Manual

14.2.4 Interrupt handling

The very high number of interrupt events generated by the FCAN system does not allow to assign an
independent interrupt vector of the V850E/CA2 to each event. Therefore, the interrupt request signals
are bundled into groups and the grouped interrupt request signal is then assigned to an independent
interrupt vector.
The concept of interrupt request signal bundling leads to the fact that all interrupt request signals of the
FCAN system are designed as interrupt pending signals. Interrupt pending signals are not automati-
cally treated by an interrupt service routine like interrupt request signals with an unambiguous interrupt
vector. Rather, on occurrence of the interrupt event the interrupt signal is generated and latched.
In the interrupt service routine the software must analyse, which particular interrupt event caused the
interrupt request by scanning the interrupt pending flags of a bundled interrupt signal group. After the
particular interrupt has been identified, the corresponding interrupt pending flag must be reset by soft-
ware at least before leaving the interrupt service routine.
GINT7 0
Bit15 Bit14
CCINTP
0 0
Bit31 Bit30
Note: CAN module 3 and CAN module 4 are available in the derivatives µPD703129 (A) and
µPD703129 (A1) only.
Remark: x = 1 to 2 for the derivative µPD703128 (A), x = 1 to 4 for the derivatives µPD703129 (A)
and µPD703129 (A1)
Chapter 14 FCAN Interface Function

Figure 14-4: FCAN Interrupt Bundling of V850E/CA2

CGINTP
0 GINT4 GINT3 GINT2 GINT1
INTMAC
0 0 0
0
Bit13 Bit12 Bit11 Bit10
0 0 0
0
Bit29 Bit28 Bit27 Bit26
Preliminary User's Manual U15839EE1V0UM00
set and clear signal
0 0 CxINT6 CxINT5 CxINT4 CxINT3 CxINT2 CxINT1 CxINT0
0
Bit9 Bit8 Bit7 Bit6 Bit5
0 0 0 0 0
Bit25 Bit24 Bit23 Bit22 Bit21 Bit20 Bit19 Bit18 Bit17 Bit16
Register Set
and clear Logic
CxINTP
CANxERR
Bit4 Bit3 Bit2 Bit1 Bit0
0 0
439