SLVUBX5C December   2022  – August 2024 TPS25762-Q1 , 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

Secure Firmware Update

TPS257xx-Q1 devices support secure firmware updates over USB using the previously-described USB endpoint method. The secure firmware update makes sure that only the binary image signed with the correct set of keys can be used to reprogram the EEPROM device. The GUI and firmware use the SHA-256 algorithm to hash and sign the binary image with RSA-PSS generated keys. A set of private and public key pairs can be generated using RSA-PSS for end-customer (OEM) development and production purposes.

During end-product production, initial programming of the EEPROM must be performed using I2C with the Full Flash binary image built with the desired set of keys. Field updates can then be done using the TPS257XX-Q1-GUI tool over a USB connection to the primary charging port with the USB EP binary image that was built with the same set of keys. The customer-specific private keys must be kept secure and need to be loaded at the time of USB field update to reprogram the device; otherwise, the secure firmware update process does not complete.