On Tue, Apr 13, 2010 at 6:54 AM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Tue, Apr 13, 2010 at 6:00 AM, Kedar Sovani <ked...@marvell.com> wrote: >> I read in this thread you mention that there is some solution for >> openocd-vcp conflict resolution on Windows as well. >> >> http://www.mail-archive.com/openocd-development@lists.berlios.de/msg06107.html >> >> I tried searching for the solution but couldn't find one. Could you >> kindly point me to the right solution for the same? > > Please use the mailing list (in the CC) > I am not sure what you mean by VCP conflict? You can use the > libusb-win32 device driver for Interface A to use OpenOCD/libftdi. > Then you can use the VCP driver for Interface B to use the virtual > com port.
Or if you build your own binary which is linked to the proprietary d2xx driver/dll , then you do not need to mess with the inf file and can just use the vendor provided driver (typically modified from the official FTDI unified driver). You can follow the instructions here. http://forum.sparkfun.com/viewtopic.php?f=18&t=11221 -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
