• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 541 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.

CCS 4.2 doesn't see XDS100v2 emulator

David R.
Expert 1295 points

Hello-

I'm trying to start project debugging using CCS 4.2 platinum and a TMS570 MCU Development Kit (with on-board XDS100v2 emulator). When I try to set up the Debug Session Configuration, the emulator isn't shown under "Connect to exact CPU"; instead a Blackhawk USB560-M emulator (which is not connected and has no driver loaded) shows up.

I have checked:

  • That the device is plugged-in and powered up (it is; white LED is on, and blue target LEDs go through their initialization routine)
  • That the XDS100 is enumerated in Device Manager (it appears exactly as shown here)

Using the remaining "CPU Resolution Options" (i.e. "Connect to first compatible CPU" and "Prompt to select CPU") in the debug session configuration window will drop me into Eclipse's Debug perspective, but no connection attempt is made. The JTAG lights on the development board never turn on.

Is there something else I can do to make CCS 4.2 recognize my XDS100v2?

Thanks,
Dave 

  • 0
    TI__Guru**** 483201 points

    David R. said:
    When I try to set up the Debug Session Configuration, the emulator isn't shown under "Connect to exact CPU"; instead a Blackhawk USB560-M emulator (which is not connected and has no driver loaded) shows up.

    Do you have a target configuration file for your device that is part of your project? If not, the project Debugger Properties will reference the target configuration of the default configuration in your Target Configurations view.

    ki

  • 0 in reply to Ki
    Expert 1295 points

    My project did have a Target Configuration (ccxml) file, but it was only selected as "active" not as "default". As soon as I made it "default", it works fine.

    Thanks,
    Dave