Drasko DRASKOVIC wrote:
Hello Laurent,
I have trouble compiling your driver in static (I copied libe from
build/i386 to stati_lib):
checking whether standard drivers can be built... yes
checking uninstalled ftd2xx distribution...
-L/home/ddraskovic/sandbox/libftd2xx_laurent/libftd2xx1.0.4/static_lib
/home/ddraskovic/sandbox/libftd2xx_laurent/libftd2xx1.0.4/static_lib/libftd2xx.a
checking whether ftd2xx library works... configure: error: Cannot
build & run test program using ftd2xx.lib
[1] 22996 exit 1 ./configure --disable-werror --enable-verbose
--enable-verbose-jtag-io
[ddraskovic@lardos:/home/ddraskovic/sandbox/openocd-0.5.0/openocd]>ls
/home/ddraskovic/sandbox/libftd2xx_laurent/libftd2xx1.0.4/static_lib/libftd2xx.a
/home/ddraskovic/sandbox/libftd2xx_laurent/libftd2xx1.0.4/static_lib/libftd2xx.a
[ddraskovic@lardos:/home/ddraskovic/sandbox/openocd-0.5.0/openocd]>
When compiled shared, I run into this standard libftd2xx compiling
error produced by libtool shuffling of libs order, but this can be
fixed as explained here :
http://albertoembedded.wordpress.com/2010/03/16/openocd-with-amontec-jtagkey2-support/
http://andrey.mikhalchuk.com/2009/06/03/solving-libopenocdso-undefined-reference-to-ft_getlatencytimer-problem-during-openocd-compilation.html
Finally, when I run OpenOCD with this driver I am getting :
Debug: 168 19 command.c:364 register_command_handler() 103584:
registering 'ocd_reset_nag'...
Debug: 169 19 ft2232.c:2433 ft2232_init() 104216: ft2232 interface
using shortest path jtag state transitions
Debug: 170 19 ft2232.c:2133 ft2232_init_ftd2xx() 104216: 'ft2232'
interface using FTD2XX with 'jtagkey' layout (0403:cff8)
Error: 171 34 ft2232.c:2239 ft2232_init_ftd2xx() 137400: unable to get
latency timer: 4
Debug: 172 84 command.c:638 run_command() 137336: Command failed with
error code -100
I however compiled OpenOCD with official libftd2xx0.4.16 - it compiles
quite fine both static and shared (for shred there is mentioned
problem in the end).
When run with this driver, there are no problems with latency timer.
However, problem : couldn't read enough bytes from FT2232 device (0 <
5) still persist.
Can you point me how to override the problems with compilation with
Amontec driver ?
Best regards,
Drasko
On Thu, Mar 17, 2011 at 5:23 PM, Laurent Gauch
<laurent.ga...@amontec.com> wrote:
Try with d2xx Linux driver attached.
Compile with d2xx support
Regards,
Laurent Gauch
http://www.amontec.com Amontec JTAGkey-3 coming soon ! Generic USB JTAG
CJTAG SWD SWO serial wire debug interface 1.5V 1.8V 2.5V 3.3V 5V auto-sense
protected IOs With RTCK support
maximum 30Mhz JTAG TCK frequeny
Drasko DRASKOVIC wrote:
On Thu, Mar 17, 2011 at 4:53 PM, Laurent Gauch
<laurent.ga...@amontec.com> wrote:
I am waiting on the log using the Amontec JTAGkey d2xx WHQL certified
driver
. Maybe we will see something different, in this case it is a trouble in
the libftdi . If the same some trouble in the higher JTAG level in
openocd
source.
It is only Windows driver right ? That would say that I must find now
Windows machine and compile latest OpenOCD for Windows... This will
take some time.
BR,
Drasko
For the driver, I will see this afternoon.
What JTAGkey dongle do you have ?
Generation - 2
Amotnec JTAGkey-2
Amontec JTAGkey-2P
Generation - 1
Amontec JTAGkey
Amontec JTAGkey Tiny
If you have a JTAGkey or JTAGkey Tiny do you get the problem : couldn't
read enough bytes from FT2232 device (0 <5), as with the JTAGkey-2 ?
Regards,
Laurent
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
