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

XC2700 Derivatives
XC2000 Family / Alpha Line
Detailed Errata Description
Both of the following conditions must be fulfilled at the same time when the trigger for the
hardware trap HWTx occurs in order to cause the problem:
1. The pipeline is cancelled due to one of the following reasons:
a) a multiply or divide instruction is followed by a mispredicted conditional (zero-
cycle) jump.
b) a class A hardware trap is triggered quasi-simultaneously with the request for a
class B trap (= HWTx), i.e. the trigger for the class A trap arrives before the
previously injected TRAP instruction for the class B trap has reached the Execute
stage of the pipeline.
In this case, the class A trap is entered, but when the RETI instruction at the end
of the class A trap routine is executed, the pending class B trap (HWTx) is not
entered, and subsequent interrupts/PECs/class B traps are postponed until the
next RETI.
c) a break is requested by the debugger.
2. The pipeline is stalled in the Execute or Write Back stage due to consecutive writes,
or due to a multi-cycle write that is performed to a memory area with wait states
(PSRAM, external memory).
Workaround
Disable overrun of pipeline bubbles by setting bit OVRUN (CPUCON2.4) = 0.
MultiCAN_AI.040 Remote frame transmit acceptance filtering error
Correct behaviour:
Assume the MultiCAN message object receives a remote frame that leads to a valid
transmit request in the same message object (request of remote answer), then the
MultiCAN module prepares for an immediate answer of the remote request. The answer
message is arbitrated against the winner of transmit acceptance filtering (without the
remote answer) with a respect to the priority class (MOARn.PRI).
Wrong behaviour:
Assume the MultiCAN message object receives a remote frame that leads to a valid
transmit request in the same message object (request of remote answer), then the
MultiCAN module prepares for an immediate answer of the remote request. The answer
message is arbitrated against the winner of transmit acceptance filtering (without the
remote answer) with a respect to the CAN arbitration rules and not taking the PRI values
into account.
If the remote answer is not sent out immediately, then it is subject to further transmit
acceptance filtering runs, which are performed correctly.
Errata Sheet
28
V1.7, 2014-10