Quick answer: Type-C is a physical and role definition, not a performance guarantee. If you are building a USB 2.0 sink, get the CC termination right, keep advertised power separate from Power Delivery, and document what your simple receptacle implementation deliberately does not do.
What the connector actually specifies
The USB-IF Type-C Cable and Connector Specification keeps several things apart: USB 2.0 operation, Type-C power advertisement, and USB Power Delivery. Because those are separate areas, connector presence alone does not establish a particular data speed or available current. Your first design step is therefore to write down the role and capability you intend, rather than assuming the connector confers them. Consult the specification release that matches your target so that section numbers and tables line up with what you actually implement.
Sink CC termination
For a sink, Table 4-28 specifies nominal 5.1 kilohm CC termination resistors, and it distinguishes tolerance and power-capability detection cases. That distinction matters: the resistor network is how a source detects an attached sink and how power is advertised. A Type-C receptacle has two CC pins, so both paths are part of the picture. Treating them as a single resistor is a common shortcut in hobby layouts, and it is worth checking for your own design rather than assuming it is sufficient.
Advertised power versus Power Delivery
Type-C power advertisement over CC and USB Power Delivery (a negotiated protocol) are different mechanisms in the specification. A receptacle wired only for basic advertisement does not imply PD negotiation, higher voltages, or 3 A capability. Avoid relying on an unqualified universal two-resistor recipe: inspect both CC paths, the maximum current your board may draw, and the protection around it for your specific implementation. This reference is a design-scope tool, not a high-power PD design.
Comparison: what the connector does and does not establish
| Property | Set by the connector alone? | What actually determines it |
|---|---|---|
| Data speed | No | The USB 2.0 (or higher) implementation behind it |
| Available current | No | CC advertisement and any Power Delivery negotiation |
| Power Delivery | No | A negotiated contract, only if implemented |
| Sink attachment detection | Partly | CC termination, nominal 5.1 kilohm for a sink |
| Charging behaviour | No | A separate power-path and charging design |
Ordered design-scope process
- State the role first: sink, source, or dual-role. Write it down before layout.
- Decide the data capability you actually implement (here, USB 2.0) and say so explicitly.
- Work out CC termination for both CC pins against the specification sink table.
- Separate the power story: advertisement only, or Power Delivery? Do not blur them.
- Confirm the maximum current your board may draw and how that path is protected.
- Document what the design does not provide: higher speed, PD, or extra current.
- Review against the specification rather than an online recipe.
Reader questions
Does a Type-C plug mean my board gets 3 A?
No. The connector alone does not establish available current; that follows from CC advertisement and any Power Delivery negotiation, which the specification treats as separate areas.
Why do both CC pins matter?
The specification sink table describes CC termination for attachment detection and power-capability signalling, and a Type-C receptacle has two CC pins. Inspecting both paths is safer than reducing them to one resistor.
Can I use a simple two-resistor circuit I found online?
Not as an unqualified recipe. Resistor tolerance, both CC paths, allowable draw, and protection should be reviewed against the specification for your own implementation.
Is a Type-C receptacle automatically USB 3.x?
No. USB 2.0 operation is described separately from the connector, so speed depends on what you implement, not on the shape of the plug.
Documentation
Documentation-based reference only: the single source is the USB-IF Type-C Cable and Connector Specification, Release 2.5. No build, bench measurement, or compliance testing was performed, so your own PCB, ESD protection, power-path behaviour, and resistor tolerances still need to be checked. For a USB 2.0 use case, the USB audio endpoint reference shows the data side in practice, and the PCB making guide is a companion for connector footprints.
