On 03/31/2011 09:10 PM, Gwennaël Arbona wrote:
Hi,
OMG it works, tornado. Thank you.
Regarding previous issue, if anyone interested:
ftd2xx is v 1.0.4 32b from FTDI website.
Also tried some strace, there are a lot of "ENOENT (No such file or
directory)" error message, but some googling showed that it
(apparently) wasn't a problem).
Speaking of strace, result is attached.
Thanks a lot.
-------------------------------------------------------------------
Gwennaël ARBONA
[email protected] <mailto:[email protected]>
2011/3/31 Mathias K. <[email protected] <mailto:[email protected]>>
Hello,
please tell us the version of the ftd2xx or read the ml.
Regards,
Mathias
Am 31.03.2011 19:14, schrieb Gwennaël Arbona:
> Hi,
>
>
> I am having a bug using OpenOCD 0.5.0-dev-00815-g8d338f3 (just
compiled).
> I am working on Debian Squeeze 32 bits. I am using ftd2xx from FTDI.
> So I got it compiled, and now it is shutting down almost immediatly.
>
> Here is my command and output:
> $ openocd -f /usr/share/openocd/scripts/interface/jtagkey.cfg
> Open On-Chip Debugger 0.5.0-dev-00815-g8d338f3 (2011-03-31-18:24)
> Licensed under GNU GPL v2
> For bug reports, read
> http://openocd.berlios.de/doc/doxygen/bugs.html
> Info : only one transport option; autoselect 'jtag'
> Error: unable to get latency timer: 4
> in procedure 'init'
>
>
> WTF is this?
>
> My hardware is a brand new JTAGKey (never used so far).
> Seems running OK, no warning from dmesg, perfectly detected
Amontec etc.
>
> If any other info is useful, feel free to ask.
>
> Thanks
>
> -------------------------------------------------------------------
> Gwennaël ARBONA
> [email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
>
>
>
> _______________________________________________
> Openocd-development mailing list
> [email protected]
<mailto:[email protected]>
> https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
[email protected]
<mailto:[email protected]>
https://lists.berlios.de/mailman/listinfo/openocd-development
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
Bruno,
Thanks
That change does in fact take care of the ftd2xx 1.0.4 driver issue
problem as seen here:
openocd -f openocd-ftdi-5352.cfg
Open On-Chip Debugger 0.5.0-dev-00811-g56f7055-dirty (2011-03-31-21:28)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
1500 kHz
srst_only separate srst_gates_jtag srst_open_drain
Warn : use 'bcm5352.cpu' as target identifier, not '0'
Info : device: 6 "2232H"
Info : deviceID: 67340952
Info : SerialNumber: TJTAGPROv1A
Info : Description: TJTAG-PRO USB FT2232H A
Info : max TCK change to: 30000 kHz
Info : clock speed 1500 kHz
Info : JTAG tap: bcm5352.cpu tap/device found: 0x0535217f (mfg: 0x0bf,
part: 0x5352, ver: 0x0)
also note that .configure needed -disable-werror, whereas libftdi did not
./configure --enable-maintainer-mode --enable-ft2232_ftd2xx --disable-werror
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
