MCF5253CVM140 Freescale Semiconductor, MCF5253CVM140 Datasheet - Page 570

• Manufacturer Part Number: MCF5253CVM140
• Description: IC MPU 32BIT 140MHZ 225-MAPBGA
• Manufacturer: Freescale Semiconductor
• Series: MCF525xr

Specifications of MCF5253CVM140

• 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: -40°C ~ 85°C
• Package / Case: 225-MAPBGA
• Family Name: MCF5xxx
• Device Core: ColdFire V2
• Device Core Size: 32b
• Frequency (max): 140MHz
• Instruction Set Architecture: RISC
• Supply Voltage 1 (typ): 1.2/3.3V
• Operating Supply Voltage (max): 1.32/3.6V
• Operating Supply Voltage (min): 1.08/3V
• Operating Temp Range: -40C to 85C
• Operating Temperature Classification: Industrial
• Mounting: Surface Mount
• Pin Count: 225
• Package Type: MA-BGA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Number Of I /o: -
• Eeprom Size: -
• Program Memory Size: -
• Lead Free Status / Rohs Status: Compliant

Universal Serial Bus Interface
following field in the siTD is used to track and detect errors in the execution of a split transaction for an
IN isochronous endpoint.
If a transaction translator returns with the final data before all of the complete-splits have been executed,
the state of the transfer is advanced so that the remaining complete-splits are not executed. It is important
to note that an IN siTD is retired based solely on the responses from the Transaction Translator to the
complete-split transactions. This means, for example, that it is possible for a transaction translator to
respond to a complete-split with an MDATA PID. The number of bytes in the MDATA's data payload could
cause the siTD[Total Bytes to Transfer] field to decrement to zero. This response can occur, before all of
the scheduled complete-splits have been executed. In other interface, data structures (for example,
high-speed data streams through queue heads), the transition of Total Bytes to Transfer to zero signals the
end of the transfer and results in clearing the Active bit. However, in this case, the result has not been
delivered by the Transaction Translator and the host must continue with the next complete-split transaction
to extract the residual transaction state. This scenario occurs because of the pipeline rules for a Transaction
Translator. In summary, the periodic pipeline rules require that on a micro-frame boundary, the Transaction
Translator holds the final two bytes received (if it has not seen an End Of Packet (EOP)) in the full-speed
bus pipe stage and gives the remaining bytes to the high-speed pipeline stage. At the micro-frame
boundary, the Transaction Translator could have received the entire packet (including both CRC bytes) but
not received the packet EOP. In the next micro-frame, the Transaction Translator responds with an
MDATA and sends all of the data bytes (with the two CRC bytes being held in the full-speed pipeline
stage). This could cause the siTD to decrement it's Total Bytes to Transfer field to zero, indicating it has
received all expected data. The host must still execute one more (scheduled) complete-split transaction in
order to extract the results of the full-speed transaction from the Transaction Translator (for example, the
Transaction Translator may have detected a CRC failure, and this result must be forwarded to the host).
If the host experiences hold-offs that cause the host controller to skip one or more (but not all) scheduled
split transactions for an isochronous OUT, then the protocol to the transaction translator is not consistent
and the transaction translator detects and reacts to the problem. Likewise, for host hold-offs that cause the
host controller to skip one or more (but not all) scheduled split transactions for an isochronous IN, the
C-prog-mask is used by the host controller to detect errors. However, if the host experiences a hold-off that
causes it to skip all of an siTD, or an siTD expires during a host hold off (for example, a hold-off occurs
and the siTD is no longer reachable by the host controller in order for it to report the hold-off event), then
the system software must detect that the siTDs have not been processed by the host controller (for example,
state not advanced) and report the appropriate error to the client driver.
24-108
•
C-prog-mask. This is an eight-bit bit-vector where the host controller keeps track of which
complete-splits have been executed. Due to the nature of the Transaction Translator periodic
pipeline, the complete-splits need to be executed in-order. The host controller needs to detect when
the complete-splits have not been executed in order. This can only occur due to system hold-offs
where the host controller cannot get to the memory-based schedule. C-prog-mask is a simple
bit-vector that the host controller sets a bit for each complete-split executed. The bit position is
determined by the micro-frame (FRINDEX[2:0]) number in which the complete-split was
executed. The host controller always checks C-prog-mask before executing a complete-split
transaction. If the previous complete-splits have not been executed, then it means one (or more)
have been skipped and data has potentially been lost. The system software is required to initialize
this field to zero before setting an siTD's Active bit to a one.
MCF5253 Reference Manual, Rev. 1
Freescale Semiconductor