Register 34: CAN Message 1 Interrupt Pending (CANMSG1INT), offset 0x140
Register 35: CAN Message 2 Interrupt Pending (CANMSG2INT), offset 0x144
The
CANMSG1INT
and
CANMSG2INT
registers hold the
INTPND
bits of the 32 message objects.
By reading these bits, the CPU can check which message object has an interrupt pending. The
INTPND
bit of a specific message object can be changed through two sources: (1) the CPU via the
CANIFnMCTL
register, or (2) the message handler state machine after the reception or transmission
of a frame.
This field is also encoded in the
CANINT
register.
The
CANMSG1INT
register contains the
INTPND
bits of the first 16 message objects in the message
RAM; the
CANMSG2INT
register contains the
INTPND
bits of the second 16 message objects.
CAN Message n Interrupt Pending (CANMSGnINT)
CAN0 base: 0x4004.0000
CAN1 base: 0x4004.1000
Offset 0x140
Type RO, reset 0x0000.0000
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
reserved
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
Type
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Reset
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
INTPND
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
RO
Type
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Reset
Description
Reset
Type
Name
Bit/Field
Software should not rely on the value of a reserved bit. To provide
compatibility with future products, the value of a reserved bit should be
preserved across a read-modify-write operation.
0x0000
RO
reserved
31:16
Interrupt Pending Bits
Description
Value
The corresponding message object is not the source of
an interrupt.
0
The corresponding message object is the source of an
interrupt.
1
0x0000
RO
INTPND
15:0
1405
June 18, 2014
Texas Instruments-Production Data
Tiva
™
TM4C1294NCPDT Microcontroller