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

Bridge data corruption #45

Closed
kevinmehall opened this issue Jun 17, 2015 · 2 comments
Closed

Bridge data corruption #45

kevinmehall opened this issue Jun 17, 2015 · 2 comments

Comments

@kevinmehall
Copy link
Member

Seems to happen with lots of small packets, and is commonly triggered with io.js versions that don't support cork on domain sockets (1.4 did support it, 2.0.2 does not).

Probably the SYNC handler takes too long and the firmware is not ready for the SPI transfer.

We need a tool to spam the ports with random echo commands, and a tool to watch the logic analyzer trace on a firmware patched to toggle a GPIO in the IRQ and watch for timing violations.

@rwaldron
Copy link
Contributor

@kevinmehall where does this stand? Is there a bug filed with io.js?

@kevinmehall
Copy link
Member Author

The original problem that made me suspect data corruption on split packets was actually a tessel.js issue and solved by #48. There are no known data corruption bugs in the bridge, but definitely could use more testing, so I am closing this issue in favor of #70.

cork is a performance optimization, but shouldn't be required for correctness. There was an io.js pull request, which I closed after they merged something equivalent. Then it got reverted because it broke something on Windows. I haven't followed progress on it recently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants