The Confusing World of USB
fabiensanglard.net
fabiensanglard.net
Nope... it's even more complicated. Up to "3.2 Gen 2x1" they have 8 wires, but "3.2 Gen2x2" has 12 wires. There's two pairs of RX and TX each, i.e. RX1- RX1+ RX2- RX2+ TX1- TX1+ TX2- TX2+ D- D+ PWR GND = 12.
And... that's still not correct: USB-C to USB-C cables have an additional CC line which carries the Type-C extra negotiation (e.g. alt mode switch, power levels.)
And just to fuck users over even more, there is a difference between a 13-pin full-function "USB 3.2 Gen2x2" cable and a 13-pin full-function Thunderbolt cable: the Thunderbolt cable reports an extra "vendor descriptor" on the Type-C negotiation channel, indicating support for TB. The cables are otherwise physically identical, but these extra bits come with a ~$15 markdown.
(Oh and the PWR/GND lines can be 3A or 5A, but at this point...)
The article is, however, correct in its conclusion: a "Thunderbolt" cable will always work for all USB standards. The only free variable on a TB cable is whether it does 3A or 5A for power.
is how you burn your Tristar in the best case scenario, and a House if you are unlucky
https://www.goodmorningamerica.com/living/story/gma-investig...
https://www.vice.com/en/article/bj34z5/why-counterfeit-light...
'Jessa Jones, owner of iPad Rehab in Honeoye Falls' cited above is a legend https://www.youtube.com/c/Mendonipadrehab/videos
I have never owned devices as buggy and temperamental as iPhones/iPads, and I absolutely hate that Apple gaslights me when I need to repair them.
Aren't active (i.e. >50cm) Thunderbolt 3 cables incompatible with USB 3 speeds due to having some active amplifier incompatible with the USB line signals?
(Not sure if the Type-C negotiation will prevent them from working; it might.)
Ed.: after a quick check, active cables seem to crop up at 40G && >= 1m. 40G 2m cables seem to all be active, at 1m it's either. Couldn't find any "20G" active cables.
And I think the maximum length for passive Thunderbolt 3 40 Gbit/s cables is indeed 50cm [2]! 50-200cm would be 20 Gbit/s only; anything above always requires active cables.
[1] https://appleinsider.com/articles/17/08/15/psa-thunderbolt-3...
[2] https://blog.startech.com/post/thunderbolt-3-the-basics/
FWIW my confidence level on "would an active TB3 cable work for USB3 if it had the proper bits set" is somewhere along 66% to 75%; this is based on the SERDES in some (most?) TB3 host silicon being able to switch to USB3 to "downgrade" a port... meaning the electrical level can't be all that different... but I haven't dug into this.
So, 15 wires in a full-feature C-C cable...
Thunderbolt still works at 20gbps over "normal" superspeed USB-C cables; the markup you're paying is generally for cables rated for 40gbps.
Your second paragraph is half-wrong. Thunderbolt cables must have an e-marker: refer to https://www.usb.org/sites/default/files/USB%20Type-C%20Spec%... Figure F-1 ("SOP'"). If the cable has an e-marker but doesn't have the Thunderbolt ID, you get passive Gen2. However, the problem is that USB3 TypeC-C cables aren't required to have an e-marker at all... in which case you drop out at the very first fork in the flow diagram.
This also leads to the funny situation that any 5A USB3 cable should work for Thunderbolt (because 5A requires the e-marker), while 3A cables may or may not work. I mean, of course the power rating makes complete sense to determine TB3 capability, right? :D
Instead, USB device manufacturers want to cost optimize everything, which probably forced the standard to become so Byzantine. Understandable from a manufacturer's point of view, but terrible from an end user perspective.
The poor enforcement of trademarks being - that there should not be a plethora of things claiming to be USB which are not spec compliant, nor should people be using names like "USB 3.2 Gen 1x1" vs the marketing name "Superspeed USB".
You also see this poor enforcement with other organizations, such as DisplayPort vs DisplayLink.
This spills over to problems with cabling, such as how much wattage is supported for power delivery or what speed data transfer is available.
Oddly Intel is the one stepping up here with Thunderbolt 4, because it is now more of a certification than a specification.
Relying on cables internals for function is just as stupid as can be.
To be fair, there were only a handful of those really early on when M.2 was just getting started and OS/BIOS support for NVMe wasn't universal yet. And hardly any of them were released as retail products; they were mostly OEM-only drives. All of those drives went out of production 3-4 years before the first host devices that require NVMe and can't work with AHCI started to show up: USB to NVMe bridge chips for external enclosures. So if you haven't encountered an AHCI M.2 SSD yet, you probably never will and knowing about them is just an obscure historical curiosity.
- Host queries some property and each cable along the way appends their value to that message and passives it along.
- The endpoints either loopback if they're the new standard or pull down the pins if they're USB-2 only.
- It follows that if no message makes it back then we're limited to USB 2.0 and if a message does make it back, we can query/configure all elements along the path of connections. Right now this is impossible which makes it impossible to detect if there is a non 50v tolerant hubs between two hubs.
- The programming/hw implementation for PD and alternate mode would also be non-insane in this model. Currently PD requires stupidly complex state machines, op amps, resistor banks or some autonomous IC to pull off and there are so many screwups because it's such an obtuse standard.
- Supporting alternate modes, and providing more diagnostic information would be much easier.
There should have only been 2 passive cable types - 2.0+PD and USB 3 gen 1 - everything else should require a smart tag on the chip.
What does "CC" stand for?
There are an added pair of pins/single wire in USB-C cables that allow the devices to a) detect the orientation of the plug and b) do extended power negotiation for the increased power capabilities of USB-C.
This should all be solved at the negotiation layer, even if that needs to be made more complex, so that the remaining components can be simpler and reasonably-behaved.
Instead, we got something that allows each device to be a bit more electrically simple, at the cost of ballooning complexity for the ultimate use case.
USB-IF took their eye off the ball, and wrote a spec for manufacturers, without thinking about the consequences to consumers.
At some point, it's a value trade-off between {working product for use cases} and {+$2 on BoM}.
As Intel loses its raw CPU performance advantage, it's new marketing materials promote "features" and "convenience". Practically speaking, USB is defined by Intel, and it is making a visible choice to allow itself a position in the market for Thunderbolt 4 by making some USB4 features optional so they can include them in TB 4, and adding other small minimum performance guarantees and hoping that is enough to sell TB 4 chips to high-end AMD motherboard makers, which in turn makes their own CPUs (with built-in thunderbolt 4) more price competitive. It is a sound business plan, but not in the best interest of consumers.
The fate of a universal lingua franca connector is too important to be left to just one company. Why is it still being defined by Intel rather than a panel?
Intel, Microsoft, Apple and even HP are notable members.
This outcome was pretty obvious, it's literally in the name of the damn thing: UNIVERSAL Serial Bus. The only way to achive that is to lower yourself to the lower common denominator.
In all seriousness though, the current state of a USB is ridiculous.
My wife innocently asked me why her USB C phone isn't triggering Android Auto in the car, and straight away you know it's because she bought a USB C power-only cable without knowing the difference.
Nice.
Less generally, these batteries can also break ground loops, which comes in handy when connecting a power supply to both a USB device and an attached analog audio device (e.g., iPhone and wired noise-canceling earbuds).
You'll note that many chargers started dropping handshaking because it was inconvenient. To be compatible with anything you need it, but there's many that don't ask, though they may only work with the equipment they were sold with. (E.g. defaults to 5V 2A charging.)
The historical design intent of USB is that, even when your laptop is in standby it still powers devices like your keyboard (so you can press keys to wake it up) and in exchange, devices promise to consume less than 2.5 milliamps (12.5 milliwatts) until they've negotiated permission to draw more from the host. After all, it'd suck if your laptop battery was going down noticeably even when the laptop was in standby.
Of course, loads of vendors of cheap devices ignore this - the makers of a $5 rechargeable bike light or USB fan aren't going to put in the components needed to negotiate charging speed. But in principle if you made a USB cable with only the power pins connected, compliant devices should only charge exceptionally slowly, if at all.
(Wall chargers, instead of enumerating as a USB host to negotiate power, used to put a certain value of resistor across the data lines, to signal what current the device could draw - this hasn't always been standardised, which is why phones and USB chargers can be incompatible)
Note also a fair number of laptops (read: every one I have used and checked) use PS/2 internally because it is interrupt driven and even lower power than USB. There are also plenty of laptops that advertise high current phone charging while off, some of which do negotiation, some of which don't.
[0] http://msdn.microsoft.com/en-us/library/windows/hardware/hh8...
Ignoring that, I'm not sure it's an improvement. Most of the power savings is having the keyboard initiate an interruptible event to wake the computer. Interpreting HID like in USB means the keyboard can't wake the computer, the computer needs to remain on to service USB interrupt endpoints.
The laptop I had with an always-on charging port actually charged things faster in standby, because that turned off the negotiation.
> defaults to 5V 2A charging
i don't think you understand how power transfer works.
voltage is applied (by the charger), and current is drawn (by the device that wants to charge). a charger cannot "dump power into" anything.
when chargers and devices attached to them engage in some sort of negotiation, that's not the device telling the charger what to do, that's the charger telling the device what its limitations are.
if you attempt to draw 3A from a device that can only do 2A, the voltage will drop outside of the specified range. to the extent that a charger can limit the charging current, it does so by dropping/cutting off the voltage until the current goes down. which isn't ideal for devices.
(perhaps you're confused by thinking that USB "chargers" are like battery chargers, and arbitrary USB devices somehow act like batteries. that's all wildly wrong.)
The main concern behind negotiation seems to be safety of the user and safety of the power supply. Detecting a safe load means detecting a not-short.
The basis for the 5V power negotiation on USB is extremely silly. The power supply is already current limited, protecting you from shorts, and the supply voltage is ~5V, quite far from anything dangerous.
This may be true for wall chargers but not devices capable of supplying power to peripherals while on battery power themselves.
For example, an external hard drive should not have to figure out that a large tablet can power it, while a phone won't, though trial and error, by attempting to spin up the disks multiple times.
Devices are going to misbehave anyway, it's probably more important to default to a reasonable level of mostly works.
Android already allows you to only use an USB connection for charging. Setting this as the default when you are in an unknown place sounds reasonable.
OTOH, a USB Y-cable physically has no data lines connected on the extra USB-A male connector; it thus provides a far stronger guarantee that there is no data travelling across them. (Not foolproof, but safer than a software-controlled switch.)
If you don't trust that cellphone won't transfer your private data via USB, I don't understand why you trust it not to do it via any wireless connection.
They're pretty nice too, the only made in Germany USB-C/lightning cables I have ever used.
Maybe it's possible to make one lacking both USB 2 and 3 data though, but I haven't seen one yet.
Nor have I seen a public USB-C outlet, for that matter, and I probably wouldn't be plugging my laptop or phone into one anyway: My own charger doesn't only protect me against bad intent, but also against cheap charging circuits that might or might not accidentally expose 220 Volt to my laptop's mainboard in case of faults.
Ouch. USB-C is even more fucked up than I thought… How does that even works with USB wall chargers?
> Nor have I seen a public USB-C outlet, for that matter
There are plenty of USB-A outlet everywhere (airport, trains, hotels, etc.), and most recent Android phones have only an USB-C port…
If they want to supply more than 5V/3A, they need to support the power delivery protocol too.
> There are plenty of USB-A outlet everywhere (airport, trains, hotels, etc.), and most recent Android phones have only an USB-C port…
Exactly: These are USB-A outlets. These are possible to implement using only a resistor network to announce the maximum charging current and always supply 5V, which is much easier to implement than variable voltage and the power delivery protocol. USB-C can do this too, but only up to 5V/3A.
USB-C devices are usually backwards compatible with all three of these when using an A-to-C cable or adapter: Legacy USB-A current identification via the D+/D- pins, USB-C resistor-based current identification via the configuration pins of USB-C and USB power delivery.
Not a criticism of the USBIF* just pointing out the motivations to underline your point.
* BTW I have plenty of criticism, this just happens not to be an example.
> badly fragmented connector world made of
Dont forget SCSI. USB killed external SCSI.
>Up to that point in time, it was a good tech stack.
USB 0.9 was 1995, USB 1.0 1996. Two years later we had Bill Gates getting embarrassed by Windows 98 BSOD on stage https://www.youtube.com/watch?v=IW7Rqwwth84. By ~2002 we ended up with 6 separate incompatible proprietary variations on micro USB. Pretty much every second Camera vendor had its won "standard".
>USB-3.X cables features 8 wires .... and the other six carry data
Sadly just adding even more confusion to the mix. 24 pins, up to 13 signals, 4 pairs (8 wires) dedicated to USB 3.2 alone.
>Thanks to DP 1.4, the bandwidth requirement can be lowered via DSP lossless compression
oh its very much lossy, Display Stream Compression (DSC) is "visually lossless" :--------) it works similar to Texture Compression, but works on blocks of lines instead of rectangles, still it does destroy information by cutting off color accuracy.
At the end of the day USB is still trivial compared to Bluetooh.
Yet the article states:
>Accordingly "USB 3.1 Gen 2" became "USB 3.2 Gen 1x1" and "USB 3.1 Gen 1" was renamed "USB 3.2 Gen 2x1".
Either way, this article gets the point across that USB has turned into a complete mess.
That's what I don't understand: Why go with both minor versions and the Gen's in a single name? They could have just retroactively rebranded USB 3.0 to USB3 Gen1, and then went USB3 Gen2, USB3 Gen3 for the 3.1 and 3.2 specs (2×2 is another mess [1]). Tech people would have understood that the specs are 0-indexed and the marketing names (GenX) are 1-indexed. Consumers would only see the Gen on ports, cables and devices.
Still, I don't even understand why hiding the raw speed number from consumers is so important: Short Numbers are always better than vagely similar marketing names: - USB3 (5Gb) - USB3 (10Gb) - USB3 (20Gb) - USB3 (40Gb) or (2×20Gb) Done.
[1] The final page of this Anandtech article is pretty spot on about Gen2×2: https://www.anandtech.com/show/16133/usb-32-gen-2x2-state-of...
The confusion created by PD/3.1/dp/hdmi/tb/etc is mostly irrelevant to me, and I think the clusterfuck there is real but overblown (so long as pd devices will charge slowly from normal 5V c ports/cables, and usb3.whatever will fall back to usb2).
I can charge my travel router, dji gimbal, gopro, android phone, ipad, and macbook pro (albeit slowly) from the same cheap cables. Neewer battery chargers are now dual micro/c, too.
Even if it were just a 5v connector it would be a win.
The fact that I can wire up a 220VAC etherkiller with a USB-C port on the end is not a failing of the USB spec or in any way the fault of the USB-IF.
It uses a USB mini connector for a 19.whatever volt power supply. Don't plug that into your external HDD by mistake.
Yes, I know USB mini is obsolete, but we still own a couple devices that use it. And the plug is stamped with the USB logo.
I also have no idea how they ever thought that was a good idea vs just using a barrel plug.
They really need to use semantic versioning and be forced to clearly display that version number on the cable or connector in a legally defined, readable size. In fact every cable type should have that. I recently bought a 2K 144Hz screen and could get the display manager to set 144Hz. Then I looked up the standard and found out HDMI 1 doesn't support 144Hz but HDMI 2 does. Not a single cable in my house has the version number written anywhere and I had to try them out until I got the right one.
What I would really appreciate is:
Cable X not compatible with Cable Y --> different major versions and completely improved specs, power requirements, AND different shape
Cable X.X is compatible with Cable X.Y but has different functionalities --> same major version, different minor version, same shape. Easily understandable by users "First thing I see is a big X, it fits with whatever I'm trying to connect with, it should work". If it doesn't then they can look closer and go "ooh.. the small Y is different. I should get Y or Y+n".
That's it.
Additionally, there are hundreds of manufactures making equipment that uses the USB ports, but which don't follow the specs beyond what's needed to "make it work", and they can't be stopped through legal or trademark enforcement as they're largely-foreign, and they just fold and re-appear as a different company if ever challenged legally.
As far as hubs are concerned... they're designed for TB uplinks; AFAIK most silicon that exists can fall back to USB3 with significantly reduced functionality but you're gambling again at that point. I'd recommend against it.
Not entirely. There are third party TB controllers by now, the problem is they're heavily guarded by NDAs.
Also, I heard that Thunderbolt 4 is the same as Thunderbolt 3, except all the optional features from 3 are required in 4.
This interview seems relevant: https://www.youtube.com/watch?v=lnSMbgndFHo&t=2m3s&feature=y...
It can be very cheap, very fast, very powerful and still be compatible with most* devices.
Any other standard trying to fix one of the aspects will drop the ball on the others - e.g. see Apple's attempts at Thunderbolt 2.
Also, "simple" has to mean something else in your world because I distinctly remember the onus of having to figure out the right baudrate, stopbit and parity bit configuration. Not to mention devices which used TTL level RS-232 and wouldn't work with other devices DESPITE having the same connector and standard.
USB is a godsend compared to that.
With USB, as long as the both ends and the cable are built to spec, it's safe to mix and match. You'll just end up with the lowest common denominator of functionality.
We used to have the "slow port/fast port" dichotomy with USB vs FireWire, but people were too cheap to pay for the fast port and eventually the slow port got fast enough to replace the fast port.
Have a feeling we'll end up with an xkcd standards [0] situation if someone comes along with a competing protocol.
It seem this is something everybody agrees with nowadays, but was it always like that? After all, USB-A plug has a prominent logo (distinguishable both on sight and by touch) that identifies up-side. It should be dead-simple to do, no? What went wrong?
- Did some laptop manufacturer mount USB-A receptacle upside-down?
- Or was that micro-B that trigger this? (for example Samsung/Nexus S and LG/Nexus 4/5 have micro-B receptacle upside-down relative to one another)
- General feeling of inferiority from Apple's Lightning plug?
- Something else altogether?
And I’ve plugged in a lot of USB cables in my time, and even read parts of the USB spec in order to implement USB. Maybe I’m just a moron though.
The major feature of usb-c isn't that it's bi-directional as in "you don't have to try 3 times", it's bi-directional as in "it's both an host and perpipheral port" but somehow everyone seems to forget that. That's why it's a C connector, it's both A and B
And the meme itself comes probably from the fact that USB-A port needs rather precise positioning to connect. Even if you are inserting connector the right way from the start, you will most likely hit metal part of the connector against metal parts of the port at first try and it will cause you to doubt yourself. You then turn it (incorrectly) and fail again, turn again (correct now) and try connecting more slowly and precisely and only then it fits :)
The other half of the time the logo is faintly embossed in black on a black substrate that your ambient lighting is just dim enough to render not visible.
Even without all that, the feeling of being slightly misaligned with the port and the feeling of trying to plug it in upside down are hard to distinguish, with many port mountings, so people assume they've got it wrong and switch orientation.
USB 1.0 needed to be cheap and simple to be adopted. Wrapping a bit of metal around a PCB was cheap and simple.
Lots of ports facing up or facing down (on the bottom side of a monitor).
Lots of cables have logos on both sides (JBL is an example at hand).
Lots of cables have NO logo (Fitbit).
The ergonomics of reaching it from the driver seat while fully seated in that seat must be an interesting study.
I owned one car long enough to be able to get the connection on the first try multiple times.
On the USB-A plug you can see inside, so if there's no logo you can go by the plastic tab inside the connector, usually white or blue plastic. The tabs have to be on complementary sides.
I was under the impression that cables with power delivery used two pairs of power and ground (upto 20V iirc). https://images.anandtech.com/doci/11667/usbtypec-pins.png
Is this correct? It seems swapped.
> This allows 40k60 on two lanes