Xiaofan Chen wrote: > On Fri, Jun 19, 2009 at 7:27 AM, Gene Smith<g...@chartertn.net> wrote: >> I already have libusb working fine on windows with jlink. Now I am >> trying to add libftdi. I have built and installed enough of libftdi to >> enable a build of openocd with --enable-ft2232_libftdi. And I installed >> the new libusb0.sys described above. > > How do you install the modified libusb0.sys? That may be > critical. Your need to check that you are really using the > modified libusb0.sys in Device Manager.
The article said copy the file to windows/system32/drivers and plug/unplug devices and it should take effect. > >> When I plug in the USB from the olimex arm-usb-ocd, a driver >> installation dialog pops up (which I have so far ignored) and I see the >> "Olimex OpenOCD JTAG" device detected in device manager. Then when I run >> openocd I get the "device not found" message as Freddie originally >> described. Do I still need to install the proprietary driver from the >> olimex CD? I thought that installing libusb and libftdi on windows would >> be enough. Well, I went ahead and installed the stuff from the cd. Now I see in device mgr that my driver is windows/system32/drivers/ftdibus.sys instead of libusb0.sys > > That should be enough. In fact, I kind of believe that you do not > need to use the modified libusb0.sys but rather a proper inf file > generated by the INF wizard for the whole device. > I used the wizard to generate and install the inf. But it was for jlink when I did it several days ago. Maybe I need to redo this procedure for the ftdi olimex device. I will uninstall the olimex driver and try the procedure again. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
