SPRUIX0D February   2021  – August 2021

 

  1.   Trademarks
  2. 1Introduction
    1. 1.1 EVM Revisions and Assembly Variants
  3. 2Important Usage Notes
    1. 2.1 Power-On Usage Note
  4. 3System Description
    1. 3.1 Key Features
    2. 3.2 Functional Block Diagram
    3. 3.3 Power-On/Off Procedures
      1. 3.3.1 Power-On Procedure
      2. 3.3.2 Power-Off Procedure
    4. 3.4 Peripheral and Major Component Description
      1. 3.4.1  Clocking
        1. 3.4.1.1 Ethernet PHY Clock
        2. 3.4.1.2 AM64x/AM243x Clock
        3. 3.4.1.3 PCIe Clock
      2. 3.4.2  Reset
      3. 3.4.3  Power
        1. 3.4.3.1 Power Input
        2. 3.4.3.2 Reverse Polarity Protection
        3. 3.4.3.3 Current Monitoring
        4. 3.4.3.4 Power Supply
        5. 3.4.3.5 Power Sequencing
        6. 3.4.3.6 AM64x/AM243x Power
      4. 3.4.4  Configuration
        1. 3.4.4.1 Boot Modes
      5. 3.4.5  JTAG
      6. 3.4.6  Test Automation
      7. 3.4.7  UART Interfaces
      8. 3.4.8  Memory Interfaces
        1. 3.4.8.1 DDR4 Interface
        2. 3.4.8.2 MMC Interfaces
          1. 3.4.8.2.1 Micro SD Interface
          2. 3.4.8.2.2 eMMC Interface
        3. 3.4.8.3 OSPI Interface
        4. 3.4.8.4 SPI EEPROM Interface
        5. 3.4.8.5 Board ID EEPROM Interface
      9. 3.4.9  Ethernet Interface
        1. 3.4.9.1 DP83867 PHY Default Configuration
        2. 3.4.9.2 DP83869 PHY Default Configuration
        3. 3.4.9.3 Ethernet LED
      10. 3.4.10 Display Interface
      11. 3.4.11 USB 2.0 Interface
      12. 3.4.12 PCIe Interface
      13. 3.4.13 High Speed Expansion Interface
      14. 3.4.14 CAN Interface
      15. 3.4.15 Interrupt
      16. 3.4.16 ADC Interface
      17. 3.4.17 Safety Connector
      18. 3.4.18 SPI Interfaces
      19. 3.4.19 I2C Interfaces
      20. 3.4.20 FSI Interface
  5. 4Known Issues and Modifications
    1. 4.1 Issue 1 - Embedded XDS110 Connection to AM64x Target in CCS
    2. 4.2 Issue 2 - MDIO Ethernet PHY Communications
    3. 4.3 Issue 3 - DC Barrel Jack Warning when Hot-Plugging
  6. 5References
  7. 6Revision History

4.1 Issue 1 - Embedded XDS110 Connection to AM64x Target in CCS

Applicable EVM Revisions: E2

Issue Description: On some EVM, the embedded XDS110 (U59) has been shown to fail initial target connection to AM64x target in CCS after first EVM and XDS110 power cycle. No problem exists when using an attached, external emulator over the CTI20 header (J25).

This failure mode can be encountered by following the steps below:

  1. XDS110 USB is attached between host PC and XDS110 USB port (J28).
  2. EVM power is enabled and the AM64x is brought up in no-boot mode.
  3. In CCS, an initial CCS target connection to the M3 DMSC core is then attempted.
  4. CCS will error out with the below dialog complaining of a DAP connection error to the target core.
    1. Hitting retry results in the same error message
GUID-42130A88-36CF-4947-BFAE-B85F7BEC657A-low.png Figure 4-2 XDS110 CCS Connection Error Dialog

Workaround 1: After the connection issue is encountered, users can unplug the USB host connection to the XDS110 emulator through USB port (J28) and then plugin the USB cable again. This power cycles the XDS110 and will clear up the connection error.

Workaround 2: After the connection issue is encountered, users can toggle TRSTSN through the XDS110 debug command-line utility xds110reset found in the CCS XDS110 utility directory.

In the Windows OS installation, for a default installation of CCS version 10.11, this tool is found in the directory C:\ti\ccs1011\ccs\ccs_base\common\uscif\xds110>

This command can be executed on the Windows command prompt/terminal when the embedded XDS110 is powered on and connected to the host PC. A similar tool is available under the Linux OS install of CCS.

GUID-4CB44950-B339-4C6B-AE5B-9FC1AEAC836D-low.png Figure 4-3 XDS110 debug reset utility command-line function