USB 3.1 Electrical Design

USB 3.1 Electrical Design
USB Compliance and
Certification
Rahman Ismail
Compliance Chair and CTO: USB-IF
With thanks to: Diane Lenox, Amanda Hosler, Jamie Grimm and Stephanie Wallick
Developer Days 2016
Hong Kong
October 18 – 19, 2016
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
1
Session Agenda
• Compliance: What/When/Where?
• USB Charging
• USB PD: More Power
• USB Type-C™ Authentication
• USB-C™: What to expect!
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
2
Compliance Program
• General Development Process
• Note that this is not a completely linear process, there is a lot of feedback and iteration
involved.
Technology
Specification
• Specification
developed to at
least a r0.9 level
Assertion
Extraction
• List all testable
assertions
• Starting point for
CTS Development
Test Description
development
• Create test outlines
to exercise devices
for specification
compliance
• TDs reviewed by
workgroup
Workgroup
development of
CTS
• Compilation of all
TDs and testing
procedure
• Includes any
additional testing
and vendor supplied
information
Interoperability
Testing
• Tests early
implementations of
the technology
• Irons out errors in
the specification
and CTS
• Exposes further
areas for testing
Certification
Testing
• Formalized testing
for USB Certification
• Utilizes finished CTS
Predictable Path To Compliance
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
3
New Connector: New Compliance Requirements
Electrical
Link
Functional
Framework
Cable & Connector
Interop
Hub
Cable ID
Alternate Mode
PHY
Protocol
Power Supply
Policy
USB-C
USB Developer Days – October 18 – 19, 2016
USB PD
USB 3.1
USB Implementers Forum © 2016
4
The Four Ways to Certify
• USB-IF Authorized Test Labs listed on the usb.org website
• Authorized per USB product category
• USB-IF Sponsored Workshops
• Available to USB-IF member companies only
• USB-IF Platform Interoperability Lab (PIL)
• Available to USB-IF member companies only
• The USB-IF Qualification by Similarity Program (QbS)
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
5
Compliance: What/When/Where?
• USB 3.1 Gen 1 and USB 2.0
•
•
•
•
Host Si: ITLs and QbS Program
Hub Si: PIL for USB 3.1 Gen 1, ITLs for USB 2.0, QbS Program for both
Cables and connectors: ITLs and QbS Program
All other products: ITLs, Workshops, QbS Program
• USB 3.1 Gen 2
• PIL
• QbS Program for Gen2 Host and Peripheral Silicon
• Target Q1 2017 for USB 3.1 Gen 2 Hub Si
• USB PD
•
•
•
•
USB PD Si: Workshops, PIL and QbS Program, @ITLs (Q4 2016)
USB E-markers: Workshops, PIL and QbS Program, @ITLs (Q4 2016)
Power Bricks: Workshops and PIL, @ITLs (Q4 2016)
Other end products: PIL
• USB-C:
• Cables and Connectors: ITLs
• Power Bricks: Workshops and PIL, @ITLs (Q4 2016)
• All other products: PIL
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
6
USB Charging
USB Developer Days – October 18 – 19, 2016
• New logo!
• Compliance Requirements
USB Implementers Forum © 2016
7
New USB Charger Logo
• Applicable to all products compliant with
the PD and USB Type-C specifications
• Minimum 15W power output
• Only certified products can use the
Charger Logo
• Hubs that are a source need to pass Hub
certification in order to use the charger logo
• Wattage in the logo refers to the highest
power output on any USB Type-C port on
the product
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
8
New USB Charger Logo Labeling Guidelines
• General categories of multi-port chargers
• Assured Capacity Chargers
• Provide stated wattage at all times
• Example: All ports capable of up to 40W at all
times
• Example: Ports provide labeled wattages at all
times
40 W
40 W
40 W
15 W
40 W
10 W
• Shared Capacity Chargers.
• Provide up to the bracketed wattage at all times
• Example:
• Each port capable of up to 40W
• however charger is only capable of up to 60W
total.
• 40W value is used in logo
USB Developer Days – October 18 – 19, 2016 September 27 – 28,
40 W
40 W
60 W
40 W
USB Implementers Forum © 2016
9
USB Charging Compliance Requirements
• Can only be use with chargers with one or more:
• USB Type-C receptacles or with a captive USB Type-C cable
• The logo is new but the compliance program is not
• The USB-IF has certified chargers prior to the USB Charger Logo release
• Same charger tests apply
•
•
•
•
USB Type-C Functional Tests
USB PD Electrical and Protocol Tests
BC 1.2 if supported
Interop
• Test with Macbook, Chromebook Pixel, Lumia 950, Nexus 5X
• Source Power Tests
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
10
USB PD:
More Power
USB Developer Days – October 18 – 19, 2016
• C&I
• 2.0/3.0
• Tools
• End User Communication
USB Implementers Forum © 2016
11
USB PD Compliance and Interoperability
• Physical Layer (Ch. 4/5)
• Test signal quality and TX/RX operation over CC line
• Test electrical characteristics and interference
• Protocol (Ch. 6)
• Test signaling, messages sequences and state operation
• Capabilities Tests, Swap Tests [DR_Swap, PR_Swap, VCONN_Swap]
• Discovery Tests [ID, SVIDs, Modes]
• Power Supply (Ch. 7)
•
•
•
•
Test power transitions and timing characteristics [Load Tests, Transition Tests]
Ensure that the power supply can deliver as per its advertised capabilities
Drop/Droop fixtures that are capable of testing up to 100W
Perform Role swap if the PD device supports
• Device/System Policy (Ch. 8/9)
• Manual IOP testing and USB CV testing
• Test Local Policy Engine, power management and configurations
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
12
The What and Where of XIDs
• What is an XID?
• Outward facing identifier used to determine certification status of a PD product
• Certification verification interface provided by the USBIF
• Using the XID as input
• Where is it used?
• One or more XIDs are provided by the USB-IF at the request of the product vendor
• The product vendor is responsible for managing their XIDs
• A vendor assigns an XID to each PD product
• XID is contained in the Cert Stat VDO field
• Cert Stat VDO field is sent in the response to a Structured VDM
• Command field set to “Discover Identity”
• Discover Identity is used to determine whether a given Cable contains an E-Marker
• E-Marked Cables are required to support Discover Identity and have an XID
• Optionally, PD capable products other than cables can support Discover Identity to identify
Port Partners
• For example, products that support Alternate Modes
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
13
Common XID mistakes
• End product vendors implementing certified PD silicon
•
•
•
•
Cannot use XID of the silicon developer
Certification is denied to companies using an XID that is not their own
Must change product XID from silicon vendor XID to your own XID
Cannot use one XID on multiple products
• Only products from the same company with cosmetic differences can use the same XID
• XID must be unique in all other cases
• Silicon vendors
• Must implement an XID for certification
• Empty Cert_Stat_VDO field is not acceptable
USB Developer Days – October 18 – 19, 2016 September 27 – 28,
USB Implementers Forum © 2016
14
USB PD Compliance Tools
• PD Revision 2.0 PD Test Vendors
• Approved
• MQP – Communications Engine MOI
• Ellisys – Deterministic MOI
• Correlation of PD Test solutions
• 2 MOIs are required to certify USB PD rev 2.0 capable products
• Communications Engine MOI
• Deterministic MOI
• Correlation done on test solutions complying to the same MOI
• High priority to enable ITLs
• USB-IF QuadraMax
• Source Power and Policy Manager Tests (drop/droop, load capabilities across one or
more Source ports, Hot Reset and Overcurrent)
• Cable E-Marker check, IR loss and Simultaneous low speed signaling
• Target availability Q1 2017
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
15
PD Certification: A Test Lab Guide to Authorization
• Visit the Power Delivery section at compliance.usb.org for all Power
Delivery compliance updates
• Mandatory Attendance at USB-IF Sponsored Workshops as volunteers
• Access to key members of the PD compliance working group
• Familiarize and learn about the test solutions used at workshops
• PD Rev 2.0 compliance plan finalized
• Ensure familiarity with equipment needed for PD Only Silicon certification
• For approved ITLs, PD Silicon can be tested at ITLs late Q4 2016
• ITL must have approved Engine MOI tester (currently MQP)
• ITL must have approved Deterministic MOI tester (currently Ellisys)
• If product passes tests, ITL sends product to PIL for QuadraMAX testing.
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
16
Where we’re getting it wrong
• Proprietary charging not allowed on the USB Type-C™ Connector
• As required by Section 4.8.2 of the USB Type-C™ specification:
• The method shall only define the current level and shall not change the voltage delivered
on Vbus.
• The method shall not alter the DFP’s role to source Vbus or the UFP’s role to sink Vbus
• DRP bit is a static capability
• Shall be set to the same value in both the source and sink cap messages
• When the DRP bit is set
• The device supports both source and sink roles
• The PR_SWAP message shall be responded to with an Accept, Reject or Wait
• PS_RDY Message
• After a VCONN_Swap a PS_RDY Message shall be sent
• No parts of the PS_RDY Message shall be sent before VCONN is on
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
17
PD Compliance Plan Timeline
• PD 2.0 Current Revision 1.09
• Upcoming Events
• USB-IF Workshop 101
• November 2016 – Taipei Taiwan
• PD 3.0 Compliance Plan at revision 0.5
• Currently being developed within PD Compliance WG
• PD Rev 3.0 information testing available at workshop 101
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
18
USB Type-C™
Authentication
USB Developer Days – October 18 – 19, 2016
• Certification
• Object ID
• Additional Certificate Data
USB Implementers Forum © 2016
19
Type-C Authentication: Compliance
• Certification available in 2017 for PD Authentication Responders
• Testing will include:
• Certificate chain validation
• Authentication Request/Response protocol
• Authentication message exchange timing
• USB-IF certificate authority (CA) will issue certificates
• Products must contain at least 1 certificate chain with USB-IF root certificate
• Steps to obtain a certificate:
1.
2.
3.
Vendor submits application
Application and Vendor ID are verified
Signed certificate is issued to vendor
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
20
Type-C Authentication: USB-IF OID
• Used to identify USB-IF
extensions in x509v3 certificates
• USB-IF OID = 2.23.145
• 2.23.145.1 = Authentication
Objects
• 2.23.145.1.1 = extended key usage
• 2.23.145.1.2 = ACD extension
• Rest of USB-IF OIDs are reserved
for future use
ISO/ITU-T Joint OID
(2)
ISO/ITU-T Joint OID
(23)
USB-IF
(145)
Type-C Authentication
(1)
Extended Key Usage
(1)
USB Developer Days – October 18 – 19, 2016
Reserved
(2  n)
ACD Extension
(2)
Reserved
(3  n)
USB Implementers Forum © 2016
21
Type-C Authentication: ACD
• ACD: Additional Certificate
Data
• Custom certificate
extension for Type-C
Authentication Products
• Must be present in all
certificates
• Defined separately for USB
and PD products
USB Developer Days – October 18 – 19, 2016
Value
PD
Source/Sink
TLV type
USB Type-C
Cable
USB
00h
VERSION
Required
Required
Required
01h
XID
Required
Required
Optional
02h
POWER_SOURCE_CAPABILITIES
Required
N/A
Conditional
03h
POWER_SOURCE_CERTIFICATIONS
Reserved
N/A
Conditional
04h
CABLE_CAPABILITIES
N/A
Required
N/A
05h
SECURITY_DESCRIPTION
Required
Required
Required
06h - FCh
Reserved
--
--
--
FDh
PLAYPEN
Optional
Optional
Optional
FEh
VENDOR_EXTENSION
Optional
Optional
Optional
FFh
EXTENSION
Optional
Optional
Optional
USB Implementers Forum © 2016
22
USB-C:
What to
expect!
USB Developer Days – October 18 – 19, 2016
• C&I
• Connector Certification
• What to Look For
• Product Certification
USB Implementers Forum © 2016
23
USB-C Compliance and Interoperability
• USB Logo Usage
• Only products that meet or exceed the compliance test requirements are eligible to display
the certified logo
• Two areas of testing
• Cable and Connectors & Products
• Cable and Connector
•
•
•
•
Mechanical
Electrical
Cable E-Marker
QuadraMAX End Product Cable (CC characteristics, IR Drop, Simultaneous traffic)
• Products
• Functional
• Electrical
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
24
Cable and Connector
• Must run the E-Marker Test
• Procedure can be found at
http://www.usb.org/developers/compliance/cable/E-Marker_Testing.pdf
• SI Test Fixture
• Board files available
• Fabrication by Luxshare ICT
• Cable Assembly Shielding effectiveness
• Available for USB-C and A
Normative shielding effectiveness test over
frequency ranges of interests
• ECN Newly Added: USB 2.0 Only USB-C Receptacle
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
25
USB Type-C Cables: What to Look For
• USB Standard-A to USB Type-C™ cables must use a 56Kohm pullup
• Legacy hosts may not support 1.5A or 3A current loads
• Ensures that USB-C peripherals do not draw more than default current
• Implementing Rd in USB-C to USB-C cables
• Non compliant!
• Implementing Rd in a cable is prohibited
• May damage existing products in the USB ecosystem
• To verify a cable does not have Rd implemented simple DC checks can be performed
•
•
•
•
Using a known source, connect the cable to the source
Measure the CC1, CC2, and VBus pins using a breakout fixture and a Digital Multimeter
One CC pin will be 0V while the other will be above 2.75V – IR drop of cable
Vbus must be 0V. Check all orientations
• USB-IF compliance tool QuadraMAX will test/catch cables having an Rd
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
26
Products
• Functional Test Assertions completed
• Most functional tests implemented and available
• Electrical test requirements/fixtures
• Available now!
• Certification testing of products can be performed at PIL
• Certification requirements:
• USB 3.1 Gen 1 or Gen 2
• USB PD if supported
• USB-C
• Logo Usage Guidelines are available at:
• http://www.usb.org/developers/logo_license/
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
27
USB Type-C Certification – Current Status
• Testing at PIL
• Types of USB Type-C products:
• Hosts and non-hub peripherals
• Up to and including USB Gen 2 speeds
• USB Type-C Only Power Bricks
•
•
•
•
•
•
The Luxshare breakout fixture used to measure USB-C current
No USB Type-C specific CV tests
Interop includes Windows 10, OSX, Android/Chrome
USB-C functional tests implemented by Ellisys and Teledyne LeCroy
QuadraMAX for Source Power tests
Looking for KGDs
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
28
USB-C Certification: Test Lab Guide to Authorization
• Compliance.usb.org for all USB Type-C™ compliance updates
• Attend USB-IF Sponsored Workshops as volunteers
• Developers of USB-C compliance program are available for questions
• All USB-C compliance equipment present.
• Become familiarized
• Ask questions to techadmin@usb.org about compliance specifications
• Specs found http://www.usb.org/developers/compliance/usbcpd_testing/
• Ask before authorization is available to avoid delays
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
29
Summary
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
30
USB Type-C Compliance Top 10
#10 Upstream facing port needs to be clearly marked
#9 All four high speed wires may be used at the same time
Impacts the design/layout of the paddle board in the connector
#8 Only use legacy Rp in USB Type-C to USB Standard-A cables
#7 Role swaps
Test with as many other vendors as possible! Discharge handling and timing
A Sourcing Device / Sinking Host (defined USB Type-C Spec) must initiate and accept DR_Swap to the UFP / DFP (respectively), PR_Swap
to the Source / Sink (respectively), and its Source / Sink Capabilities DRP and DRD bit must be set to 1
#6 Pass Through Power Budgeting
You need to account for power losses and power consumption of pass-through devices
Don’t forget that if you have a USB Standard-A port, it still draws power with nothing connected
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
31
USB Type-C Compliance Top 10
#5 When coming to a workshop with a device with a battery, bring batteries that are fully discharged!
#4 If your product supports multiple Source Capabilities, it must have more than 1 PDO listed for testing. An
end product can only get cert if the silicon was certified with the same features enabled.
#3 Proprietary charging methods
over USB are not allowed to change VBus!
Proprietary chagrining methods over USB must follow section 4.8.2 of the USB Type-C™ specification.
#2 Use
the VIF to accurately represent your product
Please send feedback regarding VIF generator / editors and other VIF issues
We want to fix tests instead of dodge configurations that are tested incorrectly.
In addition, VIF is saved by USB-IF as representation of product capabilities.
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
32
USB Type-C Compliance Top 10
If plugging in your device produces smoke
STOP TESTING!!!
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
33
Q&A
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
34
Backup Materials
USB Developer Days – October 18 – 19, 2016
USB Implementers Forum © 2016
35
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising