• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 949 views
  • Users 0 members are here
Support feedback
Options
Options

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.

CCS/TMS570LS3137: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP.

Bob Myles
Prodigy 80 points
Part Number: TMS570LS3137
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

I've read *many* similarly titled postings but I've not found a solution.

We are using a Spectrum Digital XDS560V2 STM USB Emulator on a proven TMS570LS3137 design that has worked for a couple of years now. 
We are suddenly getting the error message: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP, from both
CC Studio Version: 6.0.1.00040 and CCS UniFlash Version: 3.1.0.00026.

The identical application software is working in another station with the same versions of CCS and UniFlash and Emulator, the board works fine in
the other station and the emulator hardware has been verified to work in the other station. 

Opening the Target Configuration and running the "Test Connection" utility results in a message that the JTAG DR Integrity scan-test has succeeded 

I suspect that a configuration file has become corrupted or some similar issue but I'm new to this environment and don't quite know where to look.

I'd appreciate any clues...   

  • 0
    TI__Genius 14142 points

    Hi Bob,

    in CCS could you try the following:

    [] Launch the same target configuration. Then instead of connecting the CortexR4 or R5 (depending on your chip), go to “Show all cores” by right clicking on the red (the below is a different Hercules, but conceptionally the same)

    This will then show the non Debuggable cores.

     

    Now select and connect to the Icepick first.

    Then once connected, do a CTRL-SHIFT-R (System Reset)

    Then select and connect Dap.

    Then connect the CortexR4 or R5 (depending on your chip)

     

    Does the CortexR now connect?

    Thanks,

    --Gunter

     

  • 0 in reply to Gunter Schmer
    Prodigy 80 points

    ,Hi Gunter,

    Thank you for your quick reply.  It seems that your post had a screenshot embedded but it doesn't show up so I'm guessing about what you are suggesting. Anyway, by right-clicking the name of the .ccxml file I was able to see the "Show all cores" option, which I selected.  I then tried your steps and the Icepick and DAP seemed to connect.  The DAP only connects if I do the System Reset as you prescribed.  However, I don't know what you mean by "connect the CortexR4/R5".  I tried the next item in the list: Spectrum Digital XDS560V2 STM Emulator_0/CortexR4, but I only succeeded in launching it and getting the same error message again.  I feel that you are onto something.  I wanted to send a screen shot of what I am doing in hope that you can see where I'm walking off the path but it doesn't show.

    So here is another question: Assuming that the sequence you described was successful, would I need to perform these steps each time I wanted to debug or would I be able to make a script or a macro that would perform the sequence whenever I launched the .ccxml configuration?

    Thanks  

  • 0 in reply to Bob Myles
    TI__Genius 14142 points

    Hi Bob,

    I think you are doing it correctly, but let me double check your sequence. Here is the screenshot, hopefully it comes through this time. Again it is for an R5 part instead.

    The sequence

    [] power up your target

    [] launch your target configuration

    [] select the xxxxx.ccxml and right click to "Show all cores" (you have done this)

    [] select IcePick and right click and connect

    [] while IcePick is still selected, do a System Reset (CTRL SHFT R)

    [] select Dap and right click and connect

    [] select CortexR4 and right click and connect

    Does the CortexR4 connect now?

    If so, this would be the time to download and flash your new production image. My suspicion is that somehow the image on the failing unit is corrupted and when you power up your target it gets to a state where the CCS or Uniflash cannot connect anymore to the CortexR4 without the above steps. But with the above steps you should be able to connect to the CortexR4, download a new image and reflash. Then on a subsequent power cycle of the target, the target does not run into the state anymore and you should be able to connect normally with CCS or Uniflash.

    So essentially the above steps would need to only be done if the target runs into this state where JTAG does not connect anymore.

    Regards,

    --Gunter