Part Number: TUSB1064
Hi Sir,
My customer is using TUSB1064 in docking product. There's only two test items failed now:
TD10.102
TD10.112
Lab comment that DFP side is keep polling (in Polling.Active) status and can't get RX.detect through TUSB1064 on time. But general USB3 function is fine. Can we provide letter to waive the questions? Thanks.
Best regards,
Gary Teng
HI Gary,
Can yo send the full protocol trace files? I cannot properly read the images sent.
Lab comment that DFP side is keep polling (in Polling.Active) status and can't get RX.detect through TUSB1064 on time. But general USB3 function is fine. Can we provide letter to waive the questions? Thanks.
RX detect will happen before the polling state as per the USB 3.2 LTSSM. Is the LFPS timing out?
If USB is functional then the link must finish the polling state and enter U0.
What is the setup used to capture these protocol trcaes?
Hi Vishesh,
Please check USB 3.2 Gen 1x1 Hub LVS report in link. Thanks for your kindly help.
https://share.graniteriverlabs.com.tw/sharing/f4CFigQPX
Regards,
Gary
Hi Gary,
Can you share an image of the test setup? I'm struggling to see what is connected to the upstream and downstream ports.
TD 10.102 and TD 10.121 are USB 3.2 Hub tests.
TD 10.102
This test is related to Vbus being present on the UFP of the USB3.2 hub, and the DFP transitioning to the correct state. The TUSB1064 doe snot play a role in this state transition. Look into the PD/CC controller as these parts are responsible for state transitions due to Vbus chnages.
TD 10.121:
The TUSB1064 does not play a role in TD10.121. This is controlled by the USB 3.2 hub connected upstream. Look into the Vbus switch and the PD/ CC controller for this issue as well.
