AM6442: Best Practices for applying patches to CCS projects / version control with CCS

Nick Saulnier

Part Number: AM6442

Hello team,

I am starting to publish MCU+ examples, where the customer would apply a patch file to their MCU+ project. As a Linux guy, CCS development is still new to me. Before documenting the process of applying patches in Windows, I wanted to check on whether there are any best practices the team has developed.

Usecases that will be documented:
Windows 10 running CCS
Ubuntu 18.4/22.4 running CCS

Questions:

1) Is there a best practice for applying patches to CCS projects? Does CCS have the ability to understand and apply patch files? If not, is there a suggested process? (e.g., download git for Windows / Linux, use git apply to apply the patch, then open the project in CCS? What if the project is currently open in CCS, does it need to be closed before applying a patch? etc)

2) Code version control: Does CCS have a concept of version control? Are there any best practices around creating commits, pushing and pulling to remote repositories to apply updates to the projects open in CCS, etc?

Thanks!

over 2 years ago

0 Ki over 2 years ago

TI__Guru**** 463041 points

Hello,

CCS/Eclipse support Git via EGit. The ability to create and apply patches would be supported this way:

Please see the below links for more details:

https://www.eclipse.org/egit/

https://dev.ti.com/tirex/explore/node?node=A__AA2SpDwBBS0oZ2.tVUWlyA__ccs_devtools__FUz-xrs__LATEST

Thanks

0 Nick Saulnier over 2 years ago in reply to Ki

TI__Guru** 100640 points

Hello Ki,

Thank you for pointing to this document, I was unaware of the eGit option.

I am trying to wrap my head around the typical customer flow for a Windows customer. Here's my initial thoughts.

a) is there anything you would do differently?
b) Am I trying to do things through the git bash terminal that make more sense to do in CCS?
c) Would CCS have issues if we make the entire MCU+ SDK a git repo, instead of a single project the git repo?

1) Install MCU+ SDK

2) Install Git for Windows

3) Use git bash to turn the entire MCU+ SDK into a git repo (not just a single project), as described here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1133505/faq-tda4vm-best-practices-for-version-tracking-for-ti-s-sdk

4) use git bash to create the initial commit, create a feature branch, and checkout the feature branch

5) In CCS, import a version controlled CCS project with File->Import->Git->Projects from Git

Regards,

Nick

0 Ki over 2 years ago in reply to Nick Saulnier

TI__Guru**** 463041 points

Nick Saulnier said:
I am trying to wrap my head around the typical customer flow for a Windows customer. Here's my initial thoughts.

Unfortunately I don't have much best practices or experiences to share. I have not used EGit much with CCS projects. I do have some CCS projects in a git repo and I tend to use git bash terminal outside CCS for my git actions. Customers are certainly using EGit in CCS but I don't have much details what the exact use cases are.

Processors

Processors forum

AM6442: Best Practices for applying patches to CCS projects / version control with CCS