Open HirokiIshiguro opened 5 years ago
This may be because the receiving task processes only one packet per notification.
If two or more packets are received before the interrupt handler is activated and notified to the receiving task, the second and subsequent packets are delayed without being processed until the next notification occurs because receiving task processes only one packets .
Thanks a lot. I will fix it.
Describe the bug If user would set descriptor num to 2 or more, receive process would be corrupted. If user would set descriptor num to 1, receive process would not be corrupted. This is just reported, SheltyDog has not understood this mechanism.
Expected behavior No corrupting.
Screenshots or console output None.
To reproduce
Code to reproduce the bug
Additional context None.