Table of Contents
Advertisement
20.3.6
Message Object List Structure
This section describes the structure of the message object lists in the MultiCAN module.
20.3.6.1 Basics
The message objects of the MultiCAN module are organized in double-chained lists,
where each message object has a pointer to the previous message object in the list as
well as a pointer to the next message object in the list. The MultiCAN module provides
eight lists. Each message object is allocated to one of these lists. In the example in
Figure
20-11, the three message objects (3, 5, and 16) are allocated to the list with
index 2 (List Register LIST2).
PPREV = 5
PNEXT = 16
LIST = 2
Figure 20-11 Example Allocation of Message Objects to a List
Bit field BEGIN in the List Register (for definition, see
element in the list (object 5 in the example), and bit field END points to the last element
in the list (object 3 in the example). The number of elements in the list is indicated by bit
field SIZE of the List Register (SIZE = number of list elements - 1, thus SIZE = 2 for the
3 elements in the example). The EMPTY bit of the List Register indicates whether or not
a list is empty (EMPTY = 0 in the example, because list 2 is not empty).
Each message object n has a pointer PNEXT in its Message Object n Control Register
MOCTRn (see
Page
pointer PPREV that points to the previous message object in the list. PPREV of the first
message object points to the message object itself because the first message object has
no predecessor (in the example message object 5 is the first message object in the list,
User's Manual
MultiCAN, V2.24
Message
Object 5
EMPTY = 0
SIZE = 2
20-92) that points to the next message object in the list, and a
Controller Area Network Controller (MultiCAN)
PPREV = 5
PNEXT = 3
LIST = 2
Message
Object 16
BEGIN = 5
Register LIST2
20-27
PPREV = 16
PNEXT = 3
LIST = 2
Message
Object 3
END = 3
MCA06268
Page
20-69) points to the first
V1.0, 2011-12
TC1728
Advertisement
Table of Contents
