Raspberry Pi Foundation confirms that the recently released Raspberry Pi 4 does not work with some USB-C cables
Context & Ripple Effects
Two weeks after the Raspberry Pi 4 launched with a new USB-C power input, the Foundation has confirmed what early adopters suspected: some USB-C cables simply don't power the board. The root cause is the Pi 4's non-standard handling of the USB-C spec, which trips up compliant e-marked cables.
This is not the first time the ecosystem has collided with sloppy USB-C implementation — Amazon moved in 2016 to ban non-spec-compliant Type-C cables from its store after similar compatibility chaos with phones and laptops. The difference now is that the device maker itself, not the accessory vendor, is the non-compliant party.
First-order effects
- Buyers who already own compliant e-marked USB-C cables — the kind shipped with modern phones and laptops — find their Pi 4 won't boot, forcing them to dig out older or 'dumb' cables that happen to work.
Second-order effects
- Accessory sellers face a wave of returns and support tickets misattributed to their cables, since a fully spec-compliant product fails on a non-compliant host — inverting the usual blame pattern from the 2016 cable bans.
Third-order effects
- If single-board computers keep adopting USB-C without rigorous conformance testing, the standard's promise of universal interoperability erodes at the low end of the market, pushing hobbyist ecosystems toward bundled, verified power supplies rather than user-supplied cables.
The trend: As USB-C becomes the default power connector across computing, spec-conformance failures are shifting from cheap accessories to the devices themselves, making certified-bundle power delivery the safer norm for vendors.