I just received my new JTAGkey. Will be doing development in Linux for ARM926EJ-S.
I haven’t received my development board yet but I have installed the latest SVN trunk of OpenOCD and have scanned all the documents I can find looking for a test I can do to make sure things are setup right.
I noticed there was a test program for Windows but that won’t help me.
My /etc/fstab has this line. I’m using 2.6.24 kernel:
If you build libftdi from source it has a couple of test programs in the ‘examples’ directory. You will need to change them to use VID 0x0404 and PID 0xcff8. Especially the latter is nonstandard. Then try for instance the find_all sample program to see if it finds the JTAGkey.
If no, there is a bug in the library, most likely a format change to /proc/bus/usb. Also, many distros already have this as a kernel resident module and you don’t really need it in fstab - I know the stock CentOS5/64 SMP kernel does for instance (since it’s what I run).
When this works, focus on openocd.
Under src/target/interface you’ll find jtagkey.cfg - this is a good place to start.
When you have it all working, see if you can get it to work using libftd2xx. I wouldn’t hold my breath though.
Outstanding! I’ll try that. When I was installing some extra packages, I noticed that I already had several of the usb libs installed.
When I plug the device up, I get a yellow light and a tail of dmesg show that it saw something being attached (can’t remember the message … I’m not on my development machine now).
The only board I currently have access to is a Soekris net4526 (AMD Elan SC520 CPU) and it has JTAG/AMDDebug but I’ve never tried to use it. I wonder if I could hook to it with the JTAGkey and at least reset the board or do a boundary scan chain scan to see what devices are reported back.
Thanks suggesting things to try. Hopefully my ARM board will show up soon.