SLVUBX5B August   2023  – February 2024 TPS25762-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 USB Port Configuration Module
    2. 4.2 I2C Configuration
    3. 4.3 Internal DCDC
    4. 4.4 GPIO Configuration
    5. 4.5 External DCDC
    6. 4.6 System Configuration
      1. 4.6.1 System Power Management
      2. 4.6.2 Device IDs
      3. 4.6.3 Thermal Foldback
      4. 4.6.4 VIN Engine On or Off
    7. 4.7 Advanced Configuration
  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.   Revision History

A TPS257xx-Q1 GUI Feature - CUSTOM ID (Version Control)

There are two ways to version control a GUI-generated binary file. The first method is automatically implemented when a binary is generated, as covered in Section 5, and a timestamp will be included within the file name. In some cases, however, it is desirable to be able to uniquely identify a binary file that is loaded into an EEPROM using an EEPROM reader such as an Aardvark adapter (see Section 5.4). This can be done by integrating a user-defined version control to the binary file using the CUSTOM ID feature on the OTHER tab from the Advanced Configuration GUI page (see Figure 7-1).

GUID-20230807-SS0I-DV6W-DVW8-LGMBNRMFTQ3V-low.png Figure A-1 CUSTOM ID Menu

The CUSTOM ID feature is disabled by default. By enabling it, custom-defined values can be added to four input boxes per port. A 16-bit value can be entered in each box represented in hexidecimal format, so values up to 8 bytes for TPS25762-Q1 ("A" field only) and 16 bytes for TPS25772-Q1 ("A+B" fields) are possible.

Figure 7-2 shows a comparison of two binary output files with the CUSTOM ID feature disabled and enabled. The same "A" and "B" field data entries from Figure 7-1 are highlighted in the CUSTOM ID enabled binary shown below. Note that the custom-defined values in the binary are assembled least significant byte first.

GUID-20230807-SS0I-SD06-562P-LWRKR7FGRMTZ-low.png Figure A-2 Binary Files with CUSTOM ID Enabled vs. Disabled

The byte position of the CUSTOM ID data may vary in the binary file depending on how the device features are configured. The "A" field data entry and "B" field data entry are preceded with their respective headers that are always the same (see Figure 7-3); the header for the "A" field is 04 06 00 07 and the header for the "B" field is 40 06 00 07. Searching for the header within the binary file will allow for easy identification of the CUSTOM ID data.

GUID-20230807-SS0I-K78X-SQ5W-PTD7TDG2CZQR-low.png Figure A-3 CUSTOM ID Data Headers

Although a binary file is time stamped in the file name when it is generated using the GUI, the CUSTOM ID feature is a more reliable way to embed a custom revision/version identifier. It is integrated into the binary file generation and it can be read out of the EEPROM directly for verification purposes.