I've been having issues getting any serial communications to work when exporting a CDC class USB device (from a raspberry pi based industrial HMI).
The device seems to appear in Windows, but I have no serial data transferred. Wireshark does show usbip protocol data being exchanged (just short / empty URBs I think).
I double checked that using usbip on a Linux box, I can successfully transfer serial data to the device.
The endpoint device is our own hardware, based on an Atmel SAM4S processor, using the Atmel CDC driver. (So it's not necessarily bug free from experience with their early USB support code).
Currently using the latest release version of usbip-win2. Will try to see if the WDM driver works or not, as I've got a feeling one of the other older usbip projects did previously connect with these boards.
Any known issues that might affect a CDC class serial interface with the current usbip-win2 driver?
Any suggestions what debug steps to take to help identify the issue.
pcjc2
commented
8 months ago
I've been having issues getting any serial communications to work when exporting a CDC class USB device (from a raspberry pi based industrial HMI).
The device seems to appear in Windows, but I have no serial data transferred. Wireshark does show usbip protocol data being exchanged (just short / empty URBs I think).
I double checked that using usbip on a Linux box, I can successfully transfer serial data to the device.
The endpoint device is our own hardware, based on an Atmel SAM4S processor, using the Atmel CDC driver. (So it's not necessarily bug free from experience with their early USB support code).
Currently using the latest release version of usbip-win2. Will try to see if the WDM driver works or not, as I've got a feeling one of the other older usbip projects did previously connect with these boards.
Any known issues that might affect a CDC class serial interface with the current usbip-win2 driver?
Any suggestions what debug steps to take to help identify the issue.
Peter