USB VCP Windows 10

[Konmax]

Posted on August 08, 2017 at 14:36

Hi,

The problem is when using USB VCP under Windows 10 on the Nucleo f746 board. The COM port is not open. When connecting to Windows 7 COM port opens.

I tried to board Nucleo l432. Works under Windows 7 and Windows 10.

[GCovo]

Hello CanhNguyen,

Same situation here, but I found another source of variability.

The VCP only works if I use the Windows API directly (C++ program)

So the Teraterm terminal works, but the dotnet based YAT terminal dont.

I hope this can help ST engineers to fix it.

[Jacek.Main]

Hi,

I also encountered this problem today - couldn't open the port in putty, got the "unable to configure the port" error too.

In my case, I had to uninstall the device driver (in device manager, uninstall device & remove installed driver).

Unplugged and plugged again and it installed some generic driver and it works - it had stm32 driver before.

[David.Cheng]

have same problem

[AArt]

I had the same problem with my custom board with f405 MCU. The VCP was detected by win10, and drivers was ok. 

More than that, i was able to open COM port with Termite terminal. But my host app (based on .net) could`t open it. 

Same thing was with Qt based host app (unsupported operation error was appeared).

Fix with GET and SET line coding from Ant M helped. 

Thanks!

[JLojo]

I got the same kind of problem when migrating from Workbench to CubeIDE:

• project compiled under workbench: everything worked fine
• project compiled under CubeIDE: error 87 when trying to set the baudrate on a Windows machine.

I already had memcpy(&dwDTERate,&pbuf[0],4); in CDC_SET_LINE_CODING case, which was enough under workbench.

In order to get the same project working on CubeIDE, it has been necessary to change the definition of dwDTERate from uint32_t to uint_64t, changed the size of the memcpy from 4 to 7, and added memcpy(&pbuf[0],&dwDTERate,7); back in CDC_GET_LINE_CODING case

Thanks for the discussion who helped me focus on where the problem was...

JYL