Cypress.com: Documentation http://www.cypress.com/?app=search&searchType=advanced&id%3D183 HX2VL (CY7C65632/34/42) - IBIS http://www.cypress.com/?rID=60032 This is the IBIS model of HX2VL (CY7C65632/34/42)

]]> Fri, 18 Jan 2013 06:31:14 -0600 CY4608M: Multi-TT HX2VL Very Low-Power 4-Port Hub Development Kit http://www.cypress.com/?rID=62899
-->




CY4608M HX2VL™ USB 2.0 Multi-TT 4-Port Hub

Cypress offers a complete development kit for developing a fixed-function, very low-power Multi-TT 4-port USB 2.0 hub controller (28 QFN package) that is production ready and USB-IF compliant.


Key Features:

  • Multiple Transaction Translator.
  • Compliance with USB 2.0 specification.
  • 480/12/1.5-Mbps operation.
  • Very Low-power consumption.
  • Highly integrated solution for reduced BOM cost.
  • Supports Internal or External Voltage regulation.
  • Space Saving 5x5mm 28-pin QFN package.
  • Maximum configurability using EEPROM programming.
  • Individual or ganged port power switching and over current detection.


Hardware Description

The CY4608M HX2VL Development Kit Box includes:

  • CY7C65642-based USB 2.0 4-port Hub Board.
  • 5 VDC, 2.5A wall power supply.
  • USB cable (A-B).
  • Quick Start Guide booklet.
]]> Tue, 15 Jan 2013 05:25:47 -0600 CY4607M: Multi-TT HX2VL Very Low-Power 4-Port Hub Development Kit http://www.cypress.com/?rID=62897
-->




CY4607M HX2VL™ USB 2.0 Multi-TT 4-Port Hub

Cypress offers a complete development kit for developing a fixed-function, very low-power Multi-TT 4-port USB 2.0 hub controller (48 TQFP package) that is production ready and USB-IF compliant.


Key Features:

  • Multiple Transaction Translator.
  • Compliance with USB 2.0 specification.
  • 480/12/1.5-Mbps operation.
  • Very Low-power consumption.
  • Highly integrated solution for reduced BOM cost.
  • Supports Internal or External Voltage regulation.
  • Space Saving 7x7mm 48-pin TQFP package.
  • Maximum configurability using EEPROM programming.
  • Individual or ganged port power switching and over current detection.
     

Hardware Description

The CY4607M HX2VL Development Kit Box includes:

  • CY7C65642-based USB 2.0 4-port Hub Board.
  • 5 VDC, 2.5A wall power supply.
  • USB cable (A-B).
  • Quick Start Guide booklet.
]]> Tue, 15 Jan 2013 05:15:38 -0600 CY4605 - High-Speed Low-Power USB 2.0 Compliant 2-Port Hub http://www.cypress.com/?rID=14416 Click on Image to open in New Window

-->

Click on Image to open in New Window

EZ-USB HX2LP(TM) USB 2.0 2-Port Hub

Cypress offers a complete reference design for developing a fixed-function, low-power 2-port USB 2.0 hub that is production ready.

Key Features:
 

  • Compliance with USB 2.0
  • 480/12/1.5-Mbps operation
  • Low-power operation for bus-powered applications
  • Fit/Form/Function Compatible with CY7C65640 & CY7C65640A TetraHub(TM)
  • 8x8mm 56-lead QFN (quad flat no-lead) package
  • Integrated components for lower BOM cost
  • Individual or ganged port power switching and over current detection
  • Dedicated LED ports

Hardware Description

The EZ-USB HX2LP(TM) reference design kit includes:
 
  • CY7C65620-based demonstration unit
  • 5 VDC, 2.5A wall power supply
  • USB cable
  • Datasheet
  • Design & Application Notes
  • Hardware files
  • Schematics
  • Bill of Materials
  • Gerber and OrCAD source files
]]> Tue, 15 Jan 2013 05:02:09 -0600 CY7C65621, CY7C65631: EZ-USB HX2LP Lite™ Low Power USB 2.0 Hub Controller Family http://www.cypress.com/?rID=37932 EZ-USB HX2LP Lite™ Low Power USB 2.0 Hub Controller Family

Features

  • USB 2.0 hub controller
  • 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
  • For more, see pdf

Introduction

EZ-USB HX2LP Lite™ is Cypress’s next generation family of high performance, low power USB 2.0 hub controllers. HX2LP Lite 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 external passive components such as pull up and pull down resistors, reducing the overall bill of materials required to implement a hub design.

]]> Wed, 09 Jan 2013 00:00:57 -0600 Bus-Powered USB Hub Design Using EZ-USB HX2LP™/HX2VL - AN15454 http://www.cypress.com/?rID=12977 The content of this application note is now available in AN72332 Guidelines on System Design using Cypress' USB 2.0 Hub (HX2VL)

]]> Wed, 02 Jan 2013 04:33:36 -0600 AN69025 - Schematic Review Checklist for HX2VL http://www.cypress.com/?rID=52717 The content of this application note is now available in AN72332 Guidelines on System Design using Cypress' USB 2.0 Hub (HX2VL)

]]> Wed, 02 Jan 2013 04:26:16 -0600 AN73052 - Configuring HX2VL Parameters http://www.cypress.com/?rID=57904 The content of this application note is now available in AN72332 - Guidelines on System Design using Cypress' USB 2.0 Hub (HX2VL)

]]> Wed, 02 Jan 2013 04:16:07 -0600 AN72332 - Guidelines on System Design using Cypress' USB 2.0 Hub (HX2VL) http://www.cypress.com/?rID=54780 AN72332 provides guidelines on system design with HX2VL, a high-performance, low-power USB 2.0 high speed hub that is optimized for low-cost designs. Recommended system design and PCB Layout techniques are included here to ensure best performance and full compliance with USB 2.0 specification.

Introduction

HX2VL is the next-generation family of high-performance, low-power USB 2.0 hub controllers. The HX2VL has integrated upstream and downstream transceivers, a USB serial interface engine (SIE), USB hub control and repeater logic, and transaction translator (TT) logic. The HX2VL portfolio has Single-TT and Multi-TT versions, lowcost options with high performance.

]]> Wed, 02 Jan 2013 04:07:30 -0600 CY7C65642: HX2VL - Very Low Power USB 2.0 TetraHub™ Controller http://www.cypress.com/?rID=52722 HX2VL - Very Low Power USB 2.0 TetraHub™ Controller

Features

  • High-performance, low-power USB 2.0 hub, optimized for low-cost designs with minimum bill-of-material (BOM).
  • USB 2.0 hub controller
  • Very low-power consumption
  • Highly integrated solution for reduced BOM cost
  • Downstream port management
  • Maximum configurability
  • Available in space saving 48-pin (7 × 7 mm) TQFP and 28-pin (5 × 5 mm) QFN packages
  • Supports 0 °C to +70 °C temperature range
  • For more, see pdf
     

Functional Overview

The Cypress CY7C65642 USB 2.0 Hubs are low-power hub solutions for USB which provide maximum transfer efficiency with no TT multiplexing between downstream ports. The CY7C65642 USB 2.0 Hubs integrate 1.5 kΩ upstream pull-up resistors for full speed operation and all downstream 15 kΩ pull-down resistors and 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.

]]> Mon, 03 Dec 2012 22:43:47 -0600 CY7C65620/CY7C65630: EZ-USB HX2LP™ Low Power USB 2.0 Hub Controller Family http://www.cypress.com/?rID=14199 EZ-USB HX2LP™ Low Power USB 2.0 Hub Controller Family

Features

  • USB 2.0 hub controller
  • Automotive AEC grade option (–40 °C to 85 °C)
  • Industrial grade option (–40 °C to 85 °C)
  • Compliant with 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
  • For more, see pdf
     

Introduction

