FlexRay Module (FLEXRAYV2)
MFR4300 Data Sheet, Rev. 3
Freescale Semiconductor
129
Message Buffer Control
11
CMT
Commit for Transmission — This bit applies only to transmit message buffers and indicates whether the
message buffer contains valid data that are ready for transmission. Both the application and the FlexRay module
can modify this bit.
Application: The application sets this bit to indicate that the transmit message buffer contains valid data ready
for transmission. The application clears this bit to indicate that the message buffer data are no longer valid for
transmission.
FlexRay module: The FlexRay module clears this bit when the message buffer data are no longer valid for
transmission.
0 Message buffer does not contain valid data.
1 Message buffer contains valid data.
10
EDT
Enable/Disable Trigger — This trigger bit is used to enable and disable a message buffer. The message buffer
enable is triggered when the application writes ‘1’ to this bit and the message buffer is disabled, i.e. the EDS
status bit is ‘0’. The message buffer disable is triggered when the application writes ‘1’ to this bit and the message
buffer is enabled, i.e. the EDS status bit is ‘1’.
0 No effect
1 message buffer enable/disable triggered
Note: If the application writes ‘1’ to this bit, the write access to all other bits is ignored.
9
LCKT
Lock/Unlock Trigger — This trigger bit is used to lock and unlock a message buffer. The message buffer lock is
triggered when the application writes ‘1’ to this bit and the message buffer is not locked, i.e. the LCKS status bit
is ‘0’. The message buffer unlock is triggered when the application writes ‘1’ to this bit and the message buffer is
locked, i.e. the LCKS status bit is ‘1’.
0 No effect
1 Trigger message buffer lock/unlock
Note: If the application writes ‘1’ to this bit and ‘0’ to the EDT bit, the write access to all other bits is ignored.
8
MBIE
Message Buffer Interrupt Enable — This control bit defines whether the message buffer will generate an
interrupt request when its MBIF flag is set.
0 Interrupt request generation disabled
1 Interrupt request generation enabled
Message Buffer Status
4
DUP
Data Updated — This status bit applies only to receive message buffers. It is always ‘0’ for transmit message
buffers. This bit provides information whether the frame header in the message buffer header field and the
description of the update condtions.
0 Frame Header and Message buffer data field not updated.
1 Frame Header and Message buffer data field updated.
3
DVAL
Data Valid — The semantic of this status bit depends on the message buffer type and transfer direction.
Receive Message Buffer: Indicates whether the message buffer data field contains valid frame data. See
0 message buffer data field contains no valid frame data
1 message buffer data field contains valid frame data
Single Transmit Message Buffer: Indicates whether the message is transferred again due to the state
transmission mode of the message buffer.
0 Message transferred for the first time.
1 Message will be transferred again.
Double Transmit Message Buffer: For the commit side it is always ‘0’. For the transmit side it indicates whether
the message is transferred again due to the state transmission mode of the message buffer.
0 Message transferred for the first time.
1 Message will be transferred again.
Table 3-75. MBCCSRn Field Descriptions (Sheet 2 of 3)
Field
Description