C200 datasheet(17/82 Pages) INTEL

17 / 82 page

Specification Update

Errata

USB Babble Detected with SW Overscheduling

Problem:

If software violates USB periodic scheduling rules for full-speed isochronous traffic by

overscheduling, the RMH may not handle the error condition properly and return a

completion split with more data than the length expected.

Implication: If the RMH returns more data than expected, the endpoint will detect packet babble for

that transaction and the packet will be dropped. Since overscheduling occurred to

create the error condition, the packet would be dropped regardless of RMH behavior. If

a single isochronous data packet is lost, no perceptible impact to the end user is

expected.

Note:

USB software overscheduling occurs when the amount of data scheduled for a

microframe exceeds the maximum budget. This is an error condition that violates the

USB periodic scheduling rule.

Note:

This failure has only been recreated synthetically with USB software intentionally

overscheduling traffic to hit the error condition.

Workaround: None.

Status:

No Plan to Fix.

USB Full-/low-speed EOP Issue

Problem:

If the EOP of the last packet in a USB Isochronous split transaction (Transaction >189

bytes) is dropped or delayed 3 ms or longer the following may occur:

• If there are no other pending low-speed or full-speed transactions the RMH will not

send SOF, or Keep-Alive. Devices connected to the RMH will interpret this condition

as idle and will enter suspend.

• If there is other pending low-speed or full-speed transactions, the RMH will drop

the isochronous transaction and resume normal operation.

Implication:

• If there are no other transactions pending, the RMH is unaware a device entered

suspend and may starting sending a transaction without waking the device. The

implication is device dependent, but a device may stall and require a reset to

resume functionality.

• If there are other transactions present, only the initial isochronous transaction may

be lost. The loss of a single isochronous transaction may not result in end user

perceptible impact.

Note:

Intel has only observed this failure when using software that does not comply with the

USB specification and violates the hardware isochronous scheduling threshold by

terminating transactions that are already in progress.

Workaround: None.

Status:

No Plan to Fix.

USB PLL Control FSM not Getting Reset on Global Reset

Problem:

Intel® 6 Series Chipset and Intel® C200 Series Chipset USB PLL may not lock if a

Global Reset occurs early during a cold boot sequence.

Implication: USB interface would not be functional an additional cold boot would be necessary to

recover.

Workaround: None.

Status:

No Plan to Fix.

C200 Datasheet(PDF) 17 Page - Intel Corporation

C200 Datasheet(HTML) 17 Page - Intel Corporation

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82

Datasheet Download

Link URL