EZ-USB HX2LP™ is Cypress’s 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 TT logic. Cypress has also integrated many of the external passive components, such as pull-up and pull-down resistors, reducing the overall bill of materials required to implement a hub design.

]]> Wed, 28 Nov 2012 01:34:37 -0600 QTP 044504: (CY7C65620/CY7C65630) HX1TT Device Family, C8Q-3R Technology, Fab4 http://www.cypress.com/?rID=35793 Thu, 25 Oct 2012 05:40:45 -0600 In-System EEPROM Programming for CY7C65620/30 - KBA82845 http://www.cypress.com/?rID=32668 Answer: CY7C65620/30 supports in-System EEPROM programming. In-System programming means that the programming can be done while the EEPROM resides in the system rather than having to remove it for the sake of programming. We have implemented vendor specific USB commands in the hub to write/read the EEPROM. So boards can be built with un-programmed EEPROMs and then programmed with the proper contents later.

Blaster and primer are two software utilities that come with CY4605 and CY4606 Hub RDKs, which can be used for this in-system programming from a PC running Windows.

Blaster allows editing of the hub capability and descriptors whereas primer is a manufacturing line programming tool. Primer takes an EEPROM image (.iic file) created by Blaster and programs the Hub as soon as it is plugged in.

Note: For programming the EEPROM using the programming utilities the hub has to be connected to cyusb.sys.

]]> Wed, 10 Oct 2012 03:27:57 -0600 For HX2LP OVR# Pins, Whether They Have an Internal Pull-up Resistor or Need an External Pull-up - KBA82846 http://www.cypress.com/?rID=30026 There are no internal pull ups on the OVR# pins. They are set to inputs by default (on power-up) and do not need to have external pull-ups if you are not using the respective port at all.  The OVR# is an input  (active low) used to detect overcurent and it should be setup to default to a state of '1' (so that the port is not marked detected as over current).  If you are not using the port, you do not need to use an external pull-up, as you don't care about the status of this unused port.  If you are using this port or there is a possibility of using this port, you will need external pull-ups to set the state to '1' (no over current detected on the port).  In any case having external pull-ups (not leaving it floating) is always a good (recommended) idea regardless of whether the port is configured to be used or not.

-->

Answer: There are no internal pull-ups on the OVR# pins of HX2LP. They are set to inputs by default (on power-up) and do not need to have an external pull-up if you are not using the respective port at all. The OVR# is an input (active low) used to detect over-current and it should be setup to default to a state of '1' (so that the port is not marked or detected as over current).

If you are not using the port, you do not need to use an external pull-up, as you don't care about the status of this unused port.

If you are using this port or there is a possibility of using this port, you will need an external pull-up to set the state to '1' (no over current detected on the port).

In any case having an external pull-up (not leaving it floating) is always a good (recommended) idea regardless of whether the port is configured to be used or not.

]]> Wed, 10 Oct 2012 01:48:09 -0600 CY7C65632, CY7C65634: HX2VL™ Very Low Power USB 2.0 Hub Controller http://www.cypress.com/?rID=52723 HX2VL™ Very Low Power USB 2.0 Hub Controller

Features

  • High performance, low-power USB 2.0 Hub, optimized for low cost designs with minimum Bill-of-material
  • USB 2.0 hub controller
  • Very low power consumption
  • Highly integrated solution for reduced BOM cost
  • Downstream port management
  • Maximum configurability
  • Available in space saving 48-pin (7 × 7 mm) TQFP and 28-pin (5 × 5 mm) QFN packages
  • Supports 0 °C to 70 °C temperature range
     

Functional Overview

The Cypress CY7C6563X USB 2.0 Hubs are low power hub solutions for USB which provide maximum transfer efficiency. The CY7C6563X USB 2.0 Hubs integrate 1.5 kohm upstream pull-up resistors for full speed operation and all downstream 15 kohm pull-down resistors and 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.

]]> Tue, 09 Oct 2012 01:25:46 -0600 Cypress USB Solutions http://www.cypress.com/?rID=47005 Thu, 30 Aug 2012 01:19:26 -0600 AN69235 - Migrating from HX2/HX2LP to HX2VL http://www.cypress.com/?rID=52716 AN69235 is intended to help the developer migrate a hub design based on EZ-USB® HX2™ (CY7C65640A)/ EZ-USB® HX2LP™ (CY7C65630/20) to use the HX2VL™ (CY7C65642/32/34) hub. It also provides a feature comparison between HX2, HX2LP, and HX2VL to aid in the selection of the appropriate part number for migration. One must note that HX2 (TetraHub) is now not recommended for new designs.
 

]]> Thu, 23 Aug 2012 05:23:14 -0600 AN023 - USB Compliance Testing Overview http://www.cypress.com/?rID=12995 One of the secrets to USB’s success has been the compliance-testing program. This program verifies that your device meets the specification and works well with other USB devices.

]]> Fri, 10 Aug 2012 03:24:37 -0600 Mac OS X: Getting Started with USB - AN1105 http://www.cypress.com/?rID=12929 Developing USB drivers for Mac OS X is completely different than developing USB drivers on Mac OS 9. This application notes describe how to develop USB driver for Mac OS X. Include introducing the kernel of Mac OS X and driver architecture. Some useful example codes also be attached.

]]> Fri, 10 Aug 2012 02:57:09 -0600 CY7C65640A: TetraHub™ High Speed USB Hub Controller http://www.cypress.com/?rID=14197 TetraHub™ High Speed USB Hub Controller

Features

  • USB 2.0 Hub
  • Four Downstream Ports
  • Multiple Transaction Translators - One per Downstream Port for Maximum Performance
  • VID, PID, and DID configured from External SPI EEPROM
  • 24 MHz External Crystal
  • Small Package - Quad Flat Pack, No Leads (QFN)
  • Integrated Upstream Pull Up Resistor
  • Integrated Downstream Pull Down Resistors for all Downstream Ports
  • Integrated Upstream and Downstream Series Termination Resistors
  • For more, see pdf

Description
 
Cypress’s TetraHub™ is a high performance self powered Universal Serial Bus (USB) 2.0 hub. The Tetra architecture provides four downstream USB ports, with a Transaction Translator (TT) for each port, making it the highest performing hub possible. This single-chip device incorporates one upstream and four downstream USB transceivers, a serial Interface Engine (SIE), USB hub controller and repeater, and four TTs. It is suitable for standalone hubs, motherboard hubs, and monitor hub applications.

]]> Mon, 30 Jul 2012 03:15:50 -0600 CY7C66013C, CY7C66113C: Full Speed USB (12 Mbps) Peripheral Controller with Integrated Hub http://www.cypress.com/?rID=14196 Full Speed USB (12 Mbps) Peripheral Controller with Integrated Hub

Features

  • Full speed USB peripheral microcontroller with an integrated USB hub
    • Well suited for USB compound devices such as a keyboard hub function
  • 8-bit USB optimized microcontroller
    • Harvard architecture
    • 6 MHz external clock source
    • 12 MHz internal CPU clock
    • 48 MHz internal Hub clock
  • Internal memory
    • 256 bytes of RAM
  • For more, see pdf

Functional Overview

The CY7C66013C and CY7C66113C are compound devices with a full speed USB microcontroller in combination with a USB hub. Each device is suited for combination peripheral functions with hubs such as a keyboard hub function. The 8-bit one time programmable microcontroller with a 12 Mbps USB Hub supports as many as four downstream ports.

]]> Mon, 30 Jul 2012 03:12:26 -0600 CY7C65113C: USB Hub with Microcontroller http://www.cypress.com/?rID=14193 USB Hub with Microcontroller

Features

  • Full Speed USB hub with an integrated microcontroller
  • 8-bit USB optimized microcontroller
    • Harvard architecture
    • 6-MHz external clock source
    • 12-MHz internal CPU clock
    • 48-MHz internal hub clock
  • Internal memory
    • 256 bytes of RAM
    • 8 KB of PROM
  • For more, see pdf

Functional Overview

