TPS65983B: How to fix the PD test .

Alex Liu12

Part Number: TPS65983B

Dear all

we use the TPS65983B to using the PD test .

The PD test report fail

OWER Delivery tests	GRL C2 v1.5.93.0 FW 1.3.98	Communication Engine Test	Fail	1. TDA.2.2.5 BMC PROT DISCOV ID Header VDO bit B31 (Data Capable as USB Host)is set to NO in the vendor supplied information 2. TDA.2.2.6 BMC PROT SEQ PRSWAP DUT does not respond for power role swap message
OWER Delivery tests	GRL C2 v1.5.93.0 FW 1.3.98	PD 3.0 Test	Fail	1. TD.PD.SNK3.E11 Receiving chunked extended message TD.PD.SNK3.E19 ChunkSenderResponseTimer Timeout DUT does not respond for chunked extended message 2. TD.PD.VDM3.E1 Fields Checks Discover Identity (ID Header): Dut Sent Invalid Connector type 3. TD.PD.VNDI3.E3 VDM Identity (ID Header): Dut Sent Invalid Connector type DUT's Data capable as USB Host mismatch with VIF {DUT sent: YES ~ VIF: NO}:

pls help me to how to fix ! thans !

over 4 years ago

0 Kedar_Sirdeshpande over 4 years ago

TI__Expert 3370 points

Hello,

Can you please share your PJT file and the corresponding VIF file? Do you have the compliance tester in house? or do you have to book a lab for this?

-Kedar

0 Alex Liu12 over 4 years ago

Intellectual 320 points

Thanks very much ?

1. pls tell me the full name of PJT file .

2. i can send the VIF to you . but pls tell me you e-mail or send the mail to me

3.yes we have book a lab to test .the lab is GRL

0 Kedar_Sirdeshpande over 4 years ago in reply to Alex Liu12

TI__Expert 3370 points

Hi Alex,

My apologies, I clicked on the "Resolve" by mistake.

1. This is the file that is saved based on your configuration using the Configuration GUI. Its extension is a ".pjt"
2. You can attach the VIF to the thread.

Regards,
Kedar

0 Alex Liu12 over 4 years ago in reply to Kedar_Sirdeshpande

Intellectual 320 points

Dear Kedar

pls tell me how to attachment the VIF to the thread . i can't the funtion .

thanks very much !

alex

0 Kedar_Sirdeshpande over 4 years ago in reply to Alex Liu12

TI__Expert 3370 points

Hi Alex,

Try Dragging and dropping the files into the text window or use the Insert->Image/Video/file option.

If that doesn't work, I have sent you a personal request and we can take this thread over email.

Regards,
Kedar

0 Alex Liu12 over 4 years ago in reply to Kedar_Sirdeshpande

Intellectual 320 points

pls check the attchment

Fullscreen ACASIS__AC-TB2D__0x1__NA.xml Download

