Till Harbaum

Alternately, one could return a pointer to the result itself in the error case like so: ``` tuh_hid_report_received_cb(daddr, idx, (XFER_RESULT_SUCCESS == result)?epbuf->epin:&result, (uint16_t) xferred_bytes); ``` This would allow to forward...

I am aware that it's not easy to reproduce. I am not expecting you to debug this. But you may have some ideas and hints. I'll try to reproduce this...

Some more results: - the same happens in a minimal software setup, basically only running tinyusb on freertos - the same happens with an off-the-shelf Pi-Pico with an off-the-shelf CH334...

Interestingly, the enumeration issues that have come with the latest tinyusb/pio-usb only happens with a CPU clock < 156Mhz. At higher CPU speeds, these are gone. However, the hub/unplug issues...

This may be related/the same issue: https://github.com/sekigon-gonnoc/Pico-PIO-USB/issues/149

I haven't tested without freertos. But with my minimal test setup it shouldn't be too complex to do. Unfortunately that won't be a solution for my application. But I'll give...

Removing FreeRTOS does not make a difference. Also, the HUB doesn't seem to matter and the device being plugged also doesn't matter. What matters is whether the device being unplugged...

I am still using my own code, which is now reduced to the bare minimum and has actually less functionality left than any of the official examples. There are a...

I just found my device that would send zero-length reports under normal circumstances. It's a competition pro USB joystick. This behavior is in the app callback indistinguishable from errors. I...

Whatever the user wants. It seems these are fully programmable, so there's no work for us to do. I just mentioned it since it might be useful for your core...