Hub Checklist
USB Compliance Checklist
Hubs (Excluding Root Hubs)
For the 2.0 USB Specification
Checklist Version 1.07
January 17, 2012
USB Device Product Information
field
Date
Vendor Name
Vendor Street Address
Vendor City, State, Postal Code
Vendor Country
Vendor Phone Number
Vendor Contact, Title
Vendor Contact Email Address
Product Name
Product Model Number
Product Revision Level
Test ID Number
Manufacture, Model, & TID of
Receptacles used
Manufacture, Model, & TID of
Connectors and/or Cable
Assemblies used
Manufacture & Model Identifier
of the USB Hub Silicon used in
this hub
Signature of Preparer
—all fields must be filled in—
USB 2.0 Compliance Checklist
Hubs (Excluding Root Hubs)
Table of Contents
1
INTRODUCTION ....................................................................................................... 2
1.1
2
3
4
General Notes ................................................................................................................................ 2
MECHANICAL DESIGN AND LAYOUT ................................................................... 2
2.1
Tethered Hubs (not applicable to untethered hubs) ............................................................................ 4
2.2
Untethered Hubs (not applicable to tethered hubs) ............................................................................ 4
HUB STATES AND SIGNALS .................................................................................. 4
3.1
Hub Controller ................................................................................................................................ 4
3.2
Remote Wakeup ............................................................................................................................. 5
OPERATING VOLTAGES AND POWER ................................................................. 6
4.1
Self Power (applicable to any hub capable of operating as a self powered device) ................................. 7
4.2
Bus Power (applicable to any hub that can use bus power) .................................................................. 7
5
RECOMMENDED QUESTIONS ............................................................................... 8
6
EXPLANATIONS ...................................................................................................... 8
Revision History
version
1.06
1.05
1.04
1.03
1.02
1.01
1.00
.75
changes
Changes for 2.0
added test ID field, SP8 section ref
added H3, revised H2, H4
added E1, test description pointers
revised checklist 3.2 to fully cover spec 7.1.7.5, 11.4.4, and 11.9
revised introduction and clarified bus current draw ownership
revised M12, H1, H11, P7, inserted new H12, M13, fixed , , , typos
added preparer’s signature and changed checklist contact info
initial release: numerous clarifications/bug fixes, added contact info
first public review draft, released for Taipei USB Plugfest
January 17, 2012
date
2001.10.5
1999.8.16
1999.7.15
1999.4.9
1999.2.5
1999.1.4
1998.11.20
1998.10.26
USB 2.0 Compliance Checklist
Hubs (Excluding Root Hubs)
1 Introduction
This checklist helps designers of USB hubs (not including root hubs) to asses their products’ compliance with the
Universal Serial Bus Specification, Revision 2.0. Unless explicitly stated otherwise, all references to the USB
Specification refer to Revision 2.0.
This checklist is also used, in part, to qualify a USB hub for the USB-IF Integrators List. This document and other
USB compliance tools, including USB Check, are available in the developers section of the USB-IF’s website,
http://www.usb.org/developers/. The compliance checklists and other tools are updated periodically, so developers
should check for updates when starting new projects.
Section 5, Recommended Questions, contains questions covering areas not required by the USB Specification.
Answering these questions is not a requirement for compliance with the Specification or acceptance to the
Integrators List. However, vendors are strongly encouraged to take these questions into consideration when
designing their products.
Questions or comments regarding the Integrators List, Compliance Workshop testing results, or checklist
submissions should be sent to [email protected] If you have questions regarding the checklist itself, feel it fails to
adequately cover an aspect of the USB specification, have found an error, or would like to propose a question,
please contact the USB-IF at [email protected]
1.1


