CY7C65640A-LFXC Cypress Semiconductor Corp, CY7C65640A-LFXC Datasheet - Page 11

• Manufacturer Part Number: CY7C65640A-LFXC
• Description: IC USB HUB CONTROLLER HS 56VQFN
• Manufacturer: Cypress Semiconductor Corp
• Series: TetraHub™r

Specifications of CY7C65640A-LFXC

• Controller Type: USB Hub
• Interface: SPI Serial
• Voltage - Supply: 3.15 V ~ 3.45 V
• Operating Temperature: 0°C ~ 70°C
• Mounting Type: Surface Mount
• Package / Case: 56-VQFN Exposed Pad, 56-HVQFN, 56-SQFN, 56-DHVQFN
• Current - Supply: 260mA
• Operating Supply Voltage (typ): 3.3V
• Operating Supply Voltage (min): 3.15V
• Operating Supply Voltage (max): 3.45V
• Operating Temp Range: 0C to 70C
• Operating Temperature Classification: Commercial
• Mounting: Surface Mount
• Pin Count: 56
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• For Use With: CY4602 - KIT USB 4-PORT HUB REF DESIGN
• Lead Free Status / RoHS Status: Compliant, Lead free / RoHS Compliant
• Other names: 428-1805; CY7C65640A-LFXC

Configuration Options
Systems using TetraHub must have an external EEPROM in
order for the device to have a unique VID, PID, and DID. The
TetraHub can talk to SPI EEPROM that are double byte addres-
sable only. TetraHub uses the command format from the '040
parts. The TetraHub cannot talk to ‘080 EEPROM parts, as the
read command format used for talking to ‘080 is not the same as
‘040. The '010s and '020s uses the same command format as
used to interface with the ‘040 and hence these can also be used
to interface with the TetraHub.
Default – 0xD0 Load
When used in default mode, 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:
Configured – 0xD2 Load
Document #: 38-08019 Rev. *J
Byte
10
12
11
0
1
2
3
4
5
6
7
8
9
0xD2
VID (LSB)
VID (MSB)
PID (LSB)
PID (MSB)
DID (LSB)
DID (MSB)
EnableOverCurrentTimer[3:0], DisableOvercurrent-
Timer[3:0]
ActivePorts[3:0], RemovablePorts[3:0]
MaxPower
HubControllerPower
PowerOnTimer
IllegalHubDescriptor, Unused, FullspeedOnly,
NoPortIndicators, Reserved, GangPowered, SingleT-
TOnly, NoEOPatEOF1
Byte
0
1
2
3
4
5
6
Value (MSB->LSB)
DID (MSB)
VID (MSB)
PID (MSB)
DID (LSB)
VID (LSB)
PID (LSB)
Value
0xD0
Byte 0: 0xD2
Byte 1: VID (LSB)
Byte 2: VID (MSB)
Byte 3: PID (LSB)
Byte 4: PID (MSB)]
Byte 5: DID (LSB)
Byte 6: DID (MSB)]
Byte 7: EnableOvercurrentTimer[3:0], DisabledOvercurrent-
Timer[3:0]
Byte 8: ActivePorts[3:0], RemovablePorts[3:0]
Byte 9: MaximumPower
Byte 10: HubControllerPower
Byte 11: PowerOnTimer
Byte 12: IllegalHubDescriptor, Unused, FullspeedOnly,
NoPortIndicators, Reserved, GangPowered, SingleTTOnly,
NoEOPatEOF1
Count time in ms for filtering overcurrent detection. Bits 7–4
are for an enabled port, and bits 3–0 are for a disabled port.
Both range from 0 ms to 15 ms. See section . Default: 8 ms =
0x88.
Bits 7–4 are the ActivePorts[3:0] bits that indicates if the cor-
responding port is usable. For example, a two-port hub that
uses ports 1 and 4 would set this field to 0x09. The total num-
ber of ports reported in the Hub Descriptor: bNbrPorts field is
calculated from this. Bits 3–0 are the RemovablePorts[3:0]
bits that indicates whether the corresponding port is remov-
able (set to HIGH). This bit’s values are recorded appropriate-
ly in the HubDescriptor:DeviceRemovable field. Default:
0xFF.
This value is reported in the ConfigurationDescriptor:bMax-
Power field and is the current in 2-mA intervals that is required
from the upstream hub. Default: 0x32 = 100 mA
This value is reported in the HubDescriptor:bHubContrCur-
rent field and is the current in milliamperes required by the
hub controller. Default: 0x64 = 100 mA.
This
tor:bPwrOn2PwrGood field and is the time in 2-ms intervals
from the SetPortPower command until the power on the cor-
responding downstream port is good. Default: 0x32 = 100 ms.
Bit 7: IllegalHubDescriptor: For GetHubDescriptor request,
some USB hosts use a DescriptorTypeof 0x00 instead of
HUB_DESCRIPTOR, 0x29. According to the USB 2.0 stan-
dard, a hub must treat this as a Request Error, and STALL the
transaction accordingly (USB 2.0, 11.24.2.5). For systems
that do not accept this, the IllegalHubDescriptor configuration
bit may be set to allow TetraHub to accept a DescriptorType
Needs to be programmed with 0xD2
Least Significant Byte of Vendor ID
Most Significant Byte of Vendor ID
Least Significant Byte of Product ID
Most Significant Byte of Product ID
Least Significant Byte of Device ID
Most Significant Byte of Device ID
value
is
reported
in
CY7C65640A
the
Page 11 of 23
HubDescrip-
[+] Feedback