Debugging USB-PD Negotiation Failures
How CC-line PDO/RDO exchange, e-marker chips and TCPM state machines expose the exact point where USB-PD negotiation stalls or falls back to 5V.

Quick answer
USB Power Delivery succeeds only when the source, cable and sink agree on a supported voltage and current profile. Diagnose failures by identifying each component, reading advertised capabilities and checking the negotiation trace for fallback or rejection.
A laptop connected to a certified 100W GaN charger that trickle-charges at 15W is not a charger fault, it is a protocol fault. The hardware is fine, the cable is fine, but the USB-PD negotiation exchange that establishes the voltage and current contract between source and sink has quietly dropped to a fallback state. Most consumer troubleshooting guides tell you to “try a different cable,” which occasionally works, but understanding why it works requires looking at the actual state machine running on the CC line, not the marketing wattage printed on the brick.
#How the CC line carries the negotiation
USB Power Delivery runs entirely over the two Configuration Channel (CC) pins in a USB-C connector, using Biphase Mark Coding (BMC) at 300 kbps. Before any PD packet is sent, the connector performs analogue role and orientation detection: the source presents a pull-up resistor (Rp) on CC1 or CC2, the sink presents a pull-down (Rd), and the resistance value advertises a default current tier (900 mA, 1.5 A or 3 A) even before a single PD message is exchanged. This is the fallback layer that keeps “dumb” USB-C devices charging at a sane minimum if PD never establishes.
Once Vbus and CC are stable, the source’s Policy Engine, implemented in Linux as the tcpm (Type-C Port Manager) driver, transmits a Source_Capabilities message containing an ordered array of 32-bit Power Data Objects (PDOs). Each PDO fixed-supply entry encodes voltage in 50 mV units and maximum current in 10 mA units, plus flags for dual-role power, USB suspend support and unconstrained power. The sink parses this array, selects the best-fit PDO, and replies with a Request message carrying a Requested Data Object (RDO) that references the PDO index and the operating current it wants. If the source can service that request it sends Accept, waits for the internal power supply rail to settle, then sends PS_RDY. Only at that point does Vbus transition to the negotiated voltage.
Every failure symptom a user reports as “my charger doesn’t fast charge” maps to a specific point in this exchange collapsing, not to the charger’s rated wattage being wrong.
#Sequence of a Healthy USB-PD Negotiation
Rendering diagram...
#Three places the handshake breaks
In practice, three structural weak points account for the vast majority of negotiation failures observed in the field:

- Cable identity mismatch. Cables rated above 3 A / 60 W are required to carry an e-marker chip on the CC line, powered via Vconn, which responds to a Discover_Identity command addressed to SOP’ (Start of Packet Prime). If the e-marker CRC fails, or the cable has no e-marker at all, the source must not offer or allow current above 3 A, because the cable cannot be identified as 5 A capable. At 20 V, 3 A is 60 W.
- PD revision mismatch. A PD 3.0 source may send messages, such as Extended Source Capabilities, that a PD 2.0-only sink does not understand. Depending on the implementation, the sink may ignore the message or reject it (PD3.0 sinks answer unsupported messages with Not_Supported). The source’s
tSenderResponsetimer (24-30 ms) may then expire, and the recovery path depends on the state: a Soft Reset or a Hard Reset can follow. If negotiation restarts, the contract can fall back to a conservative default such as 5 V. Check the logs to see which reset actually occurs. - Signal integrity on cheap cable runs. BMC on the CC line tolerates modest capacitance, but long, thin, unshielded cables push rise/fall times past spec. CRC failures accumulate, each triggering a retry; once
nRetryCount(2 in PD3.0, 3 in PD2.0) is exceeded, the state machine escalates to a Hard Reset, Vbus drops and recovers withintSrcRecover(0.66-1.0 s), and negotiation restarts from zero.
These three failure classes are why the same laptop, same charger and a different cable produce wildly different charging behaviour: the cable is not a passive wire in a PD system, it is an active participant in the negotiation.
#Watching the negotiation from Linux and on the wire
On Linux, the tcpm driver logs state transitions to its own debugfs log (/sys/kernel/debug/usb/tcpm-<port>/log), not to the kernel ring buffer, which is a fast way to confirm whether a Hard Reset or Soft Reset is occurring. This is a read-only check. Illustrative example from a port acting as a sink, with exact names and format varying by driver and kernel (reading it needs root and debugfs, and each read drains the entries it shows):
1$ sudo sh -c 'cat /sys/kernel/debug/usb/tcpm-*/log'
2[ 812.441203] tcpm port0: CC1: 0 -> 1, CC2: 0 -> 0
3[ 812.443011] tcpm port0: state change SNK_ATTACHED -> SNK_STARTUP
4[ 812.481902] tcpm port0: PD_MSG: SRC_CAPABILITIES
5[ 812.502113] tcpm port0: state change SNK_NEGOTIATE_CAPABILITIES -> SNK_TRANSITION_SINK
6[ 813.104441] tcpm port0: state change SNK_READY -> HARD_RESET_SENDThe Type-C class in sysfs exposes the partner’s advertised capabilities without needing a bus analyser. Read them from the port-partner path (the directory names depend on your kernel and hardware; list the directory first):
1$ ls /sys/class/typec/port0-partner/usb_power_delivery/
2$ cat /sys/class/typec/port0-partner/usb_power_delivery/source-capabilities/1:fixed_supply/voltage
35000
4$ cat /sys/class/typec/port0-partner/usb_power_delivery/source-capabilities/1:fixed_supply/maximum_current
53000Values are typically reported in mV and mA; confirm the units on your system. Compare them against the live contract reported by your power-supply driver to see whether a full PD contract or only the fallback tier was reached.
When kernel logs are not enough, for instance to catch an e-marker Discover_Identity failure on SOP’, a hardware PD sniffer such as a Twinkie or a Power-Z KM003C captures the raw CC traffic independently of the OS driver stack, which is the only reliable way to distinguish a source-side bug from a cable-side bug. The full state diagram and message definitions are formalised in the USB Power Delivery specification published by the USB Implementers Forum, and cross-referencing observed PDO byte values against that document is the fastest way to confirm whether a device is advertising capabilities correctly.
Anyone designing a device that negotiates power dynamically alongside other subsystem contracts should apply the same discipline used in broader architectural patterns for state machine design: explicit timeouts, bounded retries, and a deterministic fallback state prevent the negotiation layer from oscillating indefinitely under marginal signal conditions.

