TIDUF29 October   2023

 

  1.   1
  2.   Description
  3.   Resources
  4.   Features
  5.   Applications
  6.   6
  7. 1System Description
  8. 2System Overview
    1. 2.1 Block Diagram
    2. 2.2 Design Considerations
      1. 2.2.1 Connectors
      2. 2.2.2 High-Speed Traces
      3. 2.2.3 Power Rails
    3. 2.3 Highlighted Products
      1. 2.3.1 DS560DF410
      2. 2.3.2 TPS62867
      3. 2.3.3 TPS7A52
      4. 2.3.4 TLV702
      5. 2.3.5 TXB0108
  9. 3Hardware, Software, Testing Requirements, and Test Results
    1. 3.1 Hardware Requirements
      1. 3.1.1 TX Output Eye Test
      2. 3.1.2 RX Link Test
    2. 3.2 Software Requirements
    3. 3.3 Test Setup
      1. 3.3.1 TX Output Eye Test
      2. 3.3.2 RX Link Test
    4. 3.4 Test Results
      1. 3.4.1 TX Output Eye Test
      2. 3.4.2 RX Link Test
  10. 4Design and Documentation Support
    1. 4.1 Design Files
      1. 4.1.1 Schematics
      2. 4.1.2 BOM
      3. 4.1.3 Altium Project
    2. 4.2 Tools and Software
    3. 4.3 Documentation Support
    4. 4.4 Support Resources
    5. 4.5 Trademarks

Software Requirements

Many of the common device configurations intended for the reference design require configuration through a TI-developed GUI called Latte. This software is required to perform the TX output eye test and the RX link test. The latest version of Latte is available for download by request through TI's website. There are two installation files that the user needs to download and execute: the Latte framework installer file and the Latte libraries updater. As of this publication, the latest Latte installation files are the following:

  • Main Installer: TI-DS560-Latte_vXpX.exe
  • Libraries updater: TI-DS560Lib_vXpX.exe

For detailed instructions on the software installation sequence, functional overview, and initialization sequence for Latte, refer to the software description sections in the DS560DF810 EVM User's Guide. The reference design follows a similar initialization sequence relative to the DS560EVM, with the following key difference:

  • In the devinit.py file, change the device address to correspond to the target device on the MCB.