I am not defeated by #tinyusb yet, but I am pulling my hair out.

At the stage of taking a break for a bit. This is almost unheard of in the way I usually work. But it is so frustrating.

So I'll try and get back to it in the morning.

I may even have to use the source, Luke, and read the actual library code.

Of course, the second I say that I have a brainwave, and now have #tinyusb (not esp_tinyusb) getting as far as my Mac trying to "enumerate" it and failing, calling the config request 5 times, so clearly it does not like my config. This is massive progress!

I did manage an hour in the hot tub, a coffee, and a sausage roll, so maybe that did the trick.

@revk Allowing yourself time to do something else to make room for shower (hot tub) thoughts is important in itself.
@revk Semi-related; have you made sure you esp board has a useful PSU cap on it somewhere? On that board of yours I got, I found it's enumeration problems on most machines via a C->A cable were fixed with a big cap;
@penguin42 I have added bigger caps on my boards these days, maybe send a pic of the board and I'll check if I have updates. This case is not that problem.
@revk No need; it's the EPD75 from 1st Dec (hmm 2024?), but I did notice on the problematic hosts it was always at 'phy init' in your serial debug where it resets.
@penguin42 ok yes, I found long USB cables led to issues and added a chunky cap to the design to fix that.
@revk the code is often the most accurate documentation :)
@ahnlak Indeed!

@revk reminds me of University days, well before the web existed - our "documentation" usually involved reading header files and working backwards from there.

Sometimes I think 'modern' programmers are missing that joy of figuring stuff out, but google really is a lot quicker...!