3 ms·
I personally blame the spec for making it far too complicated to build compliant devices and far too easy to build non-compliant devices
by amluto 7y ago
I personally blame the spec for making it far too complicated to build compliant devices and far too easy to build non-compliant devices
- toomuchequate 7y agoEasy to say. I can't imagine doing signaling and having to build a spec.
- amluto 7y agoAs far as I can tell, the spec could have been designed so that having so resistor at all would indicate a baseline cable. Since no resistor is cheaper than a resistor, the cheap cables would omit the resistor and all would be well.
- cesarb 7y ago> As far as I can tell, the spec could have been designed so that having so resistor at all would indicate a baseline cable. Isn't that exactly how the spec is? AFAIK, a baseline cable has no resistor, the resistors are on the devices on either end. Only "electronic marked" cables have a resistor, and that's where the RPi4 fails: they shorted together the pin which has the configuration wire to the other end (where the device on the other end has one of its pair of resistors) with the pin which on a baseline cable has nothing at all, but which on a more advanced cable has a resistor connected to ground. So when there's no resistor at all (baseline cable) it works; when there's a resistor, the current flows through a wrong path and the voltage ends up in the range for a different kind of device.
- amluto 7y agoNope. A compliant baseline USB-A to C cable contains a resistor.
- arghwhat 7y agoIt could not. I presume that by "baseline", you refer to a USB2.0 Type A to Type C cable. USB type C is designed to remain passive until it knows if something is connected, and what it is. For most cable types, orientation must also be detected. This means that there must be something in the cable/plug. This could of course have been a short, but to do that, those pins would have to be dedicated to detecting dumb cables. Having no pins to waste, a resistor is used instead, which allows not only allows for multiple values for detection, but leaves the pins usable for transmission while detect resistors are in place (Power Delivery, Alternate Modes). And there is absolutely no issue in that resistor. Everyone found the table, but either failed to read the 3 values, or decided "Hey, more amps is better!", ignoring whether or not the type A end would actually be able to supply it.
- snops 7y agoThe spec does try and make it simple to build compliant devices for basic features. It's only if you want higher power or bandwidth than the existing USB 2.0 that you need any kind of digital logic. For instance, a USB-C analog headphone adaptor is just some resistors and the connectors themselves, and a USB A-C cable just requires a single extra resistor so the USB C device knows there is a USB A plug on the other end and not to draw too much current. Unfortunately, dodgy manufacturers got even that wrong, see https://www.extremetech.com/computing/217556-google-engineer-challenges-usb-c-cables-for-sale-at-amazon https://www.extremetech.com/computing/217556-google-engineer...
- amluto 7y agoSimple to build simple devices is the wrong metric. The goal should have been that simple devices would be cheap enough at scale and, critically, the the correct way to build a simple device would be at least as easy as the lazy way that sort of works.
- arghwhat 7y agoThe spec sure is a mouthful, but I find strong evidence that the spec isn't at fault. The reason is the most common type of error: USB type A to type C cables using a wrong termination resistor value, signalling far too high current. We're talking about a table of currents to resistors with 3 rows: Default USB current (56K), 1.5A (22K) and 3.0A (10K). Now, if the mistake had been in the parts that deal with orientation detection, PD protocol, alternate modes, or just dealing with the high speed signals pumping up to 40Gb/s through these cables, then we could agree that it might be complicated. But if you can't pick a resistor from 3 values, then I don't know how one would write a spec that would be readable to you. EDIT: s/that\ the\ evidence/that\ the\ spec/