-
Notifications
You must be signed in to change notification settings - Fork 3k
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
disco f769: USB mass storage device is broken #15129
Comments
I found something that seems to work:
It looks like the HS OTG code is setting up a max packet size of 512 while this code expects 64. Edit: The max packet size for EP0 might be unneccesary, not sure. |
I'm not sure about the right way to actually update this since changing the packet size to 512 like this will break it on platforms that have a max size of 64. |
We should create something like: |
we don't support high speed, it would require more work as I was told.
|
I'm not sure what's happening here then. The setup on this board is
using high speed, and it seems to work fine?
…On Wed, Oct 06, 2021 at 08:17:06AM -0700, Martin Kojtal wrote:
we don't support high speed, it would require more work as I was told.
> All Host Controllers are required to have support for 8-, 16-, 32-, and 64-byte maximum packet sizes for
full-speed bulk endpoints and 512 bytes for high-speed bulk endpoints. No Host Controller is required to
support larger or smaller maximum packet sizes.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#15129 (comment)
|
@facchinm do you have any tip ? |
Our lite-fork of USBMSD library supports both, probably a similar patch could work for mainline too |
and you don't need patches like 7 comments above ? |
Yes, the link was just the tip of the iceberg 🙂 The define is then applied throughout all the other files |
So @facchinm has already come to the proper solution by conditionally setting MSD_MAX_PACKET_SIZE ? If that seems like a decent enough solution (and it does actually fix things), I'll be happy to do a PR for it. |
Maybe you can start with this kind of patch ? |
As it's been almost a year without any update, I'll close this as won't fix. |
Description of defect
Using the USB mass storage device example does not work.
Reading data fails and causes Linux to reset loop the device hoping it will work.
Target(s) affected by this defect ?
DISCO_F769NI
Toolchain(s) (name and version) displaying this defect ?
GCC_ARM
What version of Mbed-os are you using (tag or sha) ?
9dd6fb4 with #15128 applied.
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed-cli 1.10.5
gcc 11.2.0
Linux 5.14.6
How is this defect reproduced ?
Build and run the USB mass storage example.
Wireshark supports looking at Linux USB data, which roughly shows this:
The text was updated successfully, but these errors were encountered: