XC2700 Datasheet, PDF (31/62 Pages) Infineon Technologies AG – 16/32-Bit Single-Chip Microcontroller

XC2700 Derivatives
XC2000 Family / Alpha Line
Detailed Errata Description
Workaround
Do not transmit any CAN message by receive FIFO base objects or gateway source
objects with bit MOFCRn.OVIE set.
MultiCAN_AI.046 Transmit FIFO base Object position
If a message object n is configured as transmit FIFO base object and is located in the
list segment that is used for the FIFO storage container (defined by MOFGPRn.BOT and
MOFGPRn.TOP) but not at the list position given by MOFGPRn.BOT, then the MultiCAN
uses incorrect pointer values for this transmit FIFO.
Workaround
The transmit FIFO works properly when the transmit FIFO base object is either at the
bottom position within the list segment of the FIFO (MOFGPRn.BOT=n) or outside of the
list segment as described above.
MultiCAN_TC.025 RXUPD behavior
When a CAN frame is stored in a message object, either directly from the CAN node or
indirectly via receive FIFO or from a gateway source object, then bit MOCTR.RXUPD is
set in the message object before the storage process and is automatically cleared after
the storage process.
Problem description
When a standard message object (MOFCR.MMC) receives a CAN frame from a CAN
node, then it processes its own RXUPD as described above (correct).
In addition to that, it also sets and clears bit RXUPD in the message object referenced by
pointer MOFGPR.CUR (wrong behavior).
Workaround
The “foreign” RXUPD pulse can be avoided by initializing MOFGPR.CUR with the message
number of the object itself instead of another object (which would be message object 0
by default, because MOFGPR.CUR points to message object 0 after reset initialization of
MultiCAN).
Errata Sheet
31
V1.7, 2014-10