![stm32 cdc driver windows 10 stm32 cdc driver windows 10](https://i.stack.imgur.com/KArGt.png)
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. I use CubeMX to generate the code, in which the only thing I have changed is the device descriptor, although Windows still usesĭoes anybody have an idea of where to start tracking down the problem? Thank you! This makes me think it is something on the MCU USB stack where it retains information between soft resets, but I don't know how the stack works at all. It will stop working if I do a hard reset and cut power. The interesting thing I discovered is that if I plug the usb cable into the Mac or Win10 machine first and then plug it into the Win7 or 8.1 machine, I can connect to it! And it will still works after I do a soft reset. Both machines have the latest v1.5 VCP drivers from STM installed.
![stm32 cdc driver windows 10 stm32 cdc driver windows 10](https://www.keil.com/pack/doc/mw/USB/html/usbh_cust_pl2303_example_setup.png)
![stm32 cdc driver windows 10 stm32 cdc driver windows 10](https://i.imgur.com/bX83JnB.jpg)
Unable to configure serial port.'įor Windows 7 & 8.1, the device manager has the MCU listed as STMicroelectronics Virtual COM Port. For instance Putty says 'Unable to open connection to COM6. When I attempt to do the same with a Windows 7 or 8.1 machine, the COM port does not open. When I connect it to a Windows 10 or MacOS machine, I can open a terminal program and communicate with the MCU just fine. The MCU is self powered with VBus sensing. I have an embedded STM32F732 using USB FS CDC for communication. I have strange problem on my hand which I can't figure out if it is a Windows driver or USB stack issue.