Hi,
last few days ago I ordered ST-Link v3 and I found that after upgrading its firmware to double-VCP version ST Cube Programmer does not recognize it anymore. Everything is up to date, drivers, ST Cube software, ST-Link firmware... After reverse programming (to Debug + Mass Storage + VCP + Bridge) everything gets back to normal.
If ST-Link is programmed as single VCP version it appears in system as USB Debug and USB Bridge with VID 0483 and PID 774F. PID for double VCP version differs and is equal 3573.
Of course 2 COM ports appear when ST-link is programmed as double VCP, but they cannot "talk" to each other, just like they are multiplexed or something like that...
There are few screenshots attached taken while "reverse programming" to point out what's my problem.
I'd be grateful if someone tries to reproduce this strange behavior of double VCP "version".
Regards
Piotr
