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.

TPS65983B: TPS65983B certification issue in GRL C2

Part Number: TPS65983B

Hi all,

 My customer use TPS65983B in dual port tapex creek project. They meet certification issue as below. Would you please helping to check what customer can modify in VIF or FW? Thanks for your kindly help. 

  If you need MPS schematic for TDA.2.3.1.2 / TDA.2.3.2.2 debug, I can send it to you by mail.

PD2.0 fail item:

*TDA.2.2.2.3 BMC PROT SEQ CHKCAP CP ACC

*TDA.2.2.2.4 BMC PROT SEQ CHKCAP NOMRK CP ACC    

*TDA.2.3.1.2 POW SRC LOAD CP ACC

*TDA.2.3.2.2 POW SRC TRANS CP ACC

       These four items are all “Consumer/Provider Accepting Swap”, and FW returns “Soft Reset” and fail, Needs FW help

PD3.0 fail item:

        *TD.PD.SNK3.E12

                Our FW response time is too long. Needs FW help.

        *TD.PD.VNDI3.E3

                In our case, we need to return “Not_Supported”, but we return “Not define(0)” Needs FW help

        *TD.PD.VNDI3.E12

                In our case, we don’t support fast role swap and should retrun “Not supported”, Need FW help.

 

customer.zip

 

Best regards,

Gary Teng

 

  • Hi Gary,

    I've assigned this issue to the relevant expert who will get back to you shortly

  • Hi Adam,

    have any idea or suggestion?

  • Hi Gary,

    Can you post the 83B FW version? Do you have the logs for the pd3.0 fail items?

    Thanks,

    Scott

  • Hi Scott,

    1. FW version is V6.67. I've attached customer's project in zip.

    2. Please see the attached file about failed items about PD3.

    Regards,

    Gary

    pd3.zip

  • Hi Gary,

    The pd3.zip file contains 3 logs:


    TD.PD.SNK3.E13

      NA

    1. TD.PD.SNK3.E13 SinkPPSPeriodicTimer Timeout

     

         DUT doesn't Requested APDO

    Can you check or attach the VIF and pjt? We need to check the configured PDO and PPS support.


     TD.PD.VNDI3.E12

     FAIL

    1. TD.PD.VNDI3.E12 FR Swap Without Signaling Source

     

         DUT failed to send not supported message, VI file FR_SWAP_REQD_TYPE_C_CURRENT_AS_INITIAL_SOURCE is updated as zero

    I also recommend checking the VIF to make sure FR_SWAP_REQD_TYPE_C_CURRENT_AS_INITIAL_SOURCE is set to NO, however we have seen tester issues related to FRS detection in the software used for this test and this may be resolved in a future update.


    TD.PD.VNDI3.E3

      FAIL

    1. TD.PD.VNDI3.E3 VDM Identity

      FAIL

     DUT's Product type mismatch wrt VI file {DUT sent: 0 ~ Vi-File:AMC}:

    I recommend updating the VIF to match the DUT value (DUT sent: 0).

    Regards,
    Scott

  • Hi Scott,

    thank for your reply and help,

    about the PD2.0 fail item, do you have any idea and suggestion? please kindly refer the attached.

    PD2.0 fail item:

    *TDA.2.2.2.3 BMC PROT SEQ CHKCAP CP ACC

    *TDA.2.2.2.4 BMC PROT SEQ CHKCAP NOMRK CP ACC    

    *TDA.2.3.1.2 POW SRC LOAD CP ACC

    *TDA.2.3.2.2 POW SRC TRANS CP ACC

           These four items are all “Consumer/Provider Accepting Swap”, and FW returns “Soft Reset” and fail, Needs FW help

    customer PD2.0 fail item.zip

  • Hi Tommy,

    I've requested help from GRL Support on this issue because I believe it is a tester issue. The C2 failure message is the same for all issues. This is my concern:

    For TDA.2.3.2.2, the failed checkpoint is BMC_POW_SRC_TRANS_CP_ACC_1 however in the trace I see DUT accept the PRSwap (line 20). This is the goal of the checkpoint in the test spec.The failure message is an unexpected SoftReset from DUT. The only DUT initiated SR is line 27, an SOP’ message. This looks allowable via PD2 spec because DUT is newly SRC after PRSwap and contract has not been established.

    I'll update when I have a reply from GRL.

    Regards,

    Scott

  • Hi Tommy,

    I also need to ask if this test with GRL is being done as part of the TBT certification process?

    Thanks,

    Scott

  • Hi Tommy, 

    The PD2 test failures are due to a workaround for a legacy device. You will not have issues in getting approval from Intel for TBT certification.

    Regards,

    Scott

  • Hi Admin,

    This Erin from GRL,

    For TDA.2.2.2.3 and TDA.2.2.2.4, we have found that the message ID didn't reset after softRest. 
    By the way, the message ID sometimes didn't greater than previous sent message. 

    You can find the described issue for message ID in attached file.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/138/Desktop.7z

  • Hi All,

    I'd like to restate that we are aware of the PD2 failures and that they are in place as a workaround for a legacy device. Intel is aware of this issue and it should not be a problem for this device to pass Intel TBT certification.

    Regards,

    Scott