2009-09-13 09:26 PM
USB VCOM CDC support in VISTA
2011-05-17 03:51 AM
I have a problem getting my ST CDC drivers working in the vista world. I get enumeration on XP and every thing works ok. But I try to switch to Vista Home Premium (32-bit OS) and I get an error code 10 when I look at the device in the hardware device manager. So the port will not work. What can be done?
Kelly2011-05-17 03:51 AM
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=1272951&SiteID=1
Cheers, STOne-32.2011-05-17 03:51 AM
Interesting link STOne-32.
Seems a fix may be possible by modifying the inf file. The CDC driver for STM32 gets installed by running ''VCPDriver_V1.1_Setup.exe'' which is downloaded from this site. The big question is what exactly is this exe doing? Is it just installing the inf file? If so can the inf file be made available separately so that we can edit it in order to try above mentioned fixes and also so that the id strings can be modified to suit out product names? I have asked this question before without a response. Could someone at ST please comment on this? Thanks Trevor2011-05-17 03:52 AM
From what I have observed, The executable provided by ST puts an INF file into the WINDOWS/INF (hidden on XP SP3) directory. But this INF doesn't do the job. I have edited it to match others of its kind that use usbser.sys as the root driver. The problem is that Vista's usbser.sys is not ENOUGH or not working with it. I have looked at the supposed Microchip working example. It also fails on Vista. So I am of the opinion that ST needs to revamp their Driver/USB VCOM example. Also, it appears that VISTA X64 will only take SIGNED kernal level drivers. (that was taken from the post from STOne-32) So if CDC is still going to be viable in 10 years, we are going to need more support.
2011-05-17 03:52 AM
I've just tried mine on Vista Home Premium (auto updates enabled) and it works. Up to now I've been using XP.
However, my customer's engineers report that it works very intermitantly (much less than 50% of the time) for them. They are using Windows XP. I cannot recreate this intermitnt behaviour which is very frustrating. When it does not work for them a virtual com port is not created on Windows. Could it be something to do with how the driver was installed i.e. not cancelling the ''found new hardware'' wizard when prompted? Anyone got any ideas? Regards Trevor2011-05-17 03:52 AM
Is there an Update? I use Windows 7 (7100) and the Problem is the same as under Windows VISTA.
Philipp