FlexRay Communication Controller (FlexRAY)
PXN20 Microcontroller Reference Manual, Rev. 1
26-144 Freescale Semiconductor
26.6.18.1 Channel Status Error Counter Registers
The two channel status error counter registers, Channel A Status Error Counter Register (CASERCR) and 
Channel B Status Error Counter Register (CBSERCR), incremented by one, if at least one of four slot 
status error bits, vSS!SyntaxError, vSS!ContentError, vSS!BViolation, or vSS!TxConflict is set to 1. The 
status vectors for all slots in the static and dynamic segment, in the symbol window, and in the NIT are 
taken into account. The counters wrap round after they have reached the maximum value.
Table 26-116. Slot Status Content
Status Content
 static /
dynamic 
Slot
slot related status 
vSS!ValidFrame – valid frame received
vSS!SyntaxError – syntax error occurred while receiving
vSS!ContentError– content error occurred while receiving
vSS!BViolation – boundary violation while receiving
for slots in which the module transmits:
vSS!TxConflict – reception ongoing while transmission starts
for slots in which the module does not transmit:
vSS!TxConflict – reception ongoing while transmission starts
first valid – channel that has received the first valid frame
received frame related status
extracted from
a) header of valid frame, if vSS!ValidFrame = 1
b) last received header, if vSS!ValidFrame = 0
c) set to 0, if nothing was received
vRF!Header!NFIndicator – Null Frame Indicator (0 for null frame)
vRF!Header!SuFIndicator – Startup Frame Indicator 
vRF!Header!SyFIndicator – Sync Frame Indicator
Symbol 
Window
window related status
vSS!ValidFrame – always 0
vSS!ContentError – content error occurred while receiving
vSS!SyntaxError – syntax error occurred while receiving 
vSS!BViolation – boundary violation while receiving
vSS!TxConflict – reception ongoing while transmission starts
received symbol related status
vSS!ValidMTS – valid Media Test Access Symbol received
received frame related status
see static/dynamic slot
NIT NIT related status
vSS!ValidFrame – always 0
vSS!ContentError – content error occurred while receiving
vSS!SyntaxError – syntax error occurred while receiving 
vSS!BViolation – boundary violation while receiving
vSS!TxConflict – always 0
received frame related status
see static/dynamic slot