The CY7C65113C device is a one-time programmable 8-bit microcontroller with a built-in 12-Mbps USB hub that supports up to four downstream ports. The microcontroller instruction set has been optimized specifically for USB operations, although the microcontrollers can be used for a variety of non-USB embedded applications.

]]> Mon, 30 Jul 2012 02:25:27 -0600 AN1168 - High-speed USB PCB Layout Recommendations http://www.cypress.com/?rID=12982 This application note details guidelines for designing, controlled-impedance; high-speed USB printed circuit boards to comply with the USB specification. This note is applicable to all Cypress high-speed USB solutions. Some Cypress high-speed USB chips have separate application notes that address chip-specific PCB design guidelines.

]]> Mon, 23 Jul 2012 03:33:34 -0600 QTP 110306: CY7C65632/42 AT SSMC PRODUCT QUALIFICATION REPORT http://www.cypress.com/?rID=54853 Tue, 17 Jul 2012 03:36:34 -0600 QTP 031803: 24/32/40/48/56-LEAD QFN PACKAGES, PURE SN, MSL3, 260C REFLOW AMKOR-KOREA (L) QUALIFICATION REPORT http://www.cypress.com/?rID=35664 Tue, 17 Jul 2012 01:04:24 -0600 QTP 114906: 68/56 QFN (8x8x1.0mm) NiPdAu, 100% Cu Wire MSL3, 260°C Reflow ASEK-Taiwan (G) CYPRESS http://www.cypress.com/?rID=61294 Fri, 13 Jul 2012 06:53:37 -0600 Windows Hardware Certification Process for Customer Modified Cypress USB Driver Files http://www.cypress.com/?rID=65775 Cypress supplies a digitally signed driver with its reference designs and development kits. The signature on the driver files is invalidated when customer-specific information (VID, PID, strings, and so on) are added to the driver files. The following steps allow customers to obtain the ‘Certified for Windows’ logo digital signature by passing Microsoft’s Windows® Hardware Quality Labs (WHQL) testing for customer-modified Cypress USB driver files. More information on the logo programs offered by Microsoft (including cost, debug procedure etc.) is available at http://msdn.microsoft.com/en-us/windows/hardware/gg463010 and http://msdn.microsoft.com/en-us/windows/hardware/gg487530

 

Driver Signing for Windows Hardware Certification

A complete beginning-to-end walkthrough of how to digitally sign drivers is provided by Microsoft and is available at http://www.microsoft.com/whdc/winlogo/drvsign/kmcs_walkthrough.mspx

 

FAQs

Question 1: I get the following error while binding my device to CyUSB.sys in Windows 7/Vista 64-bit environment, “Windows encountered a problem installing the driver software for your device” or usage of CyUSB.sys in Vista 64-bit operating system gives Code 39 error (Code 52 in the case of Windows 7). What do these errors mean? How can they be resolved?

Answer: CyUSB.sys downloaded through our website is an unsigned driver. This error reported while an unsigned driver used in 64-bit operating systems in normal mode. Following are the steps to disable driver signature enforcement in 64-bit operating system:

a) During boot-up press F8.

b) In the list of options that appear select “Disable driver signature enforcement”.

This should resolve the issues.

Note: In the case of Windows Vista 64-bit operating system the error message is “Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)”. In the case of Windows 7 64-bit operating system it is "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)".

Question 2: What is the signing procedure when script files are used?

Answer:When script files are used, the Inf file should contain both VID/PID combinations while signing the driver. The procedure for signing the procedure is the same as that for regular drivers. The script file (.spt file) will need to be shipped along with the Inf/Sys files.

]]> Tue, 10 Jul 2012 00:57:27 -0600 CY4606 - EZ-USB HX2LP High-Speed Low-Power USB 2.0 Compliant 4-Port Hub http://www.cypress.com/?rID=14418 Click on Image to open in New Window

EZ-USB HX2LP(TM) USB 2.0 4-Port Hub

Cypress offers a complete reference design for developing a fixed-function, low-power 4-port USB 2.0 hub that is production ready. 

Key Features:
 
  • Compliance with USB 2.0
  • 480/12/1.5-Mbps operation
  • Low-power operation for bus-powered applications
  • 2-port bus-powered keyboard hub support
  • Fit/Form/Function Compatible with CY7C65640 & CY7C65640A TetraHub(TM)
  • 8x8mm 56-lead QFN (quad flat no-lead) package
  • Integrated components for lower BOM cost
  • Individual or ganged port power switching and over current detection
  • Dedicated LED ports

Hardware Description

The EZ-USB HX2LP(TM) reference design kit includes:
 
  • CY7C65630-based demonstration unit
  • 5 VDC, 2.5A wall power supply
  • USB cable
  • Datasheet
  • Design & Application Notes
  • Hardware files
  • Schematics
  • Bill of Materials
  • Gerber and OrCAD source files
]]> Sun, 06 May 2012 23:50:02 -0600 QTP 114905: 48 QFN (7x7x1.0mm) NiPdAu, 100% Cu Wire MSL3, 260°C Reflow ASEK-Taiwan (G) http://www.cypress.com/?rID=61295 Wed, 25 Apr 2012 05:50:06 -0600 EEPROM Data Sheets - E2PROM http://www.cypress.com/?rID=52590 Mon, 05 Mar 2012 04:07:51 -0600 CY4608 HX2VL Very Low-Power USB 2.0 Compliant 4-Port Hub Development Kit http://www.cypress.com/?rID=55802  


CY4608 HX2VL(TM) USB 2.0 4-Port Hub

Cypress offers a complete development kit for developing a fixed-function, very low-power 4-port USB 2.0 hub that is production ready and USB-IF compliant.

Key Features:

  • Compliance with USB 2.0 specification.
  • 480/12/1.5-Mbps operation
  • Very Low-power consumption
  • Highly integrated solution for reduced BOM cost
  • Supports Internal or External Voltage regulation
  • Space Saving 5x5mm 28-pin QFN package.
  • Maximum configurability using EEPROM programming.
  • Individual or ganged port power switching and over current detection.

Hardware Description

The CY4608 HX2VL Development Kit Box includes:

  • CY7C65632-based USB 2.0 4-port Hub Board.
  • 5 VDC, 2.5A wall power supply
  • USB cable (A-B).
  • Quick Start Guide booklet.
]]> Fri, 17 Feb 2012 11:44:20 -0600 CY4607 HX2VL Very Low-Power USB 2.0 Compliant 4-Port Hub Development Kit http://www.cypress.com/?rID=55801  

CY4607 HX2VL(TM) USB 2.0 4-Port Hub

Cypress offers a complete development kit for developing a fixed-function, very low-power 4-port USB 2.0 hub that is production ready and USB-IF compliant.

Key Features:

  • Compliance with USB 2.0 specification.
  • 480/12/1.5-Mbps operation
  • Very Low-power consumption
  • Highly integrated solution for reduced BOM cost
  • Supports Internal or External Voltage regulation
  • Space Saving 7x7mm 48-pin TQFP package.
  • Maximum configurability using EEPROM programming.
  • Individual or ganged port power switching and over current detection.
     

Hardware Description

The CY4607 HX2VL Development Kit Box includes:

  • CY7C65632-based USB 2.0 4-port Hub Board.
  • 5 VDC, 2.5A wall power supply
  • USB cable (A-B)
  • Quick Start Guide booklet.
]]> Fri, 17 Feb 2012 11:30:06 -0600 AN5038 - Migrating From EZ-USB® HX2™ to EZ-USB HX2LP™ http://www.cypress.com/?rID=12978 The HX2LP family is next-generation USB high-speed hubs. This family of hubs includes a two-port hub (CY7C65620) with a single transaction translator (TT), and a 4-port hub with a single TT (CY7C65630). The HX2LP family reduces the power consumption of the HX2 while minimizing the effects on existing designs. This Application Note highlights the difference between the products, and aids the designer in migrating existing designs to the HX2LP family.
 

]]> Thu, 12 Jan 2012 00:45:49 -0600 AN49150 - Schematic and Layout Review Checklist for HX2LP http://www.cypress.com/?rID=34185 Introduction

The Cypress CY7C65620 and CY7C65630 USB 2.0 hubs are high performance, low cost solutions for USB. The CY7C656xx USB 2.0 hubs integrate 1.5 kO upstream pull-up resistors for host notification. All downstream 15 kO pull-down resistors and series termination resistors are also integrated by the hubs on all upstream and downstream D+ and D- pins. This results in system cost optimization by providing built in support for the USB 2.0 specification.

]]> Tue, 27 Dec 2011 04:23:39 -0600 EZ-USB™ HX2LP high-speed USB 2.0 hub controller photo http://www.cypress.com/?rID=14820 Cypress's EZ-USB™ HX2LP high-speed USB 2.0 hub controller is the newest member of the low-power EZ-USB LP family. It is optimized for cost-sensitive applications including standalone hubs, monitors, docking stations, keyboards, motherboards and more.

