USB PD3.0 CTS r1.2 V2：合规测试规范

需积分: 10 160 浏览量更新于2024-07-09 收藏 2.42MB PDF 举报

USB PD3.0 Compliance Test Specification (Revision 1.2 V2) 是一份由USB-IF发布的文档，专门针对USB Power Delivery（USB PD）3.0设备的兼容性测试标准进行了详细规定。该文档涵盖了USB-IF对USB PD2.0和PD3.0规范中第5至8章以及第10章要求的测试流程。USB PD是一种电源管理技术，旨在提供灵活、高效且可扩展的充电解决方案，适用于各种电子设备，如智能手机、笔记本电脑和外部显示器。测试规格的目的是确保设备在USB PD生态系统中的互操作性和一致性，包括数据通信、电源协商、功率传输和安全功能。它要求制造商在开发USB PD3.0产品时，必须通过一系列严格的测试，以证明其产品符合USB-IF制定的标准，从而保证了设备在不同USB PD设备间的可靠性和性能。文档的核心内容可能包括： 1. **USB PD基础**：介绍了USB PD协议的基本原理，如Type-C接口、CC（Channel Communciation）信号、PD角色识别等，这对于设备如何进行功能检测和配置至关重要。 2. **电压和电流能力**：详细规定了设备支持的不同电压和电流等级，以及如何通过CC线进行协商，以确定供电和受电能力。 3. **功率路径管理**：涵盖如何正确地选择和管理不同的功率路径，确保在连接多个电源时的安全性和效率。 4. **保护机制**：涉及过载、短路、过热等保护措施，以防止设备损坏和用户伤害。 5. **安全功能**：测试对于错误处理、电源开关和电池管理系统（BMS）的验证，确保设备在发生异常情况时能正确响应。 6. **协议合规性**：检查设备是否准确执行PD协议的所有命令和事件，以及数据包的正确编码和解码。 7. **认证流程**：说明了制造商需遵循的步骤和文档提交过程，以便获得USB-IF的官方认证。 8. **版权许可**：明确指出这份测试规范仅限于用于评估产品是否符合USB PD规范，并非为了申请专利或修改专利申请。任何想要获取额外知识产权许可的第三方必须签署USB 3.0 Adopters Agreement。 USB PD3.0 Compliance Test Specification (v1.2) 是一个重要的资源，帮助设计者确保其产品在USB PD生态系统中的互操作性和质量，是电子设备制造商在开发USB PD3.0设备时不可或缺的技术参考。通过严格遵循该文档中的测试标准，制造商能够确保产品的可靠性和用户体验，同时符合USB-IF的市场准入要求。

USB Power Delivery Compliance Test Specification, Revision 1.2 V2 Page 16

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]:

In PD2 Mode:

- GoodCRC

- BIST

- Sink_Capabilities

- Accept

- Reject

- Wait

USB Power Delivery Compliance Test Specification, Revision 1.2 V2 Page 18

