
FlexRay Communication Controller (FlexRAY)
PXN20 Microcontroller Reference Manual, Rev. 1
Freescale Semiconductor
26-147
26.6.19.1 System Bus Illegal Address Access
If the system bus detects an controller access to an illegal address, the controller receives a notification
from the system bus about this event and sets the ILSA_EF flag in the
26.6.19.2 System Bus Access Timeout
The controller starts a timer when it has send an access request to the system bus. This timer expires after
2 * SYMATOR.T 2 system bus clock cycles. If the access is not finished within this amount
of time, the SBCF_EF flag in the
CHI Error Flag Register (CHIERFR)
is set.
NOTE
If the system memory read access that retrieves the first message buffer
header data from a FlexRay transmit buffer fails due to a system memory
access timeout or illegal address access, it is possible that the slot status
information for the previous slot is written into the currently used transmit
message buffer. In this case, the slot status information is not written into the
message buffer assigned to the last slot. Thus, both the message buffer
assigned to the last slot, and the currently used transmit message buffer
contain incorrect slot status information. However, if this occurs, either the
System Bus Communication Failure Error Flag (SBCF_EF) or the Illegal
System Bus Address Error Flag (ILSA_EF) will be set in the Controller
Host Interface Error Flag Register (CHIERFR).
The FlexRay module and the system memory subsystem should be
configured to avoid the occurrence of system memory access timeouts and
illegal address accesses. In case that one of the error flags
CHIERFR[SBCF_EF] or CHIERFR[ILSA_EF] is set, the application
should not use the slot status information of the message buffers.
26.6.19.3 Continue after System Bus Failure
If the SBFF bit in the
Module Configuration Register (MCR)
is 0, the controller will continue its operation
after the occurrence of the system bus access failure but will not generate any system bus accesses until
the start of the next communication cycle.
If a frame is under transmission when the system bus failure occurs, a correct frame is generated with the
remaining header and frame data are replaced by all zeros. Depending on the point in time this can affect
the PPI bit, the Header CRC, the Payload Length in case of an dynamic slot, and the payload data. Starting
from the next slot in the current cycle, no frames will be transmitted and received, except for the key slot,
where a sync or startup null-frame is transmitted, if the key slot is assigned.
If a frame is received when the system bus failure occurs, the reception is aborted and the related receive
message buffer is not updated.
Normal operation is resumed after the start of next communication cycle.
Summary of Contents for PXN2020
Page 1: ...PXN20 Microcontroller Reference Manual Devices Supported PXN2020 PXN2120 PXN20RM Rev 1 06 2011...
Page 42: ...PXN20 Microcontroller Reference Manual Rev 1 lxiv Freescale Semiconductor...
Page 64: ...Introduction PXN20 Microcontroller Reference Manual Rev 1 1 22 Freescale Semiconductor...
Page 112: ...Signal Description PXN20 Microcontroller Reference Manual Rev 1 3 44 Freescale Semiconductor...
Page 118: ...Resets PXN20 Microcontroller Reference Manual Rev 1 4 6 Freescale Semiconductor...
Page 372: ...e200z6 Core Z6 PXN20 Microcontroller Reference Manual Rev 1 13 8 Freescale Semiconductor...
Page 412: ...e200z0 Core Z0 PXN20 Microcontroller Reference Manual Rev 1 14 14 Freescale Semiconductor...
Page 821: ...Media Local Bus MLB PXN20 Microcontroller Reference Manual Rev 1 Freescale Semiconductor 27 49...
Page 822: ...Media Local Bus MLB PXN20 Microcontroller Reference Manual Rev 1 27 50 Freescale Semiconductor...
Page 1376: ...Memory Map PXN20 Microcontroller Reference Manual Rev 1 A 118 Freescale Semiconductor...