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

• 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

Universal Serial Bus Interfaces
By reading the status fields of the completed dTDs, the DCD can determine if the transfers completed
successfully. Success is determined with the following combination of status bits:
Should any combination other than the one shown above exist, the DCD must take proper action. Transfer
failure mechanisms are indicated in the Device Error Matrix.
In addition to checking the status bit the DCD must read the Transfer Bytes field to determine the actual
bytes transferred. When a transfer is complete, the Total Bytes transferred is by decremented by the actual
bytes transferred. For Transmit packets, a packet is only complete after the actual bytes reaches zero, but
for receive packets, the host may send fewer bytes in the transfer according the USB variable length packet
protocol.
21.8.5.5
It is necessary for the DCD to flush to de-prime one more endpoints on a USB device reset or during a
broken control transfer. There may also be application specific requirements to stop transfers in progress.
The following procedure can be used by the DCD to stop a transfer in progress:
21.8.5.6
Table 21-90
21-140
•
•
•
•
1. Write a '1' to the corresponding bit(s) in ENDPTFLUSH.
2. Wait until all bits in ENDPTFLUSH are ‘0.’
3. Software note: this operation may take a large amount of time depending on the USB bus activity.
4. Read ENDPTSTATUS to ensure that for all endpoints commanded to be flushed, that the
Active = 0
Halted = 0
Transaction Error = 0
Data Buffer Error = 0
It is not desirable to have this wait loop within an interrupt service routine.
corresponding bits are now ‘0.’ If the corresponding bits are ‘1’ after step #2 has finished, then the
flush failed as described in the following:
Explanation: In very rare cases, a packet is in progress to the particular endpoint when commanded
flush using ENDPTFLUSH. A safeguard is in place to refuse the flush to ensure that the packet in
progress completes successfully. The DCD may need to repeatedly flush any endpoints that fail to
flush be repeating steps 1–3 until each endpoint is successfully flushed.
summarizes packet errors that are not automatically handled by the USB controller:
Flushing/De-Priming an Endpoint
Device Error Matrix
Overflow **
ISO Packet Error
ISO Fulfillment Error
MPC8536E PowerQUICC III Integrated Processor Reference Manual, Rev. 1
Error
Table 21-90. Device Error Matrix
Direction
Both
RX
RX
Packet
Type
Any
ISO
ISO
Error Bit
Buffer
Data
0
0
1
Transaction
Error Bit
0
1
1
Freescale Semiconductor