• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 445 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.

Original question:

Multiple Target Debug with Multiple XDS510USB JTAG Pods in CCSv4.2

CCS/AM3352: How to make CCS Debugger connect to the correct core?

Christopher Weber
Genius 4995 points

Part Number: AM3352

Tool/software: Code Composer Studio

Hello,

I am using CCS7.   connecting to a Sitara device.

I am enhancing a large project, and I discovered that it has several targetConfig CCXML files in the root level, using different debugger connections.

So I created a new targetConfig ccxml file.  Set it to my XDS100v2, and made it active.

I also set the project properties, under" Debug" to XDS100v2 USB debug Probe/CortexA8, and the necessary "Run to Main", "Connect on Startup" etc...

And yet, the environment refuses to connect and load to the A8 core.  It insists on trying to load the M3 core.

How/Where to I tell this environment to NOT connect and load to the M3., and instead load the primary A8 core??

When I have created new projects, and began debugging them, I have gotten this:

However, no menu, button, or context setting I have found will ever bring this dialog up again.  It seems the only way to get this selection dialog is to completely erase the entire project and create a new one.