CY7C656XX Datasheet, PDF (11/24 Pages) Cypress Semiconductor – EZ-USB HX2LP™ Low-Power USB 2.0 Hub Controller Family

CY7C656xx
Byte
3,4
5
6
7
8
All Speed
0x0089^[6]
0x32^[6]
0x28^[6]
0xAE^[6]
0x00^[6]
0xFF^[6]
Field Name
wHubCharacteristics
bPwrOn2PwrGood
bHubContrCurrent
bDeviceRemovable
bPortPwrCtrlMask
Description
b1, b0: Logical Power Switching Mode
00: Ganged power switching (all ports’ power at once)
01: Individual port power switching (Default in CY7C656xx)
b2: Identifies a Compound Device,
0: Hub is not part of a compound device (Default in CY7C656xx),
1: Hub is part of a compound device.
b4, b3: Overcurrent Protection Mode
00: Global Overcurrent Protection. The hub reports overcurrent as a
summation of all ports’ current draw, without a breakdown of individual port
overcurrent status.
01: Individual Port Overcurrent Protection. The hub reports overcurrent on a
per-port basis. Each port has an over-current status (Default in CY7C656xx).
1X: No Overcurrent Protection. This option is allowed only for bus-powered
hubs that do not implement overcurrent protection.
b6, b5: TT Think Time
00: TT requires at most eight FS bit times of inter transaction gap on a
full-/low-speed downstream bus (Default in CY7C656xx).
b7: Port Indicators Supported,
0: Port Indicators are not supported on its downstream facing ports and the
SetPortIndicator request has no effect.
1: Port Indicators are supported on its downstream facing ports and the
SetPortIndicator request controls the indicators. See the Functional Overview
Section and the Supported USB Requests Section. (Default in CY7C656xx).
b15,. b8: Reserved
Time from when the port is powered to when the power is good on that port
Maximum current requirement for the Hub Controller at full speed.
Maximum current requirement for the Hub Controller at high speed.
Indicates if the logical port has a removable device attached (0 = removable,
1 = non-removable)
Required for compatibility with software written for 1.0 compliant devices
Configuration Options
Systems using CY7C656xx may have the option of using a
fuse ROM which is preset at the factory to configure the hub,
otherwise it must have an external EEPROM in order for the
device to have a unique VID, PID, and DID. The CY7C656xx
can communicate with SPI EEPROM that are either double
byte addressed or single byte with the 9th bit within the
instruction byte, such as the 24LC040 parts use. The 25LC080
EEPROM uses the double byte address format, and therefore
the CY7C656xx can communicate with these parts. The '010s
and '020s use the same command format as is used to
interface with the ‘040 and hence these can also be used to
interface with the CY7C656xx.
If the attached EEPROM is blank (0xFF) the hub enumerates
as a vendor class device. In this configuration the hub
connects to the Cypress driver to allow programming of the
EEPROM. Once the EEPROM is programmed a power cycle
configures the chip as a hub class device.
0xD0 Load
With this EEPROM format, only a unique VID, PID, and DID
must be present in the external SPI EEPROM. The contents
of the EEPROM must contain this information in the following
format:
Byte
0
1
2
3
4
5
6
Value
0xD0
VID (LSB)
VID (MSB)
PID (LSB)
PID (MSB)
reserved
DID (MSB)
Document #: 38-08037 Rev. *H
Page 11 of 24
[+] Feedback