• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 33 subscribers
  • Views 380 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.

TPS65987D: I have customer questions about the Application Customization Tool for the TPS65987D

Mark Pearson
Genius 12705 points
Part Number: TPS65987D

Please see the attached PPTX file.

Mark P

TPS65987 Application Customization Tool.pptx

  • 0
    TI__Genius 12700 points

    Hi Mark,

    Would it be possible for you to share your configuration project file so that I may take a look at the register settings? Also, do you happen to have any PD logs captured?

    I will take a look at all of your slides and get back to you with a response by Monday.

    Thank you,

    Hari

  • 0 in reply to Hari Patel1
    TI__Genius 12705 points

    Hari,

    I have attached the customer project file.

    Customer response: 

    "Not sure how to capture “PD logs” (or what they even are), but I attached an example project we have been using.  It is not our final version, but something we were using to test theories about how to get into different PDO contracts."

    TPS65987 gpio_test.pjt

  • 0 in reply to Mark Pearson
    TI__Genius 12700 points

    Hi Mark,

    PD logs can be collected using a PD analyzer and they show the communication between two PD controllers to help debug issues. Which GUI version are you using for this project? Your device is the TPS65987DDH, correct? 

    Also, RDO is the Request Data Object as part of a request message. For your PDO question, the TT 1/2/3 refer to the bits for up to 7 PDO's that can be mapped, with 3 being the most significant bit and 1 being the least significant bit. Is there a particular reason the customer wants a PDO for each current range for the same voltages? 

    Thank you,

    Hari

  • 0 in reply to Hari Patel1
    TI__Genius 12705 points

    Hari,

    Customer responses:

    We don’t have a PD analyzer, so won’t be able to get the logs. 

    We are using GUI build version 6.1.1.  Our part is TPS65987DDHRSHR. 

    What is the RDO used for?  Does it just say what was requested vs negotiated?

     I understand TT1 is the LSB, but my question is whether 000b is a valid output of TT1/2/3 or if 001b is the first valid output.  It is unclear since I can setup the PDOs as shown (numbering starts at “1”), but there is a GPIO that can be used for PDO “0”.

    TPS65987D Register setup.pdf

    Mark

  • 0 in reply to Hari Patel1
    TI__Genius 12705 points

    Hari,

    Customer responses:

    We don’t have a PD analyzer, so won’t be able to get the logs. 

    We are using GUI build version 6.1.1.  Our part is TPS65987DDHRSHR. 

    What is the RDO used for?  Does it just say what was requested vs negotiated?

     I understand TT1 is the LSB, but my question is whether 000b is a valid output of TT1/2/3 or if 001b is the first valid output.  It is unclear since I can setup the PDOs as shown (numbering starts at “1”), but there is a GPIO that can be used for PDO “0”.

    2438.TPS65987D Register setup.pdf

    Mark

  • 0 in reply to Mark Pearson
    TI__Genius 12700 points

    Hi Mark,

    Yes, the RDO is simply the request message that the Sink PD Controller sends on which PDO it wants to negotiate from the Source PDO message that was sent by the other PD controller. I would recommend the customer to reference the USB-IF Specification document as well for more detail.

    For the TT, yes 000b is a valid output which refers to the first initial PDO 1. For the TPS65987D, each TTx, refers to the corresponding PDO. For example, to select PDO4, you would use the TT3 event, since in the Transmit Sink Capabilities register it starts with Sink PDO 1.

    Thank you,

    Hari