SparkFun Forums

[kk6gm]

OK, I'm frustrated. I've been using Crossworks with their Cross Connect, but now at work they need a quick ARM project using free tools and an ARM-USB-TINY-H, and I've spent the entire day trying to get it to work with either IAR or the Olimex Eclipse/GCC package. OS is Windows XP. I've gone through every permutation of downloading/installing/uninstalling/cleaning the drivers (except the correct one, of course). It simply won't connect.

Then I brought home the A-U-T-H to try it on my Windows 7 machine with Crossworks and couldn't make it work there either. I read that 64-bit operation is a problem, but that doesn't explain my troubles at work.

So I'm looking for either the magic words to make this device work on an XP machine, or a recommendation for another JTAG device in that price range.

And I have never appreciated Crossworks and CrossConnect so much!

[frank26080115]

you did not explain your problem at all. have you read this http://www.catb.org/~esr/faqs/smart-questions.html ? what do you mean by "not working"? what errors are you getting? what have you tried so far to resolve those errors?

Check out http://www.seeedstudio.com/depot/bus-bl ... ?cPath=174
It probaby kicks Olimex's butt in every respect

I have Bus Blaster V1 (my own V2 is on its way) and run Win7 Pro 64 bit with OpenOCD and it works like a charm with a AT91SAM7XC512

[kk6gm]

Granted, I didn't give as much info as would be desirable, but that's because I'm writing from home and don't have the error messages in front of me. The Windows 7 / Crossworks error message is "Cannot find FTDI driver for USB device (vid = 0x15BA, pid = 0x002A...)" but I don't actually care if it runs on my home system, so I'm not particularly interested in following that up.

I know that at work I got something similar to this (I grabbed this text from a forum post somewhere):

Open On-Chip Debugger 0.4.0 (2010-08-27-20:29)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
1000 kHz
jtag_nsrst_delay: 100
jtag_ntrst_delay: 100
Warn : Unable to open FTDI Device...
Error: unable to open ftdi device: ...

But I don't remember the details of the WARN and ERROR text.

I was hoping that there might be some default "yeah, in 80% of these cases it's XYZ". If not, I'll have to try again on Monday when I've got the errors in front of me.

[PhatBob]

I had all sorts of misery with the FTDI drivers on Windows 7.
Where did you get the drivers that you're using from?
In the end I had to use the info from here:
http://www.olimex.com/dev/pdf/ARM/JTAG/ ... rivers.pdf
To remove the drivers (you will need to use an application from FTDI that properly removes them: http://www.ftdichip.com/Support/Utilities/FTClean.zip
Then get the drivers from http://www.olimex.com/dev/soft/arm/JTAG ... 20808).zip
And follow the instructions from the README.txt file (things are not as straightforward as you might think...)
I found that I had to use the FTClean app more than once during the learning experience.

Hope that this helps

Rob