Skip to content

Comment on Google engineer finds USB Type-C cable that’s so bad it fried his Chromebookparent

Comments

This was not shorting +Vpp to GND; this was putting -Vpp in the +Vpp pin. All pins are referenced to GND, which is 0V by definition, so if you put +5V in it, it's the same as subtracting 5V from the voltage in all the other pins. And since they put the 0V in +Vpp, it became -5V. Most devices aren't prepared for negative voltages.

Point taken, but I still think that the device should be protected against supplying it with a "malicious" input voltage, as there are cheap and robust components to do this. The NCP373 for example (http://www.onsemi.com/pub_link/Collateral/NCP373-D.PDF) protects against voltages between -30 to 30 V and is designed exactly with the "faulty USB cable" use case in mind, and the low-volume cost is just 50 cents (large-volume cost is probably much lower). So I think there really is no excuse for letting a faulty 5 $ USB cable destroy your 1000 - 2000 $ device, even if it supplies an input voltage of the wrong polarity.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.