Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 942 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.

TPS65986: DCD/Port detection complete GPIO?

JoFu10
Intellectual 2385 points

Part Number: TPS65986

Hi,

When we plug in any type of charger, the registers 0x1A and 0x3F change multiple times (goes from non-BC1.2 5V/500mA to DCP, then back before settling as a DCP around 600ms later). Same thing happens with some PD chargers as well.

Since these roles are being reported to different parts of the system while its still changing, the wrong roles could be reported. I didn't see any GPIO event that could represent when the Primary/secondary detection completes.

What is the best way of knowing when the DCP/SDP/CDP detect completes? We currently have a ~600ms timeout to ignore any of the first toggles, but this seems to hacky to be in our final solution.

Also what is the DCD timeout set to on the TPS65986, or does it vary between 300msec to 900msec?

Thanks,

Josh

  • 0
    TI__Mastermind 36751 points
    Hi Josh,

    I am looking into your question and will get back to you as soon as I have a suggestion.

    Thank you,
    Eric
  • 0
    TI__Guru 50120 points
    Hi Josh,

    The FW is not configured to detect the timing of the BC1.2 detection. The only data that the GUI provides regarding the detection is the BC1.2 Detection and BC1.2 status which can be accessed in the Debug Mode under Power Status (0x3f).

    Did you get the timeout range of 300ms - 900ms for the DCD timeout from the datasheet or was it a rough estimate? Just wanted to make sure that the datasheet available is the latest revised.

    Regards,
    Jimmy
  • 0 in reply to Jimmy Hua
    TI__Intellectual 2385 points
    Thanks Jimmy,

    DCD timeout range was from the USB-IF BC1.2 spec labeled T_DCD_TIMEOUT under the Timing Table.

    Is there a register that indicates when a PD contract is done negotiating? They are also seeing 0x1A and 0x3F switch between multiple states before reaching a stable state so they are not sure when to know when PD contracts are done either.

    Josh
  • 0 in reply to JoFu10
    TI__Guru 50120 points

    Hi Josh,

    You can go into the GPIO Event Map(0x5C) and designate the setting of a GPIO for a specific Source PDO negotiation. 

    Regards,

    Jimmy Hua