Operating System
Windows 11
Commit SHA
9072d97
Board
CH32Vx03-C-R0-1v0
Firmware
tusb_config.txt
What happened ?
I am using a CH32v203 Eval board (#3537) and trying to get a CDC device working on the USB-FS peripheral. It was really straightforward to get it working on the USBD port, but switching the config to USB-FS causes errors in the initial usb communications and fails to work. I suspect it is a problem with how EP0 is handled, as the initial transfer isn't acknowledged as complete in the log (see screenshot).
How to reproduce ?
I am using the cdc_dual_ports example with attached tusb_config.h uploaded on the official WCH ch32v203 eval board.
Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)
Here is the log output tusb.txt
Screenshots
I have checked existing issues, discussion and documentation
Operating System
Windows 11
Commit SHA
9072d97
Board
CH32Vx03-C-R0-1v0
Firmware
tusb_config.txt
What happened ?
I am using a CH32v203 Eval board (#3537) and trying to get a CDC device working on the USB-FS peripheral. It was really straightforward to get it working on the USBD port, but switching the config to USB-FS causes errors in the initial usb communications and fails to work. I suspect it is a problem with how EP0 is handled, as the initial transfer isn't acknowledged as complete in the log (see screenshot).
How to reproduce ?
I am using the cdc_dual_ports example with attached tusb_config.h uploaded on the official WCH ch32v203 eval board.
Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)
Here is the log output tusb.txt
Screenshots
I have checked existing issues, discussion and documentation