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.

TPS65987D: TPS65987D VIF and PD3.0 test

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS65987

Hi,

        We are using TPS65987D to develop PD3.0 power bank which works as DRP. And our customer ask for USB-IF PD3.0 certification.  I know TPS65987D has passed this certification and I also can find the TID information on USB-IF website. But in USB-IF website,  the description of TPS65987D is "Power delivery 3.0 , DRP,5V fixed ", as I know TPS65987 is a full function PD controller, it can support 5V~20V,but why the certification description is “5V fixed”? 

        In our application, we should support input / output 5V/3A 、9V/2A , and we also need get USB-IF certification, so you think TPS65987D can meet our requirement? 

       We have already done PD3.0 pre-scan with our EVT sample, there are so many question, and we believe it due to the 10.00 version firmware, I want to know how to get the newest version of TPS65987D firmware. 

       We also use TPS65987EVM to do PD 3.0 PRE-scan, there are also some fails, but maybe it due to a wrong VIF. So I want to how can I get an available VIF of TPS65987D to do PD3.0 test? 

      

Best regards,

Yu

  • Hi Yu,

    Here are answers to your concerns:

    1. TPS65987D can meet your application's power contract requirements. It has passed PD compliance with similar configurations. The silicon only test was performed with 5V fixed.

    2. To upgrade to the latest patch firmware, use the updated "TPS6598x configuration tool" found in the product folder under Tools & Software. The current version is v5.13 released 25-APR-2019.

    3. I agree compliance test failures are often due to VIF configuration issues. Sometimes differences between EVM and final product can also cause issues. I recommend finalizing the .pjt project configuration file in the TPS6598x configuration tool and then complete the VIF based on that.

    If you have specific VIF or test failure questions, feel free to post and we can discuss them here.

    Regards,
    Scott
  • Hi Scott,
    Thanks for your answers. Based on the three items I also want to know some information.
    1. TPS65987 pass PD3.0 compliance test with “DRP, 5V fixed” . Then how about “5V 9V, DRP ”,because our practical application is 5V 、9V two types volt. Can you help to do some internal test and give us a result or recommends?
    2. I am clear about how to get new version firmware, thanks.
    3. VIF has too many items, I think only IC vendor can fill it exactly for all the items. Is there any methods to get a VIF release from TI for reference ?

    Best regards,
    Yu Wang
  • Hi Scott,

            I attach some our PD3.0 test result. 

            The following is TPS65987EVM test result. The failure is mainly concentrate on USB PD consistency test / USB PD3.0 consistency test. I know some failure comes due to our VIF is not fully correct. So please provide an available VIF for PD3.0 test 

     

  • Hi,

    1. This setup will be fine in compliance as long as your .pjt project is correct for your system and settings are matching in VIF.

    3. We can help resolve the failures. You will have to correct the VIF to match your product. Let's only look at tests marked Stable. For each test you want to consider, I will need the actual failure message from the Test Report. Can you attached your current .pjt file?

    Thanks,
    Scott
  • Hi Scott,

             Our .pjt  files have already forward to you through TI internal mail process , please have a check. Many thanks !

    Best regards,

    Yu Wang

  • I cannot update the myself VIF. Here are some initial comments:

    TD.PD.VNDI.E1 VDM Identity
    ->Update VIF BCD to 0x710

    TD.PD.VNDI.E2 VDM SVID

    ->I do not have the .pjt file to check this failure. Ensure the VIF SVIDs matches the pjt
    ->Same issue for .E3

    TD.PD.VNDI.E5

     VIF sets Accept PR_swap to yes. Ensure this is desired and that the .pjt has both accept pr_swap options as selected
    TD.PD.VNDI.E7 and E9
     Looks like a tester issue. Rerun
    TD.PD.VNDI3.E1
     Looks like a tester issue. Rerun
    TD.PD.VNDI3.E10
     Related to E5 above. I think .pjt is set not to accept PR swaps. This is okay if you set VIF setting Accept PR_swap to NO
    TD.PD.VNDI3.E12
     Known issue with DH patch 5. Test is beta status and will not be run.
    TD.4.6.x series
     These tests are Ellisys beta status

    TD4.8.1
     Is Audio accessory mode enabled and desired?

    TD4.8.3
     Does this result reproduce? Scope traces of CC and VBUS may help us understand

    TD4.9.2
     Please double check that pjt settings for PR, DR, and Vconn swap are correct for the device and they match the VIF

    TD4.10.x
     Does this device enumerate as a host and device? The VIF is set as yes and the tester expects it to respond

    There are a block of failed tests starting at TD.PD.SRC.E11 these look like either tester failures or device failures. Please double check each and retest.

    Some general comments

    You have

    Modal_Operation_Supported_SOP: YES

    Does this device support alternate modes?

    Data_Capable_As_USB_Host_SOP: YES
    Data_Capable_As_USB_Device_SOP: YES

    Is this device capable of enumerating as a host and device?

    Please check these and retest.
  • Hi Scott,

            Ok, many thanks for your kindly help !

            I will follow your comments to do next step PD test.

         

            Another question, in our first version test board, we have no flash on my board, so the firmware in TPS65987D is the initial 10.00 version, then there are some bugs during debugging. Next step, I will add flash to store 10.06 version firmware just like the TPS65987EVM, do you think it can help to solve all the PD test failures? 

    Best regards,

    Yu Wang 

  • Yes, if there is no spi flash to store the firmware patch bundle and the firmware patch bundle is not sent to the TPS65987D using I2C at boot then the device will load its base image and report F707.10.00 (where the last .00 is the update or patch level). This means the device has no configuration information from the Application Config Tool and no firmware updates to solve issues. Adding flash to store a patch bundle will help a lot to solve these issues.

    Regards,
    Scott