• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 32 subscribers
  • Views 444 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TUSB320LI: CC pin identification error

Jason Fan
Intellectual 1705 points
Part Number: TUSB320LI
Other Parts Discussed in Thread: TUSB320

Hi  Experts:

 

              My customer has an issue about using the TUSB320LI, which is used in one of their mobile phone projects.

              When it recognize the UFP mode , the TUSB320 could identify the CC1 or CC2 correctly to make sure the TYPE -C Cable is inserted by the forward or the

reverse direction .

             However, when it in the DFP mode (OTG) mode, the TUSB320 only report the CC1 no matter forward or reverse insertion. The read value of REG09 is always 0x40.

             Could you please advise ? Thanks!

       

  • 0
    TI__Mastermind 36085 points

    Hello Jason,


        Please share the schematic for review, also the customer can measure the voltage on the CC pins when there is no connection and make sure that you have a the RP pressent in both pins (customer should see a pull-up voltage). Also please try to reproduce the issue with more than one cable and more than one device. Some customers got confused with the cable orientation, because they flipped the Type-C cable on the opposite side (UFP in this case), only a flip of the cable on the TUSB320's connector will cause a orientation change, so please make sure the customer is testing the same cable side.


    Regards,

    Diego.

  • 0 in reply to Diego Cortes
    TI__Intellectual 1705 points

    Hi  Diego:

                    We check the status of the CC1/CC2 pin by the meter , and found it's work normally (In DFP mode , the CC pin pull low )

                  This issue has been resolved caused by their software processing error.  Thank you for your support.