-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GD32VF103 issue with MSC #1022
Comments
Hi @hathach out of curiosity I ran the MSC demo again with the latest changes to master and...
It works now! 🎉 I haven't investigated what commit fixed the issue but I'm super exited about it and will start to port TinyUF2. Which already enumerates successfully, now on to the flashing part. |
This works with the new |
@KarlK90 great to hear that works, actually I did test it out with gd32 when doing new dwc2 driver. The msc drive does show up, so thing is definitely improved. However, there is still issue here and there. It may not work as well as other ports and I haven't got time to look further at this port. Let me know if you see any issue with gd32 |
Operating System
Linux
Board
Sipeed Longan Nano
Firmware
examples/device/cdc_msc
What happened ?
Follow up to @KarlK90 's #959 PR:
The cdc_msc example have the cdc echo fine, however, the msc does not, I hook it into analyzer. Look like there is some issue when host read 4k of data. Notice that the data is corrupted with 0x55AA repeatedly somehow. Host give up and decide device isn't properly formatted. It is probably buffer/endpoints config/overflow issue etc .. which is typical for a new port based on existing dcd driver. I will spend sometime this week (or so) to poke at GDVF103 manual to see if I could spot any issue. Hopefully it would be only an minor change.
Originally posted by @hathach in #959 (comment)
How to reproduce ?
Debug Log
Log is attached, though it doesn't show any abnormal, since the issue is caused by the corrupted buffer/payload of READ10.
1022.txt
Screenshots
The text was updated successfully, but these errors were encountered: