• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 683 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: TPS65982 Firm/Software and Generic Questions

Russell Wetherley1
Expert 4255 points
Part Number: TPS65982
Other Parts Discussed in Thread: TPS65981, TPS65987

Hello E2E,

A customer of mine is looking to use the TPS65982 and they have some questions:

  • Linux drivers - what kernels are supported?
    • Application currently is using Linux Kernel 4.04 – preference to not upgrade Kernel to risk delaying time to market
  • Is power path supported (USB-C delivers power to the device when connected and not the battery)? If not, what part would you recommend?
  • How is the device programmed in a production setting?
  • Are drivers required?  Does TI have anything?  (there is no time in the project to do any driver development)
  • How to do SW and HW setup for field programmability of the TPS firmware? 
  • Use cases are
    • System is powered down on battery, when PD is plugged in the TPS needs to negotiate the power sinking configuration (e.g. 15V 2A) so the battery charger can come on and so the system optionally could be powered up
    • Same but no battery, PD needs to autonegotiate and switch on the 15V from the PD
    • Power and data to a USB 3.0 type C device like a flash drive
    • Power and data to a USB 2.0 type C device (don’t know what this device is yet)

  • it needs to be both an upstream and downstream data port.

    Also to include one additional question up front – if the CPU SOM has Linux 4.04 support for USB 3.0, is everything else in the TPS firmware?  i.e. no Linux support or drivers for the PD and data negotiations, just programming / configuring the TPS firmware and it handles that?

Finally, as a generic question, what you suggest between the TPS65982 and TPS65981?

Thanks!

Russell

  • 0
    TI__Intellectual 1010 points
    •Linux drivers - what kernels are supported? •Application currently is using Linux Kernel 4.04 – preference to not upgrade Kernel to risk delaying time to market
    - No Linux drivers provided. But, depending on application, none may be needed.

    •Is power path supported (USB-C delivers power to the device when connected and not the battery)? If not, what part would you recommend?
    - Yes, our device supports both battery power and non-powered (we call it "dead battery") cases.

    •How is the device programmed in a production setting?
    - None of our PD controllers include flash or other non-volatile memory. TPS65982 requires a flash chip be connected to it via SPI. Newer devices can be pull configuration and patch information from a host processor via I2C. Newer devices TPS65987/88 are cheaper and may be better suited for new design than TPS65982.

    •Are drivers required? Does TI have anything? (there is no time in the project to do any driver development)
    - Not necessarily. Our devices are used in everything from PD Type-C dongles to docks, to laptops. In many dongles there is no host processor with the PD controller - the PD controller takes care of everything. In laptops there is typically an EC that communicates with PD controller via I2C to "know what is going on". We do not provide Linux drivers for this.

    •How to do SW and HW setup for field programmability of the TPS firmware?
    - TPS65982 is RAM based; firmware and configuration info must be stored on a SPI flash for it to read when powered up. TPS65987/88 are ROM based, but still need firwmare and configuration information from either flash or host processor. The configuration information tells the PD controller how to behave: is it source source/sink/either, what source/sink power contracts is supports, is it data UFP/DFP/DRP.... We provide PC based tool that creates package containing firmware/patch and config for device to use. How this package gets to a flash chip or to a host processor must be handled by the customer

    •Use cases are
    •System is powered down on battery, when PD is plugged in the TPS needs to negotiate the power sinking configuration (e.g. 15V 2A) so the battery charger can come on and so the system optionally could be powered up
    •Same but no battery, PD needs to autonegotiate and switch on the 15V from the PD
    •Power and data to a USB 3.0 type C device like a flash drive
    •Power and data to a USB 2.0 type C device (don’t know what this device is yet)
    - We support all the configuations you mention

    •it needs to be both an upstream and downstream data port.
    - We support the PD communications to support both data roles