The EZ-USB HX2LP is USB-IF and Windows® Hardware-quality lab (WHQL)-compliant and is available in four-port (CY7C65630-56LFXC) and two-port (CY7C65620-56LFXC) options. The device integrates many external passive components, such as pull-up and pull-down resistors, along with gang port power control to reduce the overall bill-of-materials required to implement a hub design. The EZ-USB HX2LP, which supports bus-powered and self-powered modes, is available in a small form factor 56-pin QFN package that is backward compatible with Cypress's TetraHub™ controller.

To download a high-resolution jpeg image of the EZ-USB HX2LP controller, click the "download" link below.

]]> Tue, 18 Oct 2011 11:07:59 -0600 Programming the EEPROM for the CY7C65640B/30/20 http://www.cypress.com/?rID=31923 The EEPROM can be read or written using vendor commands unique to the CY7C65640B/30/20. These vendor commands are in the data sheet and can be used by any programs configured with them. The reference design does supply a program which allows the writing or reading of the EEPROM. Please see the web page www.cypress.com and select reference designs for USB hubs and you will find a copy of the program.

If you program the parts using a separate EEPROM programmer, please inquire with the EEPROM programmer's vendor for further information on how to program the EEPROMs.

]]> Mon, 03 Oct 2011 00:38:41 -0600 4602B reference design kit http://www.cypress.com/?rID=31920 The CY4602B Tetrahub USB 2.0 4 Port Hub Reference Design Kit provides all materials and documents needed to move rapidly into production. The reference design kit includes

(1) Board schematics
(2) Bill of materials
(3) Gerber files
(4) Orcad files
(5) Key applications notes
(6) Product description.
(7) The CY7C656xx Data sheet
(8) USB to SPI EEPROM programming utility

]]> Mon, 03 Oct 2011 00:27:18 -0600 Bus powered device http://www.cypress.com/?rID=35114 If all these USB devices are used at the one time they would need 1102mA of power but the total provided by the motherboard USB is only 500mA. The only way to use many USB devices at once is to get a Powered USB hub.

A powered USB hub uses 0mA (from Bus) and has up to 5000mA available. If you want to or need to use many USB devices at a time, you have to get a powered hub. Some devices like scanners, even on their own need a powered hub. They can run off the motherboard, but it is not recommended if they use over 400mA. Some devices can also be plugged directly into power and use self-power mode rather than using the bus-power provided by the motherboard. You could check to see if this is an option for any devices you use.

]]> Mon, 26 Sep 2011 02:04:27 -0600 OVRx# pins http://www.cypress.com/?rID=31922 For ports which are configured as present, pull-up resistors external to the hub are required.  There are no internal resistors on the OVRx# pins, so without termination resistors the inputs can float can cause a false over current condition.

If you have disabled the port through the configuration control, external resistors are not required but are recommended.  When the port is disabled through the configuration the hub will disable the port and the port status is not reported, but floating inputs can allow noise to be feed into the chip.

The OVR# is an input that can be set to be active low or active high and should be terminated to a state appropriate for the configuration chosen.

]]> Thu, 22 Sep 2011 02:53:40 -0600 Plugging Devices into a Hubs Downstream Ports http://www.cypress.com/?rID=33437 USB devices have two power ratings, low power 100mA or less, and high power, >100mA (500mA).Each port coming out of the root hub of your PC supplies 500mA. When you connect a bus-powered hub, the hub controller requires 100mA and each downstream port is supplied 100mA. Therefore you are only allowed to connect low power devices downstream of a bus-powered hub.To connect high power devices downstream of a hub, the hub must be self powered, not bus powered. This will allow each port of the hub to have 500mA. As well, when you connect a hub or USB composite device downstream of another hub, the first hub must be self-powered.





 

]]> Fri, 16 Sep 2011 04:44:19 -0600 Moisture Sensitivity Level (MSL) of Cypress Parts http://www.cypress.com/?rID=54061 If you know the Cypress part number: 

1. Go to www.cypress.com.  On the top right, you will see a “Keyword / Part Number” search box (adjacent to “Contact Us.”) 

2. Select the “Part Number” tab above this text box.

3. Type the exact part number, for example CY8C29466-12PVXE.

4. The part number will be listed in the search results page.

5. Click on the part number link (1st column starting from the left). This will open a new web page.

Moisture Sensitivity Level (MSL) can be found by clicking the “Quality & Pb-free Data” link on the top, or by just scrolling down to the Quality & Pb-free Data” section about half way down the page.

All other Quality information for this part number (e.g., RoHS compliance, Lead/Ball Finish, Qualification Reports, IPC reports) can also be found on this web page. 

In case of any questions, or if the information is not available for a particular part number, please create a support case at www.cypress.com/support

If you do not know the Cypress part number: 

1. Go to www.cypress.com.  Browse the different products (“Products” tab on the top navigation menu) by family.

2. Once you choose the relevant product family (e.g., “Clocks and Buffers->Clock Distribution,” “Memory->FIFOs”), scroll down the particular page to get to the “Parametric Product Selector.”

3. Use this tool to find the part number by function/feature, and click on the part number you are interested in. This will lead you directly to step # 5 above.

]]> Thu, 08 Sep 2011 21:22:46 -0600 AN5044 - EZ-USB Hubs(CY7C656XX) PCB Design Recommendations http://www.cypress.com/?rID=12976 This application note presents recommendations for designing with the Cypress Semiconductor CY7C65630 and CY7C65620 components. Techniques for high-speed design must be applied to circuits using these components. Due to the packaging and high performance characteristics of the hub chips, it is recommended that applications consider the PCB thermal design.

Compatible development kits include EZ-USB HX2LP(TM) USB 2.0 2-Port Hub Reference Design Kit CY4605 and EZ-USB HX2LP(TM) USB 2.0 4-Port Hub Reference Design Kit CY4606.

The appnote applies to Tetrahub, CY7C65640A as well.

]]> Mon, 05 Sep 2011 09:26:49 -0600 What are the crystal requirements for the CY7C65620 / CY7C65630 / CY7C65640B hubs? http://www.cypress.com/?rID=31915 Below are the crystal requirements for the CY7C65620 / CY7C65630 / CY7C65640B:

Frequency: 24 MHz
Operating Mode: Fundamental mode,parallel resonant
Frequency Stability: ±500 ppm
Series Resistance: ≤60 ohms
Load Capacitance: 12 pF
Drive Level: 500 uW

External load capacitors should be 12 pF.  We frequently use ±100 ppm crystals to improve the signal quality of the eye diagram.

]]> Mon, 29 Aug 2011 03:40:07 -0600 How should the RESET pin be configurated on the CY7C65640B/30/20? http://www.cypress.com/?rID=31930 The reset pin should be configured to be a valid low signal (≤ 0.8 volts) for at least 1.9 msec.It is normally tied to VCC through a 100K resistor, and to GND through a 0.1-μF capacitor

This requirement comes from several items. The first requirement is the startup time of the crystal. This time period depends on the crystal and can consume up to 1.7 msec. Typically, most crystals will require around 1 msec. Once the oscillations have started an additional 200 usec is required to initialize the CY7C65640B, CY7C65630 or CY7C65620. After the reset is released the hub will delay USB function for an additional 3 msec. This, period is to give the crystal enough time to stabilize its frequency of oscillation.

]]> Mon, 29 Aug 2011 01:51:56 -0600 Can I use the default VID/PID and default descriptors to avoid the need for an external EEPROM ? http://www.cypress.com/?rID=31918 You do not need an external EEPROM for the hub to operate. The hub will enumerate with the default VID/PID of 0x04B4/0x6560. This configuration can be used for test/development purposes.

