A barrel-jack laptop starts receiving power the moment the plug goes in. A USB-C laptop does not: before any significant power flows, the laptop and the charger have to recognise each other, agree on a voltage and current, and switch on the power path. That negotiation is handled by a USB Power Delivery controller. When a USB-C laptop will not charge, the fault can be in the charger, the cable, the port, the PD controller, its firmware, the power-path switches or the charger IC. This guide shows how to narrow it down.
The USB-C charging chain
| Step | What happens | Board parts involved |
|---|---|---|
| 1. Attach | The charger detects a sink through the CC pins | Port, CC lines |
| 2. Default power | The charger applies 5 V on VBUS | VBUS pins |
| 3. Negotiation | The PD controller and charger agree a contract | PD controller, its firmware, CC lines |
| 4. Higher voltage | The charger raises VBUS to the agreed level | Charger |
| 5. Sink path on | MOSFETs connect VBUS to the laptop's input | Sink MOSFETs, gate drive |
| 6. Charging | The charger IC powers the system and charges the battery | Charger IC |
Background on the controller and the pins is in the glossary under pd controller and cc pins. How the power path is drawn on a board is covered in The USB-C Power Path on Laptops: From Port to Charger IC.
Step 1: rule out the charger and cable
USB-C chargers and cables vary widely. Before suspecting the laptop:
- Try a charger known to work with this model, at the laptop's required wattage.
- Try a cable rated for that power (higher-power chargers need cables that can carry their current).
- Try every USB-C port on the laptop; some ports do not accept charging at all.
Testing a charger with a plain multimeter is not enough for USB-C, because it outputs nothing until a device is attached. The reasons are explained in How to Test a Laptop Charger with a Multimeter.
Step 2: read a USB-C power meter
A USB-C power meter between the charger and the laptop is the most informative tool here. It shows VBUS voltage, current and, on many models, the negotiated contract. Its use is covered in Using a USB-C Power Meter for Laptop Diagnosis.
| Meter reading | Meaning | Where to look |
|---|---|---|
| 0 V | Charger sees no sink | CC lines, port, cable |
| 5 V, almost no current, no negotiation | Laptop not negotiating | PD controller power, firmware, CC communication |
| 5 V, then higher voltage, almost no current | Contract made, power not drawn | Sink MOSFETs, charger IC, input protection |
| Voltage cycles up and down repeatedly | Negotiation succeeds then resets | Short on input, PD controller resets, overcurrent protection |
| Correct voltage and normal current | Power reaches the laptop | Battery or charger IC, not the port |
This table alone usually tells you which half of the circuit to open up.
Step 3: CC lines and the port
With all power removed:
- Measure each CC pin at the port to ground in diode mode and compare CC1 with CC2.
- Measure VBUS at the port to ground.
- Inspect the port under magnification for bent or burnt contacts and debris.
CC lines connect to the PD controller and often pass through ESD protection. A CC line reading near zero is shorted — commonly a damaged protection part, sometimes the PD controller itself. VBUS shorted to ground prevents any negotiation, because the charger shuts down immediately. Burnt contacts on the port, especially between VBUS and neighbouring pins, are common after a damaged cable or liquid.
Step 4: power for the PD controller
The PD controller must be alive before it can negotiate. On many boards it is powered from:
- an always-on rail when the battery is present, and
- a small regulator fed from VBUS when the battery is flat or removed — so the laptop can still charge from empty.
Measure the controller's supply pins with the charger attached and the battery removed. If the controller has no supply in that state, it cannot negotiate a dead laptop back to life. Check the regulator that derives its supply from VBUS.
Step 5: PD controller firmware
Many PD controllers load their configuration from a small SPI flash chip or from internal memory. Corrupted firmware stops negotiation or produces a wrong contract. Symptoms include charging only at 5 V, charging only from certain chargers, or no response at all.
On some boards the PD firmware is updated together with the BIOS; on others it can be reprogrammed with a programmer from a known-good dump for the same board. Check the schematic for a separate flash chip near the controller. The controller also talks to the EC over I²C; if that link is broken, some designs refuse to enable charging.
Step 6: the sink path
Once a contract is made, MOSFETs between VBUS and the laptop's input rail must switch on. Their gates are driven by the PD controller or a dedicated driver.
- With the charger attached and a contract made, measure the voltage before and after the sink MOSFETs.
- Present before, missing after → check the gate drive voltage and the MOSFETs themselves.
- Present after, but the laptop still does not charge → the problem is further on: input protection, the charger IC, or the battery.
Unpowered, a shorted sink MOSFET reads near zero between drain and source, and a shorted input rail shows up as a near-zero resistance after the MOSFETs. Either can make the PD controller drop the contract repeatedly.
Step 7: the charger IC
If the input rail is powered and the laptop still does not charge, the USB-C side has done its job. From here the diagnosis is the same as for a barrel-jack laptop: the charger IC's input, its enable and ACOK-type signals, its output, and the battery. That is covered in the general charging guide.
Example: charges only at 5 V
A laptop shows "slow charger" with every USB-C charger, and a USB-C meter reads 5 V at a small current — no higher contract is ever negotiated. The CC lines read normally and the port is clean. The PD controller's supply is present. The schematic shows a small SPI flash next to the controller. Its contents are blank where a configuration should be. After programming it with the configuration from an identical working board, the meter shows a full-voltage contract within a second of plugging in, and the laptop charges normally.
FAQ
Why does my USB-C laptop charge only from some chargers?
Chargers offer different power profiles. If the laptop needs a profile a charger does not offer, or the PD firmware rejects it, charging may be slow or absent with that charger.
Can a USB-C laptop charge from a phone charger?
Sometimes, slowly, if the laptop accepts low-power contracts. Many laptops refuse to charge below a minimum wattage.
What does it mean if the meter shows the voltage going up and down?
The laptop negotiates, then something makes the contract reset — often a short or overcurrent on the input, or the PD controller restarting.
Can PD controller firmware get corrupted?
Yes, through a failed update or electrical damage. Symptoms include no negotiation or only 5 V charging.
Is a burnt USB-C port repairable?
Usually, by replacing the port. Check the CC and VBUS lines and the protection parts behind it afterwards, as port damage often spreads to them.
Bottom line
Start with a known-good charger, cable and a USB-C power meter. The meter tells you whether the fault is before negotiation (CC lines, port, PD controller power or firmware) or after it (sink MOSFETs, input rail, charger IC). Check CC and VBUS for shorts, make sure the PD controller is powered even with a flat battery, and consider its firmware when it never asks for more than 5 V. A clean vbus path is the last link before ordinary charging diagnosis takes over.