This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TUSB320: ID and CC1/CC2 status after config mode via I2c

Part Number: TUSB320

Tool/software:

what's the priority of "PORT" pin, "CC1/CC2" pin and "set register via I2C" to controll ID pin?

first scenario is .... set the mode via i2c to DFP or UFP, ID pin and CC1/CC2 will be DFP of UFP status automatically?

second is  ...when a HOST unit conect to TUSB320, after that MCU set MODE register to DFP by I2C, which MODE will be the next?

  • Hi,

    The PORT pin will set the mode of operation by default. You can set the MODE register to override DFP/DRP/UFP when the TUSB320 is in the disconnect state.

    For the first scenario, CC1/CC2 will be set to DFP or UFP depending on the mode you set in I2C if nothing is connected to the type-C port.

    In the second scenario I assume you have a host connected to the type-C port and the TUSB320 is configured as a UFP. If you set the MODE register, nothing will happen, because the 320 is not in the disconnect state.

    Best,

    Shane

  • Will ID pin be change when i set the mode in disconnect state?

    or it's only changed depend on CC1/CC2 in connected state?

  • ID will not change from setting the MODE register in disconnect state.

    ID will change when a connection is made between a UFP and the TUSB320 in DFP or DRP modes.

    For example, if the TUSB320 is configured as a DFP and you connect a UFP (flashdrive, SSD, etc.) to the type-C port, the ID pin will go low. If the TUSB320 is configured as a UFP, then ID will never go low.

    ID is meant to enable/disable the VBUS on the type-C port. You should enable the VBUS when ID goes low and disable the VBUS while ID is high.

    Best,

    Shane