• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 31 subscribers
  • Views 2061 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Error connecting to the target: (Error -1063 @ 0x00)

Jeff_e2e
Intellectual 860 points
Other Parts Discussed in Thread: LM3S811, EK-LM3S8962

Hello,

I am currently running CCS 5.4.0.00091, ARM compiler 5.0.5 emulating with a Spectrum Digital XDS560v2 USB emulator with 5.2.0.08.  I have a costume board with the TIVA TM4C1231D5PMI processor and a TI 20 Pin debug header.  I have successfully debugged code on several of these boards.  However, one board gives me the following error when I try to emulate.  

Error connecting to the target:
(Error -1063 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.
(Emulation package 5.1.114.0)

I am unsure how to go about solving this issue as I am unable to connect to the device and swapping boards and retrying does not give the same error.  Has anyone else seen this or have and insight as to how I may go about eliminating this problem?  

Thanks,

Jeff 

  • 0
    TI__Intellectual 1530 points

    Jeff,

    I would suggest to use an oscilloscope to probe the JTAG pins on the faulty board, see if you can find a pin which isn't connected properly.

    Thanks,

    Angela

  • 0
    Guru 117855 points

    You provide little history - that failing board.  If it encountered attempt to "repurpose PC0-PC3" its likely that JTAG has been lost - yielding that unwelcome message.

    LM Flash Programmer - last tab - reveals a Utility "Recovery" - which should restore that JTAG capability.  Your part is Blizzard - the help section w/in that App details the procedure...

  • 0 in reply to cb1_mobile
    Intellectual 860 points

    Hi CB1,

    Sorry some time has passed since I have been able to work on this problem.  Unfortunately I am seeing it in additional boards.  I tried connecting the lm flash programmer via a lm4f120 launch pad and lm4f232 evaluation board.  Both give the same error, "unable to initialize target - 0!"  Debug port unlock seems to successfully run through the reset, both does not eliminate the problem.  On the custom boards, the jtag header has not been used for additional I/O.  The only use is for jtag.  

    Any additional suggestions would be helpful.  

    Thanks,

    Jeff 

  • 0 in reply to Jeff_e2e
    Guru 117855 points

    Vendor's Sue Cozart here has advised against use of LX4F232 (there never were any LM4F) boards as JTAG "Output" device.  (JTAG header - that board - is intended as JTAG In)

    Launchpads have been reported to function as USB to JTAG tool - when interposed between PC and your custom board.  We do not use (nor especially like) launchpad - and there are some "hoops" which must be successfully negotiated - prior to the launchpad's issue of proper JTAG out.

    We always advise the use of external pull-up R's - each/every JTAG pin.  (relying upon internal MCU pins - when programming is already suspect - eats time, morale - pointless - our belief)

    Old standby LM3S811 boards provided simplified JTAG output - requiring only that you ground one critical pin to steer the JTAG away from the 3S811 - and onto your target.  Perhaps someone - your group or friend can provide.

    You likely should look @ your code - improper handling of Port "C" is usual suspect when JTAG functionality is lost.  (Guard agains overly broad use of Port C (i.e. insure your code does not disturb PC0-PC3) 

    If ok - look carefully @ "SysCtlClockSet()" - especially for a mismatch between xtal parameter and the actual xtal - on your board.

    Should both tips fail - Stellaris forum (very top) Ms. Cozart's post has "laundry list" of JTAG fix - "how/where" - some contributed by this reporter.   Many have found this useful...

  • 0 in reply to cb1_mobile
    Intellectual 860 points

    Ya I just realized the 232 was never going to work.  What hoops would I need to jump through to use the launchpad?  The custom board has all the pullups on those pins.  I grounded the external debug pin on the launchpad and connected the 4 pins.  I also tied grounds together (made sure I wasnt going to get bit by that one again). 

    I was unable to locate a LM3S811 but I do have a dk-lm3s9b96 and a ek-lm3s8962.  Please advise which one to move forward with. 

    thanks

  • 0 in reply to Jeff_e2e
    Intellectual 860 points

    Good news!  Reseting the jtag connection and rewriting flash seems to have saved the boards.  I was able to use the Lm4f120 launchpad.  Upon reading the wiki, I misunderstood the external debug pin.  That need not be pulled low for debug out.  (debug out for using the icd to another board i.e. what I was trying to do.)  The external debug pin is pulled low if another debugger is being used to program the board.  My mistake. 

    I am still unsure what caused the original error as other boards running the same code did not brick. 

    Thanks for the help!

  • 0 in reply to Jeff_e2e
    Guru 117855 points

    Good news indeed!   Good for you - your effort/patience rewarded.

    Suggest that you "log" all of your settings/connections (which enabled recovery) "just in case."   (should this misfortune, revisit)

    Likely worth your time to insure pull-up Rs are present, of correct value - and that all connection paths (to include solder joints) between JTAG header and MCU's JTAG pins meet your approval...