Tool/software: Code Composer Studio
Just to clarify: The problem is not where we decide to put our workspaces as that is a personal preference. The problem with the design of how this works is where code composer puts modified files including the motorware lab project configuration files after you start a lab. It is not completely putting project configuration files that end up being modified in the workspace. If you install Code Composer and Motorware from scratch, you have to manually make the same changes to the lab projects again. Sure, you can create a brand new project in your designated folder that you use GIT to maintain and copy all the source files there. But if you want to keep track of changes you made to labs with GIT, it is not feasible to put the entire ti folder with motorware installed under GIT control. It is also not worth the effort to try to extract all the necessary files from motorware and put them in a place more easily maintained by GIT as it confuses Code Composer. In my opinion, the files under motorware or c2000 should be considered read only and any files written to should be stored where they can be managed with source control like GIT. Motorware and c2000 folders should only change with ti updates.