32-bit, 33 MHz PCI interface compliant with PCI Local
■
Bus Specification Revision 2.2
Four downstream USB ports
■
Each USB port dedicated to providing full USB band-
■
width to the attached device
Full compliance with Universal Serial Bus Specifica-
■
tion Revision 1.1
OpenHCI Open Host Controller Interface Specifica-
■
tion for USB Release 1.0a compatible
Fully compatible with Microsoft Windows 98/95/Win-
■
dows NT * standard OpenHCI drivers
Fully compatible with Mac† OS 8.5 and 8.6
■
Integrated dual-speed USB transceivers
■
3 V or 5 V switchable PCI signaling
■
Low-power mode and wake-up compatible with PCI
■
Power Management Interface Specification Revision
1.1
Supports up to 127 devices per port
■
Supports peripheral hot swap and wake-up
■
Support for legacy keyboard and mouse
■
128-pin TQFP package
■
Full 12 Mbits/s bandwidth per port
■
Evaluation kit:
■
— PCI card
— Data sheet
0.25 µm technology
■
Applications
Seamless integration with 3 V or 5 V PCI-based com-
■
puter products
Supports all USB compliant devices and hubs
■
Simultaneous operation of multiple high-performance
■
devices
Description
The Agere Systems Inc. USS-344 QuadraBus provides
a single-chip four-host PCI-to-Universal Serial Bus
(USB) solution. The USS-344 interfaces directly to any
32-bit, 33 MHz PCI bus and is ideal for either onboard
applications or add-in card applications. It can easily be
configured to communicate in either a 3 V PCI environment or 5 V PCI environment simply by selecting the
appropriate communications voltage level on the VIO
input pin.
The USS-344 provides four downstream USB ports for
connectivity with any USB compliant device or hub. Fullspeed or low-speed peripherals are supported along
with all of the USB transfer types: control, interrupt,
bulk, or isochronous. The USS-344’s OpenHCI compliance offers significant USB performance benefits and
reduced CPU overhead compared to other USB UHCI
host controllers.
In addition, the USS-344 offers a significant performance advantage over all other USB host controllers
(both UHCI and OHCI) by providing full USB bandwidth
to each port rather than sharing the USB bandwidth
over all ports. This results in an increase in the number
of devices which can feasibly be connected to a
computer system as well as ensuring high-bandwidth
devices, such as video cameras and audio devices, are
always provided with the high bandwidth they need
while other USB devices are in use.
The USS-344 is a multifunction PCI device with one
single-port USB host controller per PCI function. There
are four PCI functions in the USS-344 for a total of four
single-port USB host controllers. Each single-port host
controller provides the full USB bandwidth (12 Mbits/s)
for devices connected downstream of its port.
The USS-344 is fully compatible with the Microsoft Windows standard OpenHCI drivers. The USS-344
pinout is compatible with the future release of the Agere
USB 2.0 host controller.The USS-344 is a 3.3 V device
fabricated in 0.25 µm technology. Integrated dual-speed
USB transceivers enable a single-chip PCI-to-USB
solution. The USS-344 provides full support for legacy
PC peripherals as defined in the OpenHCI Open Host
Controller Interface Specification for USB Release 1.0a.
* Microsoft, Windows, and Windows NT are registered trademarks
of Microsoft Corporation.
† Mac is a registered trademark of Apple Computer, Inc.
Features .................................................................................................................................................................. 1
Applicable Documents and Specifications ............................................................................................................... 4
Pin Information ........................................................................................................................................................ 4
PCI Function 0—Single-Port USB Host Controller 0 ....................................................................................... 12
PCI Function 1—Single-Port USB Host Controller 1 ....................................................................................... 16
PCI Function 2—Single-Port USB Host Controller 2 ....................................................................................... 20
PCI Function 3—Single-Port USB Host Controller 3 ....................................................................................... 24
USB Registers ....................................................................................................................................................... 28
Legacy Support Registers ..................................................................................................................................... 35
USB Connection Instructions...........................................................................................................................38
Test Mode Connection Instructions ................................................................................................................. 38
Power Connection Recommendations .................................................................................................................. 41
Power Management Interface ............................................................................................................................... 42
Configuration Space Offset 50h....................................................................................................................... 43
Configuration Space Offset 51h....................................................................................................................... 43
Configuration Space Offset 52h....................................................................................................................... 44
Configuration Space Offset 54h....................................................................................................................... 44
Configuration Space Offset 56h....................................................................................................................... 45
Configuration Space Offset 57h....................................................................................................................... 45
Power Consumption/Dissipation Reporting ..................................................................................................... 45
NAND Tree Mode .................................................................................................................................................. 46
Absolute Maximum Ratings ................................................................................................................................... 48
USB Electrical Characteristics ......................................................................................................................... 52
Ordering Information .............................................................................................................................................. 54
105INTANOutput/Open Drain PCI Interrupt A (Active-Low).
108INTBNOutput/Open Drain PCI Interrupt B (Active-Low).
109INTCNOutput/Open Drain PCI Interrupt C (Active-Low).
110INTDNOutput/Open Drain PCI Interrupt D (Active-Low).
119PMENOutput/Open Drain Power Management Event (Active-Low).
1, 9, 15, 20, 28, 33, 39, 46, 52, 59,
V
DD
Power3.3 V V
65, 73, 80, 106, 112, 118, 124
2, 8, 14, 21, 27, 34, 40, 45, 51, 57,
V
SS
PowerV
60, 66, 74, 107, 114, 117, 123
58VIOPowerPCI Environment Selection (3.3 V or 5 V).
* An N following the symbol names indicates active-low for the USS-344.
DD.
SS.
Table 3. USB Port Signals
PinSymbol*TypeDescription
89DPLS0BidirUSB Port 0 DPLUS.
90DMNS0BidirUSB Port 0 DMINUS.
91DPLS1BidirUSB Port 1 DPLUS.
92DMNS1BidirUSB Port 1 DMINUS.
95DPLS2BidirUSB Port 2 DPLUS.
96DMNS2BidirUSB Port 2 DMINUS.
97DPLS3BidirUSB Port 3 DPLUS.
98DMNS3BidirUSB Port 3 DMINUS.
76PRTPWR0BidirUSB Port 0 Power Enable (Active-Low).
78PRTPWR1BidirUSB Port 1 Power Enable (Active-Low).
101PRTPWR2BidirUSB Port 2 Power Enable (Active-Low).
103PRTPWR3BidirUSB Port 3 Power Enable (Active-Low).
* An N following the symbol names indicates active-low for the USS-344.
66Agere Systems Inc.
Page 7
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Pin Information
(continued)
Table 3. USB Port Signals (continued)
PinSymbol*TypeDescription
77PWRFLT0NInputUSB Port 0 Overcurrent (Active-Low).
79PWRFLT1NInputUSB Port 1 Overcurrent (Active-Low).
102PWRFLT2NInputUSB Port 2 Overcurrent (Active-Low).
104PWRFLT3NInputUSB Port 3 Overcurrent (Active-Low).
81CLK48STOPBidirUSB Clock Stop (Optional). Used to stop external
48 MHz clock in PCI power management state D3.
87, 93, 99V
88, 94, 100V
TPowerUSB Transceiver V
DD
TPowerUSB Transceiver V
SS
86RREFInputUSB 2.0 1 kΩ Precision Resistor Connection. Hi-Z if
implementation does not expect upgrade to USB 2.0.
85V
APowerUSB 2.0 Analog Power. Connect to VDD if implementa-
DD
tion does not expect upgrade to USB 2.0.
82V
APowerUSB 2.0 Analog Power. Connect to VSS if implementa-
SS
tion does not expect upgrade to USB 2.0.
84XHIPowerUSB 2.0 Crystal Oscillator XHI Connection. Hi-Z if
implementation does not expect upgrade to USB 2.0.
3ChInterrupt Line R/W00h
3DhInterrupt Pin R01h
3EhMin_GntR03h
3FhMax_LatR56h
4ChSpecial—Subsystem Write CapabilityR/W00000000h
* The revision can be identified electronically using the standard PCI Revision ID register described in this table. The revision can also be iden-
tified by physical markings using the last letter of the USS-344 identifier code printed on the device. The USS-344 identifier code will be
printed using the format USS344XY, where X will identify the package type (T) and Y will identify the revision.
† This register is normally read only. Write capability of this register is available to system BIOS only.
†
11C 1h
†
5803h
TEST1 = 1b: 00h
88Agere Systems Inc.
Page 9
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Register Overview
(continued)
Table 7. PCI Bus Configuration Memory Summary (Function 1)
Refer to Tables 32—53 for more details on each of these registers.
Configuration Space OffsetRegister NameRead/WriteDefault Value (Reset)
00h—01hVendor ID R11C1h
02h—03hDevice IDR5803h
04h—05hCommandR/W0000h
06h—07hStatusR/WTEST1 = 0b: 0210h
* The revision can be identified electronically using the standard PCI Revision ID register described in this table. The revision can also be iden-
tified by physical markings using the last letter of the USS-344 identifier code printed on the device. The USS-344 identifier code will be
printed using the format USS344XY, where X will identify the package type (T) and Y will identify the revision.
† This register is normally read only. Write capability of this register is available to system BIOS only.
* The revision can be identified electronically using the standard PCI Revision ID register described in this table. The revision can also be iden-
tified by physical markings using the last letter of the USS-344 identifier code printed on the device. The USS-344 identifier code will be
printed using the format USS344XY, where X will identify the package type (T) and Y will identify the revision.
† This register is normally read only. Write capability of this register is available to system BIOS only.
1010Agere Systems Inc.
Page 11
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Register Overview
(continued)
Table 9. PCI Bus Configuration Memory Summary (Function 3)
Refer to Tables 76—97 for more details on each of these registers.
Configuration Space OffsetRegister NameRead/WriteDefault Value (Reset)
00h—01hVendor ID R11C1h
02h—03hDevice IDR5803h
04h—05hCommandR/W0000h
06h—07hStatusR/WTEST1 = 0b: 0210h
* The revision of the USS-344 can be identified either electronically or by physical markings. The revision can be identified electronically using
the standard PCI Revision ID register described in this table. The revision can also be identified by physical markings using the last letter of
the USS-344 identifier code printed on the device. The USS-344 identifier code will be printed using the format USS344XY, where X will identify the package type (T) and Y will identify the revision.
† This register is normally read only. Write capability of this register is available to system BIOS only.
Agere Systems Inc.11
Page 12
USS-344 QuadraBus
Advance Data Sheet, Rev. 9
Four-Host PCI-to-USB OpenHCI Host Controller
PCI Registers
PCI Function 0—Single-Port USB Host Controller 0
Table 10. Vendor ID Register (00h—01h)
This register is fixed as the Agere Systems vendor ID assigned by the PCI SIG.
BitsFieldRead/WriteReset/Description
15:0Vendor IDRAssigned 11C1h
Table 11. Device ID Register (02h—03h)
This register is fixed as the Agere Systems product USS-344.
BitsFieldRead/WriteReset/Description
15:0Device IDRAssigned 5803h
Table 12. Command Register (04h—05h)
All read-only bits represent nonconfigurable features of the USS-344.
* The revision of the USS-344 can be identified either electronically or by physical markings. The revision can be identified
electronically using the standard PCI Revision ID register described in this table. The revision can also be identified by physical markings using the last letter of the USS-344 identifier code printed on the device. The USS-344 identifier code will be
printed using the format USS344XY, where X will identify the package type (M or T) and Y will identify the revision.
Table 15. Class Code Register (09h—0Bh)
The PCI class code for all OpenHCI host controllers is defined in the OpenHCI specification.
BitsFieldRead/WriteReset/Description
7:0Programming Interface R10h = OpenHCI Host Controller
15:8SubclassR03h = Universal Serial Bus
23:16Base ClassR0Ch = Serial Bus Controller
Table 16. Cache Line Size Register (0Ch)
No cache line is supported by the USS-344.
(continued)
BitsFieldRead/WriteReset/Description
7:0Cache Line SizeR00h
Table 17. Latency Timer Register (0Dh)
Controls the number of clock cycles the USS-344 may remain on the PCI bus after becoming bus master.
BitsFieldRead/WriteReset/Description
7:0Latency TimerR/WUpper 5 bits are read/write. Lower
The Base Address register is used to specify to the PCI operating system the memory size of the USS-344 device.
As recommended by the OpenHCI specification, the lower 12 bits are read only (fixed to logic 0) to indicate 4K
These Base Address registers are unused by the USS-344 device.
BitsFieldRead/WriteReset/Description
31:0BAR 1—5R00000000h
Table 22. Cardbus CIS Pointer Register (28h—2Bh)
Cardbus CIS pointer not required for the USS-344.
BitsFieldRead/WriteReset/Description
31:0CardBus CIS PointerR00000000h
(continued)
20 bits are read/write.
Table 23. Subsystem Vendor ID Register (2Ch—2Dh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem Vendor IDR/W11C1h
Table 24. Subsystem ID Register (2Eh—2Fh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem IDR/W5803h
Table 25. Expansion ROM Base Address Register (30h—33h)
Expansion ROM not supported by the USS-344.
BitsFieldRead/WriteReset/Description
31:0Expansion ROM Base
Address
R00000000h
1414Agere Systems Inc.
Page 15
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
PCI Registers
Table 26. Capabilities Pointer Register (34h)
BitsFieldRead/WriteReset/Description
7:0Cap_Ptr RTEST1 = 0b: 50h
Table 27. Interrupt Line Register (3Ch)
BitsFieldRead/WriteReset/Description
7:0Interrupt Line R/W00h
Table 28. Interrupt Pin Register (3Dh)
Interrupt A used as the PCI interrupt for this core.
BitsFieldRead/WriteReset/Description
7:0Interrupt Pin R01h
Table 29. Min_Gnt Register (3Eh)
The USS-344 can support a four DWORD master burst read or write which requires less than 500 ns.
BitsFieldRead/WriteReset/Description
7:0Min_GntR03h
(continued)
TEST1 = 1b: 00h
Table 30. Max_Lat Register (3Fh)
The USS-344 requires service at a minimum interval of 21.3 µs.
This is a special register implemented for compliance with Microsoft PC98 Specification, Chapter 9, Item 11. Bit 0
is read/write to allow the system BIOS to enable write capability of the Subsystem Vendor ID and Subsystem ID
registers (refer to Tables 23 and 24).
* The revision of the USS-344 can be identified either electronically or by physical markings. The revision can be identified
electronically using the standard PCI Revision ID register described in this table. The revision can also be identified by physical markings using the last letter of the USS-344 identifier code printed on the device. The USS-344 identifier code will be
printed using the format USS344XY, where X will identify the package type (M or T) and Y will identify the revision.
Table 37. Class Code Register (09h—0Bh)
The PCI class code for all OpenHCI host controllers is defined in the OpenHCI specification.
BitsFieldRead/WriteReset/Description
7:0Programming Interface R10h = OpenHCI Host Controller
15:8SubclassR03h = Universal Serial Bus
23:16Base ClassR0Ch = Serial Bus Controller
Table 38. Cache Line Size Register (0Ch)
No cache line is supported by the USS-344.
(continued)
BitsFieldRead/WriteReset/Description
7:0Cache Line SizeR00h
Table 39. Latency Timer Register (0Dh)
Controls the number of clock cycles the USS-344 may remain on the PCI bus after becoming bus master.
BitsFieldRead/WriteReset/Description
7:0Latency TimerR/WUpper 5 bits are read/write. Lower
The Base Address register is used to specify to the PCI operating system the memory size of the USS-344 device.
As recommended by the OpenHCI specification, the lower 12 bits are read only (fixed to logic 0) to indicate 4K
These Base Address registers are unused by the USS-344 device.
BitsFieldRead/WriteReset/Description
31:0BAR 1—5R00000000h
(continued)
20 bits are read/write.
Table 44. Cardbus CIS Pointer Register (28h—2Bh)
Cardbus CIS pointer not required for the USS-344.
BitsFieldRead/WriteReset/Description
31:0CardBus CIS PointerR00000000h
Table 45. Subsystem Vendor ID Register (2Ch—2Dh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem Vendor IDR/W11C1h
Table 46. Subsystem ID Register (2Eh—2Fh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem IDR/W5803h
1818Agere Systems Inc.
Page 19
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
PCI Registers
Table 47. Expansion ROM Base Address Register (30h—33h)
Expansion ROM not supported by the USS-344.
BitsFieldRead/WriteReset/Description
31:0Expansion ROM Base
Table 48. Capabilities Pointer Register (34h)
BitsFieldRead/WriteReset/Description
7:0Cap_Ptr RTEST1 = 0b: 50h
Table 49. Interrupt Line Register (3Ch)
BitsFieldRead/WriteReset/Description
7:0Interrupt Line R/W00h
Table 50. Interrupt Pin Register (3Dh)
If TEST0 = 0b, interrupt A is used as the PCI interrupt for this core.
If TEST0 = 1b, interrupt B is used as the PCI interrupt for this core.
(continued)
R00000000h
Address
TEST1 = 1b: 00h
BitsFieldRead/WriteReset/Description
7:0Interrupt Pin RTEST0 = 0b: 01h
TEST0 = 1b: 02h
Table 51. Min_Gnt Register (3Eh)
The USS-344 can support a four DWORD master burst read or write which requires less than 500 ns.
BitsFieldRead/WriteReset/Description
7:0Min_GntR03h
Table 52. Max_Lat Register (3Fh)
The USS-344 requires service at a minimum interval of 21.3 µs.
This is a special register implemented for compliance with Microsoft PC98 Specification, Chapter 9, Item 11. Bit 0
is read/write to allow the system BIOS to enable write capability of the Subsystem Vendor ID and Subsystem ID
registers (refer to Tables 23 and 24).
* The revision of the USS-344 can be identified either electronically or by physical markings. The revision can be identified
electronically using the standard PCI Revision ID register described in this table. The revision can also be identified by physical markings using the last letter of the USS-344 identifier code printed on the device. The USS-344 identifier code will be
printed using the format USS344XY, where X will identify the package type (M or T) and Y will identify the revision.
Table 59. Class Code Register (09h—0Bh)
The PCI class code for all OpenHCI host controllers is defined in the OpenHCI specification.
BitsFieldRead/WriteReset/Description
7:0Programming Interface R10h = OpenHCI Host Controller
15:8SubclassR03h = Universal Serial Bus
23:16Base ClassR0Ch = Serial Bus Controller
Table 60. Cache Line Size Register (0Ch)
No cache line is supported by the USS-344.
(continued)
BitsFieldRead/WriteReset/Description
7:0Cache Line SizeR00h
Table 61. Latency Timer Register (0Dh)
Controls the number of clock cycles the USS-344 may remain on the PCI bus after becoming bus master.
BitsFieldRead/WriteReset/Description
7:0Latency TimerR/WUpper 5 bits are read/write. Lower
The Base Address register is used to specify to the PCI operating system the memory size of the USS-344 device.
As recommended by the OpenHCI specification, the lower 12 bits are read only (fixed to logic 0) to indicate 4K
These Base Address registers are unused by the USS-344 device.
BitsFieldRead/WriteReset/Description
31:0BAR 1—5R00000000h
(continued)
20 bits are read/write.
Table 66. Cardbus CIS Pointer Register (28h—2Bh)
Cardbus CIS pointer not required for the USS-344.
BitsFieldRead/WriteReset/Description
31:0CardBus CIS PointerR00000000h
Table 67. Subsystem Vendor ID Register (2Ch—2Dh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem Vendor IDR/W11C1h
Table 68. Subsystem ID Register (2Eh—2Fh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem IDR/W5803h
2222Agere Systems Inc.
Page 23
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
PCI Registers
Table 69. Expansion ROM Base Address Register (30h—33h)
Expansion ROM not supported by the USS-344.
BitsFieldRead/WriteReset/Description
31:0Expansion ROM Base
Table 70. Capabilities Pointer Register (34h)
BitsFieldRead/WriteReset/Description
7:0Cap_Ptr RTEST1 = 0b: 50h
Table 71. Interrupt Line Register (3Ch)
BitsFieldRead/WriteReset/Description
7:0Interrupt Line R/W00h
Table 72. Interrupt Pin Register (3Dh)
If TEST0 = 0b, interrupt A is used as the PCI interrupt for this core.
If TEST0 = 1b, interrupt C is used as the PCI interrupt for this core.
(continued)
R00000000h
Address
TEST1 = 1b: 00h
BitsFieldRead/WriteReset/Description
7:0Interrupt Pin RTEST0 = 0b: 01h
TEST0 = 1b: 03h
Table 73. Min_Gnt Register (3Eh)
The USS-344 can support a four DWORD master burst read or write which requires less than 500 ns.
BitsFieldRead/WriteReset/Description
7:0Min_GntR03h
Table 74. Max_Lat Register (3Fh)
The USS-344 requires service at a minimum interval of 21.3 µs.
This is a special register implemented for compliance with Microsoft PC98 Specification, Chapter 9, Item 11. Bit 0
is read/write to allow the system BIOS to enable write capability of the Subsystem Vendor ID and Subsystem ID
registers (refer to Tables 23 and 24).
* The revision of the USS-344 can be identified either electronically or by physical markings. The revision can be identified
electronically using the standard PCI Revision ID register described in this table. The revision can also be identified by physical markings using the last letter of the USS-344 identifier code printed on the device. The USS-344 identifier code will be
printed using the format USS344XY, where X will identify the package type (M or T) and Y will identify the revision.
Table 81. Class Code Register (09h—0Bh)
The PCI class code for all OpenHCI host controllers is defined in the OpenHCI specification.
BitsFieldRead/WriteReset/Description
7:0Programming Interface R10h = OpenHCI Host Controller
15:8SubclassR03h = Universal Serial Bus
23:16Base ClassR0Ch = Serial Bus Controller
Table 82. Cache Line Size Register (0Ch)
No cache line is supported by the USS-344.
(continued)
BitsFieldRead/WriteReset/Description
7:0Cache Line SizeR00h
Table 83. Latency Timer Register (0Dh)
Controls the number of clock cycles the USS-344 may remain on the PCI bus after becoming bus master.
BitsFieldRead/WriteReset/Description
7:0Latency TimerR/WUpper 5 bits are read/write. Lower
The Base Address register is used to specify to the PCI operating system the memory size of the USS-344 device.
As recommended by the OpenHCI specification, the lower 12 bits are read only (fixed to logic 0) to indicate 4K
These base address registers are unused by the USS-344 device.
BitsFieldRead/WriteReset/Description
31:0BAR 1—5R00000000h
(continued)
20 bits are read/write.
Table 88. Cardbus CIS Pointer Register (28h—2Bh)
Cardbus CIS pointer not required for the USS-344.
BitsFieldRead/WriteReset/Description
31:0CardBus CIS PointerR00000000h
Table 89. Subsystem Vendor ID Register (2Ch—2Dh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem Vendor IDR/W11C1h
Table 90. Subsystem ID Register (2Eh—2Fh)
The subsystem vendor ID is R/W for compliance with Microsoft PC98 specifications. On reset, this register is read
only. System BIOS may write a 1 to Special—Subsystem Write Capability register (4Ch) bit 0 to enable write capability of this register. After configuring this register, the system BIOS must write a 0 to Special—Subsystem Write
Capability register (4Ch) bit 0 to disable write capability of this register.
BitsFieldRead/WriteReset/Description
15:0Subsystem IDR/W5803h
2626Agere Systems Inc.
Page 27
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
PCI Registers
Table 91. Expansion ROM Base Address Register (30h—33h)
Expansion ROM not supported by the USS-344.
BitsFieldRead/WriteReset/Description
31:0Expansion ROM Base
Table 92. Capabilities Pointer Register (34h)
BitsFieldRead/WriteReset/Description
7:0Cap_Ptr RTEST1 = 0b: 50h
Table 93. Interrupt Line Register (3Ch)
BitsFieldRead/WriteReset/Description
7:0Interrupt Line R/W00h
Table 94. Interrupt Pin Register (3Dh)
If TEST0 = 0b, interrupt A is used as the PCI interrupt for this core.
If TEST0 = 1b, interrupt D is used as the PCI interrupt for this core.
(continued)
R00000000h
Address
TEST1 = 1b: 00h
BitsFieldRead/WriteReset/Description
7:0Interrupt Pin RTEST0 = 0b: 01h
TEST0 = 1b: 04h
Table 95. Min_Gnt Register (3Eh)
The USS-344 can support a four DWORD master burst read or write which requires less than 500 ns.
BitsFieldRead/WriteReset/Description
7:0Min_GntR03h
Table 96. Max_Lat Register (3Fh)
The USS-344 requires service at a minimum interval of 21.3 µs.
This is a special register implemented for compliance with Microsoft PC98 Specification, Chapter 9, Item 11. Bit 0
is read/write to allow the system BIOS to enable write capability of the Subsystem Vendor ID and Subsystem ID
registers (refer to Tables 23 and 24).
Each PCI Function has one set of USB operational registers available through the memory mapped Base Address
register 0. Each set of USB operational registers represents one single-port USB host controller. Refer to Tables
99—120 for more details on each of these registers.
9Low-speed Device Attached (LSDA)0bR/WR/W
16Connect Status Change (CSC)0bR/WR/W
17Port Enable Status Change (PESC)0bR/WR/W
18Port Suspend Status Change (PSSC)0bR/WR/W
19Port Overcurrent Indicator Change (OCIC)0bR/WR/W
20Port Reset Status Change (PRSC)0bR/WR/W
(continued)
(Host Controller Driver)HC(Host Controller)
3434Agere Systems Inc.
Page 35
Advance Data Sheet, Rev. 9
June 2001
Four-Host PCI-to-USB OpenHCI Host Controller
USS-344 QuadraBus
Legacy Support Registers
The legacy support function and all registers described in this section are available on all four embedded USB host
controllers. Four operational registers are used to provide the legacy support. Each of these registers is located on
a 32-bit boundary. The offset of these registers is relative to the base address of the respective host controller core
operational registers with HceControl located at offset 100h.
Table 121. Legacy Support Registers
OffsetRegisterDescription
100hHceControl
104hHceInput
108hHceOutput
10ChHceStatus
Three of the operational registers (HceStatus, HceInput, HceOutput) are accessible at I/O address 60h and 64h
when emulation is enabled. Reads and writes to the registers using I/O addresses have side effects as outlined in
the Table 122.
Used to enable and control the emulation hardware and report various status
information.
Emulation side of the Legacy Input Buffer register.
Emulation side of the Legacy Output Buffer register where keyboard and
mouse data is to be written by software.
Emulation side of the Legacy Status register.
Table 122. Emulated Registers
I/O
Address
60hINHceOutput
60hOUTHceInput
64hINHceStatus
64hOUTHceInput
Cycle
Type
Register Contents
Accessed/Modified
Side
Effects
IN from port 60h will set OutputFull in HceStatus to 0.
OUT to port 60h will set InputFull to 1 and CmdData to 0 in
HceStatus.
IN from port 64h returns current value of HceStatus with no
other side effect.
OUT to port 64h will set InputFull to 0 and CmdData in
HceStatus to 1.
HceInput Register
Table 123. HceInput Register (104h)
BitFieldR/WDescription
7:0InputDataR/W
31:8Reserved—
I/O data that is written to ports 60h and 64h is captured in this register when emulation is enabled. This register
may be read or written directly by accessing it with its memory address in the host controller’s operational register
space. When accessed directly with a memory cycle, reads and writes of this register have no side effects.
This register holds data that is written to I/O ports 60h and 64h.
The data placed in this register by the emulation software is returned when I/O port 60h is read and emulation is
enabled. On a read of this location, the OutputFull bit in HceStatus is set to 0.
This register hosts data that is returned when an I/O read of port 60h is performed by application software.
—
HceStatus Register
Table 125. HceStatus Register (10Ch)
BitFieldR/WDescription
0OutputFullR/W
1InputFullR/W
2FlagR/W
3CmdDataR/W
4Inhibit SwitchR/W
5AuxOutputFullR/W
6Time-outR/W
7ParityR/W
31:8Reserved—
The HC sets this bit to 0 on a read of I/O port 60h. If IRQEn is set and AuxOutputFull is set to 0, then an IRQ1 is generated as long as this bit is set to 1.
If IRQEn is set and AuxOutputFull is set to 1, then an IRQ12 is generated as
long as this bit is set to 1. While this bit is 0 and CharacterPending in HceControl is set to 1, an emulation interrupt condition exists.
Except for the case of a Gate A20 sequence, this bit is set to 1 on an I/O write
to address 60h or 64h. While this bit is set to 1 and emulation is enabled, an
emulation interrupt condition exists.
Nominally used as a system flag by software to indicate a warm or cold boot.
The HC sets this bit to 0 on an I/O write to port 60h and to 1 on an I/O write to
port 64h.
This bit reflects the state of the keyboard inhibit switch and is set if the keyboard is not inhibited.
IRQ12 is asserted whenever this bit is set to 1 and OutputFull is set to 1 and
the IRQEn bit is set.
Used to indicate a time-out.
Indicates parity error on keyboard/mouse data.
—
The contents of the HceStatus register are returned on an I/O Read of port 64h when emulation is enabled. Reads
and writes of port 60h and writes to port 64h can cause changes in this register. Emulation software can directly
access this register through its memory address in the host controller’s operational register space. Accessing this
register through its memory address produces no side effects.
3636Agere Systems Inc.
Page 37
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Con-
Legacy Support Registers
(continued)
HceControl Register
Table 126. HceControl Register (100h)
BitFieldResetR/WDescription
0EmulationEnable0bR/W
1EmulationInterrupt—R
2CharacterPending0bR/W
3IRQEn0bR/W
4ExternalIRQEn0bR/W
5GateA20Sequence0bR/W
6IRQ1Active0bR/W
7IRQ12Active0bR/W
8A20State0bR/W
31:9Reserved——
When set to 1, the HC is enabled for legacy emulation. The
HC decodes accesses to I/O registers 60h and 64h and generates IRQ1 and/or IRQ12 when appropriate. Additionally,
the HC generates an emulation interrupt at appropriate times
to invoke the emulation software.
This bit is a static decode of the emulation interrupt condition.
When set, an emulation interrupt is generated when the OutputFull bit of the HceStatus register is set to 0.
When set, the HC generates IRQ1 or IRQ12 as long as the
OutputFull bit in HceStatus is set to 1. If the AuxOutputFull
bit of HceStatus is 0, then IRQ1 is generated; if it is 1, then
an IRQ12 is generated.
When set to 1, IRQ1 and IRQ12 from the keyboard controller
causes an emulation interrupt. The function controlled by this
bit is independent of the setting of the EmulationEnable bit in
this register.
Set by HC when a data value of D1h is written to I/O port
64h. Cleared by HC on write to I/O port 64h of any value
other than D1h.
Indicates that a positive transition on IRQ1 from keyboard
controller has occurred. SW may write a 1 to this bit to clear
it (set it to 0). SW write of a 0 to this bit has no effect.
Indicates that a positive transition on IRQ12 from keyboard
controller has occurred. SW may write a 1 to this bit to clear
it (set it to 0). SW write of a 0 to this bit has no effect.
Indicates current state of gate A20 on keyboard controller.
Used to compare against value written to 60h when
GateA20Sequence is active.
Must read as 0s.
Connection Instructions
Figure 6 shows a typical connection of the USS-344 to
provide four USB ports and full legacy support to a
PCI-based system. For each of the following sections,
refer to Figure 6 for guidance.
connecting the VIO signal to the signaling voltage on
the motherboard or VIO pin on the card edge of the
expansion card. The VIO pin will select the PCI
signaling level as indicated in Table 127. A 5 V reference voltage is not required for the USS-344 to be 5 V
compatible.
Table 127. PCI Signaling Levels
PCI Connection Instructions
VIO Pin Input
The USS-344 interfaces directly with any 32-bit,
33 MHz PCI bus simply by connecting all PCI related
signals directly to the signals on the host motherboard
or card edge of an expansion card. The PCI signaling
level for all PCI signals of the USS-344 is selected by
The USS-344 is a port-powered OHCI host controller
(refer to OHCI specification) requiring an external
switchable power regulator to supply downstream USB
port power controlled by the USS-344. The power
regulator interface has been designed to interface
directly with commonly used USB power regulators
with very little additional circuitry. The PRTPWR[0, 1, 2,
3] output signal is used as the switch for the power
regulator. The PRTPWR[0, 1, 2, 3] signal must be bootstrapped with a pull-up or pull-down resistor to select
the appropriate power switch polarity. Bootstrapping
with a pull-up resistor will select an active-low power
switch while bootstrapping with a pull-down will select
an active-high power switch. Figure 3 depicts a typical
board connection for both power regulator enable
polarities.
The PWRFLT[0, 1, 2, 3]N can be connected directly to
an active-low power fault regulator output to inform the
USS-344 of a USB port overcurrent condition.
DPLS[0, 1, 2, 3] and DMNS[0, 1, 2, 3] are related to the
integrated USB transceiver and are connected directly
to the USB port connector through a 28 Ω—32 Ω series
resistor for each signal. Figure 5 shows complete detail
of the USS-344 connection to USB.
CLK48 must be connected to a 48 MHz oscillator to
provide a suitable USB clock to the USS-344. If
CLK48STOP signal is used to disable the external
oscillator during D3 Power Management state,
CLK48STOP must be bootstrapped with a pull-up or
pull-down resistor to select the appropriate disable
polarity. Bootstrapping with a pull-up resistor will select
an active-low disable while bootstrapping with a pulldown will select an active-high disable. Figure 4
depicts a typical board connection for both oscillator
enable polarities. CLK48STOP must be pulled to a
stable logic value with a resistor if CLK48STOP is not
used. Figure 4 also shows the typical board connection
when CLK48STOP is not used.
Test Mode Connection Instructions
TEST[3:0] input pins present various options and test
modes for the USS-344. These pins can be connected
directly to V
(NAND tree mode) is available for a system designer to
implement. For a system designer who wishes to
implement NAND tree mode, it is recommended that a
pull-down resistor be used on TEST2 input. This will
allow an in-circuit tester to drive TEST2 high and activate NAND tree mode (see NAND Tree Mode section).
TEST3, TEST1, and TEST0 can be grounded without a
resistor.
It is also recommended that all NAND tree pins have a
corresponding PWB trace that can be driven by the incircuit tester during NAND tree mode.
Table 128. Test Mode Decodes
TEST[3:0]Description
00X0Share Interrupt A. All four controllers
00X1Individual Interrupt. Controller 0 returns
000XPower Management Interface
001XPower Management Interface
01XXNAND Test.
or ground as needed. One test mode
DD
return a 01h in the Interrupt Pin register
(3Dh) and use the PCI interrupt A pin.
01h in the Interrupt Pin register (3Dh)
and uses the PCI interrupt A pin.
Controller 1 returns 02h in the interrupt
pin register (3Dh) and uses the PCI interrupt B pin.
Controller 2 returns 03h in the Interrupt
Pin register (3Dh) and uses the PCI interrupt C pin.
Controller 3 returns 04h in the Interrupt
Pin register (3Dh) and uses the PCI interrupt D pin.
Enabled. Power management interface
enabled in all four controllers.
Disabled. Power management interface
disabled in all four controllers.
38Agere Systems Inc.
Page 39
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Connection Instructions
USS-344
Figure 3. Typical Board Connection for Both Power Regulator Enable Polarities
USS-344
PRTPWRX
CLK48STOP
(continued)
2 kΩ
2 kΩ
5 Vdc-5 Vdc
SWITCHED
REGULATOR
EN
ACTIVE-
HIGH
ENABLE
48 MHz
OSCILLATOR
EN
ACTIVE-
LOW
ENABLE
USS-344
USS-344
PRTPWRX
CLK48STOP
2 kΩ
2 kΩ
5 Vdc-5 Vdc
SWITCHED
REGULATOR
EN
ACTIVE-
LOW
ENABLE
48 MHz
OSCILLATOR
EN
ACTIVE-
HIGH
ENABLE
5-8738.r1
USS-344
CLK48STOP
2 kΩ
Figure 4. Typical Board Connection for Both Oscillator Enable Polarities or Without Oscillator
Also included in the USS-344 is the legacy PS/2 mouse and keyboard interface as defined in the OpenHCI Open
Host Controller Interface Specification for USB Release 1.0a. This legacy interface along with standard USB BIOS
drivers allows USB mice and keyboards to operate in MS-DOS* mode. Legacy support need not be implemented
by the system designer if not desired. If not implemented, A20I, MIRQ12I, and KIRQ12I must be connected to a
stable logic level. Figure 6 shows the typical legacy support connection to the USS-344. Figure 7 shows the typical
connection of the unused legacy support signals when legacy support is not desired.
CPU
SMI
A20MN
48 MHz
OSC
PCI BUS
CLK48
CLK48STOP
PCI VIO
PCI SIGNALS
32-bit, 33 MHz
PMEN
3.3 Vdc
AGERE USS-344
PCI-TO-USB
OHCI HOST
CONTROLLER
PRTPWR0
PWRFLT0N
PRTPWR1
PWRFLT1N
PRTPWR2
PWRFLT2N
PRTPWR3
PWRFLT3N
5 Vdc
5 Vdc-5 Vdc
SWITCHED
REGULATOR
5 Vdc-5 Vdc
SWITCHED
REGULATOR
5 Vdc-5 Vdc
SWITCHED
REGULATOR
5 Vdc-5 Vdc
SWITCHED
REGULATOR
VBUS = 5 Vdc
DPLS0/DMNS0
VBUS = 5 Vdc
DPLS1/DMNS1
VBUS = 5 Vdc
DPLS2/DMNS2
VBUS = 5 Vdc
DPLS3/DMNS3
USB
CONNECTOR
USB
CONNECTOR
USB
CONNECTOR
USB
CONNECTOR
8259
INTERRUPT
CONTROLLER
OPTIONAL LEGACY SUPPORT
IRQ1
IRQ12
KIRQ1I
MIRQ12I
A2OI
8042
LEGACY
DEVICE
CONTROLLER
PS/2 MOUSE
PS/2 KEYBOARD
5-7829
Figure 6. Typical Legacy Support Connection
* MS-DOS is a registered trademark of Microsoft Corporation.
4040Agere Systems Inc.
Page 41
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Legacy Configuration
48 MHz
OSC
CPU
CLK48
CLK48STOP
PCI VIO
PCI SIGNALS
32-bit, 33 MHz
PCI BUS
PMEN
(continued)
3.3 Vdc
AGERE USS-344
PCI-TO-USB
OHCI HOST CONTROLLER
5 Vdc
PRTPWR0
PWRFLT0N
PRTPWR1
PWRFLT1N
PRTPWR2
PWRFLT2N
PRTPWR3
PWRFLT3N
5 Vdc-5 Vdc
SWITCHED
REGULATOR
5 Vdc-5 Vdc
SWITCHED
REGULATOR
5 Vdc-5 Vdc
SWITCHED
REGULATOR
5 Vdc-5 Vdc
SWITCHED
REGULATOR
VBUS = 5 Vdc
DPLS0/DMNS0
VBUS = 5 Vdc
DPLS1/DMNS1
VBUS = 5 Vdc
DPLS2/DMNS2
VBUS = 5 Vdc
USB
CONNECTOR
USB
CONNECTOR
USB
CONNECTOR
USB
CONNECTOR
DPLS3/DMNS3
SMIN
A20MN
IRQ1
IRQ12
A201
KIRQ1I
MIRQ12I
2 kΩ
2 kΩ
2 kΩ
5-8740
Figure 7. Typical Connection When Not Using Legacy Support
Power Connection Recommendations
The USS-344 is a 3.3 V device. Therefore, all VDD inputs must be connected to an appropriate 3.3 V source. VDDT
provides all transceiver power and must be connected to a 3.3 V source. It is recommended that the system
designer undertake special board routing and filtering of V
induced by other components.
T and VSST to isolate these power inputs from noise
An advanced power management capabilities interface compliant with PCI Bus Power Management Interface
Specification Revision 1.1 has been incorporated into each of the USS-344 controllers. This interface allows the
USS-344 to be placed in various power management states offering a variety of power savings for a host system.
Table 129 highlights the USS-344 support for power management states and features supported for each of the
power management states. The USS-344 has the ability to internally gate-off the CLK48 input, disable the USB
transceivers, and assert USB resume signaling asynchronously (without active CLK48) in response to upstream
USB resume being detected. The USS-344 will assert PMEN and retain chip context in accordance with the rules
defined in the PCI Bus Power Management Interface Specification Revision 1.1.
Table 129. USS-344 Support for Power Management States
Power
Management
State
D0RequiredXX——XFully awake backwards com-
D1OptionalXX—XXFully awake state with PCI
D2Optional——X*XXUSB sleep state with PCI bus
hot
D3
cold
D3
State
Required/
Optional
Required—X—X*X—Deep USB sleep state with
Required—————Fully asleep backwards com-
Clk48
Active
Internally
CLK48
STOP
Active
USB
Transciever
Active
Async
Resume
Logic
Active
PMEN
Assert
Enabled
Chip
Context
Main-
tained
Comments
patible state. All logic in fullpower mode.
bus master capabilities turned
off by host. All logic in fullpower mode because of low
latency returning to D0 State.
master capabilities turned off
by host. PCI clocks may be
turned off by the system.
PCI bus master capabilities
turned off by host. PCI clocks
may be turned off by the system.
patible state. All power turned
off. Reset required to recover
to D0 state. All downstream
devices disconnected
because of power loss.
* Asynchronous resume logic active only when PME_Enable register bit is active.
A wakeup event (power management event) detected by a USB host controller is considered either an upstream
resume detected or a connect status change (device disconnecting/connecting) detected. Any of these events
detected by the USS-344 while the power management event is enabled will cause PMEN to be issued.
This power management feature is considered an extension of the PCI Specification and is only present when
enabled by the TEST1 input pin. While the TEST1 input pin is logic 0 (or ground), the power management function
is enabled, the Power Management registers and Capabilities Pointer register are accessible, and the PCI Configuration Space Status register, bit 4, will read as logic 1 (capabilities list present). While the TEST1 input pin is
logic 1, the power management function is disabled, the Power Management registers and Capabilities Pointer
register are inaccessible and read as 0h, and the PCI Configuration Space Status register, bit 4, will read as logic 0
(no capabilities list).
4242Agere Systems Inc.
Page 43
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Power Management Interface
The CLK48STOP output pin is active if all four PCI cores in the USS-344 multifunction PCI device have been
placed into the D3
while in this state. CLK48STOP is only active in D3
state-change latency to allow the external oscillator to be stopped.
PMEN is an open collector output allowing wire-OR of several PMEN signals.
The following Power Management register definitions present the specific implementation of the PCI Bus Power Management Interface Specification for the USS-344. All the following registers are located in the PCI configuration memory space of each controller in the USS-344. All further information concerning the register functions and
the system implementation of this interface should be referenced from the PCI Bus Power Management Interface Specification Revision 1.1 available from the PCI Special Interest Group.
state. This will allow the external 48 MHz oscillator to be disabled and in a low-power mode
hot
(continued)
state since this is the only low-power state with sufficient
15:1101110bRPME_Support. Specifies the states in which the PME signal can be asserted.
101bRD2_Support. This device supports the D2 power management state.
91b RD1_Support. This device supports the D1 power management state.
8:6000bRAux_Current. PMEN generation is not supported by this function. Therefore,
50b RDSI. No device specific initialization sequence is required before using this
40b RReserved.
30b RPME Clock. No clocks are required for this device to issue PMEN.
2:0010bRVersion. PCI Power Management Interface Specification Revision 1.1 compli-
Read/
Write
Name/Description
XXXX0b—PME cannot be asserted in D0 state.
XXX1Xb—PME can be asserted in D1 state.
XX1XXb—PME can be asserted in D2 state.
X1XXXb—PME can be asserted in D3
0XXXXb—PME cannot be asserted in D3
this register is not applicable and returns 000b.
device.
ant.
hot
state.
state.
cold
Configuration Space Offset 54h
Table 133. Power Management Control/Status Register
BitsDefault
Value
150bRead/
14:13See
Table 136
12:90000bR/WData_Select. The system uses this register to select the appropriate data for
80bR/WPME_En. When active (1b), the function is enabled to assert PMEN.
7:2000000bRReserved.
1:000bR/WPower_State. Represents the current power state of the function.
Read/
Write
PME_Status. This bit is set when the function would normally assert the
Write-
Clear
RData Scale. Variable based upon data select. See Table 136.
PMEN signal independent of the state of the PME_En bit.
Writing a 1b to this bit will clear the PME_Status bit and force the function to
stop asserting PMEN.
reporting in the Data Scale register and Data register.
Name/Description
4444Agere Systems Inc.
Page 45
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Power Management Interface
(continued)
Configuration Space Offset 56h
Table 134. Power Management Bridge Support Extensions
BitsDefault
Value
70b RBPCC_En (Bus Power/Clock Control Enable). This is not a PCI bridge func-
60b RB2_B3# (B2/B3 Support for D3
5:0000000bRReserved.
Read/
Write
tion.
Name/Description
). This is not a PCI bridge function.
hot
Configuration Space Offset 57h
Table 135. Data Register
BitsDefault
Value
7:0See
Table 136
Read/
Write
RRepresents the amount of power dissipated or consumed in various power
management states. Variable based upon data select. See Table 136.
Description
Power Consumption/Dissipation Reporting
Table 136. Power Consumption/Dissipation Reporting
Value In Data
Select
0000bD0 Power Consumed1Fh01bmW * 100
0001bD1 Power Consumed38h10bmW * 100
0010bD2 Power Consumed66h11bmW
0011bD3 Power Consumed07h11bmW
0100bD0 Power Dissipated37h10bmW * 10
0101bD1 Power Dissipated37h10bmW * 10
0110bD2 Power Dissipated64h11bmW
0111bD3 Power Dissipated03h11bmW
1000b—1111bReserved (single-function
PCI device configuration)
Data ReportedDataData ScaleUnits (Interpreting Data
The USS-344 can be placed in a NAND tree mode of operation for board-level production testing. The NAND tree
is designed to allow board-level contact testing of inputs and bidirectional pins of the USS-344.
To activate the NAND tree in the USS-344, force pin 63 (TEST2) to a logic high and force pin 64 (TEST3) to a logic
low. Pins 62 and 61 (TEST1 and TEST0) may be high or low. No clocks are required. When this is performed, the
NAND tree will be active and follow the order of the map presented in Table 137. Figure 8 shows the NAND tree
logic structure. The test mode connection instructions should be followed to place the USS-344 in NAND tree
mode.
The clock waveform must be delivered to each PCI component in the system. In the case of expansion boards,
compliance with the clock specification is measured at the expansion board component, not at the connector slot.
Figure 9 shows the clock waveform and required measurement points for both 5 V and 3.3 V signaling environments. Table 140 summarizes the clock specifications.
1. In general, all PCI components must work with any clock frequency between nominal dc and 33 MHz. Device operational parameters at
frequencies under 16 MHz may be guaranteed by design rather than by testing. The clock frequency may be changed at any time during the
operation of the system, as long as the clock edges remain clean (monotonic), and the minimum cycle and high and low times are not
violated. The clock may only be stopped in a low state. A variance on this specification is allowed for components designed for use on the
system motherboard only. These components may operate at any single fixed frequency up to 33 MHz and may enforce a policy of no
frequency changes.
2. Rise and fall times are specified in terms of the edge rate measured in V/ns. This slew rate must be met across the minimum peak-to-peak
portion of the clock waveform, as shown in Figure 9.
3. The minimum RSTN slew rate applies only to the rising (deassertion) edge of the reset signal and ensures that system noise cannot render
an otherwise monotonic signal to appear to bounce in the switching range.
1
2
3
30∞ns
14V/ns
50—mV/ns
5050Agere Systems Inc.
Page 51
Advance Data Sheet, Rev. 9
June 2001
USS-344 QuadraBus
Four-Host PCI-to-USB OpenHCI Host Controller
Electrical Characteristics
Tab le 141
. 5 V and 3.3 V PCI Timing Parameters
(continued)
SymbolParameterMinMaxUnit
t
VAL
t
VAL(ptp)
t
ON
t
OFF
t
SU
t
SU(ptp)
t
H
t
RST
t
RST-CLK
t
RST-OFF
t
RRSU
t
RRH
1. See the timing measurement conditions in Figure 4-8 of PCI Specification Revision 2.1.
2. For parts compliant to the 5 V signaling environment:
Minimum times are evaluated with 0 pF equivalent load; maximum times are evaluated with 50 pF equivalent load. Actual test capacitance
may vary, but results should be correlated to these specifications. Note that faster buffers may exhibit some ring back when attached to a
50 pF lump load, which should be of no consequence as long as the output buffers are in full compliance with slew rate and V/I curve specifications.
For parts compliant to the 3.3 V signaling environment:
Minimum times are evaluated with same load used for slew rate measurement (see PCI Specification, Rev. 2.1s); maximum times are evaluated with the following load circuits, for high-going and low-going edges, respectively.
CLK to Signal Valid Delay—Bused Signals
CLK to Signal Valid Delay—Point to Point
Float to Active Delay
Active to Float Delay
1, 7
1, 7
Input Setup Time to CLK—Bused Signals
Input Setup Time to CLK—Point to Point
Input Hold Time from CLK
4
Reset Active Time After Power Stable
Reset Active Time After CLK Stable
Reset Active to Output Float Delay
5, 6, 7
REQN to RSTN Setup Time10 × t
RSTN to REQN Hold Time050ns
VAL
(MAX) RISING EDGE
T
1, 2, 3
1, 2, 3
211ns
212ns
2—ns
—28ns
3, 4
3, 4
7—ns
10, 12—ns
0—ns
5
5
1—ns
100—ns
—40ns
—ns
T
VAL
(MAX) FALLING EDGE
CYC
PIN
OUTPUT
BUFFER
3. REQN and GNTN are point-to-point signals and have different output valid delay and input setup times than bused signals. GNTN has a
setup time of 10 ns; REQN has a setup time of 12 ns. All other signals are bused.
4. See the timing measurement conditions in Figure 4-8 of PCI Specification Revision 2.1.
5. RSTN is asserted and deasserted asynchronously with respect to CLK.
6. All output drivers must be asynchronously floated when RSTN is active.
7. For purposes of active/float timing measurements, the Hi-Z or off state is defined to be when the total current delivered through the compo-
nent pin is less than or equal to the leakage current specification.
For additional information, contact your Agere Systems Account Manager or the following:
INTERNET:http://www.agere.com
E-MAIL:docmaster@micro.lucent.com
N. AMERICA: Agere Systems Inc., 555 Union Boulevard, Room 30L-15P-BA, Allentown, PA 18109-3286
ASIA PACIFIC: Agere Systems Singapore Pte. Ltd., 77 Science Park Drive, #03-18 Cintech III, Singapore 118256
CHINA:Agere Systems (Shanghai) Co., Ltd., 33/F Jin Mao Tower, 88 Century Boulevard Pudong, Shanghai 200121 PRC
JAPAN:Agere Systems Japan Ltd., 7-18, Higashi-Gotanda 2-chome, Shinagawa-ku, Tokyo 141, Japan
Agere Systems Inc. reserves the right to make changes to the product(s) or information contained herein without notice. No liability is assumed as a result of their use or application.
QuadraBus is a trademark of Agere Systems Inc.