Cannot Identify Target. Check JTAG Connections ...
Using Olimex ARM-USB-OCD-H JTAG Debugger connected to a NGX Technologies BlueBoard LPC-1768-H. When trying to connect to the target (Generic FT2332 Device) get the following error:
"Cannot identify target. Check JTAG connections and that the target is powered"
Each time I try to connect I see that two of the board's LEDs D4 and D8 flash. Note that if I disconnect the board from the JTAG connector and connect the board to the USB port, my PC identifies the board indicating that the program on the board is operating when not connected to the JTAG connector. The following are Crosswork settings for the Generic FT2332 Device:
nSRST Inversion Mask 0x0200
nSRST Mask = 0x0200
nTRST Inversion Mask = 0x0000
nTRST Mask - 0x0400
Output Pins = 0x0F1B
Output Value = 0x0408
PID: 0x002B
VID: 0x15BA
JTAG Clock Divider: 10
Anybody have any suggestions on how to debug this?
Thanks!
-
We had another customer report a similar problem a few days ago - I think the settings on the Olimex website are incorrect. Try changing the following settings and see if that makes any difference:
nTRST Mask: 0x0100
Output Value: 0x0108Unfortunately, we haven't yet received the ARM-USB-OCD-H we have on order, so I'm unable to test it.
-
Thanks for feedback. I found another error on the Olimex website (the VID was wrong) but they have since corrected it. I tried the suggested settings :
nTRST Mask: 0x0100
Output Value: 0x0108and I now get the error:
"Target not responding"
I'll keep plugging away at this and if I find a solution will post it.
-
I wonder if I need to change a jumper setting on the board to allow debugging with JTAG debugger? There is a program burned into the board that runs if I don't connect the JTAG. Is it possible that there is a jumper that prohibits the JTAG from accessing the board? Unfortunately, the documentation for the board is not very comprehensive.
-
I can't see anything obvious on the schematic that would suggest this.
See http://rowley.zendesk.com/entries/45519-target-not-responding-error-message for other causes of the "target not responding" message. Note that the LPC17xx doesn't support adaptive clocking, so don't bother about that entry.
-
FYI, Using an Olimex ARM-UBS-OCD-H/Olimex STM32_LCD board ( http://www.olimex.com/dev/stm32-lcd.html ) on Linux Mint/Ubuntu 10.10.
I got it so far now that its connecting to the target ( waiting for evaluation key to try debugging still ) using the following settings:
- Use the generic FT2232 connection
- nSRST inversion Mask : 0x0200
- nSRST Mask : 0x0200
- nTRST inversion Mask: 0x0000
- nTRST Mask : 0x0100
- Output pins : 0x0f1b
- Output value : 0x0108
PID : 0x002B
VID : 0x15BA
I could ( with only connecting ) increase JTAG clock to JTAG divider 2
Rest are zero. Indeed, the values mentioned on the Olimex site were not working for me.
Also, it wouldn't connect when i tested it without starting an STmicroelectronics STM32 project. Only after using the project wizard would it connect, before that i kept getting the 'Cannot identity target' message
Tbh, Im really curious/exited if this Linux/Embedded development thing is gonna work. :)
-
I just got back onto working this issue today and I got it working based on suggestions from Rowley. I started out with a USB to JTAG issue which was caused because the Olimex website posted wrong data (they've since corrected it) Then I had the problem of the debugger not identifying the target. The cause was that (similar to your discovery) I hadn't opened a project so Crossworks didn't know what the target was. An error message indicating that a project wasn't open would have been really helpful. Everything else seems to work great now.
-
Andrew,
The Olimex site ( http://www.olimex.com/dev/arm-usb-ocd-h.html ) still mentions the following values:
nTRST Mask - 0x0400
Output Value = 0x0408As Jon mentioned, with these settings Crossworks won't connect to the target, even with an opened project.
-
Tom,
Sorry, I wasn't clear in my post. The value that I was referring to was the USB product ID which was incorrect at one time. I was unable to even talk to the JTAG debugger until that was fixed. Once I got that working I starting working with Rowley about the next problem-unable to connect to target and they notified me of the changes you mentioned above. Thanks for checking that I had changed these.
-
Have you tried the solutions mentioned here? The settings on the Olimex page (https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/) are correct now as far as i know. Check the FAQ portion there.
Please sign in to leave a comment.
Comments
16 comments