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

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: XDS200 with XDS110 on the same machine doesnt work

Gilboa Shveki
Prodigy 260 points

Tool/software: Code Composer Studio

hi

I'm developing MSP432 (XDS110) connected to M3 target with XDS200, code composer fail to connect to the XDS200 when the XDS110 is also connected to my development machine. following error presented:

Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 6.0.576.0)

any ideas on how to solve it? i must debug them both on the same machine

thanks

  • 0
    TI__Guru**** 169874 points

    Hi,

    One question: are you trying to connect to both JTAG debuggers from the same CCS session? If you are instead running two CCS instances and trying to connect, this is expected as the emulation drivers are not reentrant.

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Prodigy 260 points

    no, comlpetly different sessions (even different CCS instance). the XDS110 USB is just connected to the PC (not connected to the target), and then the XDS200 refuse to connect to the target with the above error message

  • 0 in reply to Gilboa Shveki
    TI__Guru**** 169874 points
    Hi,

    Sorry, I now noticed my sentence above was terribly unclear.

    Running two instances of CCS causes conflicts on the JTAG debug probes and is not supported. Specifically on the case of XDS110 there is an added problem: if you opened a debug session and then closed it, CCS will hijack the drivers (this is reported on bug CCSIDE-2990).

    Therefore the supported configuration is to run a single instance of CCS for debug - either connecting to each JTAG debugger/board individually or in a shared session as I showed in my previous screenshot.

    Hope this helps,
    Rafael