#Rarer faults and how to spot them
Beyond the three structural weak points above, several edge cases only appear under sustained load or unusual topology:
| Symptom | Root Cause | Diagnostic Signal | Fix |
|---|---|---|---|
| Capped at 3 A (up to 60 W at 20 V) | No e-marker chip or CRC failure on cable | Discover_Identity on SOP’ times out | Replace with rated e-marked cable |
| Charging drops mid-session | Charger thermal foldback reduces advertised PDO | New Source_Capabilities mid-contract, renegotiation event | Improve charger airflow, lower ambient load |
| Repeated brief disconnects | Hard Reset loop from CRC accumulation | tcpm log shows repeated hard reset entries | Shorter/shielded cable, check connector wear |
| Device enumerates but stays at 5 V | PD revision mismatch disrupts negotiation | Reset after a tSenderResponse timeout, or Not_Supported in a capture | Firmware update; check whether the device offers a PD2.0 compatibility setting |
| Voltage overshoot on PPS rail | Malformed RDO or spoofed PDO from compromised firmware | Vbus exceeds requested value momentarily | Enforce OVP at sink, use PD authentication where supported |
The last row is the one most engineers underestimate. Because USB-PD negotiation is a trust-based exchange (the sink largely believes what the source advertises), a compromised charger firmware (the class of attack documented publicly as BadPower) can advertise a PDO with a voltage the connected device was never designed to tolerate. The protocol has no mandatory cryptographic verification of PDO content; USB Type-C Authentication, which can run over USB PD messaging, uses GET_DIGESTS, GET_CERTIFICATE and CHALLENGE exchanges, but it is optional and adoption in consumer silicon remains limited.
#What each design choice costs
Every design decision in a USB-PD-capable product weighs how reliably it negotiates against cost, latency and safety margin:
- Fitting an e-marker adds BOM cost per cable but is the only mechanism preventing a thin, unrated cable from being told to carry 5 A continuously.
- PPS granularity, with 20 mV voltage steps in Programmable Power Supply mode, improves thermal efficiency during fast charging but requires more Request/Accept round trips, increasing negotiation latency under marginal signal conditions.
- After a Hard Reset, the mandated
tSrcRecoverwindow (0.66-1.0 s) favours protocol correctness over user-perceived responsiveness; shortening it non-compliantly risks Vbus instability. - PD authentication helps close the PDO-spoofing gap but adds implementation cost and complexity, which is part of why it remains optional rather than mandatory in the specification.
- Advertising multiple PDOs gives sinks more negotiation flexibility but extends the Source_Capabilities payload, marginally increasing enumeration time on every single plug event.
None of these trade-offs are theoretical. They are the direct explanation for why two devices carrying the same wattage rating on their packaging can behave completely differently once plugged into the same charger, and why a diagnostic approach rooted in the actual PD state machine, rather than cable swapping by trial and error, is the only reliable way to isolate whether the fault sits in the source, the cable, or the sink’s own policy engine implementation.
#Related reading
Evidence trail
Sources and verification
Primary documentation and external technical references used in this article.
About this page
Credited to
Dates
Published
Last updated
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Engineering insights, direct to you.
Receive the latest Systems Engineering tutorials, production guides, Engineering Labs and operational best practices.
Comments
Add a thoughtful note on Debugging USB-PD Negotiation Failures. Comments are checked for spam and held for moderation before appearing.