-
Notifications
You must be signed in to change notification settings - Fork 343
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
Virtual Com port fail. This device cannot start. (Code 10) #52
Comments
@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. Here is the usbip.exe log file: 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. |
Please try more recent one. I just have upload new binary release. Please check..
In this case, debug_pdu.log does not say useful things. Can you share windows kernel log?
Driver signing is explained in README and many stories will be found in comments of closed issues. |
I installed new release 0.0.6 version. The behavior the same. I got Code 10. Here is the Kernel log file: And usbip debug log file: |
@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. |
@cezuni : Here is my STMicroelectronics driver: 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: |
@cezuni : If need I can share full USBIP-Virtual-USB-Device project. |
@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. |
I was looking thought my Kernel log file and found next: Could it be the root of this issue? |
I don't think so. That warning is not important because next usb commands proceed successfully. |
@cezuni : Thank you for your help. I will try to fix cdc-acm file and respond to this issue. |
We have an OMRON PLC and getting same error code 10 This device cannot start 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 ? If needed we can give ssh root access to orangepi. 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. Thank you |
@halimselim : What version did you test with ? More detailed logs would be very helpful. Please check README to obtain logs. |
@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. |
Hi Guys. I am trying to emulate the STMicroelectronics Virtual Com Port via the usbip vhci.
As result I have net issue:
The USBIP/VHCI driver was installed properly:
Here is a log from the usbip.exe:
As a device that emulate device I use project https://github.com/lcgamboa/USBIP-Virtual-USB-Device. I run cdc-acm and get this:
Please help.
The text was updated successfully, but these errors were encountered: