• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 322 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: TPS65987DDH application

Don Foong
Expert 4100 points
Part Number: TPS65987D
Other Parts Discussed in Thread: TPS25750

Hi Team,

We have some questions regards to TPS65987DDH. Hope you can help to advice, thanks in advance.

We are using this in our first USB-C PD design on a portable wireless printer.  At first it will be configured as a simple UFP sink.  Later we may support power output to charge a smartphone.  We are also evaluating this IC for use in USB-C updates across a number of portable printers.  

In terms of configuration I need to negotiate a power contract with sufficient power to print or take the max available.  5V 3A isn't quite enough, but 9V >2.85A (about >25W) and so on at higher voltages is sufficient to print.  It can accept 5-20V input.

 

Here are a number of questions I have regarding programming this IC.

    1. Is any configuration register data retained between power cycles?
    1. The parts on my prototype board have out-of-date firmware.  Its F707.10.00 and the latest is F707.10.08.  Is updating the IC's application code required or recommended?  Is there any example code or how-to for this?  I think I understand how to do it using the "Patch Bundle Update" tasks in the programming guide.  But that's a lot of work just to load the latest FW.  Is there any possibility of buying the IC with the latest FW loaded loaded?
    1. The config tool is helpful but it doesn't expose settings for all registers.  In some cases it doesn't quite match the host interface guide.  Should I give precedence to the tool or the programming guide?  
    1. When I "save binary" what is in the image?  Does this include the register settings and the latest FW binary?  Then do I load this through the "Patch Bundle Update" tasks?  Is this a one-time operation, all the settings are permanent?  How are most designers using this part?
    1. The "AutoNegotiate Sink" register (0x37) seems key to negotiating the required power.  However the config tool doesn't expose most of the setting in the upper bytes.  Not sure how to approach this.  What is the interplay between this register and the Tx sink capabilities register?
    1. In a number of places the tool writes 0b1 to reserved bits.  For example in the 2nd byte of register 0x37.  Does this matter?

Thanks and regards,

Don

  • 0
    TI__Mastermind 30000 points

    Hi Don,

    Find answers to your questions below. You also may want to evaluate the TPS25750. If you are only wanting to source 5V and sink up to 20V, and do not need to support alternate modes, the TPS25750 is the perfect device

    • Is any configuration register data retained between power cycles?

    No, any data that you write to the PD controller will be erased during a power cycle. On power up, the PD controller will load whatever the configuration is that is programmed to the external flash

    • The parts on my prototype board have out-of-date firmware.  Its F707.10.00 and the latest is F707.10.08.  Is updating the IC's application code required or recommended?  Is there any example code or how-to for this?  I think I understand how to do it using the "Patch Bundle Update" tasks in the programming guide.  But that's a lot of work just to load the latest FW.  Is there any possibility of buying the IC with the latest FW loaded loaded?

    No, you will need to update the PD controller firmware through the use of an external EEPROM or using an external MCU using the patch bundle update process. This image is more than just the latest firmware, it also includes the configuration of the PD controller that is generated using the GUI

    • The config tool is helpful but it doesn't expose settings for all registers.  In some cases it doesn't quite match the host interface guide.  Should I give precedence to the tool or the programming guide

    Give precedence to the GUI as not all registers shown within the Host Interface guide can be changed using the GUI. 

    • When I "save binary" what is in the image?  Does this include the register settings and the latest FW binary?  Then do I load this through the "Patch Bundle Update" tasks?  Is this a one-time operation, all the settings are permanent?  How are most designers using this part?

    Yes that is exactly right. The binary that is generated from the GUI using the "save binary" combines the configuration generated using the GUI and the latest PD firmware into a single .bin file. 

    • The "AutoNegotiate Sink" register (0x37) seems key to negotiating the required power.  However the config tool doesn't expose most of the setting in the upper bytes.  Not sure how to approach this.  What is the interplay between this register and the Tx sink capabilities register?

    In the "AutoNegotiate Sink" register, you can set the minimum power capabilities of your system

    • In a number of places the tool writes 0b1 to reserved bits.  For example in the 2nd byte of register 0x37.  Does this matter?

    This is okay