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.
Tool/software: Code Composer Studio
So, I renamed a project. Using the "Rename" option in CCS 7.7 It was a Sitara, BBB project.
Boy THAT was a major mistake... Now, of course, it's broken. CCS can't debug it. Says the device is held in reset... That's BS. I've had to put up with this defect before...
After trying to gut some settings in the project, because the environment cannot do it for itself, now I get this when I press the Debug button:
Of course it can't find it. THERE IS NO PROJECT OF THAT NAME. THERE NEVER WAS IN MY "WORKSPACE V7" FOLDER.
THAT IS NOT THE PROJECT I AM EVEN WORKING ON.
What is wrong??? Why does it think it needs something THAT DOES NOT AND NEVER EXISTED?
So, I go back to the beginning, and import a fresh, untouched example project for BBB directly from the PDK. Build it, and try to launch the debugger.
SAME THING.
Literally 90% of the time I try to do something, it's broken.
Yes I've tired the "-clean" option. And a long list of other things. But whatever is broken is very well hidden, preventing me from figuring it out and solving it.
-CSW
Hi Chris,
Sorry for all the pains you are experiencing with CCS.
It looks like come issues with the refactoring and the debug launch data.
Christopher Weber said:So, I go back to the beginning, and import a fresh, untouched example project for BBB directly from the PDK. Build it, and try to launch the debugger.
Can you again try this using a new CCS workspace folder and also do steps 3-5 listed in:
http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv7#Debugger
Basically clean out your launch, debug and target config caches
Thanks
ki
Well, I got it working. Not sure how. I manually created a target config file, but now it's in the *wrong* place for it to work. It's not in the "targetconfigs" folder.
I have already done a "Clean", and delete the target config files. I didn't want to delete the .launch, or other files out of fear it would mess things up. But apparently something was already messed up.
I created a new project from scratch, and it worked ok. So, it was only when importing an example, or whatever it was I screwed up.
I go through this *every time* I try to rename a project. :-(
Why do I rename a project? Because I take a sample, modify it to get it working, then I want to take the same original project and modify it in a different manner before attempting to merge them.
I *really* wish you would fix this. Renaming a project is supposed to be a simple step. And everytime I do it, it's a setback of several hours (or days) trying to unravel what's broken.
-CSW