• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 33 subscribers
  • Views 373 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.

TPS65983B: GRL C2 compliance test issue in 983B FW1.38.06 for type-c application

Gary Teng
Genius 5860 points
Part Number: TPS65983B
Other Parts Discussed in Thread: TDA2,

Hi all,

 My customer test their dock product by using GRL C2. There's a failed item about TDA2.2.5 but we have no idea how to fix it.

 " ID Header VDO bit B29~27 (PRODUCT TYPE UFP)is not set to the vendor supplied information"

 Would you please helping to check the issue by log as attached file? Thanks.

Best regards,

Gary Teng

8233.Desktop.zip

  • 0
    TI__Expert 4455 points

    Hi Gary,

    Can you let me know:

    -TBT Reference Design used

    -83B Gui and FW version

    -Attach the complete GRL log for the failed test (zip the folder and attach if possible)

    I need to double check the exact contents of the failed packet. Your VIF looks correct and should match the reference design (set as Peripheral).

    Regards,

    Scott

  • 0 in reply to Scott T
    Genius 5860 points

    Hi Scott,

     1. They uset 983B in type-c application 

     2. 983B GUI version 3.17 (for general application, not for TBT), Bin version 1.38.06

     3. You can see log in .html file.

     About the failed description:   ID Header VDO bit B29~27 (PRODUCT TYPE UFP)is not set to the vendor supplied information   << can we read / set ID header VDO bit B29~27 from log or is that we have to set it in VIF?

    Best regards,

    Gary

  • 0 in reply to Gary Teng
    TI__Expert 4455 points

    Hi Gary,

    I checked the default template in GUI Release "windows_64bit_TPS65983B_application_customization_3_17" supporting bin 1.38.06 and found that the default setting in the Transmit ID Data Object Register for UFP Product Type is "Undefined". This does not match the UFP Product setting in the VIF (as seen in GRL log) so compliance tests will show the failure posted.

    To fix this issue, the Product type in the Project needs to match the VIF. You can generate a new binary with updated Product Type by loading your current project file in the Configuration GUI and changing the product type in Transmit ID Data Object Register from Undefined to Peripheral. You can also instead update the product type in the VIF to Undefined if you feel this is the correct setting.

    The USBIF has updated the spec for allowed product types. I also recommend loading your VIF into the official USBIF VIF Tool. This will validate your settings are allowed based on the current spec.

    Regards,

    Scott

  • 0 in reply to Scott T
    Genius 5860 points

    Hi Scott,

     I modify GUI with your suggestion and pass the test. Thanks for your kindly help.

     And I think some other failed item (TIDA.2.3.1.1 /  2.3.1.2 / 2.3.2.1 / 2.3.2.2 / 2.3.3.1) can't be fix by FW setting right...

    Best regards,

    Gary

  • 0 in reply to Gary Teng
    TI__Expert 4455 points

    Hi Gary,

    Yes, issues on these test cases are more likely to be caused by changes in the test spec versus the deprecated firmware release.

    Regards,

    Scott