• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 4687 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TPS65983: Failing TypeC tests

Dominic Plunkett69
Prodigy 175 points

Part Number: TPS65983

I'm having a problem with passing some TypeC tests.

I have selected a Provider only configuration I think. But the tester is see dual role.

 

Goal: Ensure Sink Capabilities from Provider is Rejected.
Events #75-130
PD Sequence Start (Request Sink Capabilities)
Event #75
PD Message - Get_Sink_Cap (from Tester) (SOP)
Event #76
PD Message - GoodCRC (from UUT) (SOP)
Event #77
PD Message - Sink Capabilities (from UUT) (SOP)
PDO#1 B29 - (Dual-Role) is not VIF specified value. [PROT_MSG_DATA_SNK_CAP_4]
FAIL
Vendor Parameter: Higher_Capability_Set not found in VIF. [VENDOR_INFO_MISSING]
FAIL
Vendor Parameter: Snk_PDO_Op_Current1 not found in VIF. [VENDOR_INFO_MISSING]
F*
Vendor Parameter: Num_Snk_PDOs not found in VIF. [VENDOR_INFO_MISSING]
F*
Num_Snk_PDOs not as specified - checks not completed. [VENDOR_INFO_MISSING]
F*
Event #78
PD Message - GoodCRC (from Tester) (SOP)
Get_Sink_Cap was not Rejected by UUT [BMC_PROT_SEQ_GETCAPS_3]
FAIL
(Previous Goal failed)

  • 0 in reply to Dominic Plunkett69
    TI__Genius 12990 points
    Hi Dominic,

    The template contains 0 sink PDOs however it is still a DRP. Its a DRP because the 83 is meant to be externally powered which means it never needs to act like a sink however a 5V@0A sink PDO is always needed to be able to attach to a DFP (or UFP). Therefore as a DRP, (6.4.1.1.3 of the PD3 spec states) you cant NACK your sink capabilities message, you have to have a valid sink capabilities response.

    Thanks
  • 0 in reply to Jeffrey Mueller
    Prodigy 175 points

    Thanks Jeff that has cleared up my understanding.

    I'm using the attached vendor Information file.

    I've also attached the test log. There are a few failures are these down to errors in the VIF ? Thanks in adavnce

    Report_RM_TBT3_U16_2017-06-29-09-07-42_PHY.html

    cambrionix__RM-TBT3-U16__1__0__1.txt 
    ; 
; USB-IF Vendor Info File Generator, Version 1.1.2.0
; 

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   Intro tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
$VIF_Specification: "Revision 1.12, Version 1.0"
$VIF_Producer: "USB-IF Vendor Info File Generator, Version 1.1.2.0"
UUT_Device_Type: 4        ; DRP
$Vendor_Name: "cambrionix"
$Model_Part_Number: "RM TBT3 U16"
$Product_Revision: "1"
$TID: "0"
$Port_Label: "1"

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

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   USB Type-C tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Type_C_State_Machine: 2        ; DRP
Type_C_Implements_Try_SRC: YES
Type_C_Implements_Try_SNK: NO
RP_Value: 2        ; 3A
Type_C_Is_VCONN_Powered_Accessory: NO
Type_C_Is_Debug_Target_SRC: NO
Type_C_Is_Debug_Target_SNK: NO
Type_C_Can_Act_As_Host: YES
Type_C_Host_Speed: 2        ; USB 3.1 Gen 2
Type_C_Can_Act_As_Device: YES
Type_C_Device_Speed: 0        ; USB 2
Type_C_Is_Alt_Mode_Controller: YES
Type_C_Is_Alt_Mode_Device: YES
Type_C_Power_Source: 0        ; Self-Powered
Type_C_BC_1_2_Support: 2        ; SRC
Type_C_Battery_Powered: NO
Type_C_Port_On_Hub: NO
Type_C_Supports_Audio_Accessory: YES
Captive_Cable: NO
Type_C_Sources_VCONN: YES

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   Source tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
PD_Power_as_Source: 15000        ; (15000 mW)
USB_Suspend_May_Be_Cleared: YES
Sends_Pings: NO
Num_Src_PDOs: 1

    Src_PDO_Supply_Type1: 0        ; Fixed
    Src_PDO_Peak_Current1: 0        ; 100% IOC
    Src_PDO_Voltage1: 100        ; (5000 mV)
    Src_PDO_Max_Current1: 300        ; (3000 mA)

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   Sink tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
PD_Power_as_Sink: 000        ; (000 mW)
No_USB_Suspend_May_Be_Set: NO
GiveBack_May_Be_Set: YES
Higher_Capability_Set: NO
Num_Snk_PDOs: 1

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

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   Dual Role tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Accepts_PR_Swap_As_Src: YES
Accepts_PR_Swap_As_Snk: YES
Requests_PR_Swap_As_Src: NO
Requests_PR_Swap_As_Snk: NO

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   SOP Discovery - Part One tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
Structured_VDM_Version_SOP: 0        ; V1.0
XID_SOP: 0
Data_Capable_as_USB_Host_SOP: YES
Data_Capable_as_USB_Device_SOP: YES
Product_Type_SOP: 2        ; Peripheral
Modal_Operation_Supported_SOP: YES
USB_VID_SOP: 0x2CD9
PID_SOP: 0x0100
bcdDevice_SOP: 0x0435

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;   SOP Discovery - Part Two tab
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
SVID_fixed_SOP: YES
Num_SVIDs_min_SOP: 2
Num_SVIDs_max_SOP: 2

    SVID1_SOP: 0x8087
    SVID1_modes_fixed_SOP: YES
    SVID1_num_modes_min_SOP: 1
    SVID1_num_modes_max_SOP: 1

        SVID1_mode1_enter_SOP: YES

    SVID2_SOP: 0xFF01
    SVID2_modes_fixed_SOP: YES
    SVID2_num_modes_min_SOP: 1
    SVID2_num_modes_max_SOP: 1

        SVID2_mode1_enter_SOP: YES

  • 0 in reply to Dominic Plunkett69
    TI__Genius 12990 points
    Hi Dominic,

    I am unfamiliar with the log you sent me. I will ask my team if they can help. From what I see, there are 12 errors. Are you wanting to know which errors are related to your VIF?

    Thanks
  • 0 in reply to Jeffrey Mueller
    Prodigy 175 points

    I suppose my question is 

    a) Have I made a mistake in the VIF file?

    b) Is my TypeC tester failing things incorrectly? 

    c) There is a bug in the TPS firmware?

  • 0 in reply to Dominic Plunkett69
    TI__Genius 12990 points
    Ok Thanks Dominic,

    Ill take a looksy and let you know soon.

    Thanks
  • 0 in reply to Jeffrey Mueller
    TI__Genius 12990 points
    Hi Dominic,

    Lets start with the VIF file,

    Are you manually generating VIF on USB-IF software: VIF generator 1.1.2.1?

    can you confirm the following fields are valid in the VIF? I have noticed some inconsistencies with another VIF.
    Type_C_Can_Act_As_Host: YES
    Type_C_Host_Speed: 2 ; USB 3.1 Gen 2
    Type_C_Can_Act_As_Device: YES
    Type_C_Device_Speed: 0 ; USB 2

    USB_VID_SOP: 0x2CD9
    PID_SOP: 0x0100
    bcdDevice_SOP: 0x0435


    Can you tell me what failing test you are most concerned with?
    I am still working on getting a valid 83 VIF sample file.

    Thanks
  • 0 in reply to Jeffrey Mueller
    Prodigy 175 points

    Hi,

    I'm using the VIF software generator from usb.org ( 1.1.2.0) I noticed 1.1.2.1 has now been released.

    I think the fields are correct for a thunderbolt device. 2CD9 etc is our VID

    I'm worried about any test that is going to  fail certification.

    Thanks

  • 0 in reply to Dominic Plunkett69
    TI__Genius 12990 points
    Hi Dominic,

    What tester are you using to generate the compliance report?

    Usually when there is a group of failing tests (BMC-PHY-xxx) the issue is in the VIF file. I will look at a delta of your .pjt and the template which you used and make these changes accordingly in the VIF generator and see if that generated VIF matches with yours.

    Thanks
  • 0 in reply to Jeffrey Mueller
    Prodigy 175 points

    Hi

    We are using the mpq electronics PD tester

    Thanks

  • 0 in reply to Dominic Plunkett69
    TI__Genius 12990 points

    Hi Dominic,

    how did you pick the VIF options? some are not consistent with what I am seeing in the I2C dump of your .pjt

    for instance

    Type_C_Implements_Try_SRC: YES
    Type_C_Implements_Try_SNK: NO

    I see it opposite in the dump.

    Did you change any configuration in the apex creek v3.05 template?

    Also, alot of the settings in the VIF are application specific, how am I supposed to know the details of the general settings tab and USB Type-C tab for your application?

    ***Right now, All I can do is make sure your VIF matches the 83 apex creek v3.05 template capabilities.

    Thanks

  • 0 in reply to Dominic Plunkett69
    Prodigy 175 points

    Hi

    If you have a VIF for the TPS65983 it would help me in finding errors in my VIF as I'm not exactly sure what is supported in the TPS65983.

    Thanks 

  • 0 in reply to Dominic Plunkett69
    Prodigy 175 points
    As our device is self powered I don't think we need to support Try_SNK ?
  • 0 in reply to Dominic Plunkett69
    Prodigy 175 points

    Hi

    Do you have a default VIF for the apex creek ?

    Thanks

  • 0 in reply to Dominic Plunkett69
    TI__Genius 12990 points

    Hi Dominic,

    Sorry for late reply on your issue. I have been in a job training since last monday and will resume helping you on thursday when I am done. I will send out an email to the team to see if I can find/make you a VIF for Apex Creek.

    Thanks

  • 0 in reply to Jeffrey Mueller
    TI__Genius 12990 points
    Hi Dominic,


    The BMC failures are not due to VIF. Usually from the board or test setup errors that result in failures for example the CC1/CC2 capacatiance is not correct. The foundation of the BMC failures could also be due to layout for example.

    For the VIF, there are variations in the VIF depending on how you implemented apex creek. We do not have a VIF for the TIDA. Maybe we can tackle a specific failure and we can narrow each failing case down one by one. Or we can also sure each parameter in your VIF is consistent with your apex creek design.