• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 33 subscribers
  • Views 459 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TPS65982: Failures PD Compliance test with MQP

Pascal Berten
Prodigy 130 points
Part Number: TPS65982


When running the MQP PD 2.0 compliance test again a product based on TPS65982 I'm having several failures. I did also run the test against Ellisys but these results not seem to correlate.
Attached the results VIF and pjt file.

MQP result pjt and vif.zip


Any idea what I should change in the application Customization or VIF file to get this to PASS?

 

  • 0
    TI__Intellectual 1990 points

    Hi Pascal, MQP tester covers other aspects of the PD2.0 compliance spec, therefore you may see different results.

    There are some known issues as mentioned in the other thread which will be addressed in the future FW releases.

    There seem to be some VIF related failures which I have attempted to match up with the configuration, could you try the attached VIF?

    Thanks,

    Yoon

    Fullscreen pascal__dry-run__comecer__1__ti.txt Download 
    ; 
; USB-IF Vendor Info File Generator, Version 1.2.2.2
; 

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   Intro tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
$VIF_Specification: "Revision 1.36, Version 1.0"
$VIF_Producer: "USB-IF Vendor Info File Generator, Version 1.2.2.2"
$Vendor_Name: "pascal"
$Model_Part_Number: "dry run"
$Product_Revision: "comecer"
$TID: "1"
VIF_Product_Type: 0        ; Port
$Port_Label: "ti"

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   VIF Product tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Connector_Type: 2        ; USB Type-C�
USB_PD_Support: YES
PD_Port_Type: 0        ; Consumer Only
Type_C_State_Machine: 1        ; SNK
Port_Battery_Powered: NO
BC_1_2_Support: 0        ; None

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   General PD Settings tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
PD_Specification_Revision: 1        ; Revision 2.0
SOP_Capable: YES
SOP_P_Capable: NO
SOP_PP_Capable: NO
SOP_P_Debug_Capable: NO
SOP_PP_Debug_Capable: NO
USB_Comms_Capable: NO
DR_Swap_To_DFP_Supported: NO
DR_Swap_To_UFP_Supported: NO
Unconstrained_Power: NO
VCONN_Swap_To_On_Supported: NO
VCONN_Swap_To_Off_Supported: NO
Responds_To_Discov_SOP_UFP: NO
Responds_To_Discov_SOP_DFP: NO
Attempts_Discov_SOP: NO

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   USB Type-C tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Type_C_Supports_VCONN_Powered_Accessory: NO
Type_C_Is_VCONN_Powered_Accessory: NO
Type_C_Is_Debug_Target_SNK: NO
Type_C_Can_Act_As_Host: NO
Type_C_Can_Act_As_Device: NO
Type_C_Is_Alt_Mode_Controller: NO
Type_C_Power_Source: 1        ; Bus-Powered
Type_C_Port_On_Hub: NO
Type_C_Supports_Audio_Accessory: NO
Captive_Cable: NO
Type_C_Sources_VCONN: NO

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   Sink tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
PD_Power_as_Sink: 16000        ; (16000 mW)
No_USB_Suspend_May_Be_Set: YES
GiveBack_May_Be_Set: NO
Higher_Capability_Set: NO
Num_Snk_PDOs: 2

    Snk_PDO_Supply_Type1: 0        ; Fixed
    Snk_PDO_Voltage1: 100        ; (5000 mV)
    Snk_PDO_Op_Current1: 50        ; (500 mA)

    Snk_PDO_Supply_Type2: 2        ; Variable
    Snk_PDO_Op_Current2: 90        ; (900 mA)
    Snk_PDO_Min_Voltage2: 100        ; (5000 mV)
    Snk_PDO_Max_Voltage2: 300        ; (15000 mV)

  • 0 in reply to Yu-Ning Lee
    Prodigy 130 points

    Same failures with this VIF anyhow it's time to release the firmware and cannot wait on an update. When doing an interoperability test against different wall chargers I'm not seeing a problem.

    What is your opinion, is it safe to release with this firmware knowing the issue we have?

  • 0 in reply to Pascal Berten
    TI__Intellectual 1990 points

    The compliance test has been a moving target and new failures are common with test spec/tester SW update, and as noted before, the known issues are to be addressed in the next update based upon the recent updates made to the tester SW for the upcoming USB IF compliance workshop next week.

    The end product operation may or may not be affected by the compliance failure which would be dependent upon the nature of the failure + application specific requirements.  

    BTW, I have observed most of the VIF issues are addressed with the VIF provided.  Other known failures would be observed in Ellisys and MQP.

  • 0 in reply to Yu-Ning Lee
    Prodigy 130 points

    Hi Yoon, ok clear, thanks.

    And if you join the workshop next week I might see you since I will be there ;-)