View CY7C65620-56LFXC_1338881.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

ez-usb hx2lp? low-power usb 2.0 hub controller family cy7c656xx cypress semiconductor corporation ? 198 champion court ? san jose , ca 95134-1709 ? 408-943-2600 document #: 38-08037 rev. *h revised may 3, 2007 features ? usb 2.0 hub controller ? automotive aec grade option (?40 - 85c) ? compliant with the usb 2.0 specification ? usb-if certified: tid# 30000009 ? windows hardware quality lab (whql) - compliant ? up to four downstream ports supported ? supports bus powered and self powered modes ? single transaction translator (tt) ? bus power configurations ? fit/form/function compatible with cy7c65640 and cy7c65640a (tetrahub?) ? space saving 56-pin qfn ? single power supply requirement ? internal regulator for reduced cost ? integrated upstream pull up resistor ? integrated pull down resist ors for all downstream ports ? integrated upstream and down stream termination resistors ? integrated port status indicator control ? 24 mhz external crystal (integrated pll) ? in-system eeprom programming ? configurable with external spi eeprom: ? vendor id, product id, device id (vid/pid/did) ? number of active ports ? number of removable ports ? maximum power setting for high-speed and full-speed ? hub controller power setting ? power on timer ? overcurrent detection mode ? enabled/disabled overcurrent timer ? overcurrent pin polarity ? indicator pin polarity ? compound device ? enable full-speed only ? disable port indicators ? ganged power switching ? self and bus powered compatibility ? fully configurable string descriptors for multiple language support routing logic hub repeater usb upstream port usb 2.0 phy pll serial interface engine high-speed usb control logic spi communication block usb downstream port 1 usb 2.0 phy port power control port status usb downstream port 2 usb 2.0 phy port power control port status usb downstream port 3 usb 2.0 phy port power control port status usb downstream port 4 usb 2.0 phy port power control port status spi_sck spi_cs spi_sd d+ d- pwr#[4] ovr#[4] led d+ d- pwr#[3] ovr#[3] led d+ d- pwr#[2] ovr#[2] led d+ d- pwr#[1] ovr#[1] led transaction translator tt ram d+ d - 24 mhz crystal block diagram cy7c65630 [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 2 of 24 introduction ez-usb hx2lp? is cypress? next generation family of high performance, low power usb 2.0 hub controllers. hx2lp is an ultra low power single chip usb 2.0 hub controller with integrated upstream and downstream transceivers, a usb serial interface engine (sie), usb hub control and repeater logic, and transaction translator (tt) logic. cypress has also integrated many of t he external passive components, such as pull up and pull down resistors, reducing the overall bill of materials required to implement a hub design. the hx2lp portfolio consists of: 1. cy7c65630: 4-port/single transaction translator this device option is for ultra low power applications that require four downstream ports. all four ports share a single transaction translator. the cy7c65630 is available in a 56 qfn and is also pin-for-pin compatible with the cy7c65640. 2. cy7c65620: this device option is for a 2-port bus powered application. both ports share a single transaction translator. the cy7c65620 is available in a 56 qfn. all device options are supported by cypress? world class reference design kits, which include board schematics, bill of materials, gerber files, orcad files, and thorough design documentation. usb serial interface engine the serial interface engine (sie) allows the cy7c656xx to communicate with the usb host. the sie handles the following usb activity independently of the hub control block. ? bit stuffing/unstuffing ? checksum generation/checking ? token type identification ? address checking. routing logic hub repeater usb upstream port usb 2.0 phy pll serial interface engine high-speed usb control logic spi communication block usb downstream port 1 usb 2.0 phy port power control port status usb downstream port 2 usb 2.0 phy port power control port status usb downstream port 3 usb 2.0 phy port power control port status usb downstream port 4 usb 2.0 phy port power control port status spi_sck spi_cs spi_sd d+ d- pwr#[4] ovr#[4] led d+ d- pwr#[3] ovr#[3] led d+ d- pwr#[2] ovr#[2] led d+ d- pwr#[1] ovr#[1] led transaction translator (x1) tt ram d+ d - 24 mhz crystal block diagram cy7c65620 [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 3 of 24 hub repeater the hub repeater manages the connectivity between upstream and downstream facing ports that are operating at the same speed. it supports full-/low-speed connectivity and high-speed connectivity. according to the usb 2.0 specifi- cation, the hub repeater provides the following functions: ? sets up and tears down connectivity on packet boundaries ? ensures orderly entry into and out of the suspend state, including proper handling of remote wakeups. transaction translator the transaction translator (tt) basically translates data from one speed to another. a tt takes high-speed split transactions and translates them to full-/low-speed transactions when the hub is operating at high speed (t he upstream port is connected to a high-speed host controller) and has full-/low-speed devices attached. the operatin g speed of a device attached on a downstream facing port de termines whether the routing logic connects a port to the transaction translator or hub repeater. if a full-/low-speed device is connected to the hub operating at high speed, the data transfer route includes the transaction translator. if a high-speed device is connected to this high-speed hub, the route only includes the repeater and no transaction translator since the device and the hub are operating at the same speed. when the hub is operating at full speed (the upstream port is connected to a full-speed host controller), a high-speed peripheral does not operate at its full capability. these devices only work at full speed. full- and low-speed devices connected to this hub operate at their normal speed. applications typical applications for the hx2lp device family are: ? standalone hubs ? motherboard hubs ? monitor hubs ? advanced port replicators ? docking stations ? split-pc designs ? external personal storage drives ? keyboard hubs functional overview the cypress cy7c656xx usb 2.0 hubs are high perfor- mance, low system cost solu tions for usb. the cy7c656xx usb 2.0 hubs integrate 1.5 k upstream pull up resistors for full-speed operation and all downstream 15 k pull down resistors as well as series termination resistors on all upstream and downstream d+ and d? pins. this results in optimization of system costs by providing built-in support for the usb 2.0 specification. system initialization on power up, the cy7c656xx re ads an external spi eeprom for configuration information. at the most basic level, this eeprom has the vendor id (vid), product id (pid), and device id (did) for the customer's application. for more specialized applications, other configuration options can be specified. see ?configuration options? on page 11 for more details. after reading the eeprom, if vbuspower (connected to up-stream v bus ) is high, cy7c656xx enables the pull up resistor on d+ to indicate its presence to the upstream hub, after which a usb bus reset is expected. during this reset, cy7c656xx initiates a chirp to indicate that it is a high-speed peripheral. in a usb 2.0 system, the upstream hub responds with a chirp sequence, and cy7c656xx is in a high-speed mode, with the upstream d+ pu ll up resistor turned off. in usb 1.x systems, no such chirp sequence from the upstream hub is seen, and cy7c656xx operates as a normal 1.x hub (operating at full speed). enumeration after a usb bus reset, cy7c656xx is in an unaddressed, unconfigured state (configuration value set to ?0?). during the enumeration process, the host sets the hub's address and configuration. once the hub is configured, the full hub functionality is available. downstream ports the cy7c656xx supports a maximum of four downstream ports, each of which may be marked as usable or removable in the extended configuration (0xd2 eeprom load or 0xd4 eeprom load, see ?configuration options? on page 11 . downstream d+ and d? pull do wn resistors are incorporated in cy7c656xx for each port. before the hubs are configured, the ports are driven se0 (single ended zero, where both d+ and d? are driven low) and are set to the unpowered state. once the hub is configured, t he ports are not driven, and the host may power the ports by sending a setportpower command for each port. after a port is powered, any connect or disconnect event is detected by the hub. any change in the port state is reported by the h ubs back to the host through the status change endpoint (endpoint 1). upon receipt of setportreset request for a port with a device connected, the hub does as follows: ? performs a usb reset on the corresponding port ? puts the port in an enabled state ? enables the green port indicator for that port (if not previ- ously overridden by the host) ? enables babble detection once the port is enabled. babble consists of a non-idle condition on the port after eof2. if babble is detected on an enabled port, that port is disabled. a clearportenable request from the host also disables the specified port. downstream ports can be individually suspended by the host with the setportsuspend request. if the hub is not suspended, a remote wakeup event on that port is reflected to the host through a port change indication in the hub status change endpoint. if the hub is suspended, a remote wakeup event on [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 4 of 24 this port is forwarded to the host. the host may resume the port by sending a clearportsuspend command. upstream port the upstream port includes the transmitter and the receiver state machine. the transmitter and receiver operate in high speed and full speed depending on the current hub configu- ration. the transmitter state machine monitors the upstream facing port while the hub repeater has connectivity in the upstream direction. this machine prevents babble and disconnect events on the downstream facing ports of this hub from propa- gating and causing the hub to be disabled or disconnected by the hub to which it is attached. power switching the cy7c656xx includes interface signals for external port power switches. both ganged and individual (per-port) config- urations are supported, with individual switching being the default. initially all ports are unpowered. after enumerating, the host may power each port by sending a setportpower request for that port. the power switching and over-current detection of downstream ports is managed by control pins connected to an external power switch device. pwr [n]# output pins of the cy7c656xx series are connected to the respective external power switch's port power enable signals. (note that each port power out put pin of the external power switch must be bypassed with an electrolytic or tantalum capacitor as required by the usb specification. these capac- itors supply the inrush currents, which occur during downstream device hot-attach event s.) the polarity of this pin can be configured thr ough the eeprom; see ?0xd4 load? on page 13 . overcurrent detection overcurrent detection includes 8 ms of timed filtering by default. this parameter is configured from the external eeprom in a range of 0 ms to 15 ms for both enabled ports and disabled ports individually. detection of over-current on downstream ports is managed by control pins connected to an external power switch device. the ovr[n]# pins of the cy7c 656xx series are connected to the respective external power switch's port over-current indication (output) signals. up on detecting an over-current condition, the hub reports the overcurrent condition to the host and disables the pwr# output to the external power device. the polarity of the ovr pins can be configured through the eeprom; see ?0xd4 load? on page 13 . port indicators the usb 2.0 port indicators are also supported directly by the cy7c656xx. in accordance wit h the specification, each downstream port of the hub optionally supports a status indicator. the presence of indicators for downstream facing ports is specified by bit 7 of the whubcharacteristics field of the hub class descriptor. the default cy7c656xx descriptor specifies that port indicators are supported (whubcharacter- istics, bit 7 is set). if port indicators are not included in the hub, disable this bit thro ugh eeprom settings. each port indicator pin is strate gically located directly on the opposite edge of the port with which it is associated. a port indicator provides two colors: green and amber. this is usually implemented as two separate leds, one amber and the other green. a combination of hardware and software control is used to inform the user of the current status of the port or the device attached to the port and to guide the user through problem resolution. colors and blinking provide information to the user. the significance of the color of the led depends on the opera- tional mode of the cy7c656xx. there are two modes of operation for the cy7c656xx port indicators: automatic and manual. on power up the cy7c656xx defaults to automatic mode, where the color of the port indicator (green, amber, off) indicates the functional stat us of the cy7c656xx port. in automatic mode, the cy7c656xx turns on the green led whenever the port is enabled and the amber led when an overcurrent condition is detec ted. the color of the port indicator is set by the port state machine. blinking of the leds is not supported in automatic mode. ta b l e 1 identifies the mapping of color to port state in automatic mode. table 1. automatic port state to port indicator color mapping downstream facing hub port state powered off disconnected, disabled, not configured, resetting, testing enabled, transmit, or transmitr suspended, resuming, sendeor, restart_e/s off or amber, if due to an overcurrent condition off green off [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 5 of 24 the led control lines can also be modulated with a square wave for power conservation. the polarity of these pins is programmable, see ?0xd4 load? on page 13 . in manual mode, the indicators are under the control of the host, which can turn on the leds, or leave them off. this is done by a usb hub class request. blinking of the leds is supported in manual mode. the port indicators allow the user to intervene in any error detection. for example, when babble is detected while plugging in a defective device, or when an overcurrent condition occurs, the port indicators corre- sponding to the downstream port blink green or only light the amber led, respectively. ta b l e 2 displays the color definition of the indicators when cy7c656xx is in manual mode. [1] table 2. port indicator color definitions in manual mode color definition port state off not operational amber error condition green fully operational blinking off/green software attention blinking off/amber hardware attention blinking green/amber reserved note 1. information presented in tab l e 1 and table 2 is from usb 2.0 specification t ables 11-6 and 11-7, respectively. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 6 of 24 pin configuration figure 1. 56-pin quad flat pack no leads (8 mm x 8 mm) [2] vcc selfpwr vcc gnd gnd gnd vbuspower green#[1] amber#[1] green#[2] amber#[2] green#[3]/nc amber#[3]/nc amber#[4]/nc green#[4]/nc 1 2 3 4 5 6 7 8 9 54 55 56 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 dd?[4]/nc dd+[4]/nc vcc gnd dd?[3]/nc dd+[3]/nc vcc gnd dd?[2] dd+[2] vcc gnd dd?[1] dd+[1] vcc vcc vcc vcc vcc gnd gnd gnd gnd gnd gnd d? d+ xin xout spi_cs pwr#[1] ovr#[1] pwr#[2] ovr#[2] reset spi_sck spi_sd pwr#[3]/nc ovr#[3]/rsvd pwr#[4]/nc ovr#[4]/rsvd note 2. nc and rsvd are for cy7c65620 only. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 7 of 24 pin description table table 3. pin assignments [3] pin cy7c65630 name cy7c65620 name type default description 3 vcc vcc power n/a v cc . this signal provides power to the chip. 7 vcc vcc power n/a v cc . this signal provides power to the chip. 11 vcc vcc power n/a v cc . this signal provides power to the chip. 15 vcc vcc power n/a v cc . this signal provides power to the chip. 19 vcc vcc power n/a v cc . this signal provides power to the chip. 23 vcc vcc power n/a v cc . this signal provides power to the chip. 27 vcc vcc power n/a v cc . this signal provides power to the chip. 33 vcc vcc power n/a v cc . this signal provides power to the chip. 39 vcc vcc power n/a v cc . this signal provides power to the chip. 55 vcc vcc power n/a v cc . this signal provides power to the chip. 4 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 8 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 12 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 16 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 20 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 24 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 28 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 34 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 40 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 47 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 50 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 56 gnd gnd power n/a gnd. connect to ground with as short a path as possible. 21 xin xin input n/a 24-mhz crystal in or external clock input. 22 xout xout output n/a 24-mhz crystal out. (nc if external clock is used) 46 reset# reset# input n/a active low reset. this pin resets the entire chip. it is normally tied to v cc through a 100k resistor, and to gnd through a 0.1-f capacitor. other than this, no other special power up procedure is required. 45 selfpwr selfpwr input n/a self power. indicator for bus or self powered. 0 is bus powered, 1 is self powered. 26 vbuspower vbuspower input n/a vbus. connect to the vbus pin of the upstream connector. this signal indicates to the hub t hat it is in a connected state, and may enable the d+ pull up resistor to indicate a connection. (the hub does so after the external eeprom is read). spi interface 25 spi_cs spi_cs output o spi chip select. connect to cs pin of the eeprom. 48 spi_sck spi_sck output o spi clock. connect to eeprom sck pin. 49 spi_sd spi_sd i/o/z z spi dataline connect to gnd with 15-k resistor and to the data i/o pin of the eeprom. note 3. unused port dd+/dd? lines can be left floating. leave the port power, amber, and green led pins unconnected, and deassert the overcurrent pin. do not leave the overcurrent pin floating; it is an input. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 8 of 24 upstream port 17 d? d? i/o/z z upstream d? signal. 18 d+ d+ i/o/z z upstream d+ signal. downstream port 1 13 dd?[1] dd?[1] i/o/z z downstream d? signal. 14 dd+[1] dd+[1] i/o/z z downstream d+ signal. 36 amber#[1] amber#[1] output 1 led. driver output for amber led. port indicator support. default is active low. polari ty is controlled through eeprom. 35 green#[1] green#[1] output 1 led. driver output for green led. port indicator support. default is active low. polari ty is controlled through eeprom. 30 ovr#[1] ovr#[1] input 1 overcurrent condition detection input. default is active low. polarity is controlled through eeprom. 29 pwr#[1] pwr#[1] o/z z power switch driver output. default is active low. polarity is controlled through eeprom. downstream port 2 9 dd?[2] dd?[2] i/o/z z downstream d? signal. 10 dd+[2] dd+[2] i/o/z z downstream d+ signal. 38 amber#[2] amber#[2] output 1 led. driver output for amber led. port indicator support. default is active low. polari ty is controlled through eeprom. 37 green#[2] green#[2] output 1 led. driver output for green led. port indicator support. default is active low. polari ty is controlled through eeprom. 32 ovr#[2] ovr#[2] input 1 overcurrent condition detection input. default is active low. polarity is controlled through eeprom. 31 pwr#[2] pwr#[2] o/z z power switch driver output. default is active low. polarity is controlled through eeprom. downstream port 3 5 dd?[3] nc i/o/z z downstream d? signal. 6 dd+[3] nc i/o/z z downstream d+ signal. 42 amber#[3] nc output 1 led. driver output for amber led. port indicator support. default is active low. polari ty is controlled through eeprom. 41 green#[3] nc output 1 led. driver output for green led. port indicator support. default is active lo w. polarity is cont rolled through eeprom. 53 ovr#[3] reserved input 1 overcurrent condition detection input. default is active low. polarity is controlled through eeprom. reserved. pull to deasserted state with external resistor (cy7c65620 only) 54 pwr#[3] nc o/z z power switch driver output. default is active low. polarity is controlled through eeprom. downstream port 4 1 dd?[4] nc i/o/z z downstream d? signal. 2 dd+[4] nc i/o/z z downstream d+ signal. 44 amber#[4] nc output 1 led. driver output for amber led. port indicator support. default is active lo w. polarity is cont rolled through eeprom. 43 green#[4] nc output 1 led. driver output for green led. port indicator support. default is active lo w. polarity is cont rolled through eeprom. table 3. pin assignments [3] (continued) pin cy7c65630 name cy7c65620 name type default description [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 9 of 24 default descriptors this section presents the different descriptors that are available. there is a table for each that lists the functionality of each descriptor. device descriptor the standard device descriptor for cy7c656xx is based on the information found in the spi eeprom. the information in the eeprom overrides the def ault descriptor values. if no eeprom is used, the cy7c656xx enumerates with the default descriptor values as shown below. if a blank eeprom is connected, the hub enumerates as vendor defined class instead of a hub class. this is for the purpose of programming the eeprom with the cypress driver. configuration descriptor 51 ovr#[4] reserved input 1 overcurrent condition detection input. default is active low. polarity is controlled through eeprom. reserved. pull to deasserted state with external resistor (cy7c65620 only) 52 pwr#[4] nc o/z z power switch driver output. default is active low. polarity is controlled through eeprom. table 3. pin assignments [3] (continued) pin cy7c65630 name cy7c65620 name type default description byte full-speed high-speed field name description 0 0x12 0x12 blength 18 bytes 1 0x01 0x01 bdescriptortype device_descriptor 2,3 0x0110 0x0200 bcdusb usb specification 2.0 (1.1 if forced fs) 4 0x09 0x09 bdeviceclass hub 5 0x00 0x00 bdevicesubclass none 6 0x00 0x01 bdeviceprotocol none 7 0x40 0x40 bmaxpacketsize0 64 bytes 8,9 0x04b4 0x04b4 widvendor vid (overridden by what is defined in eeprom) 10,11 0x6560 0x6560 widproduct pid (overridden by what is defined in eeprom) 12, 13 0x0915 0x0915 wbcddevice did (overridden by what is defined in eeprom) 14 0x00 0x00 imanufacturer overridden by eeprom 15 0x00 0x00 iproduct overridden by eeprom 16 0x00 0x00 iserialnumber overridden by eeprom 17 0x01 0x01 bnumconfigurations one configuration supported byte full-speed high-speed field name description 0 0x09 0x09 blength 9 bytes 1 0x02 [4] /0x07 [5] 0x02 [4] /0x07 [5] bdescriptortype config_descriptor 2 0x0019 0x0019 wtotallength length of all other descriptors 4 0x01 0x01 bnuminterfaces 1 5 0x01 0x01 bconfigurationvalue the configuration to use 6 0x00 0x00 iconfiguration 7 0xa0 0xe0 0xa0 0xe0 bmattributes value depends on pin 45 - selfpwr signal selfpwr = 0 yields 0xa0 and =1 yields 0xe0 8 0x28 0x57 [4] bmaxpower notes 4. configured speed descriptor. 5. other speed descriptor. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 10 of 24 interface descriptor endpoint descriptor device qualifier descriptor hub descriptor byte full-speed high-speed field name description 0 0x09 0x09 blength 9 bytes 1 0x04 0x04 bdescriptortype interface_descriptor 2 0x00 0x00 binterfacenumber 3 0x00 0x00 balternatesetting 4 0x01 0x01 bnumendpoints 5 0x09 0x09 binterfaceclass 6 0x00 0x00 binterfacesubclass 7 0x00 0x00 binterfaceprotocol 8 0x00 0x00 iinterface byte full-speed high-speed field name description 0 0x07 0x07 blength 7 bytes 1 0x05 0x05 bdescriptortype endpoint_descriptor 2 0x81 0x81 bendpointaddress in endpoint #1 3 0x03 0x03 bmattributes interrupt 4,5 0x0001 0x0001 wmaxpacketsize maximum packet size 6 0xff 0x0c binterval polling rate byte full-speed high-speed field name description 0 0x0a 0x0a blength 10 bytes 1 0x06 0x06 bdescriptortype device_qualifier 2,3 0x0200 0x0200 bcdusb 4 0x09 0x09 bdeviceclass 5 0x00 0x00 bdevicesubclass 6 0x01 0x00 bdeviceprotocol 7 0x40 0x40 bmaxpacketsize0 8 0x01 0x01 bnumconfigurations 9 0x00 0x00 breserved byte all speed field name description 0 0x09 blength 9 bytes 1 0x29 bdescriptortype hub descriptor 2 0x04 [6] 0x02 bnbrports number of ports supported, cy7c65630. number of ports supported, cy7c65620. note 6. this value is configured through the external eeprom. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 11 of 24 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 a ddress 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 exte rnal spi eeprom. the contents of the eeprom must contain this information in the following format: 3,4 0x0089 [6] whubcharacteristics 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-curre nt 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 bi t 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 5 0x32 [6] bpwron2pwrgood time from when the port is powered to when the power is good on that port 6 0x28 [6] 0xae [6] bhubcontrcurrent maximum curre nt requirement for the hu b controller at full speed. maximum current requirement for t he hub controller at high speed. 7 0x00 [6] bdeviceremovable indicates if the logical port has a removable device attached (0 = removable, 1 = non-removable) 8 0xff [6] bportpwrctrlmask required for compatibility with software written for 1.0 compliant devices byte all speed field name description byte value 00xd0 1 vid (lsb) 2 vid (msb) 3 pid (lsb) 4 pid (msb) 5 reserved 6 did (msb) [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 12 of 24 0xd2 load byte 0: 0xd2 needs to be programmed with 0xd2 byte 1: vid (lsb) least significant byte of vendor id byte 2: vid (msb) most significant byte of vendor id byte 3: pid (lsb) least significant byte of product id byte 4: pid (msb)] most significant byte of product id byte 5: reserved reserved. byte 6: did (msb)] most significant by te of device id byte 7: enabledovercurrenttimer[3:0], disabledovercurrenttimer[3:0] 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 ?port indica- tors? on page 4 . default: 8 ms = 0x88. byte 8: activeports[3:0], removableports[3:0] bits 7?4 are the activeports[3:0] bits that indicates if the corresponding port is usable. for example, a two-port hub that uses ports 1 and 4 would set this field to 0x09. the total number of ports reported in the hub descriptor: bnbrports field is calculated from this . bits 3?0 are the removable- ports[3:0] bits that indicates whether the corresponding logical port is removable (set to high). logical port numbers are from 1 to n where n is the total number of active ports. if port 2 is disabled then physical ports 1, 3, and 4 map to logical ports 1, 2, and 3. th ese bit values are reported ap- propriately in the hubdescriptor:deviceremovable field. default: 0xff. byte 9: maximumpower this value is reported in the configurationdescriptor:bmax- power field and is the current in 2-ma increments that is required from the upstream hub. default: 0x28 = 80 ma for full-speed and 0x57 = 174 ma for high-speed. byte 10: hubcontrollerpower this value is reported in the hubdescriptor:bhubcontrcur- rent field and is the current in milliamperes required by the hub controller. default: 0x50 = 80 ma for full-speed and 0xae = 174 ma for high-speed. byte 11: powerontimer this value is reported in the hubdescriptor: bpwron2pwrgood field and is the time in 2-ms intervals from the setportpower command until the power on the corresponding downstream port is good. default: 0x32 = 100 ms. byte 12: illegalhubdescriptor, compounddevice, full-speedonly, noportindicators, reserved, gangpowered, singlettonly bit 7: illegalhubdescriptor. for gethubdescriptor request, some usb hosts use a descr iptortypeof 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 sys- tems that do not accept this, the illegalhubdescriptor con- figuration bit may be set to allow cy7c656xx to accept a descriptortype of 0x00 for this command. default is 1. bit 6: compounddevice. indicates whether the hub is part of a compound device. this is reported in the hubdescrip- tor, whub-characteristics: b2. default set to ?0?. bit 5: fullspeed. only configures the hub to be a full-speed only device. default is set to ?0?. bit 4: noportindicators. turns off the port indicators and does not report them as present in the hubdescriptor, whubcharacteristics b7 field. default is set to ?0?. bit 3: reserved. set this bit to ?0?. bit 2: gangpowered. indicates whether the port power switching is ganged (set to 1) or per-port (set to ?0?). this is reported in the hubdescriptor, whubcharacteristics field, b4, b3, b1, and b0. default is set to ?0?. bit 1: reserved. default is set to ?0?. bit 0: reserved. default is set to ?0?. byte value (msb->lsb) 0 0xd2 1 vid (lsb) 2 vid (msb) 3 pid (lsb) 4 pid (msb) 5 reserved 6 did (msb) 7 enabledovercurrenttimer[3:0], disableovercurrenttimer[3:0] 8 activeports[3:0], removableports[3:0] 9maxpower 10 hubcontrollerpower 11 powerontimer 12 illegalhubdescriptor, compounddevice, fullspeedonly, noportindicators, reserved, gangpowered, reserved, reserved [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 13 of 24 0xd4 load byte 0: 0xd4 needs to be programmed with 0xd4 byte 1: vid (lsb) least significant byte of vendor id byte 2: vid (msb) most significant byte of vendor id byte 3: pid (lsb) least significant byte of product id byte 4: pid (msb) most significant byte of product id byte 5: reserved reserved. byte 6: did (msb) most significant byte of device id byte 7: enabledovercurrenttimer[3:0], disabledovercur- renttimer[3:0] 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 ?port indicators? on page 4 . default: 8 ms = 0x88. byte 8: maximumpower (full-speed) this value is reported in the configurationdescriptor:bmax- power field and is the current in 2-ma increments that is required from the upstr eam hub when connected at full-speed. default: 0x28 = 80 ma for full-speed. byte 9: maximumpower (high-speed) this value is reported in the configurationdescriptor:bmax- power field and is the current in 2-ma increments that is required from the upstr eam hub when connected at high-speed. default: 0x57 = 174 ma for high-speed. byte 10: reserved write zeros to this location. byte 11: reserved write zeros to this location. byte 12: hubcontrollerpower (full-speed, bus powered) this value is reported in the hubdescriptor:bhubcontrcur- rent field and is the current in milliamperes required by the hub controller when connect ed on the upstream hub as a full-speed. default: 0x50 = 80 ma for full-speed. byte 13: hubcontrollerpower (high-speed, bus powered) this value is reported in the hubdescriptor:bhubcontrcur- rent field and is the current in milliamperes required by the hub controller when connect ed on the upstream hub as a high-speed. default: 0xae = 174 ma for high-speed. byte value (msb->lsb) factory fusable 0 0xd4 1 vid (lsb) x 2 vid (msb) x 3 pid (lsb) x 4 pid (msb) x 5 reserved 6 did (msb) x 7 enabledovercurre nttimer[3:0], disableovercurrenttimer[3:0] 8 maxpower (full-speed) x 9 maxpower (high-speed) x 10 reserved 11 reserved 12 hubcontrollerpower full-speed bus powered x 13 hubcontrollerpower high-speed bus powered x 14 hubcontrollerpower full-speed self powered 15 hubcontrollerpower high-speed self powered 16 powerontimer 17 illegalhubdescriptor, compound- device, fullspeedonly, noportindi- cators, reserved, gangpowered, singlettonly, reserved x 18 amberpolarity, greenpolarity, modulateindicators, powercontrolpo- larity, overcurrentpolarity, overcurrentmode1, overcurrentmode2 x 19 write protect 20 numlangs 21 supportedstrings 22 activeports[3:0] 23 removableports[3:0] x 24 langid a =24+2n imanufacturer b =a+2n iproduct c =b+2n iserialnumber d =c+2n iconfiguration(fs) e =d+2n iconfiguration(hs) f =e+2n iinterface(0) g =f+2n reserved h=g+2n strings n:numlangs byte value (msb->lsb) factory fusable [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 14 of 24 byte 14: hubcontrollerpower (full-speed, self powered) this value is reported in the hubdescriptor:bhubcontrcur- rent field and is the current in milliamperes required by the hub controller when connect ed on the upstream hub as a full-speed. default: 0x50 = 80 ma for full-speed byte 15: hubcontrollerpower (high-speed, self powered) this value is reported in the hubdescriptor:bhubcontrcur- rent field and is the current in milliamperes required by the hub controller when connect ed on the upstream hub as a high-speed. default: 0x64 = 100 ma for high-speed. byte 16: powerontimer this value is reported in the hubdescriptor: bpwron2pwrgood field and is the time in 2-ms increments from the setportpower command until the power on the corresponding downstream port is good. default: 0x32 = 100 ms. byte 17: illegalhubdesc riptor, compounddevice, full-speedonly, noport indicators, reserved, gangpowered, reserved bit 7: illegalhubdescriptor. for gethubdescriptor request, some usb hosts use a descriptortypeof 0x00 instead of hub_descriptor, 0x29. accord ing 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 sys- tems that do not accept this, the illegalhubdescriptor con- figuration bit may be set to allow cy7c656xx to accept a descriptortype of 0x00 for this command. default set to 1. bit 6: compounddevice. indicates whether the hub is part of a compound device. this is reported in the hubdescrip- tor, whub-characteristics: b2. default is set to ?0?. bit 5: fullspeed. only confi gures the hub to be a full-speed only device. defaul t is set to ?0?. bit 4: noportindicators. turns off the port indicators and does not report them as present in the hubdescriptor, whubcharacteristics b7 field. default is set to ?0?. bit 3: reserved. set this bit to ?0?. bit 2: gangpowered. indicates whether the port power switching is ganged (set to 1) or per-port (set to ?0?). this is reported in the hubdescriptor, whubcharacteristics field, b4, b3, b1, and b0. default is set to ?0?. bit 1: reserved. default is set to ?0?. bit 0: reserved. default is set to ?0?. byte 18: amberpolarity, greenpolarity, selfpowerable, modulateindicators, powercon trolpolarity, overcurrent- polarity, overcurrentmode1, overcurrentmode2 bit 7: amberpolarity. indicates the polarity of the amber in- dicator control. (1 = high, 0 = low) bit 6: greenpolarity. indicates the polarity of the green in- dicator control. (1 = high, 0 = low) bit 5: selfpowerable. indicates whether the hub is capable of operating in self-powered mode. if ?0?, the hub is capable of bus-powered operation only. bit 4: modulateindicators. if this bit is set, the indicator out- puts are modulated by a square wave of 120 hz, for power savings. if ?0?, the outputs are static. bit 3: powercontrolpolarity. if set, the power control outputs are active high. if not set, the power control outputs are active low. bit 2: overcurrentpolarity. if se t, the over-current inputs are active high. if not set, the over-current inputs are active low. bit 1: overcurrentmode1. re ported as bit 4 of the whub- characteristics field of the hub descriptor. if set to ?1?, this bit disables over-current detection. bit 0: overcurrentmode2. re ported as bit 3 of the whub- characteristics field of the hub de scriptor. if bit 1 of this byte is set to ?0?, over-current dete ction is enabled. if this bit (bit 0) is set to ?1?, the hub reports over-current on a per-port basis. if set to ?0?, the hub reports over-current as the sum- mation of all ports? current draw. byte 19: write protect writing the value 0x42 to this field enables write protect and any future writes to the eeprom will fail. default is set to ?0?. byte 20: numlangs number of supported string languages. cy7c656xx sup- ports a maximum of 31 languages; if this field is set to ?0? or a number larger than 31, all string support is disabled. byte 21: supportedstrings this field contains a bitmap of strings supported by the hub. a set bit indicates that the standard string is supported. a bit not set indicates that the string is not supported. the hub controller returns a non-zero index for each string that is supported, and returns 0x00 for each string not supported, as indicated by this field. the bits in this field correspond to the following standard strings. bit name description 7 reserved 6 reserved 5 iinterface (0) the iinterface string index reported in the first interface descriptor (alternate setting 0). 4 iconfiguration (high-speed) the iconfiguration string index reported in the configu- ration descriptor, when operating at high-speed. 3 iconfiguration (full-speed) the iconfiguration string index reported in the configuration descriptor, when operating at full-speed. 2 iserialnumber the iserialnumber string index reported in the device descriptor. 1 iproduct the iproduct string index reported in the device descriptor. 0 imanufacturer the imanufacturer string index reported in the device descriptor. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 15 of 24 byte 22: activeports[3:0] bits 3?0 are the activeports[3:0] bits that indicates if the corresponding port is usable. for example, a two-port hub that uses ports 1 and 4 would set this field to 0x09. the total number of ports reported in the hub descriptor: bnbrports field is calculated from this. default 0x0f byte 23: removableports[3:0] bits 3?0 are the removableports[3:0] bits that indicates whether the corresponding logical port is removable (set to high). logical port numbers are from 1 to n where n is the total number of active ports. if port 2 is disabled then phys- ical ports 1, 3, and 4 map to l ogical ports 1, 2, and 3. these bit values are recorded in the hubdescriptor:deviceremovable field. default 0x0f. byte 24: langid array of langid codes supported by the hub. each langid consists of two bytes, stored lsb first. the array has num- langs entries (2 * numlangs bytes). byte a: imanufacturer array of addresses for the imanu facturer strings. each ad- dress is two bytes long, stored lsb first. the array has numlangs entries (2 * numlangs bytes). (the starting ee- prom address is based upon the number entered for numlangs. the address a = 24 + 2 * numlangs. byte b: iproduct array of addresses for the ipro duct strings. each address is two bytes long, stored lsb first. the array has num- langs entries (2 * numlangs bytes). the address b = a + 2 * numlangs. byte c: iserialnumber array of addresses for the iserialnumber strings. each ad- dress is two bytes long, stored lsb first. the array has numlangs entries (2 * numlangs bytes). the address c = b + 2 * numlangs. byte d: iconfiguration(full-speed) array of addresses for the iconfiguration (full-speed) strings. each address is two bytes long, stored lsb first. the array has numlangs entries (2 * numlangs bytes). the address d = c + 2*numlangs. byte e: iconfiguration(high-speed) array of addresses for the iconfiguration (high-speed) strings. each address is two bytes long, stored lsb first. the array has numlangs entries (2 * numlangs bytes). the address e = d + 2 * numlangs. byte f: iinterface(0) array of addresses for the iinterface(0) strings. each ad- dress is two bytes long, stored lsb first. the array has numlangs entries (2 * numlangs bytes). the address f = e + 2 * numlangs. byte g: iinterface(1) reserved byte h: strings strings addressed by the string pointers. strings must com- ply with the usb specification. the first byte must be the supported usb requests device class commands table 4. device class requests request bmrequesttype brequest wvalue windex wlength data getdevicestatus 10000000b 0x00 0x0000 0x0000 0x0002 2 byte device status getinterfacestatus 10000001b 0x00 0x0000 0x0000 0x0002 2 byte interface status getendpointstatus 10000010b 0x00 0x0000 0x0000 0x0002 2 byte endpoint status getdevicedescriptor 10000000b 0x06 0x0001 zero or language id descriptor length descriptor getconfigdescriptor 10000000b 0x06 0x0002 zero or language id descriptor length descriptor getdevicequalifierde- scriptor 10000000b 0x06 0x0006 zero or language id descriptor length descriptor getotherspeedconfigura- tiondescriptor 10000000b 0x06 0x0007 zero or language id descriptor length descriptor getconfiguration [7] 10000000b 0x08 0x0000 0x0000 0x0001 configuration value setcongfiguration [7] 00000000b 0x09 configuration value 0x0000 0x0000 none getinterface 10000001b 0xa 0x0000 0x0000 0x0001 interface number note 7. only one configuration is supported in cy7c656xx. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 16 of 24 hub class commands setinterface 00000001b 0x0b alternate setting interface number 0x0000 none setaddress 00000000b 0x05 device address 0x0000 0x0000 none setdeviceremotewakeup 00000000b 0x03 0x01 0x0000 0x0000 none setdevicetest_j 00000000b 0x03 0x02 0x0100 0x0000 none setdevicetest_k 00000000b 0x03 0x02 0x0200 0x0000 none setdevicetest_se0_nak 00000000b 0x03 0x02 0x0300 0x0000 none setdevicetest_packet 00000000b 0x03 0x02 0x0400 0x0000 none setendpointhalt 00000000b 0x03 0x00 0x0000 0x0000 none cleardevicere- motewakeup 00000000b 0x01 0x01 0x0000 0x0000 none clearendpointhalt 00000000b 0x01 0x00 0x0000 0x0000 none table 4. device class requests (continued) request bmrequesttype brequest wvalue windex wlength data table 5. hub class requests request bmrequesttype brequest wvalue windex wlength data gethubstatus 10100000b 0x00 0x0000 0x0000 0x0004 hub status (see table 11-19 of usb 2.0 specifications) change status (see table 11-20 of usb 2.0 specifica- tions) getportstatus 10100011b 0x00 0x0000 byte 0: 0x00 byte 1: port 0x0004 port status (see table 11-21 of usb 2.0 specifications) change status (see table 11-20 of usb 2.0 specifica- tions) clearhubfeature 00100000b 0x01 feature selectors [8] 0 or 1 0x0000 0x0000 none clearportfeature 00100011b 0x01 feature selectors [8] 1, 2, 8, 16, 17, 18, 19, or 20 byte 0: 0x00 byte 1: port 0x0000 none clearportfeature 00100011b 0x01 feature selectors [8] 22 (port_indicator) byte 0: - byte 1: port 0x0000 none sethubfeature 00100000b 0x03 feature selector [8] 0 or 1 0x0000 0x0000 setportfeature 00100011b 0x03 feature selectors [8] 2, 4 or 8 port 0x0000 none setportfeature 00100011b 0x03 feature selector [8] 21 (port_test) byte 0: selectors [9] 1,2, 3, 4 or 5 byte 1: port 0x0000 none notes 8. feature selector values for different feature is presented in table 6 on page 17 . 9. selector values for different features are presented in table 7 on page 17 . [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 17 of 24 setportfeature 00100011b 0x03 feature selector [8] 22 (port_indicator) byte 0: selectors [10] 0, 1, 2, or 3 byte 1: port 0x0000 none gethubdescriptor 10100000b 0x06 descriptor type and descriptor index hub descriptor length clearttbuffer 00100011b 0x08 dev_addr, ep_num tt_port 0x0000 none resettt 00100000b 0x09 0x0000 byte 0: 0x00 byte 1: port 0x0000 none getttstate 10100011b 0x0a tt_flags byte 0: 0x00 byte 1: port tt state length tt state stoptt 00100011b 0x0b 0x0000 byte 0: 0x00 byte 1: port 0x0000 none vendor commands read eeprom 11000000b 0x 02 0x00 0x00 length data this request results in length bytes of data being read from t he external memory device, and returned to the host. data is read beginning with address 0. this request fails if there is no exter nal memory device present. this request is only valid if the h ub is in the configured state; t he request fails otherwise. write eeprom 01000000b 0x01 0x00 0x00 length data this request results in length bytes of data being written to th e external memory device. data is written beginning with addres s 0. this request fails if there is no exte rnal memory device present. this request is only valid if the hub is in the configured state or if the external memory device write prot ect byte is set; the request fails otherwise. table 5. hub class requests (continued) request bmrequesttype brequest wvalue windex wlength data table 6. hub class feature selector feature selector recipient value c_hub_local_power hub 0 c_hub_over_current hub 1 port_connection port 0 port_enable port 1 port_suspend port 2 port_reset port 4 port_power port 8 port_low_speed port 9 c_port_connection port 16 c_port_enable port 17 c_port_suspend port 18 c_port_over_current port 19 c_port_reset port 20 port_test port 21 port_indicator port 22 note 10. selector values for different feature is presented in table 8 on page 18 . table 7. test mode selector for feature selector port_test (0x21) [9] port_test mode description selector value test_j 1 test_k 2 test_se0_nak 3 test_packet 4 test_force_enable 5 [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 18 of 24 upstream usb connection the following is a schematic of the usb upstream connector. downstream usb connections the following is a schematic of the usb downstream connector. led connections the following is a schematic of the led circuitry. table 8. port indicator selector for fe ature selector port_indicator (0x22) port indicator color selector value port indicator mode color set automatica lly as shown in table 1 on page 4 0 automatic mode amber 1 manual mode green 2 manual mode off 3 manual mode figure 2. usb upstream port connection vcc d? d+ shell buspower gnd d? d+ 100 k 2.2 f 10v figure 3. usb downstream port connection vcc d? gnd shell d+ dd?[x] dd+[x] pwrx 150 f 10v 0.01 f figure 4. usb downstream port connection 680 680 green#[x] amber#[x] 3.3v [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 19 of 24 system block diagram figure 5. sample schematic for 4- port self powered configuration vcc d? d+ shell gnd d? d+ 150 k 2.2 f 10v 15 k vbus vbuspower hx2lp green[1] amber[1] green[2] amber[2] green[3] amber[3] green[4] amber[4] pwr1 ovr1 pwr2 ovr2 pwr3 ovr3 pwr4 ovr4 spi_cs spi_sck spi_sd dd?[1] dd+[1] dd?[2] dd+[2] dd?[3] dd+[3] dd?[4] dd+[4] d? d+ vbuspower d- d+ dd-[1] dd+[1] dd-[2] dd+[2] dd-[3] dd+[3] dd-[4] dd+[4] green[1] amber[1] green[2] amber[2] green[3] amber[3] green[4] amber[4] pwr1 ovr1 pwr2 ovr2 pwr3 ovr3 pwr4 ovr4 spi_cs spi_sck spi_sd vcc1 vcc2 vcc3 vcc4 vcc5 vcc6 vcc7 vcc8 vcc9 vcc10 vcc11 xin xout gnd1 gnd2 gnd3 gnd4 gnd5 gnd6 gnd7 gnd8 gnd9 gnd10 gnd11 gnd12 vbuspower reset 24 mhz 12 pf 0.1 f 3.3v 100k spi eeprom spi_sd spi_sck spi_cs 5v dspwr1 dspwr3 dspwr4 power management pwr1 ovr1 pwr2 ovr2 ovr3 pwr3 pwr4 ovr4 vcc d? d+ shell gnd 150 f 0.01 f 10v dd?[1] dd+[1] dspwr1 680 680 green#[1] amber#[1] 3.3v 680 680 green#[2] amber#[2] 3.3v vcc d? d+ shell gnd 150 f 0.01 f 10v dd?[2] dd+[2] dspwr2 vcc d? d+ shell gnd 150 f 0.01 f 10v dd-[3] dd+[3] dspwr3 680 680 green#[3] amber#[3] 3.3 v 680 680 green#[4] amber#[4] 3.3 v vcc d? d+ shell gnd 150 f 0.01 f 10v dd-[4] dd+[4] dspwr4 dspwr2 12 pf spi_sd selfpwr 3.3v 3.3v 10k do di clk cs [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 20 of 24 electrical characteristics absolute maximum ratings storage temperature ................................ ?65c to +150 c ambient temperature with power applied: commercial.................... 0c to +70c automotive ................. ?40c to +85c supply voltage to ground potential .............. ?0.5v to +4.0v dc voltage applied to outputs in high z state ...............................................................?0.5v to v cc + 0.5v power dissipation (4 hs ports) .. ...................................0.9 w static discharge voltage ...........................................> 2000v max. output sink current per i/o ................................10 ma operating conditions t a (ambient temperature under bias) commercial ........ 0c to +70c automotive ..... ?40c to +85c supply voltage............................................+3.15v to +3.45v ground voltage.................................................................. 0v fosc (oscillator or crystal frequency)...... 24 mhz 0.05% parallel resonant, fundamental mode, 12-pf load capacitance, 0.5 mw usb transceiver usb 2.0 certified in full-, low-, and high-speed modes. ac electrical characteristics both the upstream usb transce iver and all four downstream transceivers have passed the usb-if usb 2.0 electrical certi- fication testing. dc electrical characteristics parameter description conditions min. typ. max. unit v cc supply voltage 3.15 3.3 3.45 v v cc rampup ramp rate on v cc 18 v/ms v ih input high voltage 2 5.25 v v il input low voltage ?0.5 0.8 v i l input leakage current 0 < v in < v cc 10 a v oh output voltage high i out = 4 ma 2.4 v v ol output low voltage i out = ?4 ma 0.4 v i oh output current high 4ma i ol output current low 4ma c in input pin capacitance 10 pf i susp suspend current 80 a i cc supply current 4 active ports full-speed host, full-speed devices 86 110 ma high-speed host, high-speed devices 231 260 ma high-speed host, full-speed devices 154 180 ma 2 active ports full-speed host, full-speed devices 77 100 ma high-speed host, high-speed devices 163 190 ma high-speed host, full-speed devices 136 160 ma no active ports full-speed host 65 90 ma high-speed host 93 120 ma [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 21 of 24 serial peripheral interface ordering information parameter description conditions min. typ. max. unit clock rise/fall time 500 ns clock frequency 250 khz data set-up time 50 ns hold time 100 ns reset period 1.9 ms ordering code package type cy7c65630-56lfxc 56-pin qfn 4-port cy7c65630-56lfxa 56-pin qfn 4-port automotive aec grade CY7C65620-56LFXC 56-pin qfn 2-port cy4606 cy7c65630 usb 2.0 4-port hub reference design kit cy4605 cy7c65620 usb 2.0 2-port hub reference design kit [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 22 of 24 ? cypress semiconductor corporation, 2006-2007. the information contained herein is subject to change without notice. cypress semiconductor corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in a cypress product. nor does it convey or imply any license under pate nt or other rights. cypress products are not warranted nor intended to be used for medical, life support, life saving, critical cont rol or safety applications, unless pursuant to an express writt en agreement with cypress. furthermore, cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected t o result in significant injury to the user. the inclusion of cypress products in life-support systems application implies that the manu facturer assumes all risk of such use and in doing so indemni fies cypress against all charges. package diagram the cy7c656xx is available in a space saving 56-pin qfn (8 8 mm) figure 6. 56-lead qfn 8 x 8 mm lf56a (subcon punch type with 6.1 x 6.1 epad) windows is a registered trademark of micr osoft corporation. tetrahub and ez-usb hx2lp are trademarks of cypress semicon- ductor corporation. all product and company names mentioned in this document are trademarks of their respective holders. +$7&+$5($,662/'(5$%/((;326('0(7$/ 5()(5(1&(-('(&02 $//',0(16,216$5(,100>0,10$;@ 127(6 3$&.$*(:(,*+7j ;= ;= ;= ! # ;=-!8 . 3%!4).'0,!.% . ;= ;= ;= ;= ;=-!8 8 # ;= ;=2%& ;=-!8 0).)$ 2 2 ;= ;= ;= ;= ;= ;=2 ;= ;= ;= ;= $)! ;= ;= ;= ;= ;= 4/06)%7 "/44/-6)%7 3)$%6)%7 62/'(5$%/( (;326(' 3$' 51-85144 *g [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 23 of 24 document history page document title: cy7c656xx ez-usb hx2lp? low-power usb 2.0 hub controller family document number: 38-08037 rev. ecn no. issue date orig. of change description of change ** 131505 02/12/2004 jtc new data sheet *a 231329 see ecn kku changed load capacitors to 12 pf, updated part numbers, added functional overviews, block descriptions, pin confi gurations, default descriptors, config- urations options, supported usb reques ts, electrical characteristics and package diagram *b 250869 see ecn ari added typical values for icc in the dc electrical characteristics table, changed mpn cy7c65650 to cy7c65640b, added cy7c65620 package *c 330195 see ecn kku added reset period in to the table in section ?serial peripheral interface? added 0xd4 eeprom load added vendor command values added v cc ramp rate updated block diagram *d 342997 see ecn kku updated features list removed from the enumeration section ?once the hub is configured, the full hub functionality is available? added reference to 0xd4 load to the downstream ports section added reference to polarity control in the power switching and over-current detection sections updated the automatic port state to port indicator color mapping table to match usb-if spec changes added led modulation to the port indicators section updated pin description table - selfpwr# to selfpwr and removed refer- ences to limitations of bus powered. added reference to polarity control on pwr#, ovr# and led control lines updated default descriptors updated eeprom list to include 25lc080 removed noeopateof1 bit added led polarity control *e 498396 see ecn teh removed all references to hx1tt and multi-tt updated block diagrams to remove ports and tts removed preliminary updated device id default added write protect description correct sample schematics to reflect latest rdk updated power consumption numbers updated part numbers *f 570287 see ecn ari corrected typo in table 3. c hanged downstream port 4 signal labels from [3] to [4]. added dimensions of e-pads to figure 6. *g 852600 see ecn kku changed feature ?2-port single tt for bus power support? to ?bus powered configurations? updated figure 5. added blank eeprom statement to the device descriptor section added blank eeprom statement to t he configurat ion options section added indicator for factory fusable options. [+] feedback [+] feedback
cy7c656xx document #: 38-08037 rev. *h page 24 of 24 *h 1019740 see ecn kku/ari added to features: automotive aec grade option (-40-85c). added to part numbers: cy7c65630-56lfxa: 56-pin qfn 4-port automotive aec grade. added absolute ambient temperature with power applied for automotive part. added operational ambient temperature under bias for automotive part. replaced tbd under absolute maximum power dissipation with 0.9 watts. removed internal part numbers referenced in figure 6 note 5. changed ?usb 2.0-compliant? to ?usb 2.0-certified? removableports updated to reflect logical ports. edited for active voice. document title: cy7c656xx ez-usb hx2lp? low-power usb 2.0 hub controller family document number: 38-08037 rev. ecn no. issue date orig. of change description of change [+] feedback [+] feedback

▲Up To Search▲

Price & Availability of CY7C65620-56LFXC

	To Download CY7C65620-56LFXC Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .