MCF5253VM140J Freescale Semiconductor, MCF5253VM140J Datasheet - Page 635

• Manufacturer Part Number: MCF5253VM140J
• Description: IC MCU 2.1MIPS 140MHZ 225MAPBGA
• Manufacturer: Freescale Semiconductor
• Series: MCF525xr

Specifications of MCF5253VM140J

• Core Processor: Coldfire V2
• Core Size: 32-Bit
• Speed: 140MHz
• Connectivity: CAN, EBI/EMI, I²C, QSPI, UART/USART, USB OTG
• Peripherals: DMA, WDT
• Program Memory Type: ROMless
• Ram Size: 128K x 8
• Voltage - Supply (vcc/vdd): 1.08 V ~ 1.32 V
• Data Converters: A/D 6x12b
• Oscillator Type: External
• Operating Temperature: -20°C ~ 70°C
• Package / Case: 225-MAPBGA
• Processor Series: MCF525x
• Core: ColdFire V2
• 3rd Party Development Tools: JLINK-CF-BDM26, EWCF
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Number Of I /o: -
• Eeprom Size: -
• Program Memory Size: -
• Lead Free Status / Rohs Status: Details

Freescale Semiconductor
15–8, 7–0
LENGTH
STAMP
31–24,
23–16,
31–28
27–24
CODE
19–16
31–29
15–-0
TIME
DATA
Field
SRR
28–0
RTR
IDE
23
22
21
20
ID
Reserved, should be cleared.
Message buffer code. Can be accessed (read or write) by the CPU and by the FlexCAN module itself, as part of
the message buffer matching and arbitration process. The encoding is shown in
Section 25.6, “Functional Overview,”
Reserved, should be cleared.
Substitute remote request. Fixed recessive bit, used only in extended format. It must be set by the user for
transmission (Tx Buffers) and will be stored with the value received on the CAN bus for Rx receiving buffers. It can
be received as either recessive or dominant. If FlexCAN receives this bit as dominant, then it is interpreted as
arbitration loss.
0 Dominant is not a valid value for transmission in Extended Format frames
1 Recessive value is compulsory for transmission in Extended Format frames
ID extended bit. Identifies whether the frame format is standard or extended.
0 Standard frame format
1 Extended frame format
Remote transmission request. Used for requesting transmissions of a data frame. If FlexCAN transmits this bit as
1 (recessive) and receives it as 0 (dominant), it is interpreted as arbitration loss. If this bit is transmitted as 0
(dominant), then if it is received as 1 (recessive), the FlexCAN module treats it as bit error. If the value received
matches the value transmitted, it is considered as a successful bit transmission.
0 Indicates the current MB has a data frame to be transmitted
1 Indicates the current MB has a remote frame to be transmitted
Length of data in bytes. Indicates the length (in bytes) of the Rx or Tx data; data is located in offset 0x8 through
0xF of the MB space (see
DLC (data length code) field of the received frame. DLC is defined by the CAN Specification and refers to the data
length of the actual frame before it is copied into the message buffer. In transmission, this field is written by the CPU
and is used as the DLC field value of the frame to be transmitted.
When RTR is set, the frame to be transmitted is a remote frame and will be transmitted without the DATA field,
regardless of the LENGTH field.
Free-running counter time stamp. Stores the value of the free-running timer which is captured when the beginning
of the identifier (ID) field appears on the CAN bus.
Reserved, should be cleared.
Standard frame identifier: In standard frame format, only the 11 most significant bits (28 to 18) are used for frame
identification in both receive and transmit cases. The 18 least significant bits are ignored.
Extended frame identifier: In extended frame format, all bits (both the 11 bits of the standard frame identifier and
the 18 bits of the extended frame identifier) are used for frame identification in both receive and transmit cases.
Data field. Up to eight bytes can be used for a data frame. For Rx frames, the data is stored as it is received from
the CAN bus. For Tx frames, the CPU provides the data to be transmitted within the frame.
Table 25-11. Message Buffer Structure Register Field Descriptions
Figure
MCF5253 Reference Manual, Rev. 1
25-13). In reception, this field is written by the FlexCAN module, copied from the
for additional information.
Description
Table 25-12
and
Table
FlexCAN Module
25-13. See
25-19