Perform the following checks on all Source Capabilities messages : [COMMON.CHECK.PD.7#1]

1. Without receiving a SOP' Discover Identity Request message from the UUT, the check fails if VIF

field Captive_Cable = No and the UUT sends Source Capabilities offering currents greater than

3A and/or voltages greater than 20V

2. The Tester checks the Number of Data Objects field in the Message Header

a. In PD3 mode, the check fails if the Number of Data Objects field in the Message Header

is not equal to VIF field Num_Src_PDOs.

b. In PD2 mode, the check fails if the Number of Data Objects field in the Message Header

is not equal to VIF field Num_Src_PDOs minus number of PPS PDOs (count of how many

Src_PDO_Supply_TypeN is set to PPS).

3. For the first PDO, the Tester check the consistency

a. B31…30 (Fixed Supply) set to 00b

b. B29 (Dual-Role Power) set to 1b if VIF field PD_Port_Type is set to Consumer/Provider,

Provider/Consumer or DRP.

c. B28 (USB Suspend Supported) set to 1b if VIF field USB_Suspend_May_Be_Cleared = NO

d. B27 (Unconstrained Power) matches VIF field Unconstrained_Power

e. B26 (USB Communications Capable) matches VIF field USB_Comms_Capable

f. B25 (Dual-Role Data) set to 1b if VIF field DR_Swap_To_UFP_Supported or

DR_Swap_To_DFP_Supported = YES

g. For Source Capabilities message before the first response from the Tester

i. Bit 24 (Unchunked Extended Messages Supported) matches VIF field

Unchunked_Extended_Messages_Supported

ii. Bits 23…22 (Reserved) set to 00b

h. For Source Capabilities message after the Tester has sent Request message

i. Bit 24 (Unchunked Extended Messages Supported) matches VIF field

Unchunked_Extended_Messages_Supported if the test is running in PD3 mode

ii. Bits 23…22 (Reserved) set to 00b if the test is running in PD3 mode

iii. Bits 24…22 (Reserved) set to 000b if the test is running in PD2 mode

i. B21…20 (Peak Current) matches VIF field Src_PDO_Peak_Current1

j. B19…10 (Voltage) set to 5V

k. B9…0 (Maximum Current) matches VIF field Src_PDO_Max_Current1

4. If it is not the first Fixed Supply PDO, check that B29…22 are set to zero

5. If it is a Programmable Power Supply APDO, check that B26…25, B16 and B7 are set to zero

6. The Tester compares all PDOs to VIF field PD_Power_as_Source and check that they meet the

requirements of the Power Rules.

7. For each PDO, the Tester checks consistency of:

a. Src_PDO_Supply_TypeN

b. If Fixed Supply PDO:

i. Src_PDO_VoltageN

ii. Src_PDO_Peak_CurrentN

iii. Src_PDO_Max_CurrentN

c. If Variable Supply PDO:

i. Src_PDO_MinVoltageN

ii. Src_PDO_MaxVoltageN

USB Power Delivery Compliance Test Specification, Revision 1.2 V2 Page 19

iii. Src_PDO_Max_CurrentN

d. If Battery Supply PDO:

i. Src_PDO_MinVoltageN

ii. Src_PDO_MaxVoltageN

iii. Src_PDO_Max_PowerN

e. If Programmable Power Supply PDO:

i. Src_PDO_MinVoltageN

ii. Src_PDO_MaxVoltageN

iii. Src_PDO_Max_CurrentN

8. The Tester checks PDOs following the first one, are in the correct order: Fixed PDOs in increasing

Voltage sequence, Battery PDOs in increasing Minimum Voltage sequence, Variable PDOs in

increasing Minimum Voltage sequence, and finally Programmable Power Supply APDOs in

increasing Maximum Voltage sequence.

9. The Tester checks that no Fixed PDO has the same voltage as any other

10. The Tester checks that no Variable PDO has the same voltage range as any other

11. The Tester checks that no Battery PDO has the same voltage range as any other

COMMON.CHECK.PD.8 Check Request Message

Description: The Tester performs additional protocol checks to all Request messages sent by the UUT.

Check Applicability: Request message

The Tester performs the following additional checks on all Request messages:

[COMMON.CHECK.PD.8#1]

1. Field check for all types of Request Data Object

a. B31…28 (Object Position) is not 000b, and the value is not greater than the number of

PDOs in the last Source Capabilities message

b. B25 (USB Communications Capable), matches VIF field USB_Comms_Capable

c. B24 (No USB Suspend), matches VIF field No_USB_Suspend_May_Be_Set

d. PD3 mode:

1. Bit 23 (Unchunked Extended Messages Supported) matches VIF field

Unchunked_Extended_Messages_Supported

2. Bit 22 (EPR Mode Capable), matches the VIF field

“EPR_Supported_As_Snk”

3. Bits 21 and 20 (Reserved) set to 000b if the test is running in PD3 mode

PD2 mode:

Bits 23…20 (Reserved) set to 0000b

2. Fixed and Variable Request Data Object

a. B19…10 (Operating Current) does not exceed the current offered by the referenced PDO

b. If B27 (GiveBack flag) = 0b

i. If B9…0 (Maximum Operating Current) is greater than the current offered by the

referenced PDO, then B26 (Capability Mismatch) is set to one

USB Power Delivery Compliance Test Specification, Revision 1.2 V2 Page 20

ii. B19…10 (Operating Current) does not exceed B9…0 (Maximum Operating

Current)

c. If B27 (GiveBack flag) = 1b

B9…0 (Minimum Operating Current) does not exceed B19…10 (Operating

Current)

3. Battery Request Data Object

a. B19…10 (Operating Power) does not exceed the power offered by the referenced PDO

b. If B27 (GiveBack flag) = 0b

i. If B9…0 (Maximum Operating Power) is greater than the power offered by the

referenced PDO, then B26 (Capability Mismatch) is set to one

i. B19…10 (Operating Power) does not exceed B9…0 (Maximum Operating Power)

c. If B27 (GiveBack flag) = 1b

B9…0 (Minimum Operating Power) does not exceed B19…10 (Operating Power)

4. Programmable Power Supply Request

a. B6…0 (Operating Current) is less than or equal to the Maximum Current offered by the

referenced PDO

b. B19…9 (Output Voltage field):

i. Greater than or equal to the Minimum Voltage field in the PPS APDO.

ii. Less than or equal to the Maximum Voltage field in the PPS APDO.

c. B8…7 (Reserved) set to zero

d. Bits 27 (Reserved) set to 0b

COMMON.CHECK.PD.9 Check Structured VDM Message

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

Check Applicability: All Structured VDM messages

The Tester performs the following checks on the Structured VDM Message Header (the first Data

Object): [COMMON.CHECK.PD.9#1]

1. Bits 31…16 (SVID) (does not apply if a message is a response to an invalid message from the

tester)

a. This field shall be set to 0xFF00 (PD SID) if Command (Bits 4…0) is a Discover Identity or

Discover SVIDs

b. This field shall not be set to 0xFF00 if Command (Bits 4…0) is 16-31 (SVID specific)

2. Bit 14…13 (Structured VDM Version) are set to 00b (when the test is running in PD2 mode)

3. Bit 14…13 (Structured VDM Version) are set to 01b (when the test is running in PD3 mode)

4. Bits 12…11 (reserved):

a. Set to 00b if Command = 0…15

5. Bits 10…8 (Object Position):

a. Set to 001b…111b if Command = Exit Mode

b. Set to 001b…110b if Command = (Enter Mode or Attention)

c. Set to 000b if Command = (Discover Identity, Discover SVIDs or Discover Modes)

6. Bit 5 (reserved) is set to 0b

7. Bits 4…0 (Command) shall be 1-6 or 16-31

剩余194页未读，继续阅读

dadalaohua

粉丝: 3729
资源: 157

USB PD3.0 CTS r1.2 V2：合规测试规范

USB_PD_R3_0 V2.0 20190829 + ECNs 2020-02-07.pdf

usb3.0 ECN

USB_PD_R3_0 V2.0 20190828.pdf

usb type-c specification release 1.4.pdf

pd.Timestamp.today().replace(day=pd.Timestamp.today().day-3) 报错了怎么办

Spire.Pdf 纯图pdf

print(pd.concat([pd.DataFrame(wine.data),pd.DataFrame(wine.target)],axis=1))

import pandas as pd pd=pd.read_csv('PCA_labels.csv') pd pd_vali=pd.read_csv('PCA_validation.csv') pd_vali有什么问题

PD CTS测试和DP CTS测试

最新资源