SLVUBX5C December   2022  – August 2024 TPS25762-Q1 , TPS25763 , TPS25763-Q1 , TPS25772-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Getting Started
    1. 2.1 Related Documents
    2. 2.2 Hardware
    3. 2.3 Software
    4. 2.4 GUI Installation and Launch
  6. 3Application Configuration Overview
    1. 3.1 Creating a New Application Configuration
    2. 3.2 Loading a Saved Configuration
  7. 4Configuration Parameters
    1. 4.1 System Power
      1. 4.1.1 System Power Management (SPM)
    2. 4.2 Internal & External DCDC
    3. 4.3 VIN Engine On or Off
    4. 4.4 Thermal Foldback
    5. 4.5 USB PORT(S)
    6. 4.6 GPIO Configuration
    7. 4.7 I2C Configuration
    8. 4.8 Device IDs
    9. 4.9 DisplayPort Alt Mode
  8. 5Application Configuration Download
    1. 5.1 Firmware Download Procedure
      1. 5.1.1 Key Upload and Binary File Generation
        1. 5.1.1.1 Firmware Update: USB Endpoint
        2. 5.1.1.2 Firmware Update: I2C
    2. 5.2 Secure Firmware Update
    3. 5.3 Optional USB Driver Installation
    4. 5.4 Direct EEPROM Programming
    5. 5.5 SSH Key Generation
  9. 6Telemetry
  10.   A TPS257XX-Q1 GUI Feature - CUSTOM ID (Version Control)
  11.   B VIN Engine On or Off (TPS257xC-Q1)
  12.   Revision History

Introduction

The TPS2576x-Q1 and TPS2577x-Q1 device family is user-configurable and can support a wide range of operational modes to meet specific use-case requirements. This programmable flexibility enables the same hardware design to support different requirements without changes to the physical hardware. Hardware system design of the TPS25763Q1EVM, TPS25762DQ1EVM, and TPS25772DQ1EVM include connection of an EEPROM memory to the TPS2576x-Q1 or TPS2577x-Q1 device through an I2C interface.

Application-specific device configuration and programming can be accomplished using the TPS257XX-Q1-GUI. This graphical user interface tool is configurable based on user requirements and generates corresponding binary files that can be downloaded into the EEPROM through an I2C interface. The GUI inherently supports the ability to update hardware using a USB endpoint connection, a mode typically used post-production once hardware has been deployed.

Note: Some graphics contained in this document can differ slightly from the current version of the GUI available from dev.ti.com because regular maintenance releases can occur ahead of updates to this guide.