Why does a USB-C product work with some chargers and cables but not others?

A prototype powers up from the charger on the development bench, then refuses to start when someone tries a different cable. Another unit charges normally until its display and radio switch on together.

These symptoms can have different causes, from incomplete connection detection to a power supply that cannot meet the product’s demands. Good USB-C PCB design considers the charger, cable and device as a complete system.

For a handheld instrument, sensor or portable controller, that means defining how the product should behave across the connections its users are likely to make.

Why a USB-C connector does not guarantee power compatibility

USB-C provides a common connector, but products using it can have different power and data capabilities. USB Power Delivery, often shortened to USB PD, adds communication that allows compatible equipment to agree suitable power settings. A USB-C socket does not, by itself, provide that functionality.

A straightforward device may operate at 5V without using USB PD. USB-C can support up to 3A at that voltage, giving 15W, but the product must respect the current available from the connected source. It cannot assume that every port supplies the maximum.

The difference between older USB-A chargers and USB-C chargers can also expose a design mistake. A traditional USB-A source can already have power present on its connector. A compliant USB-C charger with a USB-C socket waits to detect a valid connection before enabling power.

This means an incomplete design may appear functional with a USB-A-to-USB-C cable while failing with a USB-C-to-USB-C cable. That behaviour is a reason to investigate the connection-detection circuit, even if the product only needs 5V.

Start by defining the intended use. Will the product charge a battery, run continuously from USB power, or do both? Must it work from a computer port as well as a mains adapter? Those answers should guide the power architecture before the connector is added to the schematic.

Connection detection, power negotiation and protection

USB-C uses configuration-channel connections, labelled CC1 and CC2 on the socket, to detect attachment and establish the power roles. They also allow the connection to work with either plug orientation.

For a device that receives power, both CC pins need the correct, separate pull-down connections. These may be provided by individual resistors or integrated within a suitable controller. Simply connecting the power and ground pins leaves an essential part of the interface unfinished.

Where the design needs a higher input voltage, USB-C power delivery design must include negotiation of an appropriate supply. The controller’s settings and the downstream circuitry need to agree: a requested voltage must be one the electronics can safely accept.

The power budget should cover the demanding operating conditions, including startup and battery charging while the product is running. If a connected adapter offers insufficient power, define a controlled response. Depending on the application, that could mean slower charging, reduced functionality or a clear indication that a suitable supply is required. Repeatedly attempting to start and collapsing the supply creates an avoidable support problem.

Battery-powered equipment needs particular attention when the battery is depleted. The circuitry responsible for establishing the connection must still be able to start. Suitable controllers provide dead-battery support, and some can negotiate power without waiting for the main processor to run. The chosen implementation needs to support that behaviour.

Protection belongs in the same review. An accessible connector can experience electrostatic discharge, while damage or movement can allow power contacts to short to neighbouring signal contacts. Check the protection of the CC and data lines alongside the main power input, using components appropriate to the voltages the port may encounter.

The physical assembly matters too. Review connector mounting, enclosure clearance and how cable movement loads the board, particularly for equipment that will be connected frequently in service.

Testing chargers and cables before a product reaches production

Prototype validation should use a planned range of connections. Choose representative chargers, computer ports and cables based on the product requirements, then include lower-power sources to check the intended fallback behaviour.

Cable selection needs care because USB-C cables do not all have the same capabilities. Their power rating and supported data performance are separate considerations. A cable suitable for powering the product may still be unsuitable for its intended data connection.

Test both plug orientations at each USB-C socket. Check initial connection, disconnection and reconnection, then repeat with the product switched off, running and, where relevant, recovering from a depleted battery.

Apply realistic loads during those checks. For a handheld instrument, that might mean charging while the display is illuminated and measurements are being transmitted. For another device, it could be the moment an output stage is enabled. Include representative cable lengths and measure the voltage reaching the board under load, since resistance in the cable and connections causes voltage drop.

Record more than whether the product switched on. For a PD design, capture the negotiated voltage and current allowance alongside the actual input current and any resets. This helps distinguish a failed negotiation from a supply that becomes unstable when the load increases.

A useful test record identifies the charger, cable, board revision and firmware or controller configuration. If a problem appears after a component substitution or software change, those details make it easier to reproduce and investigate.

Once validation is complete, translate the findings into production checks. Where practical, exercise the USB-C input through the finished connector so the checks include its assembly and connection-detection circuitry. Keep approved controller settings under revision control and provide users with clear power-supply requirements.

At TAD, considering electronic design, prototyping and manufacturing together helps carry these decisions through to the finished assembly. USB-C PCB design then includes a defined power budget, tested connection behaviour and a repeatable production handover, helping reduce compatibility problems after delivery.

Click here to get in touch or here to read more.

‘Engineering Design, Imagine what could exist’

Got a web design question or mobile application need? Our in-house design agency, Bluebrick Studios, has you covered. Check out their site to find out how they can help you achieve your mission.

FAQs

Why does my USB-C device work with a USB-A cable but not a USB-C cable?

One possible cause is missing or incorrect configuration-channel connections. A USB-A source may already supply power, while a USB-C charger checks for a valid connection first. Inspect the CC circuitry, cable and power requirements before assuming the charger is faulty.

Does every USB-C product need USB Power Delivery?

No. A device can use USB-C for 5V power without USB PD, provided it implements the required connection detection and respects the available current. Negotiating a higher supply voltage requires USB PD support.

Will a higher-wattage USB-C charger damage a lower-power device?

A compliant, correctly implemented USB-C connection does not force the charger’s full rated power into the device. Higher PD voltages are negotiated, and the product draws current within the agreed or advertised limits. Compatibility still depends on the supported power settings, cable and device design.