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.

TUSB522P: TUSB522P support

Part Number: TUSB522P

1:  

“One of our platforms implements the TI TUSB522p redriver on a USB host controller.

 We would like to conduct some experiments which require removing or bypassing the redriver on the USB path.

 I am reaching out to obtain some guidance as to what the connections are required to remove the redriver but keep the USB port functional.

2: We have the TI USB RE-DRIVER TUSB522P on our SS port on the AMD server reference platform and are having issues getting the port to pass the USB compliance TD1.09 test .   This is the interface test

 

  • for Q1: you need to connect RX1 to TX1 and TX2 to RX2 to by pass redriver. You can use 0 ohm resistor to connect host TX to connector TX and host RX to connector RX

  • For Q2: does customer has usb traffic log for the test when pass and fail?

    Regards

    brian

  • Brian:

      Any update from customer?

    Brian Zhou

  • Hi Brian,

    Can you please help take a look at the attached USB logs?

    AMD is reporting a failure of TD1.09 test when running USB compliance. 

    APPLICATION: xHCI Command Verifier
    TEST SUITE: xHCI Interface Tests.cvtests
    OPERATING SYSTEM:
    WORKSTATION:
    DATE: Monday, November 14, 2022
    TIME: 04:13:18 PM
    OPERATOR: Administrator
    NUMBER OF TESTS: 1
    LOG NAME: xHCI Interface Compliance Tests - 2022-11-14 16-10-04
    RESULT: failed



    InitializeTestSuite
    INFO
    Test log initialized.
    INFO
    Log Level: Normal
    INFO
    User Input module initialized
    INFO
    Windows Server 2022 Standard (Build 20348.1.amd64fre.fe_release.210507-1500)
    INFO
    CVApp.exe ver 4.1.0.0
    INFO
    BaseUtilities.dll ver 4.1.0.0
    INFO
    CommandVerifierLog.dll ver 4.1.0.0
    INFO
    GuiHelper.dll ver 4.1.0.0
    INFO
    TestUtilities.dll ver 4.1.0.0
    INFO
    TestSuiteEngine.dll ver 4.1.0.0
    INFO
    VIFReader.dll ver 4.1.0.0
    INFO
    xhci_DevIOCTL.dll ver 2.2.7.0
    INFO
    xhci_TestServices.dll ver 2.2.7.0
    INFO
    USBUtilities.dll ver 1.4.5.1
    INFO
    xhci_CommandVerifierServices.dll ver 2.2.7.0
    INFO
    XHCITest.dll ver 2.2.9.0
    INFO
    XHCISpecVersion: 1.20.
    INFO
    Host VID=0x1022 PID=0x14c9 Revision=0xda HCI=0x120
    INFO
    User declared inaccessible root ports as 0x00000002
    INFO
    Device Removable bits for root ports 0x00000000
    WARNING
    Warning - host port non-removable bits do not match user description
    EnumerateEmbeddedDevices
    INFO
    Host VID=0x1022 PID=0x14c9 Revision=0xda HCI=0x120
    INFO
    MaxPorts: 4
    INFO
    Protocol Rev 2.00
    INFO
    Port offset=1 PortCount=2
    INFO
    Marking host port 2 as non-removable
    INFO
    Protocol Rev 3.10
    INFO
    Gen1Support: yes Gen2Support: yes
    INFO
    Port offset=3 PortCount=1
    INFO
    Protocol Rev 3.10
    INFO
    Gen1Support: yes Gen2Support: yes
    INFO
    Port offset=4 PortCount=1
    INFO
    Using non-removable mask for USB 2.0 hub = 0x7f
    TD.1.09 Protocol Speed ID Test
    Failed
    INFO
    Start time: Nov 14, 2022 - 16:10:39
    INFO
    Host VID=0x1022 PID=0x14c9 Revision=0xda HCI=0x120
    INFO
    Marking host port 2 as non-removable
    INFO
    --- xHCI Supported Protocol Capability Register (offset=0x470) ---
    INFO
    USB Revision=2.0, NameString=0x20425355
    INFO
    CompatiblePortOffset=1, CompatiblePortCount=2
    INFO
    PSIC=0, ProtocolSlotType=0
    INFO
    xHCI Supported Protocol Capability - USB 2.0 (PSIC=0)
    INFO
    PSIC == 0. Using default because no PSIDs defined.
    INFO
    Testing attach of HS device.
    INFO
    Got Port Status Change Event: PORTSC=0x206e1 port#1
    INFO
    Device connected - PSIV=3 (HS)
    INFO
    Testing attach of FS device.
    INFO
    Got Port Status Change Event: PORTSC=0x206e1 port#1
    INFO
    Device connected - PSIV=1 (FS)
    INFO
    Testing attach of LS device.
    INFO
    Got Port Status Change Event: PORTSC=0x20ae1 port#1
    INFO
    Device connected - PSIV=2 (LS)
    INFO
    --- xHCI Supported Protocol Capability Register (offset=0x480) ---
    INFO
    USB Revision=3.10, NameString=0x20425355
    INFO
    CompatiblePortOffset=3, CompatiblePortCount=1
    INFO
    PSIC=2, ProtocolSlotType=0
    INFO
    xHCI Supported Protocol Capability - USB 3.10 (PSIC=2)
    INFO
    [0] Protocol Speed ID=0x00050134
    INFO
    PSIV=4, PSIE=3, PLT=0, PFD=1, LP=0, PSIM=5
    INFO
    Assuming this PSID describes SS Gen1x1 ports
    INFO
    [1] Protocol Speed ID=0x000A4135
    INFO
    PSIV=5, PSIE=3, PLT=0, PFD=1, LP=1, PSIM=10
    INFO
    Assuming this PSID describes SS Gen2x1 ports
    INFO
    Counted 2 PSI Dwords describing 3.1 ports
    INFO
    Testing attach of SS device.
    INFO
    Got Port Status Change Event: PORTSC=0x21203 port#3
    INFO
    Device connected - PSIV=4 (SS)
    FAIL
    Aborted
    FAIL
    INFO
    Stop time: Nov 14, 2022 - 16:13:17
    INFO
    Duration: 158 seconds (2 minutes, 38 seconds).
    INFO
    Stopping Test [ TD.1.09 Protocol Speed ID Test: Number of: Fails (2); Aborts (0); Warnings (0) ]
    Summary
    INFO
    TEST SUITE SUMMARY: [ Fails (2); Aborts (0); Warnings (1) ]
    INFO
    TEST RESULTS: [ Passed (0); Failed (1) ]
  • Hi Brian,

    This is customer response.

    From: Schwartz, Erika <Erika.Schwartz@amd.com>
    Sent: Friday, December 9, 2022 8:44 AM
    To: Goulet, Michael <Michael.Goulet@amd.com>; Hazel, Cameron <cameron.b.hazel@ti.com>; Heeg, Madison <mheeg@ti.com>; Schwartz, Erika <Erika.Schwartz@amd.com>; Talbert, Jason <jason.talbert@amd.com>; Lam, Ranger <ranger.lam@amd.com>; Kao, Kevin <Kevin.Kao@amd.com>; Lim, Leon <Leon.Lim@amd.com>; Guo, Jiahong <j-guo1@ti.com>; Butterfield, Brian <bbutterfield@ti.com>
    Subject: [EXTERNAL] FW: TI USB RE-DRIVER TUSB522P USB compliance support

     

    [AMD Official Use Only - General]

     

    Hello Mr. Butterfield,

     

    We appreciate your response on the rework.

     

    Unfortunately, after the rework our platform was unreliable.  However, we would like to see continue moving forward with root causing our test failure.

    Quick summary: We obtain a passing test case (at 100% rate) of the USB xHCICV compliance interface test on the non-redriver USB Host Controller, and a failing test case (at 99% rate) on the controller with the TI redriver in the path.

     

    I am attaching two sets of zip files.  One zip contains passing log/trace on the non-redriver port and the other zip contains the failed logs/trace on the TI redriver port.

     

    Would you please review the data and compare as per the redriver spec?   We appreciate your feedback on the trace analyzes as well as suggested next steps, if possible.

     

    -erika

     

    From: Butterfield, Brian <bbutterfield@ti.com>
    Sent: Monday, November 14, 2022 10:57 AM
    To: Goulet, Michael <Michael.Goulet@amd.com>; Hazel, Cameron <cameron.b.hazel@ti.com>; Heeg, Madison <mheeg@ti.com>
    Cc: Schwartz, Erika <Erika.Schwartz@amd.com>; Talbert, Jason <jason.talbert@amd.com>; Lam, Ranger <ranger.lam@amd.com>; Kao, Kevin <Kevin.Kao@amd.com>; Lim, Leon <Leon.Lim@amd.com>; Guo, Jiahong <j-guo1@ti.com>
    Subject: RE: TI USB RE-DRIVER TUSB522P USB compliance support

     

    Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.

     

    Hi Michael,

    Let us know if this helps to make progress, but we do have a follow up question. 

    “One of our platforms implements the TI TUSB522p redriver on a USB host controller.
     We would like to conduct some experiments which require removing or bypassing the redriver on the USB path.

    I am reaching out to obtain some guidance as to what the connections are required to remove the redriver but keep the USB port functional.

    2: We have the TI USB RE-DRIVER TUSB522P on our SS port on the AMD server reference platform and are having issues getting the port to pass the USB compliance TD1.09 test .   This is the interface test”

     

    for Q1: you need to connect RX1 to TX1 and TX2 to RX2 to by pass redriver. You can use 0 ohm resistor to connect host TX to connector TX and host RX to connector RX

     

    For Q2: does customer has usb traffic log for the test when pass and fail?

     

    Thank you,

    Brian

     

    From: Goulet, Michael <Michael.Goulet@amd.com>
    Sent: Friday, November 11, 2022 1:41 PM
    To: Butterfield, Brian <bbutterfield@ti.com>; Hazel, Cameron <cameron.b.hazel@ti.com>; Heeg, Madison <mheeg@ti.com>
    Cc: Schwartz, Erika <Erika.Schwartz@amd.com>; Talbert, Jason <jason.talbert@amd.com>; Lam, Ranger <ranger.lam@amd.com>; Kao, Kevin <Kevin.Kao@amd.com>; Lim, Leon <Leon.Lim@amd.com>; Guo, Jiahong <j-guo1@ti.com>
    Subject: [EXTERNAL] RE: TI USB RE-DRIVER TUSB522P USB compliance support

     

    [AMD Official Use Only - General]

     

    Thank you. I appreciate that.

     

    From: Butterfield, Brian <bbutterfield@ti.com>
    Sent: Friday, November 11, 2022 3:41 PM
    To: Goulet, Michael <Michael.Goulet@amd.com>; Hazel, Cameron <cameron.b.hazel@ti.com>; Heeg, Madison <mheeg@ti.com>
    Cc: Schwartz, Erika <Erika.Schwartz@amd.com>; Talbert, Jason <jason.talbert@amd.com>; Lam, Ranger <ranger.lam@amd.com>; Kao, Kevin <Kevin.Kao@amd.com>; Lim, Leon <Leon.Lim@amd.com>; Guo, Jiahong <j-guo1@ti.com>
    Subject: RE: TI USB RE-DRIVER TUSB522P USB compliance support

     

    Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.

     

    Hi Michael,

    We’re starting to look into this.

    Some key individuals who support this are out of office today but we are running this down in parallel until they get back. 

     

    Thank you,

    Brian

     

    From: Goulet, Michael <Michael.Goulet@amd.com>
    Sent: Friday, November 11, 2022 12:32 PM
    To: Butterfield, Brian <bbutterfield@ti.com>; Hazel, Cameron <cameron.b.hazel@ti.com>; Heeg, Madison <mheeg@ti.com>
    Cc: Schwartz, Erika <Erika.Schwartz@amd.com>; Talbert, Jason <jason.talbert@amd.com>; Lam, Ranger <ranger.lam@amd.com>; Kao, Kevin <Kevin.Kao@amd.com>; Lim, Leon <Leon.Lim@amd.com>
    Subject: [EXTERNAL] TI USB RE-DRIVER TUSB522P USB compliance support

     

    [AMD Official Use Only - General]

     

    Brian, Cameron and Madison,

     

                    We have the TI USB RE-DRIVER TUSB522P on our SS port on the AMD server reference platform and are having issues getting the port to pass the USB compliance TD1.09 test .   This is the interface test.

     

    We need support from you to figure out how to get this test to consistently pass. 

     Do you have other users that have been able to get their designs to pass certification?

     Are there setting that we should be trying that will help this issue?

    What other info do you need from us to get to the bottom of this?

     

    Thnaks

  • Jiahong:

        What is this CV test? Do you have test description for TD1.09?

        Also for trace log of fail, it shows HC1-2nd-pass, it's pass or fail? Almost same as the other one

    Regards

    brian

  • I listed the failed logs/trace on the TI redriver port. The other is passing log/trace on the non-redriver port. Customer would like us to review the data and compare as per the redriver spec? I will ask them for test description of TD1.09.

    APPLICATION: xHCI Command Verifier
    TEST SUITE: xHCI Interface Tests.cvtests
    OPERATING SYSTEM:
    WORKSTATION:
    DATE: Monday, November 14, 2022
    TIME: 04:36:14 PM
    OPERATOR: Administrator
    NUMBER OF TESTS: 1
    LOG NAME: xHCI Interface Compliance Tests - 2022-11-14 16-34-30
    RESULT: passed



    InitializeTestSuite
    INFO
    Test log initialized.
    INFO
    Log Level: Normal
    INFO
    User Input module initialized
    INFO
    Windows Server 2022 Standard (Build 20348.1.amd64fre.fe_release.210507-1500)
    INFO
    CVApp.exe ver 4.1.0.0
    INFO
    BaseUtilities.dll ver 4.1.0.0
    INFO
    CommandVerifierLog.dll ver 4.1.0.0
    INFO
    GuiHelper.dll ver 4.1.0.0
    INFO
    TestUtilities.dll ver 4.1.0.0
    INFO
    TestSuiteEngine.dll ver 4.1.0.0
    INFO
    VIFReader.dll ver 4.1.0.0
    INFO
    xhci_DevIOCTL.dll ver 2.2.7.0
    INFO
    xhci_TestServices.dll ver 2.2.7.0
    INFO
    USBUtilities.dll ver 1.4.5.1
    INFO
    xhci_CommandVerifierServices.dll ver 2.2.7.0
    INFO
    XHCITest.dll ver 2.2.9.0
    INFO
    XHCISpecVersion: 1.20.
    INFO
    Host VID=0x1022 PID=0x14c9 Revision=0xda HCI=0x120
    INFO
    User declared inaccessible root ports as 0x00000000
    INFO
    Device Removable bits for root ports 0x00000000
    EnumerateEmbeddedDevices
    INFO
    Host VID=0x1022 PID=0x14c9 Revision=0xda HCI=0x120
    INFO
    MaxPorts: 4
    INFO
    Protocol Rev 2.00
    INFO
    Port offset=1 PortCount=2
    INFO
    Protocol Rev 3.10
    INFO
    Gen1Support: yes Gen2Support: yes
    INFO
    Port offset=3 PortCount=1
    INFO
    Protocol Rev 3.10
    INFO
    Gen1Support: yes Gen2Support: yes
    INFO
    Port offset=4 PortCount=1
    TD.1.09 Protocol Speed ID Test
    Passed
    INFO
    Start time: Nov 14, 2022 - 16:34:39
    INFO
    Host VID=0x1022 PID=0x14c9 Revision=0xda HCI=0x120
    INFO
    --- xHCI Supported Protocol Capability Register (offset=0x470) ---
    INFO
    USB Revision=2.0, NameString=0x20425355
    INFO
    CompatiblePortOffset=1, CompatiblePortCount=2
    INFO
    PSIC=0, ProtocolSlotType=0
    INFO
    xHCI Supported Protocol Capability - USB 2.0 (PSIC=0)
    INFO
    PSIC == 0. Using default because no PSIDs defined.
    INFO
    Testing attach of HS device.
    INFO
    Got Port Status Change Event: PORTSC=0x206e1 port#1
    INFO
    Device connected - PSIV=3 (HS)
    INFO
    Testing attach of FS device.
    INFO
    Got Port Status Change Event: PORTSC=0x206e1 port#1
    INFO
    Device connected - PSIV=1 (FS)
    INFO
    Testing attach of LS device.
    INFO
    Got Port Status Change Event: PORTSC=0x20ae1 port#1
    INFO
    Device connected - PSIV=2 (LS)
    INFO
    --- xHCI Supported Protocol Capability Register (offset=0x480) ---
    INFO
    USB Revision=3.10, NameString=0x20425355
    INFO
    CompatiblePortOffset=3, CompatiblePortCount=1
    INFO
    PSIC=2, ProtocolSlotType=0
    INFO
    xHCI Supported Protocol Capability - USB 3.10 (PSIC=2)
    INFO
    [0] Protocol Speed ID=0x00050134
    INFO
    PSIV=4, PSIE=3, PLT=0, PFD=1, LP=0, PSIM=5
    INFO
    Assuming this PSID describes SS Gen1x1 ports
    INFO
    [1] Protocol Speed ID=0x000A4135
    INFO
    PSIV=5, PSIE=3, PLT=0, PFD=1, LP=1, PSIM=10
    INFO
    Assuming this PSID describes SS Gen2x1 ports
    INFO
    Counted 2 PSI Dwords describing 3.1 ports
    INFO
    Testing attach of SS device.
    INFO
    Got Port Status Change Event: PORTSC=0x21203 port#3
    INFO
    Device connected - PSIV=4 (SS)
    WARNING
    Skipping Gen1x2 device iteration because there is no compliance device for this configuration.
    INFO
    --- xHCI Supported Protocol Capability Register (offset=0x4A0) ---
    INFO
    USB Revision=3.10, NameString=0x20425355
    INFO
    CompatiblePortOffset=4, CompatiblePortCount=1
    INFO
    PSIC=2, ProtocolSlotType=0
    INFO
    xHCI Supported Protocol Capability - USB 3.10 (PSIC=2)
    INFO
    [0] Protocol Speed ID=0x00050134
    INFO
    PSIV=4, PSIE=3, PLT=0, PFD=1, LP=0, PSIM=5
    INFO
    Assuming this PSID describes SS Gen1x1 ports
    INFO
    [1] Protocol Speed ID=0x000A4135
    INFO
    PSIV=5, PSIE=3, PLT=0, PFD=1, LP=1, PSIM=10
    INFO
    Assuming this PSID describes SS Gen2x1 ports
    INFO
    Counted 2 PSI Dwords describing 3.1 ports
    INFO
    Testing attach of SS device.
    INFO
    Got Port Status Change Event: PORTSC=0x21203 port#3
    INFO
    Device connected - PSIV=4 (SS)
    WARNING
    Skipping Gen1x2 device iteration because there is no compliance device for this configuration.
    INFO
    Stop time: Nov 14, 2022 - 16:36:14
    INFO
    Duration: 95 seconds (1 minute, 35 seconds).
    INFO
    Stopping Test [ TD.1.09 Protocol Speed ID Test: Number of: Fails (0); Aborts (0); Warnings (2) ]
    Summary
    INFO
    TEST SUITE SUMMARY: [ Fails (0); Aborts (0); Warnings (2) ]
    INFO
    TEST RESULTS: [ Passed (1); Failed (0) ]
  • So this is the trace for failed one with redriver?

  • ok, let me check again, unplug in the trace look similar to the good one.

    regards

    brian

  • Jiahong:

        Can customer test with USBtreeview by plug flash driver in and out and works fine?

    Regars

    brian

  • keep ticket active