Skip to content
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

If there is no ongoing traffic, analyzer can retain buffered traffic until capture is stopped #137

Open
martinling opened this issue Jul 14, 2024 · 0 comments
Labels

Comments

@martinling
Copy link
Member

Due to the way that buffers are managed internally, the gateware will not respond to a poll from the host until it has 512 bytes of capture data ready, to fill a full DATA packet.

On an active high or full speed bus, this is guaranteed to happen regularly, due to the constant flow of SOF packets.

On a low speed bus however, there are no SOF packets, and the entire enumeration process may add up to less than 512 bytes of capture, meaning that no packets at all are seen in Packetry while the capture is ongoing.

Workaround: stop the capture to see the missing data. Buffers are flushed to the host when the capture is stopped.

Solution: we should be willing to send a short packet to the host if a full packet has not been achieved after some timeout.

@martinling martinling added the bug label Jul 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant