USB4 Gen3

Announcements

Live Webinar: USB-C adoption. Simple & Cost-efficient solutions | April 18th @9am or 5pm CEST. Register now !

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
Alan
Level 1
Level 1
5 sign-ins First reply posted First question asked

To whom it may concerned ,

a CCG2 is emplyed on our USB4 Gen3 cable product which undergoes the compliance test w/ 3 items failed — 

1)Ra is out of 800 Ohm ~ 1.2K Ohm ( 3 pcs  tested and 1/3 ok w/ Vconn @423 mV ,and 2 out of 3 NG w/ Vconn = 402 mV )

2) PD3 modes - checking SVIDs ( The UUT shall return a number of SVIDs in between 1 and 1, actual 2 (TEST.PD.VDM.CBL.1#3)

3)Checking Headers (Message ID 0): Manufacturer String shall be null terminated (COMMON.CHECK.PD.10#1 x 1)

Kindly advise the countermeasure of the above 3 issues.

f.y.i. 1)NG test report 2)SVID on VIF 3)SVIDs setting on CCG2 are on the attached photos。

Thank you and best Regards,

Alan Huang 

1B636117-D33E-48D1-9D05-A40A2C3890A7.png

BDBD6DA1-DB7E-4E6C-87A0-54C5428C9183.png

3AA78ADA-2D7A-49D6-8664-D27FF9F3D4B7.jpeg

C1A91CBB-60FD-4054-87DB-1B3553F1A060.jpeg

0 Likes
1 Solution
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Hello Alan,

Get_manufacturer_info message is defined in PD3.1 specification, the correct format is below:

ShifangZ_26_0-1635911582258.pngShifangZ_26_1-1635911617425.png

 

From the Ellisys trace you attached, it seems the packages of response Get_manufacturer_info message is correct. You could discuss with tester with the specification and identify why tester reports error on Message ID.

 

Best Regards,

Lisa

View solution in original post

0 Likes
5 Replies
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Hello ,

1)Ra is out of 800 Ohm ~ 1.2K Ohm

>> Recommend you check the Diode on VCONN is close to the specification list on the datasheet or not?

ShifangZ_26_0-1634564661780.png

 

2)PD3 modes - checking SVIDs

>> It seems that the VIF is not match the firmware configuration, The VIF only have one, but firmware have two. 

 

3) Checking Headers (Message ID 0): Manufacturer String shall be null terminated

>> Could you please kindly add the ellisys trace file for this specified test? I would like to take a look which specified NULL is looking for.

 

Best Regards,

Lisa

0 Likes
lock attach
Attachments are accessible only for community members.

Hi

1)Ra is out of 800 Ohm ~ 1.2K Ohm

>> Recommend you check the Diode on VCONN is close to the specification list on the datasheet or not?
 
Alan 2021-10-19 : Do you mean if the diode's characteristic is equal or similar to NSR0620P2T5G  ? and appreciate to learn  how the diode impact the Ra ?
 

2)PD3 modes - checking SVIDs

>> It seems that the VIF is not match the firmware configuration, The VIF only have one, but firmware have two.

Alan 2021-10-19 :The issue is closed if firmware is configured to one SVID ... but is that ok ?
 

3) Checking Headers (Message ID 0): Manufacturer String shall be null terminated

>> Could you please kindly add the ellisys trace file for this specified test? I would like to take a look which specified NULL is looking for.

Alan 2021-10-19 :  attached is Ellisys USB compliance report for your reference
 
BTW , there're new issues found on LAB test , kindly check and advise , thanks !
 
4-1) Cable did not respond with GoodCRC and VDM [CAB_PHY_MSG_1] 
4-2) Cable VDO B23:B21 - (VDO Vers) are not 011b. [CAB_PROT_DISCOV_R3_D4a]
4-3) Number of VDOs is not 6. [CAB_PROT_DISCOV_R3_F1]
( MQP test report attached )
 
5) CVSh could not enumerate or maintain traffic with CVSd at USB 2.0. ( Teledyne Lecroy USB compliance result attached )
0 Likes

Hi Lisa,

trace reports are in .mrq , ult , usb file formats and are invalid to be attached here , what should we proceed ?

Regards,

Alan

 

0 Likes

8005E9D0-DCAD-4865-A270-143788F5F7BE.jpeg

 Hi

trace report of message ID issue for your reference .

Alan

0 Likes
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Hello Alan,

Get_manufacturer_info message is defined in PD3.1 specification, the correct format is below:

ShifangZ_26_0-1635911582258.pngShifangZ_26_1-1635911617425.png

 

From the Ellisys trace you attached, it seems the packages of response Get_manufacturer_info message is correct. You could discuss with tester with the specification and identify why tester reports error on Message ID.

 

Best Regards,

Lisa

0 Likes