5 ms·
This has always been a criticism of USB C and it proves true time and time again. USB-C tries to be too many things to too many people and ends up with a huge
by loeg 7y ago
This has always been a criticism of USB C and it proves true time and time again. USB-C tries to be too many things to too many people and ends up with a huge matrix of incompatibility as a result.
- teilo 7y agoAnd the criticism is completely invalid here. The power spec is very clear and unambiguous, and there is only one way to get it right. It is not the fault of the spec when manufacturers cannot be bothered to produce a circuit that has already been designed for them in the spec itself.
- TazeTSchnitzel 7y agoThe USB Power Delivery specification is very complicated and covers, despite the name, a lot more than power delivery.
- cesarb 7y agoBut in this particular case, USB Power Delivery was not involved, only basic USB-C. The USB-C plug was designed so that simple uses, like the 15W charging RPi has, do not need USB Power Delivery at all, just a couple of identification resistors and a way to read the resulting voltage (which will tell whether you can use the full 3A or must use less).
- silversconfused 7y agoToo complex and overreaching is certainly a valid fault.
- oceanswave 7y agoIf a spec defines a fully working part, and you go off and tackle the complexity by designing your own part that turns out to be non-compliant, then the blame is on the spec?
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- CriticalCathed 7y agomaybe the spec is onerous
- CamperBob2 7y agoOr vague, or just plain incorrect. I could see making a mistake like this. The earlier USB specs called for goofy things like grounding the shield to the enclosure entrance via parallel RC networks instead of bonding it properly, as well as adding various bypass capacitors to the data lines(!). These guidelines were poorly thought out, widely misinterpreted and even more widely ignored. They have conditioned engineers to make their own judgment calls in areas where they really should have been both more descriptive and more prescriptive, so maybe this is one of those cases. I haven't looked at the post-USB 2 specs at all but wouldn't be surprised if they are nowhere near as clear, unambiguous, and well-thought-out as people here are saying.
- silversconfused 7y agoHey, it worked(?) for the web!
- squeaky-clean 7y agoThe spec is not the product. The USB C spec is not a USB C charger. It may not be a valid criticism of the spec but it's a 100% valid criticism of USB-C
- michaelt 7y agoBlame for this problem is 80% on RPi, no doubt, but I'd say 20% of the problem is someone deciding to allow multiple cables, some with active components in them. If they'd instead specified that every detachable USB C cable must be 40 Gbps / 100 watt capable, and any lower-spec cable must be captive to the device (like mouse and keyboard cables are) then this problem wouldn't have happened.
- mmastrac 7y ago> If they'd instead specified that every detachable USB C cable must be 40 Gbps / 100 watt capable, and any lower-spec cable must be captive to the device (like mouse and keyboard cables are) then this problem wouldn't have happened. If you are specifying that every cable is going to be $30 minimum, then your spec is dead from day 0. The USB-C committee has to balance a spec that will be used by a significant chunk of the planet, not all of whom can afford expensive cables.
- beatgammit 7y agoI like RJ-45 for this. I can choose between several different cables that are all compatible and pay only for the features/speed I need.
- dingaling 7y agoFull-spec cables are only $30+ because that includes a premium margin for being full-spec, as a differentiator. If all USB-C detached cables had to meet full-spec then there would be price competition.
- monocasa 7y agoWhat happens with A to C converters and legacy cables? Or do we just not support A devices anymore?
- adrianmonk 7y agoIt seems like the spec must be at least reasonably clear because after these mistakes are made, someone like Benson Leung can always point to it and the community has little trouble adjudicating that yes, the spec said this one thing, but someone did that other thing instead. Given this has happened time and time again, it seems like a process flaw more than a document flaw. Maybe well-meaning people just make mistakes. Or maybe people knowingly cut corners to save money (because saving on parts is a pressure that will never go away). Or something else. So some sort of process fix seems to be needed, one that will (1) reward those who succeed and/or (2) punish those who try to get away with violating the spec and/or (3) create tools (like test equipment or certification services or processes) to make compliance easier to achieve for those who are trying to. So, for example, could the Pi people have used some kind of device that would plug in and run through all the combinations? Or could there have been a canned list of test cases (representatives of different types of chargers, how they should behave) they should have run? Or could they have sent a prototype device off to USB Shouldn't Suck Labs to have them test it? Or email a schematic to them to have it reviewed by an engineer?
- smittywerben 7y ago> Given this has happened time and time again I wasn’t aware there were different specs until a few weeks ago. I’m sure the rpi4 was in development since last year. They should have tested more cables, maybe they can fix it somehow.
- majewsky 7y ago> maybe they can fix it somehow Given the problem description (wrong number of resistors), I doubt that they'll be able to fix it in the existing boards. I don't know how feasible it is for them to retool, but maybe we'll see a model 4.1 with an additional resistor show up at some point.
- Causality1 7y agoI wish there was some kind of patent or trademark law that could be used to punish companies who advertise with the word "USB" or "Type-C" without adhering to the spec.
- CamperBob2 7y agoIt is interesting that the USB Forum, for all their VID/PID douchebaggery, didn't register the trademark and enforce it on non-compliant implementations. That would have been right in line with demanding that everyone buy 65,536 IDs at a time for thousands of dollars while attempting to prohibit resale.
- DuskStar 7y ago> The power spec is very clear and unambiguous, and there is only one way to get it right. Obviously not, since there is a way to get it almost right, which is what the Pi 4 demonstrates here. Experience from cryptography suggests that for a spec to be truly unambiguous, any deviation should make the implementation fail obviously in as many situations as possible.
- umvi 7y agoUSB in general seems like a deep, deep rabbit hole. You could devote your entire career to becoming a USB expert. The USB 2.0 spec is like 700 pages long. The 3.0 spec is like 500 pages long and requires you to be familiar with the 2.0 spec at the very start. I started digging into USB for a project and the rabbit hole kept going deeper and deeper; I never fathomed the amount of complexity hidden under the hood of USB until I needed to start talking to a Qualcomm modem on the other side of a USB 3.0 connection (and the modem, even though it is a single device, enumerates 16+ USB 3.0 endpoints, which is a problem for a lot of ARM SoCs, or at least the vendors we tried!).
- yrro 7y agoWhat do they all do!?
- derefr 7y agoI would guess that they're basically directly exposing the modem's ACPI device subtree over USB, the same way they would over PCIe. So you've got one endpoint corresponding to the data TX DMA region; one corresponding to the data RX DMA region; one corresponding to the command IO stream input; one corresponding to a command error channel; one corresponding to each different axis of mode-setting; etc.
- marcosdumay 7y agoWell, this design is better than the alternative. Composing simple devices in a hierarchical address is much better than the old complex devices that had everything explained on the same datasheet, but it had 300 pages and no two devices were alike.
- m463 7y agoThat said, the serial cables that preceeded USB had very simple specs that put the brunt of interconnection complexity on the user. 7 bits even parity? 8 bits no parity? hardware or software flow control? how do I know the modem is connected? lots o' fun!
- ksec 7y agoWhich is the single reason why I hate USB-C, and I don't want USB-C to replace lightning. And yet people keep saying USB-C will get better, the controller will get better, the quality of USB-C cable will get better. And Time and Time again it has proved vendors only care about cost, not quality.
- nothrabannosir 7y ago* customers, not vendors. Vendors respond to the market.
- heyoni 7y agoSure. That’s why it’s taken decades after the ubiquity of the Internet for movie production houses to put their content on streaming services.
- pasabagi 7y agoI think the problem is, there's a distinction between a customer and a user. The customer just looks at the object, judges if it's adequate, then takes the cheapest one that meets that rough criterion. That's a very different kind of test to actually using the thing.
- viraptor 7y ago> people keep saying USB-C will get better Maybe people remember the beginning of USB. No cable marked charging/data but some are charging-only. Different resistances interfering with charging. USB 1 hubs pretending to be 2. It was all sorted out with time. Now USB 2 seems like magic that just works everywhere, but it really used to suck. (The experience, not the tech itself)
- addicted 7y agoThere are some very bad lightning connectors too. In fact, you can buy lightning connectors that will destroy your iphone. Poor quality implementations in order to save costs have nothing to do with USB-C vs Lightning. In fact, because Apple charges so much to be able to build official lightning devices, people are more likely to go with unofficial cables from unknown brands. At least USB-C cables and chargers are a lot cheaper for reputed brands to manufacture officially.
- rbanffy 7y agoI guess there is some market for a USB-C compliance tester gadget you can plug into a device and check exactly how compatible it is.
- windexh8er 7y agoBenson Leung from the linked article... "The Figure 4–9 I posted above isn’t simply a rough guideline of one way of making a USB-C receptacle. It’s actually normative, meaning mandatory, required by the spec in order to call your system a compliant USB-C power sink. Just copy it." The reason this is wrong on the Pi is not because of "a huge matrix of incompatibility", but of ignorance to a mandatory design spec that is provided to everyone already. It seems to parallel crypto from a high level. Yes, USB-C can be complex. But they did the hard work here so: don't roll your own and use this free and complete reference implementation.