Hello Freddie, what is the md5sum from your libusb0.sys file under:
\windows\system32\drivers The original file from the binary distribution libusb-win32-device-bin-0.1.12.1 is: 34d6730e198a5b0fce0790a6b4769ef2 *libusb0.sys Regards, Michael -----Ursprungliche Nachricht----- Von: openocd-development-boun...@lists.berlios.de [mailto:openocd-development-boun...@lists.berlios.de]im Auftrag von Freddie Chopin Gesendet: Sonntag, 21. Juni 2009 17:26 An: openocd-development Betreff: Re: [Openocd-development] Universal ft2232 .inf file forwindows/libusb-win32 Xiaofan Chen pisze: > Have you tried this with all of the three JTAG tools? Nope [; I only have JTAGkey here, but the only difference visible to drivers is the VID/PID combination [; > It seems to me that you are using libusb-win32 with individual > interfaces and I am not sure that would work. It works for me - I can install the drivers and OpenOCD compiled with libftdi support is able to communicate with the core. > Do you used the hacked libusb0.sys? Currently no, but I was using that a while ago, so I'm not sure whether it's not loaded in the RAM or something. I can upload openocd executable with libftdi support somewhere and post a download link for others to test. 4\/3!! _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