General Notes
All voltages are referenced to the hub’s USB ground.
Active extension cables violate the USB Specification since they do not allow for proper bus topology
management. A one-port hub integrated into the end of a 26ns cable is legal, and fulfils the same role without
raising the possibility of violating power distribution and turnaround time requirements. The hub must be a
bus-powered hub unless a power supply is used to meet the requirements for a self powered USB port.
2 Mechanical Design and Layout
ID
M1
question
What is the manufacture and model identifier of the connectors or cables used with this hub?
Manufacturer:
M2
Model:
If the connectors or cables used in this peripheral are NOT listed on the USB Integrators List attach a
Connector and Cable Assembly checklists covering this hub’s connectors and cable assemblies.
What is the manufacture and model identifier of the USB silicon used in this hub?
Manufacturer:
M3
Model:
If the silicon used in this peripheral is NOT listed on the USB Integrators List attach a Hub Silicon
checklist covering this hub’s USB silicon.
If the hub includes permanently attached devices, attach the appropriate checklists for those devices.
January 17, 2012
USB 2.0 Compliance Checklist
Hubs (Excluding Root Hubs)
Hub vendors are strongly encouraged to review the Connector and Cable Assembly and Hub Silicon checklists
regardless of whether or not their device’s cabling, connectors, and silicon appear on the Integrators List.
ID
question
M4
Does the hub have type A receptacles on all user-accessible downstream
ports?
Can the hub’s data lines withstand voltages between –1.0 and 4.6V applied
with a source impedance of 39 2% for up to 100ns?
When tri-stated, can any data line be continuously shorted to VBUS, GND,
the other data line, or the connector’s shield without damage occurring?
When driving 50% of the time, can any data line be shorted to VBUS, GND,
the other data line, or the connector’s shield without damage occurring?
Do all downstream ports have 15k 5% pull down resistors on D+ and D?
Do all D+ and D- traces present a characteristic impedance of 45 15% to
GND and a differential impedance of 90 15%, between the hub’s cable
connections and termination resistors?
Do all downstream ports present 150pF or less capacitance on D+ and D-?
If edge rate control capacitors are used:
Are they located between the transceiver pins
and the hub’s termination resistors?
Is their capacitance less than 75pF and balanced within 10%?
For full-speed signals originating at the hub, is the signaling rate
12.000Mb/s .25%, even if the hub uses spread spectrum clocking?
For low-speed signals originating at the hub, is the signaling rate 1.50Mb/s
1.5%, even if the hub uses spread spectrum clocking?
Is the maximum propagation delay for a signal with full- speed edges on any
route through the hub (including up to 1ns of propagation time from the
hub’s upstream to the hub silicon and up to 3ns of propagation time from
the hub silicon to any downstream port):
44ns or less if the hub has a detachable cable?
70ns or less if the hub has a fixed cable?
Is the maximum propagation delay on any route through the hub for a signal
to, or from, a low- speed device connected directly to the hub (including up
to 1ns of propagation time from the hub’s upstream port to the hub silicon
and up to 3ns of propagation time from the hub silicon to any downstream
port):
274ns or less if the hub has a detachable cable?
300ns or less if the hub has a fixed cable?
Are the hub’s upstream receivers and transmitters within 1ns of its upstream
cable connection?
Are the hub’s downstream receivers and transmitters within 3ns of its
downstream cable connections?
Does the hub present sufficient capacitance between VBUS and GND on its
upstream and downstream ports to prevent adverse effects from flyback
voltages when a cable is disconnected? (A minimum of 1.0F is
recommended for the upstream port.)
Does the hub have only one upstream port?
Are you using the USB pins on any of the USB connectors on your device
for any other purposes except for USB?
M5
M6
M7
M8
M9
M10
M11
M12
M13
M13
M14
M15
M16
M17
M18
M19
January 17, 2012
response
yes
no
sections
in spec
6.2
yes
no
7.1.1
yes
no
7.1.1
yes
no
7.1.1
yes
no
7.1.5
yes
no
7.1.6
yes
no
7.1.6
7.1.6
yes
yes
yes
no
no
no
7.1.11
yes
no
7.1.11
7.1.14
yes
yes
no
no
7.1.14
yes
yes
no
no
yes
no
7.1.16
yes
no
7.1.16
yes
no
7.2.4.2
yes
yes
no
no
11.1.1
USB 2.0 Compliance Checklist
2.1
Tethered Hubs
Hubs (Excluding Root Hubs)
(not applicable to untethered hubs)
Tethered hubs are hubs with a captive upstream cable.
MT1
Does the captive cable have a series A plug?
MT2
Does the hub pull up D+ with a 1.5k 5% resistor attached to a voltage
source between 3.0 and 3.6V or with a Thevénin source of at least 900?
2.2
Untethered Hubs
yes
yes
no
no
6.2
7.1.5
(not applicable to tethered hubs)
Untethered hubs are hubs with a detachable upstream cable.
MUT1 Does the have a series B receptacle?
MUT2 Does the hub pull up D+ with a 1.5k 5% resistor attached to a voltage
source between 3.0 and 3.6V?
MUT3 Does the hub’s upstream port present 100pF or less on D+ and D-?
yes
yes
no
no
6.2
7.1.5
yes
no
7.1.6
3 Hub States and Signals
E1
Are the hub’s differential and single-ended USB signals within spec? Note:
yes
no
7.1.6
This test is especially important if ferrite beads or a common mode choke is
used on the USB data lines, as these components often pose a significant
signal integrity hazard.
For details on testing USB signals, consult the USB-IF’s signal quality test description, which can be downloaded
from the USB-IF Compliance Program webpage.
3.1
H1
H2
H3
H4
H5
H6
H7
Hub Controller
Can the hub pull up D+ on its upstream port from 0V to at least 2.0V within
2.5s?
Is the hub’s pullup active only when VBUS is high?
Is the VBUS switching threshold for the hub’s pullup control between 1.0V
and 4.0V?
If the hub is bus powered, or uses bus power to run any of its components,
does it pullup its upstream D+ line within 100ms of VBUS exceeding 4.01V?
When the hub is plugged into the bus, does it meet all power-on and
connection timing requirements, as illustrated in Figure 7-19?
Does the hub respond to a reset no sooner than 2.5s and no later than 10ms
after the SE0 begins?
Is the hub’s reset recovery time less than 10ms?
January 17, 2012
yes
no
7.1.5
yes
yes
no
no
7.1.5
7.1.5
yes
no
7.1.5
yes
no
yes
no
7.1.7.1
7.3.2
7.1.7.3
yes
no
7.1.7.3
USB 2.0 Compliance Checklist
H8
H9
H10
H11
H12
H13
H14
H15
H16
H17
H18
H19
H20
H21
H22
H23
H24
H25
At the end of the reset recovery time:
Is the hub’s controller in the default state?
The frame timer unlocked?
Is an SE0 driven on all downstream ports?
Are all port status bits set to their default values?
Can the hub correctly handle more than one USB RESET with no
intervening packets?
Does the hub begin the transition to its suspend state after its upstream bus
segment has been idle for 3ms, regardless of the hub’s state?
Has the hub’s power consumption dropped to its suspended value after the
hub’s upstream bus segment has been idle for 10ms?
When suspended, does the hub recognize any non-idle state on the bus,
excluding a reset, as a resume signal?
When suspended, does the hub recognize a reset and act on the signal
so that it enters the default state?
Hubs (Excluding Root Hubs)
yes
yes
yes
yes
yes
no
no
no
no
no
7.1.7.3
9.1.1
11.2.1
11.5.1
11.16.2.6
7.1.7.3
yes
no
7.1.7.4
yes
no
7.1.7.4
yes
no
7.1.7.5
yes
no
Does the hub recognize a Klow- speed EOPJ transition on its upstream
port as the end of resume signaling?
Is the hub able to accept a SetAddress() request 10ms after resume is
signaled?
Does the hub complete its wakeup within 20ms?
Can the hub function correctly with frame lengths between 995 and 1005s?
yes
no
7.1.7.5
7.1.7.3
9.1
7.1.7.5
yes
no
7.1.7.5
yes
yes
no
no
7.1.7.5
7.1.12
Does the hub enumerate correctly on tier 6, when subjected to worst-case
hub bit skews and delay times?
Does the hub controller allow an interpacket delay of at least two full- speed
bit times?
Is the hub’s controller transaction timeout 16–18 full-speed bit times?
Does the combination of the hub’s pullup and the 15k 5% pulldown
resistor at the port above the hub yield a voltage between 2.7 and 3.6V when
the bus is idle?
Does the hub complete SetAddress() or a standard request with no data in
less than 50ms?
Does the hub pass a full Chapter 9 test, as performed by USB Check?
yes
no
yes
no
7.1.14
7.1.19
7.1.18
yes
yes
no
no
7.1.19
7.3.2
yes
no
yes
no
Does the hub controller implement a default control endpoint 0 for all
addresses?
Does the hub pass a full Chapter 11 test, as performed by USB Check?
yes
no
7.3.2
9.2.6.3
Chapters
8 and 9
9.1.1.4
yes
no
H26
H27
Chapter
11
11.16.1
11.16.1
Does the hub complete a standard request with no data stage within 50ms?
yes
no
Does the hub deliver the first and all subsequent data packets, except for the
yes
no
last data packet, for a standard request with a data stage within 50ms?
H28
Does the hub deliver the last data packet for a standard request with a data
yes
no
11.16.1
within 50ms?
Hub vendors are strongly encouraged to complete all bus transactions as quickly as is practical. See section 9.2.6.1
for details.
3.2
W1
W2
Remote Wakeup
Does the hub wait at least 5.0ms after its bus segment enters the idle state
before sending a remote wakeup?
Does the hub signal remote wakeup by driving K upstream for at least 1ms,
January 17, 2012
yes
no
7.1.7.5
yes
no
7.1.7.5
USB 2.0 Compliance Checklist
W3
W4
W5
W6
W7
W8
W9
W10
W11
but not more than 15ms?
After driving K, does the hub immediately tri-state its buffers without
driving the bus to any non-K state?
When acting as an intermediate hub, does the hub repeat a remote wakeup
on its upstream port within 100s of receiving the remote wakeup at any
downstream port?
When acting as an intermediate hub, does the hub drive resume on its
upstream port for at least 1ms?
When acting as an intermediate hub, does the hub stop driving resume on its
upstream port and reverse connectivity no more than 15ms after it began
driving resume?
When acting as the controlling hub, does the hub drive resume on only the
downstream port which received the resume signal?
When acting as the controlling hub, does the hub drive resume within 100s
of receiving the resume signal?
When acting as the controlling hub, does the hub drive resume on the
resumed downstream port for at least 20ms?
Does the hub generate a remote wakeup when any C_PORT_SUSPEND bit
is set, regardless of whether or not remote wakeup is enabled?
If remote wakeup is enabled, does the hub generate a remote wakeup when
any bit is set in the hub change field or a port change field?
Hubs (Excluding Root Hubs)
yes
no
7.1.7.5
yes
no
7.1.7.5
yes
no
7.1.7.5
yes
no
7.1.7.5
yes
no
yes
no
yes
no
yes
no
yes
no
7.1.7.5
11.9
7.1.7.5
11.9
7.1.7.5
11.9
11.4.4
9.6.2
11.4.4
9.6.2
yes
yes
yes
no
no
no
7.1.7.1
7.2.1
7.2.3
yes
no
7.2.3
yes
no
7.2.3
yes
no
7.2.4.1
7.2.3
yes
yes
no
no
7.2.4.1
7.2.4.1
4 Operating Voltages and Power
P1
P2
P3
P4
P5
P6
P7
P8
Is the port power rail stabilization time (t2) less than 100ms?
Does the hub source no current to VBUS under any circumstance?
When the hub is suspended, is average current drawn from VBUS 500A or
less, excluding current drawn by devices attached downstream from the hub
but including devices included in the hub’s unit load?
If the hub’s current draw spikes during suspend, is the maximum spike
height less than 100mA and is the spike’s edge rate less than 100mA/s for
VBUS between 4.02 and 5.25V? (Excluding current drawn by devices
attached downstream from the hub but including devices included in the
hub’s unit load.)
When the hub wakes up from suspend, does it limit any inrush currents
drawn from VBUS to 100mA or less, excluding current drawn by devices
attached downstream from the hub but including devices included in the
hub’s unit load?
Does the hub limit the inrush current drawn from VBUS, either by using
capacitors smaller than 10F or by using soft-start circuits, such that no
more than 10F of capacitance is charged by currents higher than 100mA
when the hub is hot plugged?
Does the hub draw no inrush current from the bus at configuration time?
Does the hub have at a total of at least 120F of low ESR bypass
capacitance at its downstream ports?
January 17, 2012
USB 2.0 Compliance Checklist
P9
P10
P11
4.1
SP1
SP2
SP3
SP4
SP5
SP6
SP7
SP8
4.2
BP1
BP2
BP3
BP4
BP5
BP6
BP7
BP8
Hubs (Excluding Root Hubs)
Does the hub’s port bypassing limit the maximum voltage droop at any of its
downstream ports to 330mV, even when subjected to hot-plug inrush
currents with peaks of 7.5A or more? (As of this writing, the highest inrush
current the USB-IF has observed from a within spec configuration is
7.40A.)
Does the hub’s descriptor include the port power turn on time?
(bPwrOn2PwrGood should be zero for a hub without power switching.)
If the hub implements ganged power switching, does it conform to the
requirements of section 11.11.1?
Self Power
7.2.4.1
yes
no
yes
no
11.15.2.1
11.11
11.11.1
yes
no
7.2.1
yes
no
7.2.1.2.1
yes
no
7.2.1.2.1
yes
no
7.2.1.3
yes
no
7.2.2
yes
no
7.2.2
yes
no
7.2.2
yes
no
11.13.5
(applicable to any hub that can use bus power)
Can the hub supply 0 to 100mA to each of its downstream ports when using
only bus power?
Does the hub allow host controlled power switching of its downstream
ports?
When reset, does the hub turn off power to all downstream ports?
Does the hub draw the amount of current specified in its MaxPower field or
less at all times, excluding current provided to downstream ports, provided
its VBUS is between 4.02 and 5.25V?
Can the hub operate in its unconfigured state with a steady-state VBUS of
4.35–5.25V?
Can the hub operate in its unconfigured state with a transient VBUS as low as
4.02V?
Can the hub operate in its configured state with a steady-state VBUS of 4.50–
5.25V?
Can the hub operate in its configured state with a transient VBUS as low as
4.17V?
January 17, 2012
no
(applicable to any hub capable of operating as a self powered device)
Can the hub supply 0 to 500mA on each of its downstream ports when using
self power?
Does the hub implement overcurrent protection to prevent more than 5A
from being drawn from any downstream port?
Is the hub’s overcurrent protection resettable without user mechanical
intervention, such as replacing a fuse?
Does the hub draw the amount of current specified in its MaxPower field or
less from the bus at all times, including when powering up a downstream
port, provided its VBUS is between 4.02 and 5.25V?
Can the hub operate in all states with a steady-state upstream VBUS of 4.35–
5.25V when using self power?
Can the hub operate in all states with a transient upstream VBUS as low as
4.02V when using self power?
Can the hub maintain VBUS between 4.75 at 5.25V at all of its downstream
connectors for DC loads between 0 and 500mA per downstream port when
using self power?
If an overcurrent condition occurs, does the hub report the event to the host?
Bus Power
yes
yes
no
7.2.1
yes
no
yes
yes
no
no
7.2.1.1
11.11
7.2.1.1
7.2.1.3
yes
no
7.2.2
yes
no
7.2.2
yes
no
7.2.2
yes
no
7.2.2
USB 2.0 Compliance Checklist
Hubs (Excluding Root Hubs)
BP9
Is the maximum DC voltage drop between the hub’s cable connections
yes
no
7.2.2
100mV?
BP10
When the hub wakes up from suspend, does it limit any inrush currents to
yes
no
7.2.3
100mA or less, excluding current delivered to its downstream ports?
BP11
Does the hub limit the inrush current when one or more of its downstream
yes
no
7.2.4.1
ports is turned on?
Note: the 100mA current draw allowed for a bus powered hub includes all current drawn by the hub except current
passed to downstream USB ports via VBUS, GND, D+, D-, or cable EMI shields. Thus, the 100mA includes the
power required to drive the hub’s upstream port but does not include the power supplied to downstream devices or
required to drive downstream data lines—since the hub and any device connected directly to the hub will not drive
signals simultaneously, the hub can “borrow” the downstream devices’ signaling current.
In the case of a self-powered hub which uses a bus powered upstream interface, no current from upstream is
allocated for the hub’s downstream ports. Thus, the current used to drive the downstream ports must be drawn from
the hub’s power supply, not from upstream. In this case, a USB controller with split supplies or external USB
transcievers must be used to isolate the downstream drivers from upstream power.
For details on testing USB power provision, consult the USB-IF’s drop and droop test description, which can be
downloaded from the USB-IF Compliance Program webpage.
5 Recommended Questions
R1
R2
R3
R4
R5
R6
R7
R8
Are the hub’s signal swings matched as closely as possible?
If ferrite beads are used in the hub’s USB connections, are they present on
only the VBUS and GND lines?
Does the hub limit its total current consumption to 500mA or less when one
or more of its downstream ports is turned on?
Does the hub complete all commands as quickly as is practical?
If the hub is self-powered and does not operate any of its components from
bus power, does it only signal an attach when both bus power and external
power are available?
Can a bus powered hub withstand a short on its downstream port either until
the upstream hub current limits or until the bus powered hub’s optional
overcurrent limiting trips?
Is a downstream port fully powered on before connect detection and bus
speed evaluation is performed?
Is the hub’s average response time less than 5ms for all requests?
yes
yes
no
no
7.1.2
7.1.6
yes
no
yes
yes
no
no
7.2
7.2.4.1
9.2.6.1
yes
no
yes
no
yes
no
11.16.1
6 Explanations
This section should be used to explain any “no” answers or clarify any answers on checklist items above. Please
key entries to the appropriate checklist question.
January 17, 2012
USB 2.0 Compliance Checklist
January 17, 2012
Hubs (Excluding Root Hubs)
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement