• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 32 subscribers
  • Views 291 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.

TPS65982: Modifications to the TIDA-01243

Mark Pearson
Genius 12705 points
Part Number: TPS65982
Other Parts Discussed in Thread: TIDA-01243, , TUSB8041, TPS65987D

My customer is using the TIDA-01243 as a starting point and is adding an additional HDMI port as well as replacing the NRND TPS65986 with the TPS65982.

Here are the customer questions... please contact me for the Block diagram/schematics. I will not post them here.

    •  A fundamental question on the U52 (currently TPS65986).  The way I understand this IC is that he controls the Type C USB by identifying insertion/de-assertion, cable orientation, and then manages power negotiations.  The way it does all of this is using the CC1/CC2 pins.  For power negotiations though, does it communicate with the host (PC) which then manages the power of the system?  I guess what I am getting hung up on is when does it charge with 20V/5A, 20V/3A, or 5V/3A, etc.?  U52 is not connected to U24 (TUSB8041), so how can it manage charging?
    • I am replacing U52 with TPS65982 which has a few more signals that I think I terminated properly.  I am leaving the HV Gates open and so then this becomes a drop in replacement, correct?  And this is the right move, correct?

  • Eval board audio doesn’t work - looking to replace with the PCM2912A because a MIC input is needed. But would like to know why the TIDA-01243 audio does not work.
  • USBA port loses charging capabilities when USB C connection is lost.
  • Programming (TIDA-01243 ICs) – Do we have to worry about programming anything?  How to do it? Etc.

Thanks!

  • 0
    TI__Mastermind 27515 points
    Hello Mark,

    Thank you for posting your question here on E2E.

    1. Yes, the Type-C PD controller detects insertion/de-assertion, cable orientation, and then manages power negotiations. For power negotiations, the PD controller on both the sink and source side communicate with one another about how much power can be supplied and how much power the sinking system needs. For this specific reference design, the barrel jack is connected directly to the PPHV power path of the TPS65986 supplying the 20V, and system 5V is connected to the PP5V power path. Upon initial connection, an Rp/Rd will be presented on either side. The internal switch in the TPS65986 connecting PP5V to VBUS will close, and the dock will begin the source 5V. The two PD controllers will then begin to go through power negotiation, and the sink will request 20V at xA. The TPS65986 will then close its internal switch connecting PPHV to VBUS, and now the dock is supplying 20V.

    Typically within other designs, we have a dcdc connected to PPHV and a series of resistor dividers connected to the feedback pin of the dcdc and GPIOs on our PD controller. This would allow for the dcdc to potentially supply all PDO's (5V, 9V, 15V, 20V). This example can be found on the TPS65987DEVM

    For future testing/debugging, I would recommend purchasing a PD analyzer such as this one from Total Phase. This will allow for you to reach PD messaging between a DFP and UFP device.
    www.totalphase.com/.../

    2. If you are not using the external power path offered by the TPS65982, I would recommend moving instead to the TPS65987D. Since the TPS65986 is currently being NRND, the replacement we recommend is the TPS65987D.

    3. I do not know why the audio portion of this reference design is not working, and would recommend posting a separate question so that the engineers responsible for supporting the PCM2707C can comment.

    4. Based on my initial look through, this should not occur as the two ports should be independent of one another. However, the TPS65982 controls the DP/DM lines connected to the Type-A port, so there could be something within the TPS65982 configuration to where is does not negotiate charging unless it detects a device connected to its Type-C port.

    5. You will need to program the TPS65986 and TPS65982 which can be done by an external SPI flash, or can be done via I2C from a central EC