SLLSEN9F May   2015  – March 2022 TUSB320

PRODUCTION DATA  

  1. Features
  2. Applications
  3. Description
  4. Revision History
  5. Pin Configuration and Functions
  6. Specifications
    1. 6.1 Absolute Maximum Ratings
    2. 6.2 ESD Ratings
    3. 6.3 Recommended Operating Conditions
    4. 6.4 Thermal Information
    5. 6.5 Electrical Characteristics
    6. 6.6 Timing Requirements
    7. 6.7 Switching Characteristics
  7. Detailed Description
    1. 7.1 Overview
    2. 7.2 Functional Block Diagram
      1. 7.2.1 Cables, Adapters, and Direct Connect Devices
        1. 7.2.1.1 USB Type-C Receptacles and Plugs
        2. 7.2.1.2 USB Type-C Cables
        3. 7.2.1.3 Legacy Cables and Adapters
        4. 7.2.1.4 Direct Connect Devices
        5. 7.2.1.5 Audio Adapters
    3. 7.3 Feature Description
      1. 7.3.1 Port Role Configuration
        1. 7.3.1.1 Downstream Facing Port (DFP) – Source
        2. 7.3.1.2 Upstream Facing Port (UFP) – Sink
        3. 7.3.1.3 Dual Role Port (DRP)
      2. 7.3.2 Type-C Current Mode
      3. 7.3.3 Accessory Support
        1. 7.3.3.1 Audio Accessory
        2. 7.3.3.2 Debug Accessory
      4. 7.3.4 I2C and GPIO Control
      5. 7.3.5 VBUS Detection
    4. 7.4 Device Functional Modes
      1. 7.4.1 Unattached Mode
      2. 7.4.2 Active Mode
      3. 7.4.3 Dead Battery Mode
      4. 7.4.4 Shutdown Mode
    5. 7.5 Programming
    6. 7.6 Register Maps
  8. Application and Implementation
    1. 8.1 Application Information
    2. 8.2 Typical Application
      1. 8.2.1 DRP in I2C Mode
        1. 8.2.1.1 Design Requirements
        2. 8.2.1.2 Detailed Design Procedure
        3. 8.2.1.3 Application Curves
      2. 8.2.2 DFP in I2C Mode
        1. 8.2.2.1 Design Requirements
        2. 8.2.2.2 Detailed Design Procedure
        3. 8.2.2.3 Application Curves
      3. 8.2.3 UFP in I2C Mode
        1. 8.2.3.1 Design Requirements
        2. 8.2.3.2 Detailed Design Procedure
        3. 8.2.3.3 Application Curves
    3. 8.3 Initialization Set Up
  9. Power Supply Recommendations
  10. 10Layout
    1. 10.1 Layout Guidelines
    2. 10.2 Layout Example
  11. 11Device and Documentation Support
    1. 11.1 Receiving Notification of Documentation Updates
    2. 11.2 Support Resources
    3. 11.3 Trademarks
    4. 11.4 Electrostatic Discharge Caution
    5. 11.5 Glossary
  12. 12Mechanical, Packaging, and Orderable Information

Programming

For further programmability, the TUSB320 device can be controlled using I2C. The TUSB320 device local I2C interface is available for reading/writing after TI2C_EN when the device is powered up. The SCL and SDA terminals are used for I2C clock and I2C data respectively. If I2C is the preferred method of control, the ADDR pin must be set accordingly.

Table 7-5 TUSB320 I2C Addresses
TUSB320 I2C Target Address
ADDR pin Bit 7 (MSB) Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 (W/R)
H 1 1 0 0 0 0 1 0/1
L 1 1 0 0 0 0 0 0/1

The following procedure should be followed to write to TUSB320 I2C registers:

  1. The controller initiates a write operation by generating a start condition (S), followed by the TUSB320 7-bit address and a zero-value R/W bit to indicate a write cycle
  2. The TUSB320 device acknowledges the address cycle
  3. The controller presents the sub-address (I2C register within the TUSB320 device) to be written, consisting of one byte of data, MSB-first
  4. The TUSB320 device acknowledges the sub-address cycle
  5. The controller presents the first byte of data to be written to the I2C register
  6. The TUSB320 device acknowledges the byte transfer
  7. The controller may continue presenting additional bytes of data to be written, with each byte transfer completing with an acknowledge from the TUSB320 device
  8. The controller terminates the write operation by generating a stop condition (P)

The following procedure should be followed to read the TUSB320 I2C registers:

  1. The controller initiates a read operation by generating a start condition (S), followed by the TUSB320 7-bit address and a one-value R/W bit to indicate a read cycle
  2. The TUSB320 device acknowledges the address cycle
  3. The TUSB320 device transmits the contents of the memory registers MSB-first starting at register 00h or last read sub-address+1. If a write to the T I2C register occurred prior to the read, then the TUSB320 device starts at the sub-address specified in the write.
  4. The TUSB320 device waits for either an acknowledge (ACK) or a not-acknowledge (NACK) from the controller after each byte transfer; the I2C controller acknowledges reception of each data byte transfer
  5. If an ACK is received, the TUSB320 device transmits the next byte of data
  6. The controller terminates the read operation by generating a stop condition (P)

The following procedure should be followed for setting a starting sub-address for I2C reads:

  1. The controller initiates a write operation by generating a start condition (S), followed by the TUSB320 7-bit address and a zero-value R/W bit to indicate a read cycle
  2. The TUSB320 device acknowledges the address cycle
  3. The controller presents the sub-address (I2C register within the TUSB320 device) to be read, consisting of one byte of data, MSB-first
  4. The TUSB320 device acknowledges the sub-address cycle
  5. The controller terminates the read operation by generating a stop condition (P)
Note:

If no sub-addressing is included for the read procedure, then the reads start at register offset 00h and continue byte-by-byte through the registers until the I2C controller terminates the read operation. If a I2C address write occurred prior to the read, then the reads start at the sub-address specified by the address write.