Xiaofan Chen wrote, On 06/19/2009 07:35 PM: > Glad to hear that OpenOCD works with the libusb-win32/libftdi > combination. > > As for the com port, if it is part of the device, then using libusb-win32 > device driver (as the driver of the whole USB composite device) will > disable it. That is the side effect. > > http://article.gmane.org/gmane.comp.lib.libusb.devel.windows/2088 > "whole device? > You have to replace the 'composite device driver' by libusb's device driver. > It should work then. > See http://tinyurl.com/dxxnal for an architecture overview. > This method has one drawback though: your device doesn't work as a > mass-storage-device or printer any more since Windows will stop loading > the drivers." > > Stephan Meyer (author of libusb-win32) was answering > the question of how to use libusb-win32 with a usb composite > device (printer/mass storage/etc).
I notice that there is another "composite usb device" under usb devices in dev mgr. I also see it on the list when I run the inf wizard. I think you are saying I need to make another inf file for that device (with wizard) and replace its microsoft driver with the libusb driver for that device too. That will allow the serial port to work on the olimex (and the jtag functionality to continue). However, if I plug in, say, a usb memory stick or my usb camera (mass storage) or a printer it will not be seen since the driver is replaced by libusb. Am I anywhere close to understanding what this means? Losing the ability to have USB mass storage (or a printer) is kind of bad, if I understand what you are saying. I assume, also, that you don't have these limitations with the proprietary ftd2xx driver? _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
