This FAQ is intended to provide general guidelines of version tracking on TIs PDK to make it easier to track and share the code changes between customers and TI support.
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.
Please note that this FAQ takes example of ti-processor-sdk-rtos-j721e-evm-08_02_00_05, but the guidelines remains similar for other Jacinto SDKs as well.
Setting up Git
There are several components in the PDK that are maintained as separate repos on TI side. This section provides details of setting up separate git repos for those components so the repos are similar on TI side and customer side making it easier to share patches.
Initialize a git repo at top level PDK folder.
Do initial commit for each of the repos before you make any changes. This will allow you to share your changes against the original version.
Now we can make the required changes. It’s always a good idea to make a separate branch before making any changes. This way you can always switch to the original version without much effort.
git diff ID1..ID2 > example.patch
Where ID1 is the commit ID of the very first initial commit
Where ID2 is the commit ID of the commit for your changes
git diff master example_branch > example.patch
git diff > example.patch