Closed kumekay closed 4 years ago
I finally managed to make cp210x work by manually selecting USP/IP STUB driver for the device, though it's behavior is not always correct when I try to attach a different cp210x device, bind command reports success, but then attach in linux fails ( in device manager device is listed as serial adapter, but not usd-ip stub)
@kumekay :
This error means that you did not copy usbip_stub.inx into a working directory. Well, usbip.exe error message should be more friendly.
usbip: error: calc_hash: path not found: C:\Users\serge\AppData\Local\Temp\stuD670.tmp\usbip_stub.inf
usbip: error: failed to update driver: 2
usbip: error: bind_device: error binding device on busid 1-185: err: 0
I remembered that there's no case of cp210x on stub. cp210x on vhci seems to work. (refer #144) I have no cp210x device. So, your windows kernel log is required to resolve your issue.
Ok, it doesn't seem to be a usbip-win issue, so close for now
I have a number of development boards that use cp120x usb-serial chips.
My intent is use Windows 10 host (2004) and WSL 2 (ubuntu 18.04).
I compiled WSL2 kernel with usbip support and required modules, downloaded build 0.10.0 of the tool and installed certificates as described in the readme. And most of my devices work just fine, for example ST-Link and Profilic based USB-UART boards, I mean they are binded successfully on windows and then attached in WSL 2.
However I experience difficulties with all mine CP120x based boards. I've tried to use another linux machine as a host and attach them in WSL2 - it also works fine, but using Windows as host I cannot bind them.
Example output:
I've tried to compile latest code from the git (commit 6d82d0a4f3bf28d2700e257ad0cd2aacc5b2fc89 ), but got a slightly different error:
@cezanne Do you know something special about these USB-UART bridges? And thank you so much for this wonderful tool!