Other Parts Discussed in Thread: TMS320F280025C, C2000WARE
Just wasted several hours because I could not connect to my Launcpad, i did find a small known error in the debugger setup when inporting from CS200ware. Solved by this video Change the Debug Probe in example projects
When testing connection from within the target config editor (ccxml) The connection now was fine and working.
I then spend 2 hours figuring out why I still could not flash.
The project that i was testing with is the led_ex1_blinky
Because I am using the Launch pad board i changed the Active build config to CPU1_LAUNCHXL_FLASH, fine and dandy it defines the _LAUNCHXL_F280025C macro as described i need to in the board manual.
After having tried out a lot of different things, i finally found the problem
When you have selected the CPU1_LAUNCHXL_FLASH build configuration the files under targetconfigs looks like this
Well yes as soon as you know it, it is obvious where the problem is. But because the TMS320F280025C.ccxml is greyed out and icon has the unused slash over it, i never looked closer at the name.
And i did not notice the [active] remark in the graphically disabled filename....
This kept be busy for more than two hours....
Until I realized this contradiction in the GUI, and right clicked and selected the correct one as being active.
Please either fix CCS so it respects the excluded from build setting and follows the build configuration.
Or do not set this attribute on the ccxml files in the build configurations of your examples, it is only making the pour developers cry out in confusion.
My setup:
Code Composer Studio
Version: 10.2.0.00009
/C2000Ware_3_04_00_00
Windpws 10
