Closed PoroCYon closed 1 month ago
(cc @gregdavill since he is the author of the driver/backend/port?)
There is a PR regarding ch32 issues, you can give a try: https://github.com/hathach/tinyusb/pull/2392/
Glad it works, it can be closed once PR merged.
Operating System
Linux
Board
CH32V307 (using both the SCDZ devboard and a custom board)
Firmware
Provided at https://github.com/PoroCYon/tinyusb-bug-repro --- both a CH32V307 version, and an RP2040 version which does functions correctly.
What happened ?
On the CH32V307, using DFU, the following effects may be observed:
CFG_TUSB_DEBUG=2
or ASAN enabled, while without it happens much more randomlyHow to reproduce ?
Compile and load the provided firmware onto the chip. Then run
dfu-util -D payload.py
. Watch how the data in the hexdump changes, the CRC changes (for hard to spot single-byte errors), and how sometimes, hangs/crashes occur.Debug Log as txt file (LOG/CFG_TUSB_DEBUG=2)
This gist contains three log files:
log-vkart-rp2040.log
: RP2040, working correctlylog-vkart-ch32v307.log
: CH32V307, showing erratic behavior, withCFG_TUSB_DEBUG
=0log-vkart-ch32v307.2.log
: CH32V307, withCFG_TUSB_DEBUG
=2, showing wrong but repeatable outputScreenshots
No response
I have checked existing issues, dicussion and documentation