However, for production, you will need your own VID/PID in order to pass USB compliance and get the hub certified. You can configure the hub to use your VID/PID in one of two ways:

  1. Add an external EEPROM to your design. The external EEPROM will be programmed to provide your VID/PID, descriptors and other hub configuration settings.
  2. Purchase your parts with the internal fuse links set to your VID/PID (this is a factory function only and cannot be done after packaging).

Please see the datasheet for more information.

]]> Mon, 29 Aug 2011 00:52:01 -0600 Replacement part for CY7C65630-56LFXC http://www.cypress.com/?rID=39782 The CY7C65630-56LFXC has been replaced by the part CY7C65630-56LTXC. Both the parts are the same with the only difference in the singulation of the package. Cypress is moving from punch singulation to saw singulation.The saw singulation process is more stable and supports a more reliable supply source for our customers.Also find attached the related PCN.

 


 

]]> Mon, 29 Aug 2011 00:43:01 -0600 How should the unused port (D+ and D-) be configured in the CY7C65640B/30/20? http://www.cypress.com/?rID=31921 Downstream D+ and D- have internal 15K pull downs and there series termination resistors on all upstream and downstream D+ and D- pins.These unused ports  (D+/D-) lines can be left floating. The port power, AMBER, and GREEN LED pins should be left unconnected, and the over current pin should be tied high for the default polarity. The over current pins are input pins are not used if the port is not define in the configuration of the hub.  The only affect of leaving these pins float is  additional noise may be brought into the chip. It is recommended to tie these pins for the default polarity of the overcurrent pins.

 

]]> Mon, 29 Aug 2011 00:34:19 -0600 CY7C66113 be used as a dual device http://www.cypress.com/?rID=31405 No. The only way that  this device allows for two implementations is as a Hub + function, no Function + Function is allowed.

USB does allow for multiple keyboards (in Windows, potential  problems in Mac platform with multiple keyboards)  You would need Two micro's, one to implement each keyboard and USB would take care of noticing the two keyboards seperately on the Host side.

]]> Tue, 05 Jul 2011 02:31:37 -0600 To add more code when no space is available for CY7C65113 http://www.cypress.com/?rID=31452 Please see the listing file.  The following is a snippet from the *lst file. There is some space at the end of the lower 4K block at 0x0F08


  0F08                XPAGEON

  0F08

  0F08            ;------------------------------------------------------------------------

  0F08            ; Upper 4K of EPROM

  0F08            ; Include most hub support routines to the upper half of code space.

                       ; <-  Space of 248 bytes available here

  0F08            ;------------------------------------------------------------------------

  1000                ORG     UPPER_4K

  1000            ;------------------------------------------------------------------------

  1000            ; HUB.ASM

  1000            ;------------------------------------------------------------------------

  1000                XPAGEON

There is about 248 bytes available.  You may insert the additional code at this location.  Please make sure that you do abide by the rules as per the CYasm Guide regarding calling a function across blocks.

]]> Tue, 05 Jul 2011 02:28:14 -0600 When code compiled with the ByteCraft C compiler is loaded into CYDB not all of the debugging features are functional http://www.cypress.com/?rID=31421 The ByteCraft C compiler requires that the following line be in the C code.

#pragma option INSTRUCTIONTIMING +k

This line is required for a complete listing file to be generated which enables all of CYDB's debugging features.

]]> Mon, 27 Jun 2011 22:25:12 -0600 When developing a USB hub with the CY3654+P03 development kit why don't any devices show up in the device manager http://www.cypress.com/?rID=31420 The CY3654D301 application board in the CY3654+P03 development kit is designed with port power switches on board.  The CY7C65113 doesn't have enough I/O to operate the power swithces, therefore power isn't never supplied to Vbus of the downstream ports.

If you jump the DAC[4] and DAC[5] pins on the CY3654D301 board to ground, then the power switches (active low) will supply power to the downstream ports.  This will enable bus powered downstream devices to operate and get recongnized.

]]> Mon, 27 Jun 2011 22:12:57 -0600 Two unknown devices always show up when using the CY3654+P03 dev kit http://www.cypress.com/?rID=31418 The CY3654D301 application board in the CY3654+P03 dev kit only has two physical USB ports.  The other two USB port data signals (D+ and D- for ports 3 and 4) are not brought out and are left floating.  Since these signals are floating the hub may report to the host that there are devices connected.

To fix this the developer can ground the four data dignals which are brought out to TP9, TP10, TP11, and TP12 on the CY3654D301  board.

]]> Mon, 27 Jun 2011 22:01:10 -0600 two "Unknow Device" shown when running the CKHub reference design on my CY3654+P03 board http://www.cypress.com/?rID=31409 The CKHub reference design was written for both the CY7C66013 (48-pin package) and CY7C 66113 (56-pin package). That's why, to be flexible, the design of the new released application board CY3654D301 Rev A provides both 48-pin socket and 56 socket for the user to connect to the development kit through the flex cable.

One of the internal differences between the CY7C 66013 and CY7C66113 is that the CY7C66013 (48 pins) does not have a DAC port which is used in the current protection circuit in the CKHub design. In other words, if the applications board is used as the CY7C66013 (48 pins), the default of the board disables the current protection circuit which powers off the downstream ports. That's the reason why devices connected to the downstream ports are not detected.

A work around solution is to manually connect the DAC[4] and DAC[5] pins to Vss (DAC[4] and DAC[5] are used to enables the current protection circuit which then powers the downstream ports, these pins are located on J4 of the applications board).

Also, in the option.inc file, you should change the number of maximum ports to 3 because only 3 ports are available on the applications board. Note that after modifying the option.inc, don't forget to recompile CKHub.asm.

]]> Fri, 24 Jun 2011 04:08:43 -0600 a ceramic resonator instead of a crystal for CY7C64x13, CY7C65x13 and CY7C66x13 http://www.cypress.com/?rID=31404 The CY7C64x13, CY7C65x13 and CY7C66x13 all require a crystal or an external clock source.  A ceramic resonator does not allow the microcontroller to meet the timing specifications of full speed USB and therefore a ceramic resonator is not recommended for these parts.

]]> Fri, 24 Jun 2011 03:47:01 -0600 some questions for the CY7C65100 VID and PID http://www.cypress.com/?rID=31458 It uses Cypress VID and PID. Yes, you can change the VID and PID. The VID and PID are located in the ROM device_descriptor_table.



  

]]> Wed, 22 Jun 2011 05:10:45 -0600 Can an external clock source be used instead of a crystal? If so what do I do with the unused XTALOUT pin? http://www.cypress.com/?rID=31457 An external source can be used to clock the microcontroller.  The external source should be connected to XTALIN while XTALOUT is left floating.  Grounding Xtalout will effectively short the internal clock to ground.

]]> Wed, 22 Jun 2011 04:51:13 -0600 some information about CY7C65100 http://www.cypress.com/?rID=31454 The CY7C65100 Series is a fixed-function USB hub device.  These are self-contained devices and require no firmware development for your design, thereby reducing the design risk associated with some microcontroller solutions.

For programmable USB Hub part, please look into the CY7C65x13 and CY7C66x13 parts. These devices are One Time Programmable 8-bit microcontrollers with a built-in 12-Mbps USB hub that supports up to seven downstream ports.

]]> Wed, 22 Jun 2011 04:33:21 -0600 My device uses >400 ma (but <500mA) . Is it possible to configure it as a bus powered device? http://www.cypress.com/?rID=31453 If all these USB devices are used at the one time they would need 1102mA of power but the total provided by the motherboard USB is only 500mA. The only way to use many USB devices at once is to get a Powered USB hub.

A powered USB hub uses 0mA (from Bus) and has up to 500mA available. If you want to or need to use many USB devices at a time, you have to get a powered hub. Some devices like scanners, even on their own need a powered hub. They can run off the motherboard, but it is not recommended if they use over 400mA. Some devices can also be plugged directly into power and use self-power mode rather than using the bus-power provided by the motherboard. You could check to see if this is an option for any devices you use.

]]> Wed, 22 Jun 2011 04:27:39 -0600 About CY7C65100, CY7C65103 and CY7C66113 USB hub solutions http://www.cypress.com/?rID=31449 We currently have 3 hub designs:

1-  Fixed function USB 1.1 Compliant 4-port hub (using CY7C65100)

2-  7 ports-hub, compliant to USB 1.1 Spec (using CY7C65103)

3-  Combi Keyboard Hub  (USB 1.1 hub, using CY7C66113)

The CY7C65100 is preprogrammed with a fixed function 4-port hub. The CY7C65100 is intended to be used in the 4-port hub reference design. Developers cannot modify this design. To customize the CY7C65100, developer should obtain the CY7C65100's firmware, customize it and program it on the CY7C65113. The CY7C65113 is a blank part that allows customization.

The firmware preprogrammed in the CY7C65100 is originated from the Keyboard + Hub firmware (CKHub - Composite USB/PS/2 Keyboard + Hub reference design) with the keyboard portion being disabled in the firmware. There's no app note for the CY7C65100 design, just the schematic.

We do not have any reference design for the CY7C65113 because this family is the re-configurable version of the CY7C65100.

We have another hub design, the 7-ports hub, which uses the CY7C65013 part. This design has an app note that discusses the hub firmware architecture. This firmware is the origin of our hub designs (CKHub and then CY7C65100). 

]]> Wed, 22 Jun 2011 03:59:52 -0600 Unused downstream ports of CY7C65x13 and CY7C66x13 full speed USB Hub http://www.cypress.com/?rID=31443 The Dowstream D+ and D- port pins of CY7C65x13 and CY7C66x13 full speed USB Hub needs external pull down 15k resistors if not used or disabled. Please refer to Sample Schematic section of the datasheet where this is illustrated. .

]]> Wed, 22 Jun 2011 02:01:56 -0600 GPIO Glitches on CY7C66013 http://www.cypress.com/?rID=31442 This was a result of a timing problem on the Rev. E part. It was fixed in Revision G of the part.

]]> Wed, 22 Jun 2011 01:49:14 -0600 A USB hub is plugged into USB1.1 host and produces USB2.0 signal rate at the downstream ports? http://www.cypress.com/?rID=31436 Please note that the USB hub is just a repeater. If it is connected to a USB1.1 host, its downstream ports can only get USB1.1 signal rate. In order to get "USB2.0 capable" at the downstream ports, you need to have a USB2.0 hub connected to a USB2.0 host.

]]> Wed, 22 Jun 2011 01:40:31 -0600 Driver for USB Hub controller (CY765100,CY765113 and CY765013) http://www.cypress.com/?rID=31439 No, the CY765100,CY765113 and CY765013 enumerate as a Generic Hub which uses the USB Hub Class Driver that is built in Windows OS. There's no driver needed from the user.

]]> Wed, 22 Jun 2011 01:35:33 -0600 EEPROM for Cypress TetraHub USB hub controller http://www.cypress.com/?rID=29992 Cypress TetraHub USB hub controller can talk to SPI EEPROM that are double byte addressable 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.

]]> Tue, 21 Jun 2011 22:20:47 -0600 Differences between the CY7C65100 and CY7C65113 http://www.cypress.com/?rID=31430 The CY7C65113 has the same pinouts as the CY7C65100. The only difference is that the CY7C65113  is an OTP (one time programmable) part where as the CY7C65100 is not a programmable part. You can program the CY7C65113 with the firmware that runs on the CY7C65100. So there should not be any major changes needed when switching between these two products. The CY7C65100 firmware is based on our CKHub example that is provided with the 'Code Examples' available as part of the CY3654 and CY3654-P03 development kit.

]]> Sun, 19 Jun 2011 23:56:32 -0600 Compliance compatability of the USB Hub CY7C65113 http://www.cypress.com/?rID=31429 Yes, you can connect a USB 2.0 compliant device to a USB 1.1 compliant hub. USB 2.0 compliant devices are backwards compatible with USB 1.1 devices. The USB 1.1 is an old revision of the USB specification. USB 1.0 and 1.1 are part of the USB 2.0 specification but, the 2.0 version of the specification, has added high-speed USB as an option.

]]> Sun, 19 Jun 2011 22:21:34 -0600 Emulator feet and Programming adapter for 56-QFN device CY7C66113 http://www.cypress.com/?rID=31427 The CY7C66113/CY7C66113C 56-QFN part does not have an emulator feet or programming adapter that is provided by Cypress. For emulation purposes, please use the 56-SSOP feet initially and then migrate to the 56-QFN. 

There are 3rd party programmers that provide programmers for the 56-QFN 66113 Cypress part:

BP Microsystems - The device appears as CY7C66113-56LFC.

DataI/O and MQP Electronics also support the CY7C66113 devices. Please contact them directly regarding adapters/programmers for the QFN part.

]]> Sun, 19 Jun 2011 22:13:15 -0600 Does the code given for EEPROM connected with CY7C65620 and CY7C65630 works with CY7C65640A? http://www.cypress.com/?rID=31426 No, the hub part CY7C65620 and CY7C65630 can work with D0, D2 and D4 load but device CY7C65640A can work only with D0 and D2 load. Also the format of D2 load of the devices is not same with the format of D2 load of CY7C65640A. So, in order to make the EEPROM contents of CY7C65620 and CY7C65630 part to work with CY7C65640A the bytes needs to be jumbled up, for example the number of active ports in D2 load of CY7C65640A is at byte number 5 but in CY7C65620 and CY7C65630 part it is byte number 8. So, the device needs to be configured according to their Load Descriptor.

]]> Sun, 19 Jun 2011 22:05:20 -0600 Difference between CY65113, CY65013 and CY65100 USB Hubs http://www.cypress.com/?rID=31424 The CY65100 is preprogrammed with a fixed function 4-port hub. The CY65100 is intended to be used in the 4-port hub reference design which is provided by Cypress, free of charge. In other words, developers cannot modify the firmware of this reference design.

On the other hand, the CY65113 is a blank part. Using one of the hub reference firmware, developers can customize their hub design and program it on the CY65113.

The CY65013 is also a blank part, but it support up to 7 port hub application while the CY65113 can only support 4 port hub application. The CY65013 and CY65113 allow customization.

]]> Sun, 19 Jun 2011 21:47:43 -0600 When I run the CY3654 emulator, why does the mouse cursor starts moving all over the screen? http://www.cypress.com/?rID=31419 The CY3654 emulator has some selftest code already programmed into it.  If you do not download your own HEX file then the emulator will default to the selftest code.

The selftest code is what Cypress refers to as the "logo" code.  It is basically mouse firmware that moves the cursor really fast spelling "USB" (most of the time it doesn't look like it spells USB though).  As a mouse this code will enumerate as a standard HID device and you can view it as such in the device manager.

To stop the mouse movement, unplug the USB cable.  Then try downloading your HEX file again.

]]> Sun, 19 Jun 2011 21:22:25 -0600 TetraHub BUSPOWER pin tied to 5V http://www.cypress.com/?rID=29996 If the BUSPOWER pin is tied high (pulled up to 5V), the device will not be able to detect the presence of VBUS. So even when the hub device is not plugged into the host, the hub will have enabled the pull up on the D+ which is not legal. You must have the BUSPOWER pin connected to VBUS in order to detect the connect and disconnect event.

Please note that as per section 7.1.5.1 of the USB 2.0 specification, the voltage source on the pull-up resistor must be derived from or controlled by the power supplied on the USB cable such that when VBUS is removed, the pull-up resistor does not supply current on the data line to which it is attached.

