mc9s12xf512 Freescale Semiconductor, Inc, mc9s12xf512 Datasheet - Page 489

• Manufacturer Part Number: mc9s12xf512
• Description: S12x Microcontrollers 16-bit Automotive Microcontroller
• Manufacturer: Freescale Semiconductor, Inc

Freescale Semiconductor
FOVB_EF
FOVA_EF
SBCF_EF
MBU_EF
MSB_EF
LCK_EF
DBL_EF
DPL_EF
FID_EF
Field
12
11
10
9
8
7
6
5
4
Receive FIFO Overrun Channel B Error Flag — This flag is set when an overrun of the Receive FIFO for
channel B occurred. This error occurs if a semantically valid frame was received on channel B and matches the
all criteria to be appended to the FIFO for channel B but the FIFO is full. In this case, the received frame and its
related slot status information is lost.
0 No such error
1 Receive FIFO overrun on channel B has been detected
Receive FIFO Overrun Channel A Error Flag — This flag is set when an overrun of the Receive FIFO for
channel A occurred. This error occurs if a semantically valid frame was received on channel A and matches the
all criteria to be appended to the FIFO for channel A but the FIFO is full. In this case, the received frame and its
related slot status information is lost.
0 No such error
1 Receive FIFO overrun on channel B has been detected
Message Buffer Search Error Flag — This flag is set if the message buffer search engine is still running while
the next search cycle must be started due to the FlexRay protocol timing. In this case, not all message buffers
are considered while searching.
0 No such event
1 Search engine active while search start appears
Message Buffer Utilization Error Flag — This flag is asserted if the application writes to a message buffer
control field that is beyond the number of utilized message buffers programmed in the
Segment Size and Utilization Register
If the application writes to a MBCCSRn register with n > LAST_MB_UTIL, the FlexRay block ignores the write
attempt and asserts the message buffer utilization error flag MBU_EF in the
0 No such event
1 Non-utilized message buffer enabled
Lock Error Flag — This flag is set if the application tries to lock a message buffer that is already locked by the
FlexRay block due to internal operations. In that case, the FlexRay block does not grant the lock to the
application. The application must issue the lock request again.
0 No such error
1 Lock error detected
Double Transmit Message Buffer Lock Error Flag — This flag is set if the application tries to lock the transmit
side of a double transmit message buffer. In this case, the FlexRay block does not grant the lock to the transmit
side of a double transmit message buffer.
0 No such event
1 Double transmit buffer lock error occurred
System Bus Communication Failure Error Flag — This flag is set if the FlexRay block was not able to transmit
or receive data via the system bus in time. In the case of writing, data is lost; in the case of reading, the
transmission onto the FlexRay bus is stopped for the current slot and resumed in the next slot.
0 No such event
1 System bus communication failure occurred
Frame ID Error Flag — This flag is set if the frame ID stored in the message buffer header area differs from the
frame ID stored in the message buffer control register.
0 No such error occurred
1 Frame ID error occurred
Dynamic Payload Length Error Flag — This flag is set if the payload length written into the message buffer
header field of a single or double transmit message buffer assigned to the dynamic segment is greater than the
maximum payload length for the dynamic segment as it is configured in the corresponding protocol configuration
register field max_payload_length_dynamic in the
0 No such error occurred
1 Dynamic payload length error occurred
Table 13-23. CHIERFR Field Descriptions (Sheet 2 of 3)
MC9S12XF - Family Reference Manual, Rev.1.19
(MBSSUTR).
Description
Protocol Configuration Register 24
Chapter 13 FlexRay Communication Controller (FLEXRAY)
CHI Error Flag Register
(PCR24).
Message Buffer
(CHIERFR).
489