Module Operation
1243
SPNU563A – March 2018
Copyright © 2018, Texas Instruments Incorporated
FlexRay Module
•
By writing SUCC1.CMD(3-0) = 0111 (FREEZE command) from all states
•
When exiting from NORMAL_ACTIVE state because the clock correction failed counter reached the
“maximum without clock correction fatal” limit and SUCC1.HCSE is set
•
When exiting from NORMAL_PASSIVE state because the clock correction failed counter reached the
“maximum without clock correction fatal” limit and SUCC1.HCSE is set
The communication controller exits from this state to DEFAULT_CONFIG state
•
By writing SUCC1.CMD(3-0) = 0001 (CONFIG command)
When the communication controller transits from HALT state to DEFAULT_CONFIG state all configuration
and status data is maintained for analyzing purposes.
When the host writes SUCC1.CMD(3-0) = 0110 (HALT command), the communication controller sets bit
CCSV.HRQ and enters HALT state at next end of cycle.
When the host writes SUCC1.CMD(3-0) = 0111 (FREEZE command), the communication controller enters
HALT state immediately and sets the CCSV.FSI bit in the communication controller status vector register.
The POC state from which the transition to HALT state took place can be read from CCSV.PSL(5-0).
26.2.7 Network Management
The accrued network management (NM) vector is located in the Network Management Registers
(NMV1/2/3). The communication controller performs a logical OR operation over all NM vectors out of all
received valid NM frames with the Payload Preamble Indicator (PPI) bit set. Only a static frame may be
configured to hold NM information. The communication controller updates the NM vector at the end of
each cycle.
The length of the NM vector can be configured from 0 to 12 bytes by NEMC.NML(3-0). The NM vector
length must be configured identically in all nodes of a cluster.
To configure a transmit buffer to send FlexRay frames with the PPI bit set, the PPIT bit in the header
section of the corresponding transmit buffer has to be set WRHS1.PPIT. In addition the host has to write
the NM information to the data section of the corresponding transmit buffer.
The evaluation of the NM vector has to be done by the application running on the host.
NOTE:
In case a message buffer is configured for transmission / reception of network management
frames, the payload length configured in header 2 of that message buffer should be equal or
greater than the length of the NM vector configured by NEMC.NML(3-0).When the
Communication Controller transits to HALT state, the cycle count is not incremented and
therefore the NM vector is not updated. In this case NMV1/2/3 holds the value from the cycle
before.
26.2.8 Filtering and Masking
Filtering is done by comparison of the configuration of assigned message buffers against current slot and
cycle counter values and channel ID (channel A, B). A message buffer is only updated / transmitted if the
required matches occur.
Filtering is done on:
•
Slot counter
•
Cycle counter
•
Channel ID
The following filter combinations for acceptance / transmit filtering are allowed:
•
Slot c Channel ID
•
Slot c Cycle c Channel ID
All configured filters must match in order to store a received message in a message buffer.