Section 7.2.1 of the USB 2.0 specification states that devices may not provide power to the pull-up resistor on D+/D- unless VBUS is present (see Section 7.1.5). When VBUS is removed, the device must remove power from the D+/D- pull-up resistor within 10 seconds. So if the BUSPOWER pin is tied high (pulled up to 5V), the hub will consider the device to be in a connected state even though it is not plugged into the host. And the hub will have enabled the pull up on the D- which is not legal as explained above. You must have the BUSPOWER pin connected to VBUS in order to detect the connect and disconnect event and disable/enable the pull up on D+ accordingly.

]]> Sun, 19 Jun 2011 21:15:00 -0600 Tetrahub Source Code http://www.cypress.com/?rID=29995 The TetraHub is a fixed function part.  It is not a programmable part.  It does not require any code to be loaded in it as it is a fixed function hub device. The part can be configured (VID/PID/DID, number of ports available, number of removable versus non-removable ports, etc) using  an external SPI EEPROM.  Please refer to Configuration Options section of the TetraHub datasheet for further information on using an EEPROM to configure the part. As far as the host end is concerned, the driver to support the hub functionality is included in the OS. Hence you do not need to develop your own driver as it uses the hub class driver included with the OS. 

]]> Sun, 19 Jun 2011 20:56:00 -0600 Higher Power consumption of TetraHub when in unconnected powered state http://www.cypress.com/?rID=29994 When the hub is connected to the host and there are no devices plugged into the downstream ports (no bus activity in the downstream ports), the host will issue a suspend request and the hub will be suspended. In suspended state the TetraHub will draw about 100 uA as specified in DC Electrical Characteristics section of the TetraHub Datasheet. Hence you see a drop in power consumption when plugged into the host.

Section 11.6.3.4 of the USB 2.0 Spec states the following
"Suspend
This state is entered when:
-The 3 ms timer expires in the ReceivingJ "

This J state for a continuous 3 ms is interpreted as a suspend signal by the USB device. Having the device unplugged may not (most likely not) cause the hub internal logic to detect a suspend signal. It is the lack of activity and a constant IDLE (J) state that signals a suspend event to the device which in turn causes the hub to go into low power mode.

When the TetraHub is not connected to the host but is in a powered state, the USB datalines D+ and D-are floating. The Hub must detect a suspend signal (J state for about 3 ms) in order for it to go into low power mode. Since the D+ and D- are not in a driven state (J), the hub does not see a suspend signal, and it does not go into low power mode.

]]> Thu, 16 Jun 2011 00:19:21 -0600 SPI Interface with TetraHub http://www.cypress.com/?rID=29988 No. The TetraHub is a fixed function device and is the master. It can talk to an external EEPROM using certain protocols as specified in the SPI EEPROM datasheet. Note that during reset the SPI lines are in a driven state and cannot be driven by any external processor and hence cannot be used to program the TetraHub.

]]> Wed, 15 Jun 2011 22:23:49 -0600 Multiple USB devices connected to hub at the same time or during power-up http://www.cypress.com/?rID=29979 Here in the case of power-up of the hub with multiple USB devices connected, first the hub enumerates. Then the hub enumerates the devices one by one through appropriate status change interactions with the host. In the case of multiple USB devices connected at the same time as well the hub enumerates the devices one by one through appropriate status change interactions with the host. Here the hub takes care that no more than one device takes address zero at a time.

]]> Wed, 15 Jun 2011 22:07:31 -0600 the unused GREEN# and AMBER# LED output pins of TetraHub http://www.cypress.com/?rID=30027 If not using the unused GREEN# and AMBER# LED output pins of TetraHub, you can leave them unconnected.

]]> Wed, 15 Jun 2011 21:33:12 -0600 What software comes with the Tetrahub reference design kit (CY4602)? http://www.cypress.com/?rID=30022 The TetraHub is a fixed  function hub.  Being a fixed function USB device, there is no risk or added engineering effort required for firmware development.  You do not need to write any firmware for the design. The only programmability is realated to the configuration of the device via an external EEPROM which allows to change the VID, PID and DID of the device and define various other features: EnableOverCurrentTimer/DisableOverCurrentTimer , ActivePorts/RemovablePorts, etc. Please refer to Configuration Options section of the TetraHub Datasheet for further information on this feature.

]]> Wed, 15 Jun 2011 04:30:53 -0600 Input threshold of HX2 BUSPOWER pin http://www.cypress.com/?rID=30003 The input threshold of BUSPOWER pin is about 1.5 V, so when connected to VBUS or any input exceeding the threshold will result in driving the pull up on D+, signalling a connect event. When BUSPOWER pin is connected to 3.3 V, it should work as well.

]]> Wed, 15 Jun 2011 03:56:05 -0600 TetraHub, QFN package overheating issue http://www.cypress.com/?rID=30018 QFN (Quad Flatpack No Leads) package, being a lead free package, the electrical contact of the part to the PCB (Printed Circuit Board) is made by soldering the lands on the bottom surface of the package directly to the PCB. Hence special attention is required to the heat transfer area below the package to provide a good thermal bond to the circuit board. Please refer to the Quad Flat Package No Leads (QFN) Package Design Notes section in the datasheet. You also can  refer to the application note on Surface Mount Assembly of Amkor’s MicroLeadFrame (MLF) Technology on Amkor’s website at this URL: http://www.amkor.com/products/notes_papers/MLF_AppNote.

]]> Wed, 15 Jun 2011 03:49:31 -0600 Default TT Mode of HX2 http://www.cypress.com/?rID=30016 The TetraHub defaults to single TT because at the time of designing HX2 the 2.0 drivers (from Microsoft) were not able to support multiple TT hubs. In order to change the mode to multiple TT, the host must issue a SetInterface Request to the TetraHub. Note that the TeraHub has an option of 0xD2 Load where an external SPI EEPROM is used to set various fileds of the hub descriptor. You may use an EEPROM to set the hub to default to multiple TT mode on enumeration using this 0xD2 load. When the host determines that the hub can indeed support multiple TT, it will send the hub device a Set-Interface request, when the hub will be set to multiple TT Mode.

]]> Wed, 15 Jun 2011 03:09:26 -0600 Win98 Drivers for TetraHub http://www.cypress.com/?rID=30012 Win 98 Drivers are offered by 3rd party vendors that ship the host controller add in cards (ex Orange Micro, Adaptec, etc..) Since the drivers written by third party for Windows 98 are for generic hubs only, the TetraHub will exhibit performance functionality in single TT mode only.

]]> Wed, 15 Jun 2011 02:55:29 -0600 How are muliple Tetrahubs with same VID/PID addressed without having any serial number? http://www.cypress.com/?rID=30009 The VID/PID/DID can be modified from the deafult Cypress VID/PID/DID by using an external SPI EEPROM. A vendor must use his own VID/PID/DID (VID different than the Cypress defaults). The OS assigns a unique adresse to each of the TetraHubs and referes/talks to the device by this address. So a serial number is not really relevant or needed. For hubs, there is no reason for a system other than the OS itself to access them. The OS maintains the device tree in its memory. A user program could "walk the tree" as it is called, polling the OS as to what is connected at each node of the USB device tree. But again, there should really be no reason for any application to do so as the TetraHub is a fixed function.

]]> Wed, 15 Jun 2011 02:18:30 -0600 Any schmitt triggers on TetraHub RESET pin? http://www.cypress.com/?rID=30001 The TetraHub RESET pin is a standard IO. There are no schmitt triggers or other components on it. There are no rise or fall time specs for it.

]]> Wed, 15 Jun 2011 01:45:50 -0600 TetraHub during RESET http://www.cypress.com/?rID=30002 This RESET# pin will reset the entire chip. Everything is reset on RESET#. TetraHub will actually be in an unaddressed, unconfigured state, waiting for a USB bus reset and enumeration. For the states of the IOs, note that most of the resets in the chip are synchronous. So, at power-up, before the clock is running, they really can be unknown. Towards the end of reset, the SPI_SCK should be driving, SPI_SD not. SPI_CS# will be driving as well. The EEPROM is reread.

]]> Wed, 15 Jun 2011 01:43:30 -0600 Suspend current specifications on the CY7C65640 http://www.cypress.com/?rID=29998 The suspend current 100uA has to be without D+ resistor. The host has a 15K ohm pull down and the device has the 1.5Kohm pull up. This gives the voltage of 3.3 volts across 16.5 K ohms, which is 200uA. There is a little bit of difference from this due to the regulator and of course the resistors are without any tolerance. From what we have measured, the pull up current can be as much as 250 uA.

]]> Mon, 13 Jun 2011 05:03:41 -0600 State of TetraHub PWR# pins http://www.cypress.com/?rID=29997 On power-up, the PWR# pins will be driven by the TetraHub, but to unknown states. If the hub sees a bus reset upstream (when plugged into the host), then the hub controller itself will be reset and the PWR# lines will be driven high. Now, if it is disconnected (but the hub is still in a powered state) it will will remain in the previous state (whatever it was at before being unplugged).

]]> Mon, 13 Jun 2011 04:47:49 -0600 Byte 7 of the EEPROM for a 0xD2 load. http://www.cypress.com/?rID=30000 There are two different timers for the overcurrent condition, one for an enabled port and the other for a disabled port. Both these timers are used for making sure when an overcurrent condition occurs, the hub will report it after the time set in bits 0..3 (for disabled port) and bits 4..7 (for enabled port) of byte 7 of the EEPROM. The difference is that an enabled port might lose its configuration information if there is a power glitch, while a disabled port has no such problem. A disabled port will need a bus reset to make it enabled, and this reset should restore its operation. In essence, this is an extra filter for overcurrent conditions.

]]> Mon, 13 Jun 2011 03:51:27 -0600 Is the TetraHub device USB compliant? http://www.cypress.com/?rID=26119 Yes. The TetraHub USB hub silicon has gone through and passed the USB compliance test. This is posted on the USB-IF integrators list (http://www.usb.org/developers/compliance/integrators), Test ID Number : 30000089. Please be informed that each product needs to go through its own compliance tests to get the USB certification. Your hub device will need to pass USB-IF compliance as a seperate USB device.

]]> Mon, 13 Jun 2011 03:18:14 -0600 Can the TetraHub interface with a small (1K/2K) EEPROM? http://www.cypress.com/?rID=26122 The TetraHub does not support EEPROM sizes larger than 4K. The 4K EEPROM 25LC040 was used initially because it was the smallest SPI EEPROM we could find at the time. But ST-Micro and Atmel sell 2K and 1K. Fairchild (and maybe Xicor) also sell 2K. From the look of the datasheet of some of these parts HX2 will work with the 1K and 2K devices, which would waste less memory, and maybe save a few cents. But we have NOT tested and confirmed  these parts. The SPI EEPROM used (and recommended) in the reference design is MICROCHIP 25LC040. TetraHub can interface with the '010s and '020s and '040s due to the read command format being the same. It cannot interface with 8K EEPROM 25LC080.

]]> Mon, 13 Jun 2011 03:10:33 -0600 Are USB Hub drivers standard so that the user need not write a specific USB Hub class driver? http://www.cypress.com/?rID=32931 Yes, Windows includes a standard USB Hub class driver.  As long as your design meets the specifications of the HUB class, you will be able to utilize the Windows built-in HUB class driver.  In this case, you would not need to develop your own driver. The usbhub.sys is the driver that you will be using.  All that you really need to do is have the correct class descriptors so that when your device enumerates it uses this class driver.

]]> Mon, 13 Jun 2011 03:10:13 -0600 Buffer per TT? http://www.cypress.com/?rID=26121 The TetraHub has 4 (4K each) buffers per TT. Enter 4.

]]> Mon, 13 Jun 2011 03:03:15 -0600 TetraHub WHQL Certification http://www.cypress.com/?rID=26123 The TetraHub Reference Design Board (CY4602) passed WHQL certification.

]]> Mon, 13 Jun 2011 02:30:49 -0600 Reliable Enumeration of CY7C656xx Hub with Reset Consideration http://www.cypress.com/?rID=35308 The RESET must have at least the 2 msec after you get valid power. This issue here is to not use an RC network in this type of design. The reason deals with the fact that if you get other power sources on or partly on they leak into the chip and charge the capacitor. This kills the reset. So having a signal which is a dock reset or a reset that is applied whenever the 3.3 volts on the chip is not valid works best. The issue is not so much problems between the VBUSPOWER and the RESET it is a problem of not getting a reset because the design leaks voltages and charges caps. So, if you use a driven reset and it comes after you get valid power on the chip and it is applied for the 2 msec or longer everything should work right.

If the RC circuit is slower than the turn on time then there is a chance that the reset will never be seen because it will rise along with the power up of the part. A correct power on sequence will have the part get stable power then ~10mS later the reset line will go high. So the final RC fvalues depend on the regulator used.

]]> Fri, 10 Jun 2011 05:35:18 -0600 Linux driver for CY7C65630 USB Hub http://www.cypress.com/?rID=51695  

Cypress  does not provide a specific driver of USB Hub for Linux OS.There is no  need to install any drivers for the USB Hub product. The CY7C65630 USB Hub is compliant with USB 2.0 SPEC that will use the built-in Linux drivers. On the http://www.linux-usb.org/ web page it states the the linux's kernel should be at least 2.4.22.
]]> Tue, 31 May 2011 04:40:46 -0600 Programming the EEPROM for the TetraHub http://www.cypress.com/?rID=29985 You need to use a separate EEPROM programmer. Please inquire the vendor where you purchased the EEPROM from for further information on how to program these parts.
 

Related Documents and Links:
BP Microsystems

]]> Thu, 19 May 2011 08:14:05 -0600 Crystal Specification of the HX2 (CY7C65640/CY7C65640A) http://www.cypress.com/?rID=30019 When a 24 MHz (± 0.05%) crystal is used in the design, Cypress recommends that for proper operation the load capacitance of the crystal should be between 20 pF and 33 pF. This affects both the load capacitors and the crystal being used.

]]> Thu, 19 May 2011 07:54:45 -0600 PCB design guide for the TetraHub http://www.cypress.com/?rID=30004 We recommend that you follow the standard guidelines for designing any high speed USB platform. Following are two application notes that you may find useful.

]]> Thu, 19 May 2011 07:50:31 -0600 Microsoft Windows driver support for Multi TT of TetraHub http://www.cypress.com/?rID=30013 Yes, it does. The Microsoft drivers are now available via Windows Update for Windows XP (Service Pack 1) and Windows 2000 (Service Pack 4) OS release.

]]> Thu, 19 May 2011 07:28:44 -0600 Do I really need an EEPROM for the TeraHub? http://www.cypress.com/?rID=30008 As far as the functionality of the TeraHub goes you do not need an EEPROM. The device will enumerate with the default VID/PID of 0x04B4/0x6560.

Although it is not necessary to have an EEPROM for the device, we recommend that you use an EEPROM to have the device enumerate with your own VID/PID. You will need you own VID/PID in order to pass the USB compliance and get the device certified. For this, you will indeed need an EEPROM for to overwrite the default cypress VID/PID with your own vendor VID/PID. Also Along with the option of changing the VID/PID (0xD0 EEPROM load), users also have options (0xD2 load) on setting the number of ports, power consumption etc... Please see the datasheet for more information. This can only be done with an external EEPROM.

You will indeed need an EEPROM for to overwrite the VID/PID with your own vendor VID/PID for passing compliance and have the device certified. Also along with the option of changing the VID/PID (0xD0 EEPROM load), users also have options (0xD2 load) on setting the number of ports, power consumption etc... Please see the datasheet for more information. This can only be done with an external EEPROM.

Various fields of the wHubcharacterestic that defaults to 0 is recommended to be set to 1 and can only be done using the EEPROM. For example:

(1) IllegalHubDescriptor: For GetHubDescriptor request, some USB hosts use a DescriptorTypeof 0x00 instead of HUB_DESCRIPTOR, 0x29. According to the USB 2.0 standard, 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 of 0x00 for this command. Default is 0, recommended setting is 1 which can be set using the EEPROM. See Datasheet section 8.2 for further information

(2) NoEOPatEOF1: This turns off the EOP generation at EOF1 in full-speed mode. Note that several USB 1.1 hosts can not handle EOPatEOF1 properly. Cypress recommends that this option be turned off for general-purpose hubs. Default is 0, recommended setting is 1 which can be set using the EEPROM. See Datasheet section 8.2 for further information

]]> Thu, 19 May 2011 07:23:06 -0600 Unused USB port pins in TetraHub http://www.cypress.com/?rID=30007 The TetraHub downstream USB port D+ and D- have internal 15K pull down. These unused ports D+/D- lines can be left floating. The port power, AMBER, and GREEN LED pins should be left unconnected, and the overcurrent pin should be tied high. The overcurrent pins are input pins and they should not be left floating. They need to be tied high.

]]> Thu, 19 May 2011 07:18:13 -0600