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.

TPS65988: Connection issue in loopback mode (TPS65988 port 1 connect to its' port 2)

Part Number: TPS65988


Hi Sir,

We found connection issues while we connect 65988 in loopback mode(Port 1 connects to it Port2). We tested it in 3 scenarios:

(1) Port 1 – DRP, Port 2 – DRP: Fail with 2 symptoms

(2) Port 1 – DFP, Port 2 – UFP: Same as above

(3) Port 1 – UFP, Port 2 – DFP: Pass

In case (1) and case (2) above it failed in 2 symptoms, one is no connection always (always means that wait > 1.5mins) and one is connection built at a very late stage. Meaning that results are inconsistent.

Case 1 (Refer to DRP-DRP-FinalConnect.ccgx attached) starts at 401 Seconds. However, the connection keeps failing until 455 Seconds. It takes 55 seconds to build a valid connection.

While looks into the Type-C state we could see that the initial UFP (Port 2 in this case since it implemented Try.SNK and Port1 implement Try.SRC) side removes the Rd firstly (VBUS removal after). In this case, we could notice the UFP side is doing the removal rather than DFP.

(Zoom in look): I checked every disconnect is caused by Rd removal (No VBUS removal firstly in this case). And I see here’s a Try.SNK state at first Type-C connection. This shall be incorrect since we shall implement no Try on both sides and DPTX shall be DFP/Source preference.

Case2 below shows the same that Port 2 removes the Rd firstly:

We also tried to reset the PDC in the middle but it doesn't help the connection.

One more piece of information we could supplement is Port 2 0x30 register bytes 2-9 show all 0 even it indicates it receives two valid PDOs from Port1(Value 0x2 in the first byte).

Any suggestion of how to improve this will be welcome.

  • Hi,

    Which version of FW and GUI are you using? Why do you need this loopback connection, is that such a use case?

    Regards.

  • Hi,

    GUI Version:6.1.1, Firmware Version: f707.10.08.

    Yes, since our application is DP test equipment. Port 1 is DPTX and Port2 is DP RX in our application. We use loopback connection to demo our devices for Display functionalities. Connection time is really unstable in loopback. 

  • Hi Steven,

    I have tested with either GUI 6.1.1 or 6.1.2 on TPS65988DH and both are able to connect consistently on all 3 scenarios.

    See attached PD logs.

    Since we have released the 6.1.2, please go ahead and use that.

    If you still see the issue, please send your pjt file.

    Regards,

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/138/both-DRP.tdc

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/138/DFP_2D00_UFP.tdc

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/138/UFP_2D00_DFP.tdc

  • Hi Sir,

    We found out that if we disable USB-C Try behavior on both ports, the connections could be made consistently within 8 seconds. Port 1 originally was designed with Try.SRC and Port 2 was designed with Try.SNK. 

    It seems in your case didn't implement any Try behavior on both ports, could you try with the setting above (Port1 Try.SRC, Port2 Try.SNK) and see if you could duplicate the issue?

    We'll try to test with 6.1.2 meanwhile. Thank you!

  • Hi Steven,

    I have tested again using try.src and snk and it's consistently establishing the contract.

    See attached pjt and pd logs with GUI 6.1.2.

    trysrc_snk.pjt

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/138/both-DRP_5F00_try_5F00_src_5F00_snk.tdc

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/138/DFP_5F00_UFP_5F00_try_5F00_src_5F00_snk.tdc