<?xml version="1.0" encoding="utf-8"?>
<vif:VIF xmlns:opt="http://usb.org/VendorInfoFileOptionalContent.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:vif="http://usb.org/VendorInfoFile.xsd">
  <vif:VIF_Specification>3.14</vif:VIF_Specification>
  <vif:VIF_App>
    <vif:Vendor>USB-IF</vif:Vendor>
    <vif:Name>VIF Editor</vif:Name>
    <vif:Version>3.2.0.1</vif:Version>
  </vif:VIF_App>
  <vif:Vendor_Name>ACASIS</vif:Vendor_Name>
  <vif:Model_Part_Number>AC-TB2D</vif:Model_Part_Number>
  <vif:Product_Revision>0x1</vif:Product_Revision>
  <vif:TID>NA</vif:TID>
  <vif:VIF_Product_Type value="0">Port Product</vif:VIF_Product_Type>
  <vif:Certification_Type value="0">End Product</vif:Certification_Type>
  <vif:Product />
  <vif:Component>
    <vif:Port_Label>C</vif:Port_Label>
    <vif:Connector_Type value="2">Type-C®</vif:Connector_Type>
    <vif:USB4_Supported value="false" />
    <vif:USB_PD_Support value="true" />
    <vif:PD_Port_Type value="0">Consumer Only</vif:PD_Port_Type>
    <vif:Type_C_State_Machine value="1">SNK</vif:Type_C_State_Machine>
    <vif:Port_Battery_Powered value="false" />
    <vif:BC_1_2_Support value="0">None</vif:BC_1_2_Support>
    <vif:PD_Spec_Revision_Major value="3" />
    <vif:PD_Spec_Revision_Minor value="0" />
    <vif:PD_Spec_Version_Major value="0" />
    <vif:PD_Spec_Version_Minor value="0" />
    <vif:PD_Specification_Revision value="2">Revision 3</vif:PD_Specification_Revision>
    <vif:SOP_Capable value="true" />
    <vif:SOP_P_Capable value="true" />
    <vif:SOP_PP_Capable value="false" />
    <vif:SOP_P_Debug_Capable value="false" />
    <vif:SOP_PP_Debug_Capable value="false" />
    <vif:Manufacturer_Info_Supported_Port value="true" />
    <vif:Manufacturer_Info_VID_Port value="32903">8087</vif:Manufacturer_Info_VID_Port>
    <vif:Manufacturer_Info_PID_Port value="0">0000</vif:Manufacturer_Info_PID_Port>
    <vif:Unconstrained_Power value="false" />
    <vif:ID_Header_Connector_Type_SOP value="3">USB Type-C® Plug</vif:ID_Header_Connector_Type_SOP>
    <vif:Chunking_Implemented_SOP value="true" />
    <vif:Unchunked_Extended_Messages_Supported value="true" />
    <vif:Security_Msgs_Supported_SOP value="false" />
    <vif:Num_Fixed_Batteries value="0" />
    <vif:Num_Swappable_Battery_Slots value="0" />
    <vif:USB_Comms_Capable value="true" />
    <vif:DR_Swap_To_DFP_Supported value="false" />
    <vif:DR_Swap_To_UFP_Supported value="false" />
    <vif:VCONN_Swap_To_On_Supported value="false" />
    <vif:VCONN_Swap_To_Off_Supported value="false" />
    <vif:Responds_To_Discov_SOP_UFP value="true" />
    <vif:Responds_To_Discov_SOP_DFP value="false" />
    <vif:Attempts_Discov_SOP value="false" />
    <vif:Type_C_Can_Act_As_Host value="false" />
    <vif:Type_C_Can_Act_As_Device value="true" />
    <vif:Type_C_Supports_Audio_Accessory value="false" />
    <vif:Type_C_Supports_VCONN_Powered_Accessory value="false" />
    <vif:Type_C_Is_VCONN_Powered_Accessory value="false" />
    <vif:Type_C_Is_Debug_Target_SNK value="false" />
    <vif:Captive_Cable value="true" />
    <vif:Captive_Cable_Is_eMarked value="false" />
    <vif:Type_C_Port_On_Hub value="true" />
    <vif:Type_C_Power_Source value="0">Externally Powered</vif:Type_C_Power_Source>
    <vif:Type_C_Sources_VCONN value="false" />
    <vif:Type_C_Is_Alt_Mode_Controller value="false" />
    <vif:Type_C_Is_Alt_Mode_Adapter value="false" />
    <vif:Device_Supports_USB_Data value="true" />
    <vif:Device_Speed value="3">USB 3.2 Gen 1x2</vif:Device_Speed>
    <vif:Device_Max_USB2_Speed value="2">High Speed</vif:Device_Max_USB2_Speed>
    <vif:Device_Contains_Captive_Retimer value="false" />
    <vif:Device_Truncates_DP_For_tDHPResponse value="false" />
    <vif:PD_Power_As_Sink value="15000">15000 mW</vif:PD_Power_As_Sink>
    <vif:No_USB_Suspend_May_Be_Set value="false" />
    <vif:GiveBack_May_Be_Set value="false" />
    <vif:Higher_Capability_Set value="false" />
    <vif:FR_Swap_Reqd_Type_C_Current_As_Initial_Source value="0">FR_Swap not supported</vif:FR_Swap_Reqd_Type_C_Current_As_Initial_Source>
    <vif:Num_Snk_PDOs value="1" />
    <vif:SnkPdoList>
      <vif:SnkPDO>
        <vif:Snk_PDO_Supply_Type value="0">Fixed</vif:Snk_PDO_Supply_Type>
        <vif:Snk_PDO_Voltage value="100">5000 mV</vif:Snk_PDO_Voltage>
        <vif:Snk_PDO_Op_Current value="300">3000 mA</vif:Snk_PDO_Op_Current>
      </vif:SnkPDO>
    </vif:SnkPdoList>
    <vif:XID_SOP value="0" />
    <vif:Data_Capable_As_USB_Host_SOP value="false" />
    <vif:Data_Capable_As_USB_Device_SOP value="true" />
    <vif:Product_Type_UFP_SOP value="2">PDUSB Peripheral</vif:Product_Type_UFP_SOP>
    <vif:Product_Type_DFP_SOP value="0">Undefined</vif:Product_Type_DFP_SOP>
    <vif:Modal_Operation_Supported_SOP value="true" />
    <vif:USB_VID_SOP value="32903">8087</vif:USB_VID_SOP>
    <vif:PID_SOP value="0">0000</vif:PID_SOP>
    <vif:bcdDevice_SOP value="1639">0667</vif:bcdDevice_SOP>
    <vif:SVID_Fixed_SOP value="false" />
    <vif:Num_SVIDs_Min_SOP value="1" />
    <vif:Num_SVIDs_Max_SOP value="1" />
    <vif:SOPSVIDList>
      <vif:SOPSVID>
        <vif:SVID_SOP value="32903">8087</vif:SVID_SOP>
        <vif:SVID_Modes_Fixed_SOP value="true" />
        <vif:SVID_Num_Modes_Min_SOP value="1" />
        <vif:SVID_Num_Modes_Max_SOP value="1" />
        <vif:SOPSVIDModeList>
          <vif:SOPSVIDMode>
            <vif:SVID_Mode_Enter_SOP value="true" />
            <vif:SVID_Mode_Recog_Value_SOP value="0">00000000</vif:SVID_Mode_Recog_Value_SOP>
          </vif:SOPSVIDMode>
        </vif:SOPSVIDModeList>
      </vif:SOPSVID>
    </vif:SOPSVIDList>
  </vif:Component>
</vif:VIF>

0 Kedar_Sirdeshpande over 4 years ago in reply to Alex Liu12

TI__Expert 3370 points

Hi Alex,

Please share the project file with the "pjt" extension as well as your complete compliance report (html) also.

Regards,
Kedar

0 Alex Liu12 over 4 years ago in reply to Kedar_Sirdeshpande

Intellectual 320 points

pls check the prj file TB3_2DP.pjt

0 Kedar_Sirdeshpande over 4 years ago in reply to Alex Liu12

TI__Expert 3370 points

Hi Alex,

For TDA.2.2.5 BMC PROT DISCOV ID Header VDO bit B31 (Data Capable as USB Host)is set to NO in the vendor supplied information &
DUT's Data capable as USB Host mismatch with VIF {DUT sent: YES ~ VIF: NO}:
- Set the VIF parameter: "Type_C_Can_Act_As_Host" to "YES"

For 2. TDA.2.2.6 BMC PROT SEQ PRSWAP DUT does not respond for power role swap message
- Your VIF is missing a setting for "Accepts_PR_Swap_As_Src" and "Accepts_PR_Swap_As_Snk". Please set appropriate values.

For 3. TD.PD.SNK3.E11 Receiving chunked extended message TD.PD.SNK3.E19 ChunkSenderResponseTimer Timeout DUT does not respond for chunked extended message
- Your Project file does not support chunking. Please change the VIF parameter "Chunking_Implemented_SOP" to "NO"

For 2. TD.PD.VDM3.E1 Fields Checks Discover Identity (ID Header): Dut Sent Invalid Connector type &
TD.PD.VNDI3.E3 VDM Identity (ID Header): Dut Sent Invalid Connector type
- The PD test specification has changed since TPS65983B was last certified.. Try to set bits 30:29 of least significant 32 bit value in Transmit Identity Register's Raw Register field view to "3" to match your VIF setting of "Plug".

Please try these changes and let me know. Also, as requested earlier, please provide the failure reports. They have additional data that helps understand the failure better.

Regards,
Kedar

0 Alex Liu12 over 4 years ago in reply to Kedar_Sirdeshpande

Intellectual 320 points

For TDA.2.2.5 BMC PROT DISCOV ID Header VDO bit B31 (Data Capable as USB Host)is set to NO in the vendor supplied information &DUT's Data capable as USB Host mismatch with VIF {DUT sent: YES ~ VIF: NO}:
- Set the VIF parameter: "Type_C_Can_Act_As_Host" to "YES"
------> For our Dut, it is connected to the computer, belongs to UFP, so it is device
For 2. TDA.2.2.6 BMC PROT SEQ PRSWAP DUT does not respond for power role swap message
- YourVIF is missing a setting for "Accepts_PR_Swap_As_Src" and "Accepts_PR_Swap_As_Snk". Please set appropriate values.
------>If the DUT Type are 1(Consumer/Provider), 2 (Provider/Consumer), or 4 (DRP)can choose setting as "Accepts_PR_Swap_As_Src" and "Accepts_PR_Swap_As_Snk" in the VIF generator，
but now it declares as consumer，so can not setting as you said。
For 3. TD.PD.SNK3.E11 Receiving chunked extended message TD.PD.SNK3.E19 ChunkSenderResponseTimer Timeout DUT does not respond for chunked extended message
- Your Project file does not support chunking. Please change the VIF parameter "Chunking_Implemented_SOP" to "NO"
------>we will verify it again.
For 2. TD.PD.VDM3.E1 Fields Checks Discover Identity (ID Header): Dut Sent Invalid Connector type &
TD.PD.VNDI3.E3 VDM Identity (ID Header): Dut Sent Invalid Connector type
- The PD test specification has changed since TPS65983B was last certified.. Try to set bits 30:29 of least significant 32 bit value in Transmit Identity Register's Raw Register field view to "3" to match your VIF setting of "Plug".
------>The current software of the DUT declare "00b -- Reserved, for compatibility with Legacy systems". This requires software of the DUT declare that the TBT interface is plug (11b – USB Type-C Plug),

0 Kedar_Sirdeshpande over 4 years ago in reply to Alex Liu12

TI__Expert 3370 points

For #1: In the project file, in the Transmit Identity Configuration Register enable the bit corresponding to "Device" advertisement.

For #2: I would require PD logs and the complete compliance report (which I requested earlier also) to investigate.

For #4: Can you share PD logs along with compliance report? Isn't the manual update of "Connector Type" bits in the Tx Identity register's Header information reflecting your modifications during DiscIdentity process?

0 Alex Liu12 over 4 years ago in reply to Kedar_Sirdeshpande

Intellectual 320 points

Dear Kedar

1. how to set the :The PD test specification has changed since TPS65983B was last certified.. Try to set bits 30:29 of least significant 32 bit value in Transmit Identity Register's Raw Register field view to "3" to match your VIF setting of "Plug".