Virtual Com port fail. This device cannot start. (Code 10) about usbip-win

[cezuni]

@MarkOstis : What version did you test ? More detailed logs are required to resolve the issue. Please read the tail part of README.md. I have just added the information about how to generate usbip-win logs.

[MarkOstis]

@MarkOstis : What version did you test ? More detailed logs are required to resolve the issue. Please read the tail part of README.md. I have just added the information about how to generate usbip-win logs.

I am using commit 59c0929.
OS: Windows 10 Version 1809 (OS Build 17763.557)
The project was built with the VS 2017 (v141), Windows SDK Version: 10.0.17763.0.

Here is the usbip.exe log file:
debug_pdu.log

Note, I also tried to emulate hid-mouse and hid-keyboard devices. The device attached/detached successfully without errors.

One more thing, I was not able to sign USB/IP VHCI driver. To be able to install the driver I temporary disabled the driver signature checks in Windows 10.

[cezuni]

I am using commit 59c0929.

Please try more recent one. I just have upload new binary release. Please check..

debug_pdu.log

In this case, debug_pdu.log does not say useful things. Can you share windows kernel log?

One more thing, I was not able to sign USB/IP VHCI driver. To be able to install the driver I temporary disabled the driver signature checks in Windows 10.

Driver signing is explained in README and many stories will be found in comments of closed issues.

[MarkOstis]

I installed new release 0.0.6 version. The behavior the same. I got Code 10.

Here is the Kernel log file:
KernelLog_StartEmulate.LOG

And usbip debug log file:
debug_pdu.log

[cezuni]

@MarkOstis : Can you share STMicroelectronics drivers? I tried to reproduce your case but my result logs are different from yours. Maybe STMicroelectronics driver must seem to be installed.

[MarkOstis]

@cezuni : Here is my STMicroelectronics driver:
stm32_vcp_driver.zip

As I mentioned before, I use USBIP-Virtual-USB-Device and try to emulate cdc-acm.c device. It seems like it is a Virtual comport. I rewrote the cdc-acm.c file to emulate STMicroelectronics Virtual com port. Here is my version of USBIP-Virtual-USB-Device cdc-acm.c file:
cdc-acm.txt

[MarkOstis]

@cezuni : If need I can share full USBIP-Virtual-USB-Device project.

[cezuni]

@MarkOstis : I have same results with you after installing STMicroelectronics driver and replacing with your cdc-acm.c. Sadly, there's no faulty log about usbip-win.
In my opinion, the reason why STMicroelectronics device goes into wrong state is that STMicroelectronics driver have removed the device. (guessed from IRP_MN_REMOVE_DEVICE in kernel logs) VHCI seems to be not guilty. :) I recommend you to check cdc-acm.c source.

[MarkOstis]

I was looking thought my Kernel log file and found next:
00000141 0.06881560 usbip_vhci: vhci_internal_ioctl: Leave: STATUS_INVALID_PARAMETER

Could it be the root of this issue?

[cezuni]

I was looking thought my Kernel log file and found next:
00000141 0.06881560 usbip_vhci: vhci_internal_ioctl: Leave: STATUS_INVALID_PARAMETER

Could it be the root of this issue?

I don't think so. That warning is not important because next usb commands proceed successfully.

[MarkOstis]

@cezuni : Thank you for your help. I will try to fix cdc-acm file and respond to this issue.

[halimselim]

We have an OMRON PLC and getting same error code 10 This device cannot start
When PLC connected directly to usb port(without usbip) it works well on win10 with the usb drivers

Other basic usb devices(usb drive,barcode scanner, serial converter) also work without problem through usbip.

Could you please check and confirm you get the same error ?
usbip.exe list -r 79.137.39.83 (This is an orangepi linux server, usb bus id 7-1 is binded)

If needed we can give ssh root access to orangepi.
We can also pepare a test environment with a virtual windows pc directly connected to omron plc through usb.(to show it is working well without usbip). You may use this windows pc to compile and debug usbip code.

We are a new startup based in Turkey. If we could solve this problem we will be happy to contribute to this project in some way. For example we have bought the usb token certificate from GlobalSign to sign the driver. We can share the signed driver with public. So people don't need to do bcdedit etc.
Could this be harmful to us ? What is your opinion?

Thank you

[cezuni]

@halimselim : What version did you test with ? More detailed logs would be very helpful. Please check README to obtain logs.

[cezuni]

@halimselim : It would be more desirable that your issue is discussed in other page even though plc failed similar to this issue. I'll create a new issue for your case.