STM32F417, Host MSC tuh_msc_read10 problem #1032
Replies: 2 comments 1 reply
-
|
Yes, there are other people with similar problems. Trouble is they are also at a loss as to how to solve the problem. I'm hitting the same issue on RP2040, although the cb is being called most of the time, it is definitely not being called about 1 in 7 calls, seems to be non-determinate and random. I'm trying to stitch together a working version from various forks - the host stack is heavily under development and getting a working set of files is a bit of a challenge right now. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I was able to solve it temporarily but later I had to switch onto other parts of our system. I will get back to USB in a couple of months. I remember that there where many problems with the callbacks not called properly and in order. Could be a design flaw or that the build system needs some tweaking. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We have an in-house platform with our own HAL and Synoptics USB driver for low level USB and HCD. I am integrating tinyusb and so far has been ok. I have integrated Chan's FatFS on top of tinyusb. At the moment I have not lifted the OS yet so I am running "bare metal".
Inquiry and finding the device seems fine and I have tested with a couple of different devices.
However, when reading from filesystem I am running into some issues in tuh_msc_read10. The callback does not executed which in turn means that data from device is not read before notification to stack.
Anyone with similar problem?
Best Regards
/s
Beta Was this translation helpful? Give feedback.
All reactions