Please use the mailing list. Thanks. You need to use
"Reply All".

On Mon, Jul 20, 2009 at 9:56 PM, Leonard Heins<[email protected]> wrote:
> Thanks. Installed it but sadly there is a problem, I guess because of
> the change of ftdi library and the libusb - I am using a JTAGkey from
> Amontec.
> The output on running is:
>
> Open On-Chip Debugger 0.2.0 (2009-07-18-09:50) Release
> $URL:
> http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openo
> cd.c $
> For bug reports, read
> http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
> jtag_nsrst_delay: 200
> jtag_ntrst_delay: 200
> Error: unable to open ftdi device: device not found
> Runtime error, file "command.c", line 469:
>
> The JTAGkey drivers are loaded and the device appears in device manager.
> Switching back to 0.1.0 works.
> Any ideas?
>
>

You have to use the libusb-win32 device driver instead of the original
driver. Freddie has already include the JTAGKey libusb-win32
device driver in the file
C:\Program Files\OpenOCD\0.2.0\drivers\ft2232.zip

-- 
Xiaofan http://mcuee.blogspot.com
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to