• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 740 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TPS65982 CC Pin issue .

Tino Pan
Intellectual 300 points
Other Parts Discussed in Thread: TPS65982, TPS6598X-CONFIG, TPS65982-EVM

Dear All ,

We have use the TPS65982 , attached file is my circuit.

I only set the 5V DRP mode about TPS65982 . In system power down , the TPS65982 will correctly identify the DFP type in the insert USB type-C adapter. I have remove adapter and enable system .The TPS65982 can not correctly identify the type in the insert adapter.  I have tried to measure the voltage about CC pin, the voltage is 0V.INET_T413_REV01_20151223_1800 (6).pdf

  • 0
    TI__Mastermind 30310 points

    Pan,

    Can you provide details on the test method used to observe this failure?

    • Step by Step procedure with Ecosystem block diagram (what is plugged in and when?)
    • FW Loaded into SPI Flash for TPS65982 (.bin, .json, & .ctb files generated by TPS6598X-CONFIG Config Tool, Zipped up in 1 folder)
    • Oscilloscope screen shots measuring CC1, CC2, VBUS, and VIN_3V3
      • CC1, CC2, & VBUS must be measured at the Type-C port, and VIN_3V3 is located on header J5, pin 3 of the TPS65982-EVM

    My suspicion is that either:

    1. You say the "system power down", so:
      1. If the TPS65982 system is powered-down then you are in Dead Battery mode needing to boot up as a Sink, then maybe the RPD_G1/G2 pins are not shorted to CC1/2 to support Dead Battery
      2. If the "far-end" system is powered-down on the other end of the Type-C cable, maybe there is no Rd pull-down on the other product for the TPS65982 to detect
    2. The FW is setting the TPS65982 as a UFP-Only with an Rd pull-down resistor on CC1/CC2. If this is the problem & an un-powered accessory is connected, then both CC pins will be stuck at 0V and Type-C detection cannot occur