Hello everyone,
we're using a NXP LPC2368 in a project, that includes connection to a PC via USB (virtual serial connection). When connecting the LPC2368 to a WindowsXP-PC for the first time, a hardware configuration assistent starts. Following this assistent, the user must specify the path to the file 'mcb2300-vcom.inf' that is originally provided with the uVision IDE. This file contains information for installing the correct usb driver for the virtual serial connection. WindowsXP uses a generic driver file 'usbser.sys' to make the USB connection to the LPC2368 work. As we know now, the usbser.sys should have a newer version number, for example 5.1.2600.xxxx. A stable working version of the file is provided by ServicePack3 for WindowsXP.
Here's the problem: On MANY WindowsXP-PCs the hardware configuration manager fails and its not possible to establish the virtual serieal connection. But all the PCs have ServicePack3 installed and consequently an actual version of the usbser.sys generic driver file. We suppose that there's a problem with various usb host controllers used on mainboards, but we can't dictate our customers to use a special hardware in their PCs.
Is it possible that some usb host controllers on mainboards cannot work with LPC2368 in vCOM-Mode? Has anyone ideas to definitely locate and maybe solve the problem? We can't test hundreds of different hardware configurations in PCs...
I'm looking forward to your answers...