James Henstridge on Nostr: npub1pfe56…9e2dm It's probably down to how the configuration channel is wired up on ...
npub1pfe56vzppw077dd04ycr8mx72dqdk0m95ccdfu2j9ak3n7m89nrsf9e2dm (npub1pfe…e2dm) It's probably down to how the configuration channel is wired up on the USB-C side. It probably looks like a "legacy device adapter" from the USB-C side, so the configuration pin would be wired to ground with a specific pull down resistor. The USB 2.0 data and power pins would then be wired straight through to the corresponding Lightning pins.
To instead act as a host (the various "OTG" modes it says the adapter doesn't support), CC would instead need to be wired to 5V via a different pull up resistor. If it is possible to build an adapter that supports OTG, it'd need active electronics inside.
This is one of the simpler explanations of how the negotiation works in USB-C: https://medium.com/@leung.benson/usb-type-c-s-configuration-channel-31e08047677d
To instead act as a host (the various "OTG" modes it says the adapter doesn't support), CC would instead need to be wired to 5V via a different pull up resistor. If it is possible to build an adapter that supports OTG, it'd need active electronics inside.
This is one of the simpler explanations of how the negotiation works in USB-C: https://medium.com/@leung.benson/usb-type-c-s-configuration-channel-31e08047677d