← Journal Hardware · · 6 min

USB-C power input design for small devices

Design a USB-C power input that works with every charger and cable: CC resistors, protection, inrush, charger choice and when PD is worth it.

Milo Perović
Founder & lead engineer

  • Battery
  • EMC
  • Power
  • USB-C
USB-C power input design for small devices

Almost every small connected device we see now charges over USB-C, and the USB-C power input is where a surprising number of first prototypes fail. The connector looks like a simple 5 V jack, but it is a negotiated interface: get two resistors wrong and some chargers will deliver nothing at all, while others work perfectly on your desk.

This post is for founders and engineers who want a charging port that works with every charger and cable a customer might own.

What a USB-C power input actually has to do

A USB-C source does not put voltage on VBUS until it sees a sink attached. It detects that sink through the two configuration channel pins, CC1 and CC2. Only one of them connects through the cable, depending on which way the plug is inserted, so the device has to present the right termination on both.

For a device that only consumes power, the job breaks down into a short list:

  • Present a 5.1 kΩ pull-down (Rd) on each CC pin, separately.
  • Survive hot-plug transients, ESD and the occasional out-of-spec charger.
  • Limit inrush so the source does not trip or brown out.
  • Draw no more current than the source advertises.
  • Keep the battery and system rail from back-feeding VBUS when unplugged.

None of this needs a USB controller. Without Power Delivery, a USB-C sink is limited to 5 V, at up to 3 A if the source advertises it, which is plenty for most battery-powered sensors and wearables.

The two-resistor mistake that breaks chargers

The most common fault we find is CC1 and CC2 tied together to a single resistor. It looks equivalent on paper and it often works with a USB-A to USB-C cable, which is exactly why it survives into prototypes. With a proper C-to-C cable it can fail in two ways.

With a single 5.1 kΩ resistor shared by both pins, an electronically marked cable connects its own low-value termination to the joined net, in parallel with yours. The source then sees the wrong resistance and may classify the device as an accessory rather than a sink. Two resistors in parallel (2.55 kΩ to ground on a joined net) is outside the Rd range entirely. In both cases the result is the same: some chargers refuse to switch on VBUS.

The fix costs one extra 0402 resistor per board. Each CC pin gets its own 5.1 kΩ to ground, with a 1% tolerance part. If you use a 6-pin power-only receptacle, the same rule applies, as both CC pins are still there.

Legacy cables are not a test

A USB-A to USB-C cable contains its own pull-up on CC, so the charger never sees your termination at all. A board can pass every test with that cable and fail with the customer’s laptop charger. Always validate with a genuine C-to-C cable, including at least one e-marked cable, and a couple of different wall chargers.

Reading how much current the source allows

The source advertises its capability through the pull-up it puts on CC: default USB power, 1.5 A or 3 A, all at 5 V. With your 5.1 kΩ in place, those three levels show up as distinct voltage bands on the active CC pin, roughly a few hundred millivolts for default, around 1 V for 1.5 A and around 1.6–1.7 V for 3 A.

If your charger current is fixed at 500 mA or less, you can ignore this. If you want faster charging, read both CC pins with an ADC or a pair of comparators, take the higher one, and set the charger current to match. Default USB power is only 500 mA on a USB 2.0 port, so a device that pulls 1 A from an old laptop port without checking is relying on the port’s tolerance rather than the specification.

Protecting the USB-C power input from the outside world

The connector is the most exposed part of the product. We treat protection as part of the USB-C power input design, not an afterthought for the EMC lab.

  • ESD: low-capacitance TVS diodes on CC1, CC2 and any data lines, placed right at the connector, with a short ground return. For our approach to finding problems before formal testing, see EMC pre-compliance testing before you book a lab.
  • Hot-plug ringing: cable inductance and low-ESR ceramic input capacitors form a resonant circuit. On plug-in, VBUS can briefly overshoot well above 5 V. A VBUS TVS rated for the expected voltage, and sometimes a small electrolytic or polymer capacitor for damping, keeps downstream parts inside their absolute maximum ratings.
  • Overvoltage: a faulty or cheap charger can present more than 5 V. Many charger ICs tolerate a higher input than they operate at, but check the absolute maximum, not just the recommended range. If in doubt, add an overvoltage protection switch.
  • Reverse current: when unplugged, the battery side must not drive VBUS. Most charger ICs block this internally; discrete power paths often do not.

Inrush and bulk capacitance

USB limits how much capacitance a device may present directly on VBUS at attach, traditionally 10 µF for USB 2.0 devices. Large capacitance behind the connector causes a current spike that can make a weak source drop out or reset. If you need more bulk capacitance for a radio or motor, put it behind a load switch or charger with soft-start rather than straight on VBUS.

Charger and power path choices

Behind the connector, the decision is mostly about whether the device must run while charging with a flat battery. A simple linear charger such as the MCP73831 charges a single Li-ion cell at up to 500 mA and is fine for small wearables, but the system load shares the charge current, which can confuse charge termination.

A power-path charger, for example the TI BQ24072 family, powers the system from VBUS when present and charges the battery with what is left. That matters if the device must boot from USB with a flat or missing battery.

NeedTypical choiceTrade-off
Small cell, slow chargeLinear charger, ≤500 mAHeat rises with current and input-to-battery voltage drop
Run from USB with flat batteryLinear power-path chargerMore pins, still dissipates heat at high current
Fast charge, larger cellsSwitching chargerEfficiency gained, layout and EMI become critical
9 V or more neededPD sink controller plus chargerCost, firmware or NVM configuration, more testing

Heat is easy to underestimate. A linear charger dropping 5 V to a 3.7 V cell at 1 A dissipates around 1.3 W, which is a lot inside a small sealed enclosure. For more on budgeting the other end of the power chain, see where the microamps really go in low-power design.

When USB Power Delivery is worth it

Power Delivery lets the sink negotiate higher voltages such as 9, 15 or 20 V over the CC line. It is worth the complexity when you need more than about 15 W, charge multi-cell packs, or want short charge times on a larger battery.

Standalone sink controllers such as the ST STUSB4500 negotiate a configured profile without any firmware on your main microcontroller, which keeps the design simple. Two things to plan for: the device must still accept plain 5 V from non-PD chargers, and the Rd termination must be present with no power at all, so a device with a completely flat battery can still start charging. Check that the controller you choose supports this dead-battery behaviour.

A checklist before you commit

  1. Separate 5.1 kΩ, 1% resistors on CC1 and CC2, never joined.
  2. TVS protection on VBUS and CC at the connector, with a short ground path.
  3. Bulk capacitance directly on VBUS kept within the USB limit; extra capacitance behind soft-start.
  4. Charger input absolute maximum checked against overshoot and faulty chargers.
  5. Current draw matched to the advertised CC level, or fixed at 500 mA.
  6. Behaviour with a flat or missing battery decided and tested.
  7. Validated with C-to-C cables, an e-marked cable, a laptop port and several wall chargers, including both plug orientations.

None of these items costs much on the bill of materials. Fixing them after a production run means a board respin.

Working on something similar?Free scoping call →