Try reducing the JTAG clock frequency by increasing “JTAG Clock Divider” to something like 15 or 20. I don’t have the software on this computer, but I think you can get to that setting by right clicking on the “Olimex-Arm-USB-OCD” item in the targets window and selecting properties.
If that doesn’t work, you can try posting your question on the CrossWorks support page.
I tried increasing the “JTAG Clock Divider” to 10, 20, 50 etc and no lock.
Also posted the query on Crossworks support, but they are still to get back. I am pretty much stuck here. I even have a cross-connect lite and an arm swd adapter.
It has a similar problem.
I believe if i crack one of these, all can be cracked. Will post if i am successful. But meantime please keep your guesses coming as i am desperate.
Regarding the driver, the ARM-USB-OCD should show up as two devices, a serial port and a JTAG interface. You should be able to see both if you view by connection in Device Manager. If you don’t see the JTAG interface you can [try to reinstall the drivers].
It has been so long since I installed the drivers that I can’t remember any details. And I have not used Crossworks.
I thought about suggesting you install openOCD and run it from the command line to verify that your hardware is ok. But I seem to recall reading about problems with two different drivers trying to “grab” the same hardware. Best to keep it as simple as possible.
Unless (warning - I haven’t the foggiest clue here) openOCD is already installed, and Crossworks tries to connect to the openOCD GDB server. If that were the case you could run openOCD from the CLI and get more detail.
I haven’t tried the Olimex-Arm-USB-OCD jtag but I have used the Cross-Connect Lite and had similar problems. As is usually the case it was operator error. Verify that the cable is oriented correctly and that the target is powered. I haven’t had a problem since. Oh, and the Cross-Connect Lite requires the adapter from Rowley; you can’t use just an adapter from, say, Segger.