On Sat, Jul 31, 2010 at 5:11 PM,  <olof.tang...@telia.com> wrote:

> When I plug in the JTAG interface it is recoginized as 2 instances of
> LibUSB-Win32 Devices in the device mangager. The drivers are working
> properly according to the dialog boxes. The
> LED on the USB interface is not lit however. The LPC-H2148 is powered
> from its USB interface and is recognized
> as a CDC ACM port.
>
> I then try to run OpenOCD the following happens:
>
> Error: couldn't read enough bytes from FT2232 device (0 < 81)
> Error: couldn't read from FT2232
> Error: couldn't read enough bytes from FT2232 device (0 < 81)
> Error: couldn't read from FT2232
> Command handler execution failed
> Warn : jtag initialization failed; try 'jtag init' again.

>From what I read in the libftdi mailing list this is a problem with libftdi.

First solution, you may want to try out libftdi-0.18, You need to replace
the libftdi-0.17 dll inside Freddie's package
(C:\Program Files\OpenOCD\0.4.0\libftdi.dll)
with the 0.18 dll. I have the 0.18 binary download here (for 32bit
Windows). I am not so positive if this helps, but no harm trying.
http://picusb.googlecode.com/files/libftdi-0.18_mingw32.zip

Second solution, switching to libftdi-1.0 will probably solve
the problem.

To use libftdi-1.0 with OpenOCD, you need to do two things.
1) Switch the driver to WinUSB, you can do that easily with
Zadig and libusb-1.0 Windows binary snapshots.
http://www.libusb.org/wiki/windows_backend
http://libusb-winusb-wip.googlecode.com/files/zadig.exe
http://libusb-winusb-wip.googlecode.com/files/libusb_2010.07.31.7z

2) Get libftdi-1.0 binary from here.
http://picusb.googlecode.com/files/libftdi1_05July2010.zip
Replace libftdi.dll with the dll inside the above zip file.
Replace libusb0.dll from Freddie's package with the libusb-1.0.dll
inside the  libusb_2010.07.31.7z package.



-- 
Xiaofan
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to