I get the same semi functional result as on Fedora 12 (same hardware)
before as shown below. I also observed that not using the '-c "jtag_khz
1000"' locks the (FT2232H ?) hardware somehow. After that my JTAG
interface won't respond the correct command line until it has been
disconnected and reinsterted. This happens both with Linux and
WindowsXP.
Result:
C:\Documents and Settings\olof\Desktop\openocd_04Aug2010_mingw32>bin
\openocd -f interface/olimex-arm-usb-tiny-h.cfg -f target\lpc2148.cfg -c
"jtag_khz 1000"
Open On-Chip Debugger 0.5.0-dev (2010-08-04-19:54)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
RCLK - adaptive
adapter_nsrst_delay: 200
jtag_ntrst_delay: 200
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
1000 kHz
Info : max TCK change to: 30000 kHz
Info : clock speed 1000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Command handler execution failed
in procedure 'transport'
Command handler execution failed
in procedure 'init'
On Wed, 2010-08-04 at 20:57 +0800, Xiaofan Chen wrote:
> On Mon, Aug 2, 2010 at 5:30 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> > On Mon, Aug 2, 2010 at 9:43 AM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> >> On Mon, Aug 2, 2010 at 4:17 AM, Olof Tångrot <olof.tang...@telia.com>
> >> wrote:
> >>> It also crashes with the replacement version libftdi that is linked to
> >>> libusb-1.0 discussed earlier.
> >>
> >> Hmm, I will try it out myself. I am not so sure if this has something
> >> to do with the version of the libusb-1.0 Windows backend snapshot
> >> version. There was a bug in the recent snapshot. Supposedly
> >> the latest snapshot will help. And this may also have something
> >> to do with the fact that libftdi-1.0 may not be 100% backward
> >> compatible with libftdi.
> >>
> >
> > You are right. The exe is not compatible with libftdi-1.0 and
> > libusb-1.0 Windows backend.
>
> Just in case you want to try out Windows as well, here is
> the Windows test binary with libftdi-1.0, it is a test binary
> with only ft2232-libftdi enabled.
>
> http://code.google.com/p/picusb/downloads/list
> http://picusb.googlecode.com/files/openocd_04Aug2010_libftdi1_mingw32.zip
>
> OpenOCD: with only ft2232-libftdi support, only for testing,
> cross-built under Linux with MinGW, 04-August-2010
>
> libusb-1.0.dll: downloaded from the following website.
> http://www.libusb.org/wiki/windows_backend (pbr291 MinGW32 binary snapshots)
>
> libftdi.dll:
> cross-built under Linux with MinGW from libftdi-1.0 git 04-August-2010
>
> Take note to use libftdi-1.0 under Windows, you need libusb-1.0
> Windows backend. And currently you need to use WinUSB driver,
> not the FTDI driver or libusb-win32 device driver.
>
> You should use Zadig to install the WinUSB driver for the JTAG
> interface (typically interface 0) of your FT2232 device. You
> can download Zadig from here.
> http://www.libusb.org/wiki/windows_backend
>
> I do not have FT2232H based device. The binary is only tested
> with TI/Luminary EK-LM3S1968 demo board (FT2232D based,
> Interface 0 used for JTAG, interface 1 used for VCP) and under
> Windows 7 32bit.
>
> D:\work\openocd\openocd_04Aug2010_mingw32\bin>openocd -f board\ek-lm3s1968.cfg
> Open On-Chip Debugger 0.5.0-dev (2010-08-04-19:54)
> Licensed under GNU GPL v2
> For bug reports, read
> http://openocd.berlios.de/doc/doxygen/bugs.html
> Info : only one transport option; autoselect 'jtag'
> 3000 kHz
> adapter_nsrst_delay: 100
> srst_only separate srst_gates_jtag srst_open_drain
> Info : clock speed 3000 kHz
> Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part:
> 0x
> ba00, ver: 0x3)
> Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints
>
> D:\work\openocd\openocd_04Aug2010_mingw32\bin>ver
>
> Microsoft Windows [Version 6.1.7600]
>
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
