「USB功率传输符合性测试规范1.4版」

USB

需积分: 17 158 浏览量更新于2023-12-31 收藏 3.11MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

USB Power Delivery Compliance Test Specification是一个针对USB PD3.1设备的符合性测试规范。该文档涵盖了USB-IF对USB PD2.0和PD3.1规范第5至8章和第10章要求的符合性测试。本规范的修订版本为1.4 Version 3，发布日期为2022年4月22日。 USB Power Delivery是一种开放标准的充电技术，它允许充电器和设备之间以高速和高功率传输电力。USB Power Delivery允许设备通过USB接口进行快速充电，并支持双向电力传输。该技术可广泛应用于移动设备、电脑、显示器、汽车等各个领域。为了保证USB Power Delivery设备的互操作性和性能，USB-IF提出了一系列的符合性测试要求。USB Power Delivery Compliance Test Specification规定了测试设备在符合USB PD2.0和PD3.1规范中相关章节的要求的情况下的行为和性能。该规范涵盖了以下主要方面的测试： 1. 电源能力测试：测试设备的最大功率传输能力、电源协商能力和电源切换能力等。 2. 协议测试：测试设备的通信协议符合USB PD2.0和PD3.1规范的要求，包括消息格式、协议交互流程和错误处理等。 3. 电力发送测试：测试设备在不同电压和电流条件下的电力发送能力，包括电压和电流稳定性、电源过载保护等。 4. 电力接收测试：测试设备对于外部电源提供的电力的接收能力，包括电压和电流稳定性、电源过载保护等。 5. 安全性测试：测试设备在异常情况下的安全性能，包括过压保护、过流保护和短路保护等。此外，USB Power Delivery Compliance Test Specification还规定了测试设备的测试环境和测试方法，包括测试仪器的使用、测试步骤的执行和测试结果的评估等。通过进行USB Power Delivery符合性测试，可以确保设备在各种使用场景下的稳定性和互操作性。符合性测试还能确保设备对异常情况的响应能力，从而提高设备的安全性。总之，USB Power Delivery Compliance Test Specification是一个非常重要的规范，它为USB PD3.1设备的开发和测试提供了指导和标准。通过进行符合性测试，可以保证设备的性能和安全性，促进USB Power Delivery技术的广泛应用。

资源详情

资源推荐

USB Power Delivery Compliance Test Specification, Revision 1.4 Version 3 Page 16

2. If VIF field Port_Source_Power_Type is not set to Shared, then the preparation procedure is

complete.

3. Otherwise, if the VIF field Master_Port is set to YES, the Tester sends a BIST Shared Test Mode

Entry message to the UUT, and the preparation procedure is complete.

4. If the VIF field Master_Port is set to NO, the Tester uses the VIF to locate a component which

has the VIF field Master_Port parameter is set to YES and requests the operator to connect the

Test Cable to that Port on the UUT. If one is not found, the check fails [TEST.PREP.PR.1#1]

5. When this has been done, the Tester sends a BIST Shared Mode Test Entry message to the UUT.

6. The Tester requests the operator to connect the Test Cable to the Port under Test.

7. When this has been done, the preparation procedure is complete.

TEST NOTES:

• Once the UUT is placed in the test mode it is expected to remain in the test mode till it is

powered down.

• The test procedure should be performed only one time per port.

3 Common Checks, Bring-up Procedures, and Common Procedures

This chapter describes the Common Checks, Bring-up Procedures, and Common Procedures that would

be repeated in the tests described in the subsequent chapters.

3.1 Common Checks

3.1.1 PD2 and PD3 Modes

The common procedures in this subsection are applicable when the test is running in PD2 and PD3

modes.

COMMON.CHECK.PD.1 Check Preamble

Description: The Tester performs the physical layer checks on the Preamble sent by the UUT.

Check Applicability: All PD messages

The Tester performs the following checks on the Preamble of all PD messages

[COMMON.CHECK.PD.1#1]

- The check fails if the first bit of the Preamble does not start at least tInterFrameGap after the

end of the last bit of the preceding message

- The check fails if the Preamble is not a 64-bit sequence of alternating '0's and '1's. (In practice

the last 60 bits are checked as there is some uncertainty about detecting the initial bits.)

- The check fails if the Preamble does not end with a single “one”.

USB Power Delivery Compliance Test Specification, Revision 1.4 Version 3 Page 17

COMMON.CHECK.PD.2 Check Message Header

Description: The Tester performs the protocol checks on the Message Header sent by the UUT.

Check Applicability: All PD messages except GoodCRC

The Tester performs the following checks on the Message Header of all PD messages except GoodCRC

and Returned BIST Counters: [COMMON.CHECK.PD.2#1]

1. For Source Capabilities and Discover Identity messages before the first response from the Tester

after detaching, Hard Reset or Error Recovery

a. Bit 15 (Extended for PD3). The check fails if this field is not set to 0b

b. Bit 7…6 (Specification Revision). The check fails if this field is not set to 10b. If the

message is a Discover Identity over SOP’ and it is not the first time the message has

been sent after the detach, Hard Reset, or Error Recovery, this check does not apply.

c. Bit 4…0 (Message Type). The check fails if the Message Type is not valid

2. All messages

a. Bits 7…6 (Specification Revision). The check fails if this field is set to either 00b or 11b.

3. Bits 14…12: Number of Data Objects

a. When the Extended field is set to zero, the check fails if Number of Data Objects field

does not match the number of 32-bit Data Objects that follow the Message Header

b. When the Extended bit (in the Message Header) is set to 1b and Chunked bit (in the

Extended Message Header) is set to 1b, the check fails if the size in bytes of the payload

following the Message Header is not 4 times the Number of Data Objects

c. When the Extended bit (in the Message Header) is set to 1b and Chunked bit (in the

Extended Message Header) is set to 0b, the check fails if Number of Data Objects field is

not set to 000b

d. Data messages:

i. Request message: Number of Data Objects = 1

ii. Battery_Status message: Number of Data Objects = 1

iii. Alert message: Number of Data Objects = 1

iv. Get_Country_Info message: Number of Data Objects = 1

v. Enter_USB message: Number of Data Objects = 1

vi. EPR_Request message: Number of Data Objects = 2

4. Bits 11…9: MessageID. The check fails if the value is not 000b under the following conditions:

a. The first message on each SOP* type after a Hard Reset was sent or received

b. The message is a Soft_Reset

c. The first message on the same SOP* type after receiving Soft_Reset

d. The first message on SOP after a successful Power Role Swap

e. The first message on SOP after a successful Fast Role Swap

f. The first message on each SOP* type upon initial entry to Attached state

g. The first message on each SOP’ and SOP” after a Cable Reset

5. Bits 11...9: MessageID. If MessageID is incremented for a valid retry scenario as described in the

test procedures, fail the check. (On retry the message all fields should remain the same from the

previously received message.) Else, fail the check if MessageID is not incremented.

USB Power Delivery Compliance Test Specification, Revision 1.4 Version 3 Page 18

6. Bits 11…9: MessageID. Except for conditions as mentioned above, the check fails if MessageID is

incremented by three comparing to the previously received message

7. Bit 8: Port Power Role (SOP packet type only)

a. The check fails if Port Power Role does not represent the UUT port power role

b. For a Ping or GotoMin message, the check fails if Port Power Role is not Source

c. For a Request, the check fails if Port Power Role is not Sink

d. The check fails if the Port Power Role is not Sink for the first PS_RDY during a Power

Role Swap

e. The check fails if the Port Power Role is not Source for the second PS_RDY during a

Power Role Swap

8. Bit 8: Cable Plug (SOP’ and SOP’’), the Tester checks that it follows the rule:

a. 0b Message originated from a DFP or UFP

b. 1b Message originated from a Cable Plug or VP

9. Bit 5: Port Data Role (SOP packet type only). The check fails if Port Data Role does not represent

the UUT port data role

10. Bit 5: Port Data Role (SOP’ and SOP’’ packet types). The check fails if Port Data Role is not set to

zero

COMMON.CHECK.PD.3 Check GoodCRC

Description: The Tester performs the protocol checks on the GoodCRC message received by the Tester.

Check Applicability: All GoodCRC messages except in TEST.PD.PHY.ALL.5 Receiver Interference Rejection

The Tester performs the following checks on the reception of GoodCRC message:

1. The check fails if the GoodCRC is not received or received after tTransmit max has expired. The

delay is measured between the last bit of the EOP of Tester sent message and the first bit of the

Preamble of the UUT sent GoodCRC Message. [COMMON.CHECK.PD.3#1]

2. Perform the following checks on the Message Header of GoodCRC message:

[COMMON.CHECK.PD.3#2]

a. Bit 15 (Reserved for PD2, Extended for PD3). The check fails if this field is not set to 0b

b. Bits 11…9: MessageID. The check fails if MessageID is not the same as the value in the

preceding message sent by the Tester

c. Bit 8: Port Power Role (SOP packet type only). The check fails if Port Power Role does

not represent the UUT port power role.

d. Bit 8: Cable Plug (SOP’ and SOP’’), the Tester checks that it follows the rule:

i. If VIF_Product_Type is 0 (Port Product) and

Captive_Cable_is_eMarked as NO, the check fails if the field is not

set to 0.

ii. If VIF_Product_Type is 1 (Cable), the check fails if the field is not

set to 1.

e. Bits 7…6 (Specification Revision). The check fails if this field is not set to 01b when the

message this GoodCRC is responding to has a Specification Revision field set to 01b

f. Bits 7…6 (Specification Revision). The check fails if this field is set to 11b.

USB Power Delivery Compliance Test Specification, Revision 1.4 Version 3 Page 19

g. Bit 5: Port Data Role (SOP packet type only). The check fails if Port Data Role does not

represent the UUT port data role

h. Bit 5: Port Data Role (SOP’ and SOP’’ packet types). The check fails if Port Data Role is

not set to zero

i. Bits 4…0 (Message Type) is set to 0001b

COMMON.CHECK.PD.4 Check Atomic Message Sequence Response

Description: The Tester performs additional protocol checks on response messages as part of the Atomic

Message Sequence (AMS).

Check Applicability: All PD response messages when an AMS has started

The Tester performs the following check when an AMS has started:

1. As part of an AMS, the check fails if the UUT does not respond to a message (sent by the

Tester) within tSenderResponse max or tVDMSenderResponse max from the last bit of the

EOP of the GoodCRC message sent [COMMON.CHECK.PD.4#1]. The following are the

exceptions:

a. PS_RDY message as part of Power Negotiation AMS

b. PS_RDY message as part of Power Role Swap AMS

c. PS_RDY message as part of VCONN Swap AMS

d. Security_Response message as part of Security AMS

e. Enter Mode command request as part Enter Mode AMS

f. Exit Mode command request as part Exit Mode AMS

g. Not Supported message as part of chunked request

COMMON.CHECK.PD.5 Check Unexpected Messages and Signals

Description: The Tester performs additional protocol checks on unexpected messages sent by the UUT.

Check Applicability: All PD messages

Unless specifically mentioned, the check fails if Soft_Reset message (using SOP packet) is sent by the

UUT during a test [COMMON.CHECK.PD.5#1].

Unless specifically mentioned, the check fails if the UUT sends a Hard Reset or a Cable Reset signal

[COMMON.CHECK.PD.5#2].

Unless specifically mentioned, the check fails if GotoMin message is sent by the UUT

[COMMON.CHECK.PD.5#3]. The Tester does not set the GiveBack flag during a test.

The following messages sent by the UUT are unexpected during a test when the Tester is in

PE_SRC_Ready, PE_SNK_Ready or PE_CBL_Ready state (Policy Engine States as described in the base

specification), and the check fails. This does not apply to such messages when they are expected in

these states as a normal part of the protocol (examples are Not Supported received after an Alert,

Firmware_Update_Request or Security_Request). [COMMON.CHECK.PD.5#4]:

剩余285页未读，继续阅读

sumansuman

粉丝: 2
资源: 12

会员权益专享

「USB功率传输符合性测试规范1.4版」

USB Power Delivery 3.0 Specification

Universal Serial Bus Revision 3.0 Compliance Test Specification

USB4电气一致性测试规范USB4 Electrical Compliance Test Specification V1.02

给我找个PD协议的文件资料,需要下载网址给我

USB Compliance测试指令

USB Compliance运行前，需要对USB接口做的配置命令

USB COMPLAINCE 测试前需要对USB VID PID做哪些改动

dp 1.2a phy cts

pipe_tx_compliance

mipi d phy cts 1.2

ModuleNotFoundError: No module named 'torchaudio.compliance'

the compiler compliance specif

用perl语言将japi-compliance-checker工具实现导出json报告

compliance index

functional safety and proof of compliance pdf

编写SQL，按照表中字段的数据为PSGCC,PHBSX,PHBBJ,PSGHZ顺序，表名为compliance_contact_management，字段有GUID,MARKET_ID，Contactx_NO，CONTANCTS_NAME.

解释下这段代码 # 导入代码依赖 import torchaudio import torchaudio.compliance.kaldi as kaldi from ais_bench.infer.interface import InferSession import numpy as np from swig_decoders import map_batch import IPython

universal serial bus type-c connectors and cable assemblies compliance docum

会员权益专享

最新资源