Skip to content
Discussion options

You must be logged in to vote

I got it working by using a “CH34x VCP shim” because the FS‑600 used in this project here https://github.com/SunboX/radpro-wifi-bridge exposes its USB UART as a vendor‑specific interface (0xFF/0x01/0x02) instead of proper CDC-ACM descriptors. TinyUSB’s host stack only binds its CDC driver when it sees the full Communication/Data interface pair plus the CDC functional descriptors. So when the CH34x shows up, TinyUSB shrugs and leaves the interface untouched. The shim steps in to claim those VID/PID combos, synthesise the CDC bits TinyUSB expects, and stub out control requests (like SET_LINE_CODING) that the CH34x ignores anyway.

To make this unnecessary, TinyUSB would need upstream support…

Replies: 4 comments 8 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
8 replies
@SunboX
Comment options

@SunboX
Comment options

@SunboX
Comment options

@hathach
Comment options

@SunboX
Comment options

Answer selected by SunboX
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants