-
Notifications
You must be signed in to change notification settings - Fork 27
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
packetry --test-cynthion option (Windows) panics running Low-speed test #139
Comments
Noticed in the Cynthion Discord forum that @mossmann had seen what looks like a similar issue with the Apollo device. |
Thanks for the update. The driver selection is supposed to happen automatically, and it uses the same WCID descriptors for low speed as it does at the other speeds, so I'm not sure yet what's going wrong there in the low speed case. It seems like it must be at least partially system-specific, as I didn't see this happen on my own Windows 10 test system. We'll need to see if we can reproduce this, after clearing out cached descriptor info. Good to know you found a workaround though. |
I've been able to reproduce this now. |
The panic is fixed in #164. The cause of the test failure was not being able to open the test device. This was due to the low speed version of the test device not being assigned the WinUSB driver. That issue needs to be solved on the gateware side, and is now tracked here: greatscottgadgets/cynthion#168. |
The --test-cynthion option of packetry for Windows completes the High-speed and Full-speed tests but panics during the Low-speed test with the following output to the console:
Testing at Low (1.5Mbps):
Opening analyzer device
Disabling test device
Enabling test device
Capture enabled, speed: Low (1.5Mbps)
thread 'thread '' panicked at mainsrc\test_cynthion.rs' panicked at :src\test_cynthion.rs66::2763::
64called Result::unwrap() on an Err value: Failure in capture thread
Caused by:
0: Sender was dropped
1: oneshot canceled:
called Result::unwrap() on an Err value: Test device not foundnote: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: process didn't exit successfully: target\debug\packetry.exe --test-cynthion (exit code: 101)
(The version of packetry being used has been 'enhanced' to allow options when running from the Windows CLI)
Two USB Analyzer devices can be seen in Device Manager under 'Universal Serial Bus devices'; during the High-speed and Full-speed tests a USB Analyzer Test Device is also seen there. During the Low-speed test a USB Analyzer Test Device is seen under 'Other devices' showing that no compatible driver is available:
The text was updated successfully, but these errors were encountered: