kopia lustrzana https://github.com/micropython/micropython
9a43989a86
Only when dynamic USB devices are enabled. The issue here is that when the USB reset triggers, the dynamic USB device reset callback is called from inside the TinyUSB task. If that callback tries to print something then it'll call through to tud_cdc_write_flush(), but TinyUSB hasn't finished updating state yet to know it's no longer configured. Subsequently it may try to queue a transfer and then the low-level DCD layer panics. By explicitly stalling the endpoint first, usbd_edpt_claim() will fail and tud_cdc_write_flush() returns immediately. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au> |
||
|---|---|---|
| .. | ||
| mp_cdc_common.c | ||
| mp_usbd.c | ||
| mp_usbd.h | ||
| mp_usbd_descriptor.c | ||
| mp_usbd_runtime.c | ||
| tusb_config.h | ||