![]() We can share the signed driver with public. For example we have bought the usb token certificate from GlobalSign to sign the driver. If we could solve this problem we will be happy to contribute to this project in some way. You may use this windows pc to compile and debug usbip code. 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). If needed we can give ssh root access to orangepi. Usbip.exe list -r 79.137.39.83 (This is an orangepi linux server, usb bus id 7-1 is binded) Other basic usb devices(usb drive,barcode scanner, serial converter) also work without problem through usbip.Ĭould you please check and confirm you get the same error ? When PLC connected directly to usb port(without usbip) it works well on win10 with the usb drivers ![]() => Please how can i handle to fix this issue! if there is a wrong value generated by CubeMX! or a change that should i do in my environement (PID, VID.We have an OMRON PLC and getting same error code 10 This device cannot start If you do all of that, the Windows 10 out-of-the-box VCP driver can be used. Since you do not return any values, the virtual com port remains as driver-not-loaded. #define USBD_INTERFACE_STRING_FS "CDC Interface" Without the point 3, Windows will send the baud rate information and then read the baud rate, expecting to get back the same values. Once that is done, and your board is connected in bootloader mode (by holding the boot button down) you should be able to select DFU within. Open Zadig, choose Options > List All Devices. #define USBD_CONFIGURATION_STRING_FS "CDC Config" Hold the Bootloader Button and connect the board to your PC via USB. #define USBD_PRODUCT_STRING_FS "STM32 Virtual ComPort" #define USBD_MANUFACTURER_STRING "STMicroelectronics" I thought that the probem is related to my USB converterĪctivate USB_Device middelware in CDC modeĬheck the CubeMX file attached for more detailsīut the problem still exist!=> VCP error ''This device cannot start(code 10)''.Īnd here is the define in "usbd_desc.c" file ![]() In the first case, i tried to configure UART but when i connect my USB TTL converter to my PC: it informs me that VCP error ''This device cannot start(code 10)''. I want to handle STM32F407 Disco via VCP. It seems Windows 10 is more fussy or requires more information ?Īnyone have any further information to share ? If it's not a bug in the Windows driver, then I'm guessing it might be either a setting in the USB device descriptors or configuration, or a bug in the USB stack on the STM32. I'm thinking it must be something to do with the device capabilities (what Windows thinks the capabilities of the com port is, and what Windows thinks I am allowed or not allowed to set). I've looked at all the values set in the `DCB` structure and they all look ok. ![]() The error code is `87` which is an INVALID PARAMETER. I connects and enumerates on Win7, Win 10 and Mac, but only Win7 and Mac can open the device as a serial port (COM port).ĭebugging this I found that the low level windows API to `SetCommState()` was returning `false` on Windows 10 (it must return True on Windows 7 as it opens the port ok). A proprietary STM32F4 board using onbard USB.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |