MCF5253VM140J Freescale Semiconductor, MCF5253VM140J Datasheet - Page 569

• 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

The software must apply the following rules when calculating the schedule and linking the schedule data
structures into the periodic schedule:
24.9.12.3.2 Tracking Split Transaction Progress for Isochronous Transfers
Isochronous endpoints do not employ the concept of a halt on error, however the host controller does
identify and report per-packet errors observed in the data stream. This includes schedule traversal
problems (skipped micro-frames), timeouts and corrupted data received.
In similar kind to interrupt split-transactions, the portions of the split transaction protocol must execute in
the micro-frames they are scheduled. The queue head data structure used to manage full- and low-speed
interrupt has several mechanisms for tracking when portions of a transaction have occurred. Isochronous
transfers use siTDs for their transfers and the data structures are only reachable using the schedule in the
exact micro-frame in which they are required (so all the mechanism employed for tracking in queue heads
is not required for siTDs). The software has the option of reusing siTD several times in the complete
periodic schedule. However, it must ensure that the results of split transaction N are consumed and the
siTD re-initialized (activated) before the host controller gets back to the siTD (in a future micro-frame).
Split-transaction isochronous OUTs utilize a low-level protocol to indicate which portions of the split
transaction data have arrived. Control over the low-level protocol is exposed in an siTD using the fields
Transaction Position (TP) and Transaction Count (T-count). If the entire data payload for the OUT split
transaction is larger than 188 bytes, there will be more than one start-split transaction, each of which
require proper annotation. If host hold-offs occur, then the sequence of annotations received from the host
will not be complete, which is detected and handled by the transaction translator. See
“Split Transaction Scheduling Mechanisms for Isochronous,”
used during a sequence of start-split transactions.
The fields siTD[T-Count] and siTD[TP] are used by the host controller to drive and sequence the
transaction position annotations. It is the responsibility of the system software to properly initialize these
fields in each siTD. Once the budget for a split-transaction isochronous endpoint is established, S-mask,
T-Count, and TP initialization values for all the siTD associated with the endpoint are constant. They
remain constant until the budget for the endpoint is recalculated by the software and the periodic schedule
adjusted.
For IN-endpoints, the transaction translator simply annotates the response data packets with enough
information to allow the host controller to identify the last data. As with split transaction Interrupt, it is the
host controller's responsibility to detect when it has missed an opportunity to execute a complete-split. The
Freescale Semiconductor
•
•
The software must ensure that an isochronous split-transaction is started so that it will complete
before the end of the B-Frame.
The software must ensure that for a single full-speed isochronous endpoint, there is never a
start-split and complete-split in H-Frame, micro-frame 1. This is mandated as a rule so that case 2a
and case 2b can be discriminated. According to the core USB specification, the long isochronous
transaction illustrated in Case 2b, could be scheduled so that the start-split was in micro-frame 1
of H-Frame N and the last complete-split would need to occur in micro-frame 1 of H-Frame N+1.
However, it is impossible to discriminate between cases 2a and case 2b, which has significant
impact on the complexity of the host controller.
MCF5253 Reference Manual, Rev. 1
for a description on how these fields are
Universal Serial Bus Interface
Section 24.9.12.3.1,
24-107