MPC8536E-ANDROID Freescale Semiconductor, MPC8536E-ANDROID Datasheet - Page 1439

• Manufacturer Part Number: MPC8536E-ANDROID
• Description: HARDWARE/SOFTWARE ANDROID OS
• Manufacturer: Freescale Semiconductor
• Series: PowerQUICC ™r
• Type: MPUr

Specifications of MPC8536E-ANDROID

• Contents: Board
• For Use With/related Products: MPC8536
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

By definition, the host controller cannot reach an siTD at the wrong time. If the I/O field indicates an IN,
then the start-split transaction includes only the extended token plus the full-speed token. Software must
initialize the siTD[Total Bytes To Transfer] field to the number of bytes expected. This is usually the
maximum packet size for the full-speed endpoint. The host controller exits this state when the start-split
transaction is complete.
The remainder of this section is specific to an isochronous OUT endpoint (that is, the I/O field indicates
an OUT). When the host controller executes a start-split transaction for an isochronous OUT it includes a
data payload in the start-split transaction. The memory buffer address for the data payload is constructed
by concatenating siTD[Current Offset] with the page pointer indicated by the page select field (siTD[P]).
A zero in this field selects Page 0 and a 1 selects Page 1. During the start-split for an OUT, if the data
transfer crosses a page boundary during the transaction, the host controller must detect the page cross,
update the siTD[P] bit from a zero to a one, and begin using the siTD Page 1 with siTD[Current Offset] as
the memory address pointer. The field siTD[TP] is used to annotate each start-split transaction with the
indication of which part of the split-transaction data the current payload represents (ALL, BEGIN, MID,
END). In all cases, the host controller simply uses the value in siTD[TP] to mark the start-split with the
correct transaction position code.
T-count is always initialized to the number of start-splits for the current frame. TP is always initialized to
the first required transaction position identifier. The scheduling boundary case (see
to determine the initial value of TP. The initial cases are summarized in
After each start-split transaction is complete, the host controller updates T-count and TP appropriately so
that the next start-split is correctly annotated.
which must be accomplished by the host controller.
Freescale Semiconductor
BEGIN
BEGIN
Case
1, 2a
1, 2a
MID
MID
ALL
TP
T-count
T-count
Table 21-69. Transaction Position (TP)/Transaction Count (T-Count) Transition Table
next
!=1
!=1
!=1
=1
0
1
1
TP next
MPC8536E PowerQUICC III Integrated Processor Reference Manual, Rev. 1
BEGIN
Table 21-68. Initial Conditions for OUT siTD TP and T-Count Fields
END
END
MID
MID
ALL
N/A
TP
When the OUT data payload is less than (or equal to) 188 bytes, only one start-split is required
to move the data. The one start-split must be marked with an ALL.
When the OUT data payload is greater than 188 bytes more than one start-split must be used
to move the data. The initial start-split must be marked with a BEGIN.
Transition from ALL, to done.
Transition from BEGIN to END. Occurs when T-count starts at 2.
Transition from BEGIN to MID. Occurs when T-count starts at greater than 2.
TP stays at MID while T-count is not equal to 1 (for example, greater than 1). This case can
occur for any of the scheduling boundary cases where the T-count starts greater than 3.
Transition from MID to END. This case can occur for any of the scheduling boundary cases
where the T-count starts greater than 2.
Table 21-69
illustrates all of the TP and T-count transitions,
Description
Description
Table
21-68.
Universal Serial Bus Interfaces
Figure
21-57) is used
21-105