|
|
|
|
|
by mike_d
1062 days ago
|
|
> doing that sort of thing is almost certainly a waste of time. A waste of time for both parties, because the author is wrong. As Wikipedia helpfully points out: "The designation C refers only to the connector's physical configuration or form factor and should not be confused with the connector's specific capabilities" From the write up it looks like he was able to get it working with the minimum 3A required by the cable spec. You don't actually have to support C-to-C cables if you choose to not to communicate with the e-marker. |
|
> USB-C devices may optionally provide or consume bus power currents of 1.5 A and 3.0 A (at 5 V) in addition to baseline bus power provision; power sources can either advertise increased USB current through the configuration channel, or they can implement the full USB Power Delivery specification using both BMC-coded configuration line and legacy BFSK-coded VBUS line.
And further down:
> However, to connect a USB 2.0/1.1 device to a USB-C host, use of Rd[57] on the CC pins is required, as the source (host) will not supply VBUS until a connection is detected through the CC pins.
See: https://en.wikipedia.org/wiki/USB-C
As the device doesn't implement the full USB PD specs, it must advertise that it wants power through the CC (configuration channel) pins. This is part of the specifications and it must be properly implemented.