MICROCHIP USB57 Series Devices
Especificacións
- Product Name: USB57xx Devices
- Manufacturer: Microchip Technology, Inc.
- Author: Andrew Rogers
INTRODUCIÓN
This document provides information that helps users start designing with Microchip USB57xx products. It covers select-ing an appropriate device within the device family, device configuration requirements, driver availability, as well as the support and design resources available.
Seccións
This application note discusses the following topics:
- Section 2.0, Product Selection
- Section 3.0, Special Features
- Section 4.0, Configuration
- Section 5.0, Additional Support and Design Resources
- Section 6.0, Contacting Support
Referencias
The USB57xx products have a wide range of supporting documentation and collateral that can be used to assist with the design and implementation process. See Table 1.
TÁBOA 1: USB57XX SUPPORTING DOCUMENTS
| Categoría | Título | Descrición |
| Schematic and PCB Design Guidelines | USB5734 Hardware Design Checklist (DS00002968C) | Step-by-step design guidance for USB5734 devices. |
| USB5744 Hardware Design Checklist (DS00002970B) | Step-by-step design guidance for USB5744 devices. | |
| USB5742 Hardware Design Checklist (DS00002969B) | Step-by-step design guidance for USB5742 devices. | |
| AN26.2 Implementation Guidelines for Microchip’s USB 2.0 and USB 3.1 Gen 1
and Gen 2 Hub and Hub Combo Devices |
Contains a wide range of general details for USB hardware design. Schematic and layout guidance is provided which is generally applicable to any kind of USB (or similar high- speed protocols) design. | |
| Notas de aplicación | AN1903 – Configuration Options for the USB5734, USB5744, and USB5742 | Provides the device register map and information on how to program a USB57xx device. |
| AN1905 – USB Battery Charging with the USB57x4 Hub Controller Family | Contains a description of the USB battery charging operation of USB57xx downstream ports. | |
| AN5003 – Debugging USB3 Link Issues on Microchip USB3 Hubs | Features general guidelines for understanding link issues and the tuning parameters that can be tried to improve results. |
| Categoría | Título | Descrición |
| AN4767 – USB5734 FlexConnect Operation | Details FlexConnect principles of operation, how to control FlexConnect, and system design considerations. | |
| AN1997 – USB-to-GPIO Bridging with Microchip USB 3.1 Gen 1 Hubs | Provides technical description and usage guidelines for the USB-to-GPIO feature. | |
| AN1998 – USB to I2C Bridging with Microchip USB 3.1 Gen 1 Hubs | Provides technical description and usage guidelines for the USB-to-I2C/SMBus feature. | |
| AN1999 – USB to SPI Bridging with Microchip USB 3.1 Gen 1 Hubs | Provides technical description and usage guidelines for the USB-to-SPI feature. | |
| AN2000 – USB to UART Bridging with Microchip USB 3.1 Gen 1 Hubs | Provides technical description and usage guidelines for the USB-to-UART feature. | |
| AN2050 – Disabling USB 3.1 Gen 1 Portion of Downstream Ports on Microchip USB57x4 Hubs | The Microchip USB57x4 family of 4-port USB Hubs allows for the USB 3.1 Gen 1 PHY associated with any of the down- stream-facing ports to be disabled via OTP (One-Time Programmable) configuration. | |
| Microchip USB57xx USB Type-C Applications | The USB57xx family of devices does not support USB Type- C® natively, but can be used within a USB Type-C application with external circuitry. This document provides guidance
e examples. |
SELECCIÓN DE PRODUTOS
The USB57xx devices are available with several port configurations and varying feature sets. The end-system integrator must select the device which best accommodates the interfaces that are required for their specific end system while minimizing package size.
Table 2 displays the maximum interfaces supported by each device. Note that it is not possible to enable all of these interfaces at once as the devices are pin-limited. For each application, the programmable pin options should be closely examined to determine the best mix of interfaces that can be supported concurrently for each application.
TÁBOA 2: USB57XX FAMILY OF DEVICES COMPARISON
| Dispositivo |
Paquete |
Revisión de silicio |
Características | |||||
| Upstream Port Configuration | Portos abaixo | Hub Feature Controller | Bridging Features | FlexConnect Support | BC1.2
Apoio |
|||
| USB 5734 | 64 QFN | B | Tipo B | (4x) USB3.2 Gen1 USB
Portos tipo A |
Activado | GPIO, SPI, I2C/SMBus, UART | Port 1 Only | All Down- stream Ports |
| USB 5744 | 56 QFN | B | Tipo B | (4x) USB3.2 Gen1 USB
Portos tipo A |
Activado | GPIO, SPI, I2C/SMBus, UART | Ningún | All Down- stream Ports |
| USB5744B (X01) | 56 QFN | B | Tipo B | (4x) USB3.2 Gen1 USB
Portos tipo A |
Desactivado | Ningún | Ningún | All Down- stream Ports |
| USB5742B | 56 QFN | B | Tipo B | (2x) USB3.2 Gen1 USB
Portos tipo A |
Activado | GPIO, SPI, I2C/SMBus, UART | Ningún | All Down- stream Ports |
| USB5742B (X01) | 56 QFN | B | Tipo B | (2x) USB3.2 Gen1 USB
Portos tipo A |
Desactivado | Ningún | Ningún | All Down- stream Ports |
CARACTERÍSTICAS ESPECIAIS
The Hub Feature Controller
The Hub Feature Controller is an embedded device internal the to hub used to handle many special features. These include runtime register read and write, handling FlexConnect commands, bridging features, and OTP memory pro-gramming and reading.
The Hub Feature Controller uses a generic USB device class controllable through the WinUSB driver on Windows® an dlibusb on Linux®.
The USB5734 always enables the Hub Feature Controller by default (end-system integrators can optionally disable it).
The USB5744 and USB5742 devices have ordering options for Hub Feature Controller to be enabled or disabled by default. These part numbers end in “X01.” (See Table 2.)
Bridging Features
Bridging features allow a USB host to interface with embedded devices through the hub device. The USB host communicates to the internal Hub Feature Controller device embedded inside the USB hub to send or receive data through on e of the bridge interfaces.
The bridge interfaces supported are:
- GPIO
- SPI of up to 60 MHz
- I2C/SMBus of up to 400 kHz
- UART of up to 115.2 kHz
Some of the bridging features can be used in parallel together, while others are mutually exclusive. Consult the specific USB57xx device data sheet for details.
The GPIO, SPI, I2C/SMBus, and UART use the generic USB device class, which is controllable through the WinUSB driver on Windows and libusb on Linux.
End-system integrators are required to write their own end applications to make use of the bridging features. Microchi p provides two software resources to make the software development easy:
- Windows-only: MPLAB® Connect Configurator
MPLAB Connect® Configurator includes a GUI for quickly trying out bridging features. A DLL package is also included for controlling the bridging features from your own application. - Linux-only: Linux Application Code Examples
This package includes numerous example applications which leverage the standard libusb Linux library for USB device control. This code can be used as a reference for designing your own end applications.
FlexConnect (USB5734 Only)
- USB5734 supports FlexConnect of both the USB2 and USB3 communication channels with downstream port 1.
- FlexConnect can be controlled via a USB command to the Hub Feature Controller device using direct FlexConnect register manipulation through I2C/SMBus or by GPIO control. GPIO requires configuration to be set to ‘Configuration 2 – FlexConnect Mode’ via the CFG_STRAP hard strapping pin. Only one control method should be used at a time to avoid control conflicts leading to non-deterministic behavior.
- FlexConnect requires careful design choices since there is no standard use case for this feature. A common way to use the feature is to allow two different hosts to alternatively control the USB hub and all downstream devices. Only one hu b can control the hub and device tree at a time, and the full device tree must be fully re-enabled each time host control is haded off.
- Another implementation involves “swapping” a host-device relationship wherein the original USB host to the USB57xx becomes a device, and a component which was operating as a device switches to Host mode. This requires careful consideration to properly control three separate system components during role changes.
- Common issues include determining what connectors and cables to use. For example, when a Type-A port is used on a downstream port and FlexConnect is enabled for that downstream port, connecting a new host to that “Flex Port” requires a non-standard Type-A-to-Type-A cable. In addition, there could be VBUS back-drive problems (and the potential to trigger overcurrent alerts) if both ends of the cable supply 5V VBUS.
- Supporting FlexConnect with USB Type-C ports can be exceptionally challenging as Type-C VBUS, VCONN, and CC control must be well thought out and managed appropriately to ensure reliable connections can be made while flexed.
- Refer to AN4767 – USB5734 FlexConnect Operation for detailed design guidance.
BC1.2 Battery Charging
All USB57xx devices support BC1.2, which is a USB-IF maintained standard for allowing portable devices to charge up to 1.5A from 5V VBUS.
A BC1.2 handshake is always initiated by the portable device. It is achieved through short pulses on the D+ and D–USB2 data lines. The hub downstream port responds accordingly to complete the handshake, depending on which mode of operation the hub port is in.
Dedicated Charging is a charge-only profile and only operates when the USB57xx is not connected to a USB Host.
Charging Downstream Port mode allows for charging and data, and it operates when the USB57xx is connected to a USB host when BC1.2 CDP mode is enabled.
The BC1.2 hardware configuration straps on USB57xx enable both CDP and DCP mode.
CONFIGURACIÓN
Default Factory-Programmed Configurations
The USB57xx devices have many configuration features and several programmable function pins available which enable different I/O capabilities. Each device has unique configuration options selectable via CFG_STRAP hardware pin, which makes default programmable function pin selections based on the most anticipated use cases for the device. Each device also includes factory-programmed configuration settings and may also include factory programmed FW patches.
Additional End-System Integrator Configuration
It is expected that end-system integrators will reconfigure the USB57xx to meet their individual system needs. Peripherals and each pin function can be selected individually to customize the solution. Only changes from the default factory preconfigured settings need to be made.
The following methods for end-system-integrator configuration are flexible:
- OTP
- Serial (I2C/SMBus) from embedded serial controller
- Upstream USB host control during runtime
Additionally, a separate firmware image can be executed from an SPI Flash memory device in special cases where custom firmware implementation is needed. Microchip develops all customized firmware images based on special, case-by-case business negotiations. When executing the firmware image from an SPI Flash device, internal OTP memory configuration is ignored. Instead, an equivalent configuration mechanism is also executed through and stored within the SPI Flash memory device.
Configuration details and the device register map located in the AN1903 – Configuration Options for the USB5734, USB5744, and USB5742 are available on the USB57xx product page on Microchip.com
Each configuration stage is optional. Generally, end-system integrators select only one method of configuration. Any individual settings modified in later configuration steps overrides register changes made in previous steps. See Table 3 for more information on the configuration methods.
TÁBOA 3: NOTES ON CONFIGURATION METHODS
| Compoñente | Notas |
| OTP | The USB57xx devices have 8 kB of OTP configuration memory. The factory-programmed OTP con- figuration load only occupies a small fraction of this total available memory (i.e.: typically <1 kB) to ensure sufficient space is left for end-system integrator use. The end-system integrator can program OTP memory a number of times until the OTP memory is completely filled. Only registers which are specifically manipulated by the OTP configuration are impacted. OTP is loaded sequentially in the order it was programmed, so if the same register(s) are manipulated multiple times, the last sequentially programmed setting(s) will take effect. |
| Flash SPI | An external SPI Flash is an option for special use cases that require a custom firmware image. Custom firmware images are developed by Microchip by a special agreement with an end-system integrator. The SPI Flash memory size depends on the firmware image size needs, but 1 MB is generally sufficient for most customized firmware needs. |
| Configuración en serie | Serial Configuration is enabled through hardware pin strap options. When enabled, the USB57xx device waits indefinitely for the I2C/SMBus or SPI master to configure the device and issue a special command to enter the Runtime phase. The I2C/SMBus or SPI controller will be able to read back any configuration settings already modified by OTP or EEPROM. |
Ferramentas de configuración
Microchip maintains several tools which can be used for configuring a USB57xx. See Table 4.
TÁBOA 4: USB57XX CONFIGURATION TOOLS
| Ferramenta | Sistema operativo compatible | Capacidades |
| MPLAB Connect® Configurator GUI | Windows® |
|
| MPLAB Connect Configurator Command Line Interface (CLI) Tool | Windows |
|
| MPLAB Connect Configurator (DLL) Library | Windows | Enables users to develop their own application that can program/read back configurations, manipulate register settings, control FlexConnect, and control bridging features. |
| Linux® Appli- cation Code Examples | Linux | Includes numerous sample applications that leverage the standard libusb capabilities of Linux to program/read back configurations, manipulate register settings, control FlexConnect, and control bridging features. |
Nota 1: The VSM Filter allows the Windows host to send vendor-specified commands to the hub endpoint directly. This is typically blocked by Windows OS. The VSM commands to the hub are required for communicating with a Microchip Smart Hub which has its internal Hub Feature Controller device USB endpoint disabled. If MPLAB Connect Configurator detects a Microchip Smart Hub, but the Hub Feature Controller is not present, it will attempt to re-enable the Hub Feature Controller temporarily (while the tool is running) via a VSM command. With the Hub Feature Controller device temporarily enabled, MPLAB Connect Configurator can then carry out the various features supported by the tool (such as programming, register read/write, etc.). Also note that if the VSM command support is internally disabled via the hub configuration (i.e.: previously set in OTP) by an end system integrator, this command will not be successful and the user will not able to read back configuration or program new ones.
The USB57xx family devices use standard USB-IF defined device classes. This means that no customer or special drivers are required to operate the device.
ADDITIONAL SUPPORT AND DESIGN RESOURCES
Users may access Microchip’s wide range of hardware and software design tools that support projects with the USB57xx. Most items in Table 5 are available from the device product page. Items that are not linked to the product page are available upon request through a support case (see https://www.microchip.com/en-us/support).
| Categoría | Elemento | Descrición |
| Hardware de avaliación | EVB-USB5734 | Evaluation board for the USB5734 device |
| EVB-USB5744 | Evaluation board for the USB5744 device | |
| Ferramentas de simulación | USB3 IBIS-AMI Model | A model of the Microchip USB3 PHY which can be used to simulate PCB performance. Contact your sales representative or submit a support case to request this model. |
| USB3 HSPICE Model | A model of the Microchip USB3 PHY which can be used to simulate PCB performance. Contact your sales representative or submit a support case to request this model. | |
| Ferramentas de software | MPLAB® Connect Configura- tor | Windows-based tools for hub configuration and smart hub features. |
| Linux® USB57xx, 58xx, 59xx ACE Package | Linux-based tools for hub configuration and smart hub features. | |
| USB57xx Firmware and Default Configuration Package | A package of configuration files, firmware patches, and firm- ware images. Configuration files contain details of the default production OTP contents of USB57xx devices. |
CONTACTO CON SOPORTE
For additional support, visit the support section of www.microchip.com. A support case can be submitted online to receive personalized assistance, including product selection support, design guidance, design check services, and troubleshooting.
All end-system integrators are strongly encouraged to make use of Microchip’s free design review servizos: https://www.microchip.com/en-us/support/design-help/design-check-services.
ANEXO A: HISTORIAL DE REVISIÓNS
TÁBOA A-1: REVISION HISTORY
| Data e nivel de revisión | Sección/Figura/Entrada | Corrección |
| DS00006176A (09-16-25) | Lanzamento inicial | |
Información do microchip
Marcas comerciais
O nome e o logotipo de "Microchip", o logotipo "M" e outros nomes, logotipos e marcas son marcas rexistradas e non rexistradas de Microchip Technology Incorporated ou das súas filiais e/ou filiais nos Estados Unidos e/ou noutros países ("Microchip Marcas comerciais”). Pódese atopar información sobre as marcas comerciais de Microchip en https://www.microchip.com/en-us/about/legal-information/microchip-trademarks.
- ISBN: 979-8-3371-2015-7
Aviso Legal
Esta publicación e a información que aparece aquí só poden usarse con produtos Microchip, incluso para deseñar, probar e integrar produtos Microchip coa súa aplicación. O uso desta información de calquera outra forma viola estes termos. A información relativa ás aplicacións do dispositivo ofrécese só para a súa comodidade e pode ser substituída por actualizacións. É a súa responsabilidade asegurarse de que a súa aplicación cumpre coas súas especificacións. Póñase en contacto coa súa oficina local de vendas de Microchip para obter asistencia adicional ou obtén soporte adicional en www.microchip.com/en-us/support/design-help/client-support-services.
ESTA INFORMACIÓN ESTÁ PROPORCIONADA POR MICROCHIP "TAL CUAL". MICROCHIP NON OFRECE REPRESENTACIÓNS OU GARANTÍAS DE NINGÚN TIPO, XA EXPRESA OU IMPLÍCITA, ESCRITA OU ORAL, LEGAL OU DE OUTRO MODO, RELACIONADA COA INFORMACIÓN, INCLUÍENDO PERO NON LIMITADO A NINGÚN TIPO DE GARANTÍAS IMPLÍCITAS DE NON INFRACCIÓN, COMERCIABILIDADE, COMERCIABILIDADE E COMERCIALIZACIÓN. GARANTÍAS RELACIONADAS CO SEU ESTADO, CALIDADE OU RENDEMENTO.
EN NINGÚN CASO MICROCHIP SERÁ RESPONSABLE DE NINGÚN TIPO DE PERDA, DANO, CUSTO OU GASTO INDIRECTO, ESPECIAL, PUNITIVO, INCIDENTAL OU CONSECUENCIAL DE NINGÚN TIPO RELACIONADO COA INFORMACIÓN OU O SEU USO, AÍNDA QUE SE SEXA O CAUSADO QUE SEXA O SEU ADVERTENCIA. POSIBILIDADE OU OS DANOS SON PREVISIBLES. NA MÁXIMA MEDIDA PERMITIDA POLA LEI, A RESPONSABILIDADE TOTAL DE MICROCHIP SOBRE TODAS LAS RECLAMACIONS DE CALQUERA FORMA RELACIONADAS COA INFORMACIÓN OU O SEU USO NON SUPERARÁ O IMPORTE DAS TAXAS, SE HOXE, QUE TIÑAS PAGADA DIRECTAMENTE A MICROCHIP POLA INFORMACIÓN.
O uso de dispositivos Microchip en aplicacións de soporte vital e/ou de seguridade corre totalmente a risco do comprador, e o comprador comprométese a defender, indemnizar e eximir a Microchip de calquera e todos os danos, reclamacións, demandas ou gastos derivados de tal uso. Non se transmite ningunha licenza, implícita ou doutra forma, baixo ningún dereito de propiedade intelectual de Microchip a menos que se indique o contrario.
Función de protección de código de dispositivos de microchip
Teña en conta os seguintes detalles da función de protección de código nos produtos Microchip:
- Os produtos de microchip cumpren as especificacións contidas na súa ficha de datos de microchip.
- Microchip considera que a súa familia de produtos é segura cando se usa da forma prevista, dentro das especificacións de funcionamento e en condicións normais.
- Microchip valora e protexe agresivamente os seus dereitos de propiedade intelectual. Os intentos de incumprir as funcións de protección do código do produto Microchip están estrictamente prohibidos e poden infrinxir a Digital Millennium Copyright Act.
- Nin Microchip nin ningún outro fabricante de semicondutores poden garantir a seguridade do seu código. A protección do código non significa que esteamos garantindo que o produto sexa "irrompible". A protección do código está en constante evolución. Microchip comprométese a mellorar continuamente as funcións de protección do código dos nosos produtos.
FAQ
Where can I find step-by-step design guidance for specific USB57xx devices?
You can refer to documents like USB5734 Hardware Design Checklist, USB5744 Hardware Design Checklist, and USB5742 Hardware Design Checklist for step-by-step design guidance tailored to each device in the USB57xx family.
How can I disable the USB 3.1 Gen 1 portion of downstream ports on Microchip USB57x4 Hubs?
The USB 3.1 Gen 1 PHY associated with downstream ports can be disabled via OTP configuration. Refer to AN2050 for detailed instructions.
Documentos/Recursos
 |
MICROCHIP USB57 Series Devices [pdfGuía do usuario USB5734, USB5744, USB5744B, USB5742B, USB57 Series Devices, USB57 Series, Devices |