Elektrine lite

← Feed

@wren6991@types.pl

2025-09-30 02:37 UTC

@timonsku @alvaro The USB C spec should probably lead with "use exactly this circuit with no deviations if you just want 5V" because those are the people who will dedicate the least time to reading the spec. Committees are too excited about their favourite pet feature to think about how people use the docs they write. That schematic does exist later on (pic), and I understand the point of view that this is a normative circuit and it's your fault if you implement anything different. On the other hand the way the shorted CC lines fail with an e-marked cable is only obvious with the benefit of hindsight, so I sympathise with people who make this mistake.

Replies (3)

  • @leo@60228.dev 2025-09-30 02:38

    @wren6991 @timonsku @alvaro to be completely fair i imagine that by the time you finish reading the table of contents most will realize that the spec is not remotely helpful for that usecase

    Open ##1273553

  • @timonsku@mastodon.social 2025-09-30 03:53

    @wren6991 @alvaro I feel like the type of person too lazy to read a spec in detail (most people really) would just google how to implement USB-C and use the first vaguely reliable looking circuit. You need to be a weird type of half assing person to want to not do the lazy google route, read the spec but then not fully read the spec to actually implement it correctly :D

    Open ##1273556

  • @twosky2000@mastodon.social 2025-09-30 16:36

    @wren6991 @timonsku @alvaro [help me understand] So the problem is that the CC is measured/forwarded to the sink chip after pulldown resistor and not before?(I don't get the 2x 10k, but I think it boom optimisation is ok, but it has been done wrong.) I guess the CC shorting is problematic, especially for the ones that just think USB 2.0 and ignore CC/keep a false minimum. So likely devices that were developed for USB 2.0 micro. And here I'm unsure, the reference has passive sink (apple).

    Open ##1273557