You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently spent time reverse engineering the USB protocol for some test equipment so I could control it via Linux.
The protocol in question has the host send a command word through a bulk endpoint, then the host sends a zero length packet through the same endpoint so the device knows to begin processing what is in the buffer.
After emulating the protocol above in PyUSB the device would work in Windows while overwriting the libusb driver, and it would work in native Linux, but it would not work in Windows using USB passthrough to WSL2.
I used Wireshark to analyze the USB packets and noticed that the zero length packets were being dropped when the device was being forwarded to WSL2.
I am not certain it is a usbipd issue, but it seems plausible.
The text was updated successfully, but these errors were encountered:
I recently spent time reverse engineering the USB protocol for some test equipment so I could control it via Linux.
The protocol in question has the host send a command word through a bulk endpoint, then the host sends a zero length packet through the same endpoint so the device knows to begin processing what is in the buffer.
After emulating the protocol above in PyUSB the device would work in Windows while overwriting the libusb driver, and it would work in native Linux, but it would not work in Windows using USB passthrough to WSL2.
I used Wireshark to analyze the USB packets and noticed that the zero length packets were being dropped when the device was being forwarded to WSL2.
I am not certain it is a usbipd issue, but it seems plausible.
The text was updated successfully, but these errors were encountered: