Problems communicating Amontec JTAG key.

Development Boards MicroMod
1

We have Amontec JTAG key working successfully with old open OCD (r717), I believe provided by Amontec.

We want to upgrade to latest openocd (for access to new processors), so got the V0.4.0 version from

http://download.berlios.de/openocd/open … .0.tar.bz2

We can successfully connect to the jtag key with the old open OCD, but not new.

Does anyone have any ideas what’s going on?

I have included logs of the sessions with the config files for the jtag interface, and contents of the files.

New openocd, new config file***

C:>openocd -f C:\sw_devel\OpenOCD\0.4.0\interface\jtagkey.cfg

Open On-Chip Debugger 0.4.0 (2010-02-22-19:05)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.berlios.de/doc/doxygen/bugs.html

Error: unable to open ftdi device: device not found

Command handler execution failed

Old openocd, old config file********

C:>“C:\Program Files\openocd-r717\bin\openocd-ftd2xx.exe” -f C:\sw_devel\OpenOCD\0.4.0\interface\jtagkey.cfg

Open On-Chip Debugger (2008-06-19 19:00) svn: 717

URL: http://svn.berlios.de/svnroot/repos/openocd/trunk

Error: ft2232.c:1419 ft2232_init_ftd2xx(): unable to open ftdi device: 2

Error: ft2232.c:1434 ft2232_init_ftd2xx(): ListDevices: 2

Error: ft2232.c:1436 ft2232_init_ftd2xx(): 0: Amontec JTAGkey A

Error: ft2232.c:1436 ft2232_init_ftd2xx(): 1: Amontec JTAGkey B

Old openocd open config file*******

C:>“C:\Program Files\openocd-r717\bin\openocd-ftd2xx.exe” -f C:\sw_devel\trunk\

common\moPhy3250_startup\lpc3250_jtagkey–hack.cfg

Open On-Chip Debugger (2008-06-19 19:00) svn: 717

URL: http://svn.berlios.de/svnroot/repos/openocd/trunk

Error: jtag.c:1351 jtag_examine_chain(): JTAG communication failure, check con

nection, JTAG interface, target power etc.

Error: jtag.c:1556 jtag_init_inner(): trying to validate configured JTAG chain

anyway…

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1565 jtag_init_inner(): Could not validate JTAG chain, exit

Error: jtag.c:1351 jtag_examine_chain(): JTAG communication failure, check con

nection, JTAG interface, target power etc.

Error: jtag.c:1556 jtag_init_inner(): trying to validate configured JTAG chain

anyway…

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1456 jtag_validate_chain(): Error validating JTAG scan chain, IR

mismatch, scan returned 0x00

Error: jtag.c:1565 jtag_init_inner(): Could not validate JTAG chain, exit

Warning: telnet_server.c:624 telnet_init(): no telnet port specified, using defa

ult port 4444

Warning: gdb_server.c:2015 gdb_init(): no gdb ports allocated as no target has b

een specified

***************** New jtag config *****************

Amontec JTAGkey

http://www.amontec.com/jtagkey.shtml

interface ft2232

ft2232_device_desc “Amontec JTAGkey”

ft2232_layout jtagkey

ft2232_vid_pid 0x0403 0xcff8

***************** Old jtag config file **************

#interface

interface ft2232

ft2232_device_desc “Amontec JTAGkey A”

ft2232_layout jtagkey

ft2232_vid_pid 0x0403 0xcff8

2

Are you able to open the JTAGkey from the Amontec JTAGkey Demo software ?

If not, you driver is not well installed.

Regards,

Laurent

http://www.amontec.com

3

Are you able to open the JTAGkey from the Amontec JTAGkey Demo software ?

If not, you driver is not well installed.

Regards,

Laurent

http://www.amontec.com

4

Thanks for the suggestions.

Laurent actually solved this for us via Amontec support.

It needed a compile with the proprietary d2xx library, and possibly slightly different drivers from Amontec.

As an aside, we built with Msys, and Mingw. Not with the normal cygwin.

So far no problems… but our research continues.

Many thanks.

-Rob.