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 CCS windows issue

Other Parts Discussed in Thread: TMDSEMU200-U

Tool/software: Code Composer Studio

Hi ,

related to topic: http://e2e.ti.com/support/tools/ccs/f/81/p/754990/2790753?tisearch=e2e-sitesearch&keymatch=user:4983

After long time I start playing again. What I did is:

Open .ccxml configuration file and change "Connection" from Texas Instruments XDS2xx USB Debug Probe  to  Texas Instruments XDS2xx USB Onboard Debug Probe.

Now I'm able to connect to the probe.
Have you any idea why is that?

Regards, Mare

  • Mare,

    The two variants of the debug probe have very slight differences, which was a remnant of the days where CCS required a license to operate - it was completely unlocked for development kits but required a paid license to work with the standalone version of the XDS200 (TMDSEMU200-U).

    That said, nowadays I use both connections interchangeably with both my onboard and standalone target devices. Also, when looking at your previous thread, this change does not necessarily explain how the original connection worked for a while and then slowly started to fail. In this case I really am at a loss as to the exact root cause of the problem - you could potentially blame any temporary files created with the previous connection that were overwritten by the new one, but in my experience the issue usually shows itself as an instantaneous fault and not a degradation.

    At any rate, I am glad the system is working for you again. I will try to replicate some of this but unfortunately I can't promise much.

    Regards,
    Rafael