Hi all, Hi Xiaofan , I've had problems with my netbook and finally I reinstalled XP . I've downloaded once more openocd 0.4.0 for windows and extracted it .
You are talking in of of your answers of Inf directory in openocd directory, which I don't find, are you talking about the drivers directory ? Anway searching for inf pattern in the openocd directory resulted in no file found . I guess you were talking about the inf directory of libusb-win32-device-bin.1.1.14.3 which contains the inf wizard . I've downloaded libusb-win32-device-bin-1.1.14.3 on sourceforge and extracted it besides openocd directory in My documents\Download directory . I got into the directory containing the inf wizard and executed it . An inf file has been created , in that directory , and meanwhile, as I had to plug in the jtagkey-tiny to create the inf file, a driver installation assistant popped up . I chose "Don't search for a driver, I will chose it manually" ( translation from french ) and I had then to choose in a list of type of devices , I chose Usb controller and the answer was that non suitable driver was found . I have then been asked to set a directory where the "Disk " is . I guess this is useful if the drivers were stored in a disk . Anyway, I entered the directory which contains the inf file . The answer of the system is that the specified directory doesn't contain any information concerning your device . Is there a way to check that the device is functional ? It is new actually . Thanks for your help, Cédric C'est au pied du mur qu'on voit mieux le mur --- En date de : Lun 28.6.10, [email protected] <[email protected]> a écrit : De: [email protected] <[email protected]> Objet: Openocd-development Digest, Vol 45, Issue 44 À: [email protected] Date: Lundi 28 juin 2010, 12h00 Send Openocd-development mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.berlios.de/mailman/listinfo/openocd-development or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Openocd-development digest..." Today's Topics: 1. Re: unable to find device ( jtagkey-tiny using openocd 0.4.0 under XP ) (cedric libre) 2. Re: unable to find device ( jtagkey-tiny using openocd 0.4.0 under XP ) (Xiaofan Chen) ---------------------------------------------------------------------- Message: 1 Date: Sun, 27 Jun 2010 03:06:57 -0700 (PDT) From: cedric libre <[email protected]> To: Xiaofan Chen <[email protected]> Cc: Openocd-Dev <[email protected]> Subject: Re: [Openocd-development] unable to find device ( jtagkey-tiny using openocd 0.4.0 under XP ) Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" Hi, ?I am a windows newbie, so thank you very much for your patience ?and kindness Xiaofan . ?Unfortunately, I don't understand things in the second :-) . ?I deinstalled the amontec drivers from the device manager menu and even the devices . I've also deleted the ftd2XX.sys file from the ?WINDOWS tree . ?I plugged the programmer off, and a little later plugged it on . ?I selected the manual selection , but at the bottom of the first window ?that appears after having chosen to do a manual installation , appears a yellow exclamation mark signal stating : " This driver has not been digitally signed " even before that I tell the path to the driver ?I'd like to install . Seems windows is hooked up to the amontec jtag driver that I installed first and that even before deinstallation of it, it is still there somewhere on the computer . ?In this dialog if I click on Next, the installer tries to install the amontec ?drivers without asking for it , but I guess it as it asks for the ftd2XX file that I deleted, and otherwise if I click on Provided Disk , I can tell the directory that contains the .inf file previously created , but finally the installer answers that the directory specified doesn't contain any information relevant for the device . ?What should I do ? ?Thanks in advance for your precious help, ?C?dric ? --- En date de?: Dim 27.6.10, Xiaofan Chen <[email protected]> a ?crit?: De: Xiaofan Chen <[email protected]> Objet: Re: [Openocd-development] unable to find device ( jtagkey-tiny using openocd 0.4.0 under XP ) ?: "cedric libre" <[email protected]> Cc: "Openocd-Dev" <[email protected]> Date: Dimanche 27 juin 2010, 1h48 Please use "Reply All". On Sat, Jun 26, 2010 at 11:00 PM, cedric libre <[email protected]> wrote: > > I used the installer, anyway ftdi.dll and libusb0.dll were not present in > ?WINDOWS/system32 directory . > ?I copied both dlls inside WINDOWS/system32? but I still get the same error > message : > > ?Error : unable to open ftdi device : device not found . > > ?Was it a mistake to install amontec drivers ? As I mentioned before, >> It clearly says that "this version was compiled to use libftdi? + >> libusb-win32 libraries". But you just do not believe me... You can not use the Amontec drivers (ftd2xx) with the binary which is using libftdi. You need to install the libusb-win32 driver. Freddie provided the inf file to do that. It is inside the Zip file. libusb-win32_ft2232_driver-100223 ********** info.txt ***************** WHY LIBUSB-WIN32 DRIVERS? _________________________ Since June/July of 2009 due to alleged GPL license violation OpenOCD cannot be distributed with support for ftd2xx.dll library. That's why FT2232 JTAGs have to be used via libusb-win32 drivers, and OpenOCD will be linked with libftdi library. Because of that OpenOCD users have to use different JTAG drivers. This small document provides a basic "how to" of libusb-win32 drivers for FT2232 based JTAGs. Users who need OpenOCD linked with ftd2xx.dll can build the software from sources. DEVICES SUPPORTED BY THIS DRIVER PACKAGE ________________________________________ The .inf file provided with the driver in that package has entries for most of existing FT2232 JTAGs. These devices are: ??? - Amontec JTAGkey ? ? ? ? ... DRIVER INSTALLATION ___________________ If there were FTDI drivers installed in the system, they have to be manually removed (via system's Device Manager) and then libusb-win32 drivers have to be installed manually. In case of "JTAG + UART/RS-232" devices only the driver for the JTAG channel needs to be removed. In case of "JTAG-only" devices the driver for the second (unused) channel also can (but doesn't have to) be replaced. Uninstallation of ftd2xx.dll driver: When the device is plugged, open the Device Manager (Control Panel > System > Hardware > Device Manager), right click on the JTAG device (in "Universal Serial Bus controllers" group) and Uninstall it. Now unplug the JTAG and wait a few moments. Installation of libusb-win32 driver: Plug the device to the USB port of your PC. The system should discover a new device and the installation wizard should be started. Don't use automatic methods (as this will probably install the drivers you just removed) - use "Don't search. I will choose the driver to install" (fully manual mode) instead. Succesfully installed driver(s) will be displayed in the "LibUSB-Win32 Devices" group in the Device Manager. ... *************************************** -- Xiaofan http://mcuee.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.berlios.de/pipermail/openocd-development/attachments/20100627/0d168346/attachment-0001.html> ------------------------------ Message: 2 Date: Mon, 28 Jun 2010 07:34:30 +0800 From: Xiaofan Chen <[email protected]> To: cedric libre <[email protected]> Cc: Openocd-Dev <[email protected]> Subject: Re: [Openocd-development] unable to find device ( jtagkey-tiny using openocd 0.4.0 under XP ) Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 On Sun, Jun 27, 2010 at 6:06 PM, cedric libre <[email protected]> wrote: > ?I deinstalled the amontec drivers from the device manager > menu and even the devices . I've also deleted the ftd2XX.sys file from the > ?WINDOWS tree . > ?I plugged the programmer off, and a little later plugged it on . > Ok, maybe this is easier for you. Reinstall the Amontec driver. Then locate the device in Device Manager, choose to "update the driver", manually point it to the INF directory of OpneOCD. You should be ok then. The device may be listed in two places since it is a USB composite device (Channel A and Channel B), so you may need to do this twice. If Channel B is using VCP driver, then you should only do the "update driver" thingy for Channel A. -- Xiaofan http://sourceforge.net/projects/libusb-win32/ ------------------------------ _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development End of Openocd-development Digest, Vol 45, Issue 44 ***************************************************
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
