OpenOCD does not see JTAGkey2

When I run the following command string: openocd -f interface/jtagkey2.cfg -f board/str910-eval.cfg

I get the error message “Error: unable to open ftdi device: device not found”

Setup information:

Windows XP with Service Pack 3.

If I go into device manager I do see “Amontec JTAGkey ( Channel A )” and “Amontec JTAGkey ( Channel B )” listed under Universal Serial Bus Controllers. If I go to properties they both show as device working properly. The driver version is listed as 3.1.2.0

The Device Instance Id’s show up as USB\VID_0403&PID_CFF8&MI_00\6&24CB189E&0&0000 and USB\VID_0403&PID_CFF8&MI_01\6&24CB189E&0&0001 (No idea of these matter but I figured when in doubt it’s better to include it)

If I try to check the adapter using JTAGkey Demo the “Select a JTAGkey” box does not let me select anything so I suspect I have a driver problem somewhere even though the JTAGkey2’s power LED is turned on. I have the exact same results with a second JTAGkey2. I have also tried on another PC (also running XP) and get the same results with either adapter.

I figure I must be missing something but I have no idea what; any help would be greatly appreciated. Thanks in advance!

Please download our last Amontec JTAGkey Driver from :

http://www.amontec.com/download/amontec … 091124.zip

Go to device manager of Windows and update both channel A and channel B

of Amontec JTAGkey .

This driver is signed and certified for Windows WHQL 32bits and 64bits. NO WARNING MESSAGE AS UNCERTIFIED DRIVERS .

This driver is generic for all our JTAGkey series and works very well.

Let me know if this resolve your trouble.

Regards,

Laurent Gauch

http://www.amontec.com/

USB JTAG Cable 1.3V to 5.5V 32mA RTCK … = Amontec JTAGkey-2 series

Amontec - thanks for the quick reply. Updating the driver did help some since JTAGkey Demo can now recognize the JTAgkey2.

Unfortunately I still get the same “unable to open ftdi device: device not found” error from OpenOCD. Is there anything else I should check?

Thanks,

Dave

Build OpenOCD for JTAGkey FTDI D2XX driver .

Regards,

Laurent

http://www.amontec.com

let me know how !

Laurent

http://www.amontec.com

I have searched through the OpenOCD manual and haven’t found any references to building for the FTDI driver other than:

“MS-Windows needs complex and confusing driver configuration for every peripheral. Such issues are unique to each operating system, and are not detailed in this User’s Guide.” I assume this is referring to the windows driver itself which is now wprking but I am not comptetely sure.

It’s probably worth backing up a bit at this point. I am on my home PC at the moment and have downloaded OpenOCD but do not see anything that resembles an install file. I assume that I must have previoiusly used a pre compiled version at work that did not include support for FT2232? Anyway how do I turn the OpenOCD files into something that I can install? I assume that I will need TCL or Cygwin or something along those lines but the OpenOCD documentation doesn’t cover compiling so I am a bit stuck.

While I on the subject it may help to point out my final goal. I am writing a Labview based program for a program/test fixture. I have the testing portion under control but this is my first need for JTAG programming. I am not doing anything other than loading (and verifying) the Microcontrollers internal flash (ST Micro ARM911) with code. One programming option is to have Labview run a “command line” command. Here is where I thought OpenOCD would be useful. The other option is to talk to and control the JTAGkey2 directly from within Labview. The latter method would be preferable but (assuming I could talk to the JTAGkey2 hardware) I am afrraid this may be too complex especially given the very tight schedule I have. I remember seeing JTAGkey Labview drivers but I do not see them on the Amontec sebsite at the moment and from what I recall they were very low level.

I do not know if our ST development system will output SVF files but if it can then using amtsvfplayer.exe may be a viable option.

Any opinions you have on this would be greatly appreciated.

Thanks,

Dave

Just found the sparkfun thread on building OpenOCD for windows as well as the instructions found here:

http://piconomic.co.za/fwlib/_b_u_i_l_d … o_c_d.html

I will give it a try.

HAMERMAN409:
Amontec - thanks for the quick reply. Updating the driver did help some since JTAGkey Demo can now recognize the JTAgkey2.

Unfortunately I still get the same “unable to open ftdi device: device not found” error from OpenOCD. Is there anything else I should check?

Thanks,

Dave

Hi I had exactly the same problem !

Only different is:

Crossworks don’t work with the JTAGKey2p !!!

I have following error:

cannot identify target.check JTAG connection…

Can anyone help me ?

kind regards

Yello