• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 357 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TPS65994AE: TPS65994BH 24H2 HLK test fail

Steven Chen
Prodigy 20 points
Part Number: TPS65994AE

Tool/software:

During the 24H2 HLK testing, we encountered the following failures (log files are attached for reference):

  1. UCSI Connector One Identification [Type-C MUTT]
  2. UCSI Get Connector Status command - USB device detection [Type-C MUTT]

UCSI Connector One Identification [Type-C MUTT]_X580WNT-D_0305.htm UCSI Get Connector Status command - USB device detection [Type-C MUTT]_X580WNT-D_0305.htm

We would like to ask for your assistance to check if these failures are related to FW settings or logic, and whether any adjustments are required.

Below are the system details and PD .pjt file for your reference:

  • Platform: Intel Arrow Lake HX
  • Controller: Thunderbolt 5 (Barlow Ridge)
  • PDO Port A: Output: 5V/3A; Input: 5V/3A, 20V/5A
  • PDO Port B: Output: 5V/3A; Input: 5V/3A

Please ensure compliance with the Intel Barlow Ridge specifications.

x580_TBT5_F909p12p15_30DA_v3118_20250106.pjt

  • 0
    TI__Mastermind 31530 points

    Hi,

    One of our team member will respond to you shortly.

    Regards

  • 0
    TI__Genius 12665 points

    Hi Steven,

    Please provide I2C_EC (I2C1) SCL/SDA logs using a logic analyzer so we can investigate the UCSI commands over I2C. We need this to investigate the failures, as we have very limited information from the test result logs.

    One quick check: Please ensure that when sending a UCSI command to Port B, the Port B I2C address is used, and the connector number is set as 2 in the UCSI command input.

    Best,

    Alex

  • 0 in reply to Alex Liu
    Prodigy 20 points

    Hi Alex,

    Alex Liu said:
    Please provide I2C_EC (I2C1) SCL/SDA logs using a logic analyzer so we can investigate the UCSI commands over I2C. We need this to investigate the failures, as we have very limited information from the test result logs.

    I2C_EC (I2C1) log is provided in the file below.

    UCSI Connector One Identification [Type-C MUTT]_X580WNT-D_0305.CSV

    UCSI Get Connector Status command - USB device detection [Type-C MUTT]_X580WNT-D_0305.CSV

    Alex Liu said:
    One quick check: Please ensure that when sending a UCSI command to Port B, the Port B I2C address is used, and the connector number is set as 2 in the UCSI command input.

    For UCSI CMD, we have followed the specification to send the correct ADDRESS and NUMBER to Port 2.

    Please help to check and confirm

    Thanks.

  • 0
    Prodigy 20 points

    We attempted to modify the "TBT Controller Type" in "Global System Configuration (0x27)" from "BR platform" to "ICL or later platform", and it allowed us to pass the HLK test.

    We would like to ask if there are any differences or potential risks in changing the setting, considering that our Thunderbolt controller is Barlow Ridge.

    Please let us know your thoughts.

    Thanks.

  • 0 in reply to Steven Chen
    TI__Genius 12665 points

    Hi Steven,

    We have seen similar cases like this, but it is difficult to pinpoint exactly what changes when TBT Controller is set to ICL or Later Platform fixes this HLK failure. We have recommended using ICL or Later Lake platform in the past for Barlow Ridge, so this should be ok. 

    I did see in the logs that after EC issues UCSI commands to the PD, it does not seem to read back the command result from the PD to determine complete/failure. I recommend checking this, as EC should be able to handle UCSI command errors from PD. EC is expected to read back PD register 0x08 for command status, then on command complete (read of 0x00 00 00 00), read back PD register 0x09 for CMD data result.

    If there are further issues, please let us know, and we can investigate it. 

    Best,

    Alex