Replies: 1 comment
-
I forgot to ask the main question: How is TinyUSB handling this case? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I am trying to use the STM32 usb functions and I figured out that if the host sends information fragmented in 2 packets of 64 bytes (let's say the first 3 bytes of one complete piece of data that is supposed to be 8 bytes is sent with packet 1 and the other 5 are being sent with packet 2, first 3 bytes are at data_1[61 to 63] and the other 5 bytes are at data_2[0 to 4]. Any idea how I can handle this using report id's and their known size?
This is my bit of code where I read that buffer and that is faulty because I only read the first byte and the other information that is written after that is lost and if everything doesn't line up perfectly when reading again, everything crashes down:
Beta Was this translation helpful? Give feedback.
All reactions