jtag woes

Kirk Bratvold

September 13, 2013 16:55

Once upon a time, I had two PC's with CrossStudio for ARM 2.0.5, two Amontec JTAGKey adaptors, and two target devices (Vincotec A1091's), all working smoothly.

Upon returning to development after a few-month hiatus, I find that nothing works: Crossworks only reports "Cannot identify target. Check JTAG connections and that the target is powered".

I've gone through the hardware and software checklist. I've replaced my target hardware. I've replaced my JTAG adaptor with a CrossConnect. I've replaced one of my PC's. I've replaced my USB cables. I've replaced my power supply. I still get the same error.

What should I do next? Can CrossStudio expire or somehow break?

Comments

11 comments

Dr Danish Ali

September 16, 2013 11:00
Does your project actually have a specified target processor?

I had similar error messages when I was accidentally trying to download a library rather than a "complete" project with specified cpu, main()

So starting a new project/solution with a simple "hello world" main() would be a quick test.
0

Comment actions Permalink
Richard Webb

September 16, 2013 13:05
Check that Target | Targets | Properties | JTAG | Adaptive Clocking is set to "auto."

Did you recently upgrade from 2.0.5 to the current 2.3.3?

It may also be helpful to isolate the problem if you monitor the JTAG lines with a logic analyzer. I have a 2x10 IDC receptacle crimped onto the JTAG ribbon cable on all of my adapters just for that purpose. I've attached part of a JTAG session with an STM32F processor as an example.
0

Comment actions Permalink
Paul Curtis

September 16, 2013 13:46
Make sure you have a project loaded and that it is made active. The "cannot identify target" means that the JTAG ID of the part can't be read, i.e. that JTAG device readout is failing.

CrossStudio does not "expire" or change its operation after sleeping for months.
0

Comment actions Permalink
Nick Price

September 16, 2013 14:51
I've recently had to re-install my Driver and the MSL430.DLL from the Rowley website after it refused to ID any chips. But my Elprotronic FET-Pro430 was working fine.

So, download the Elprotronic FET-Pro430 Lite software, and see if it connects, that will prove your wiring.

Regards

Nick
0

Comment actions Permalink
Paul Curtis

September 16, 2013 14:58
...but that is for MSP430, it has little chance of connecting to an ARM device.
0

Comment actions Permalink
Nick Price

September 16, 2013 15:07
Oops. I thought you were talking MSP430. D'oh

Ignore me
0

Comment actions Permalink
Kirk Bratvold

September 16, 2013 15:59
Yes, project is active. Yes, jtag is auto adaptive clock. Still running Rowley 2.0.5; haven't upgraded yet.
0

Comment actions Permalink
Paul Curtis

September 16, 2013 16:11
Make sure you have selected a configuration that isn't Common. If you've altered any JTAG IR/DR pre/post bits, that can also have an effect.

What happens if you right-click the target interface in the Targets window and select Explore? Do you see your device in the JTAG chain?
0

Comment actions Permalink
Kirk Bratvold

September 16, 2013 16:36
Do you mean the active configuration in the project explorer window? I'm using THUMB Flash Debug (or Release) which is the config that I've always used.

When I do 'Explorer', nothing seems to happen.
0

Comment actions Permalink
Paul Curtis

September 16, 2013 16:42
> When I do 'Explorer', nothing seems to happen

No, Explore. Nothing happens, not even a dialog?
0

Comment actions Permalink
Kirk Bratvold

September 16, 2013 16:54
No window was appearing. But after monkeying with the active config (it's 'common' now) and restarting the IDE, JTAG works now. And the Explore window too.

I hate to be in one of those "I have no idea how it broke or how it fixed" situations, but I guess that's it ;)
0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?