Other Parts Discussed in Thread: MSP430F2013
Hello, (There USED to be a check box for "my question is about CCS... that's now gone)
I am looking for answers. There are none of value I can find.
Lets talk about ccxml files...
When I create a Hello World tutorial file, and press debug, it magically creates a ccxml file, loads it to the target (BBB in my case) and lets me debug it.
So now a gazillion things have been done behind my back... none of which is explained.
If I right click on a project, and select Debug As... Code Composer Debug Session, it does the EXACT same thing.
If I instead select Debug Configurations, I get a different screen. Let's look at it, as I have three projects open.
Pick one: TestNDK
That project has a ccxml in the root named "TestNDK-xds.ccxml" Well the dialog shows me ${target_config_active_default:TestNDK}.
Close, but not a match... where does it get these values? I can find nothing in the project properties | Debug section, or anywhere else, that maps ${target_config_active_default:TestNDK} to the TestNDK-xds.ccxml
When I open the ccxml file, I get a completely different page. Absolutely nothing in common.
I can see it allows me to pick the MCU. And the advanced setting has a bunch of settings that I can find no help on.
I see the BBB/A8 setting has a GEL file, but the path is relative. TO WHAT? Apparently something NOT related to the project.I had to hunt it down... And it's 1000's of line that look like C code and contain stuff that I see in Starterware header files.
I also read years ago that the environment was moving away from GEL files. Of course trying to find that old doc page would be nearly impossible.
If I change the MCU, the GEL file is erased. Where does it get the GEL files, and what happens if there isn't one? Do I have to make one by hand?
Lets now look at the project IoT-Test...
This is a mess, nothing matches.
The debug dialog has all four cores checked.
Of course, it claims the ccxml file is part of the project. ${target_config_active_default:IoT-Test} But I have no idea what name it THINKS it is supposed to be.
The ACTUAL file located in the targetConfigs folder is named BeagleBone_Black.ccxml. Which is the one under the dialog as XDS100v2 (the name of the JTAG device connected to it).
Where in the project IoT-Test does it know to use that ccxml file?
It gets worse.
If I click Target tab, it says the device is IcePick... Unless I click a different...? What? (That window on the left has no name.)
I click TestND... then click back to IoT-Test... when I click back it's set to M3_wakeupSS_0
Neither of which is correct.
So, this setting is wrong. And yet the environment magically knows what settings I want to use when debugging this project. Based on some environment variable that doesn't exist.
And to complicate matters...
The IoT-Test project, when I start it, it loads the code into the device. It is using that ccxml file. Which is what is expected.
And that has an ccxml file name of BeagleBone_Black.ccxml...
But the list in that "Debug" dialog (whatever it is...) also shows a XDS100V2. And THAT entry is the one that points to a BeagleBone_Black.ccxml.
Okay, so maybe IoT-Test magically knows to use that BeagleBone_Black.ccxml file, instead of whatever that environment variable name is.
And yet, it doesn't have anything in the project or program settings. So it knows to use some setting, and even knows to load the program when it is not set to...?
To make things more confusing there is another huge project that cannot be loaded automatically. It MUST be "connected" in the debug perspective when the device powers up. It uses the XDS100v2 setting, which ALSO has no setting in the project/program. And it DOES NOT load the program (which is behavior I want)
Why does one configuration without a project/program setting know to load it anyway, but another knows NOT to?
And this is just a start of what I cannot understand or figure out...
