Cannot Identify Target. Check JTAG Connections ...

Comments

16 comments

  • Avatar
    Andrew Shepard

    Note that I am powering the board via it's USB connector connected to my PC.

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    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: 0x0108

    Unfortunately, we haven't yet received the ARM-USB-OCD-H we have on order, so I'm unable to test it.

    0
    Comment actions Permalink
  • Avatar
    Andrew Shepard

    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: 0x0108

    and I now get the error:

    "Target not responding"

    I'll keep plugging away at this and if I find a solution will post it.

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    OK, now try reducing the JTAG clock frequency by increasing the "JTAG > JTAG Clock Divider" target property.

    0
    Comment actions Permalink
  • Avatar
    Andrew Shepard

    Thanks, reduced to 10, then 15 but still have the issue.

    0
    Comment actions Permalink
  • Avatar
    Andrew Shepard

    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.

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    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.

    0
    Comment actions Permalink
  • Avatar
    Tom Bulsink

    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. :)

    0
    Comment actions Permalink
  • Avatar
    Andrew Shepard

    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.

    0
    Comment actions Permalink
  • Avatar
    Tom Bulsink

    Andrew,

    The Olimex site ( http://www.olimex.com/dev/arm-usb-ocd-h.html ) still mentions the following values:

    nTRST Mask - 0x0400
    Output Value = 0x0408

    As Jon mentioned, with these settings Crossworks won't connect to the target, even with an opened project.

    0
    Comment actions Permalink
  • Avatar
    Andrew Shepard

    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. 

    0
    Comment actions Permalink
  • Avatar
    Tom Bulsink

    Andrew,

    Ah okay, glad it's working now for you ( and me :) )

    I sent a message to Olimex pointing out their oversight, maybe they will update their site now.

    0
    Comment actions Permalink
  • Avatar
    freemo716

    i got the same problem , can someone help me with that ? 

    0
    Comment actions Permalink
  • Avatar
    Tom Bulsink

    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.

    0
    Comment actions Permalink
  • Avatar
    freemo716

    yes , i tried , but i get this error when i double clicked on "olimex arm-usb-ocd " interface that i created , when i clicked on "generic ft 2232" i get this error "cannot find libusb driver for usb device vid=0x15ba ,pid =0x0003"

    0
    Comment actions Permalink
  • Avatar
    freemo716

    i did some changes on generic ft2232 interface properties, and now i am getting same error on this interfaces too...

    0
    Comment actions Permalink

Please sign in to leave a comment.