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.

TMS320F280023C: driverlib in git

Part Number: TMS320F280023C

Hi

I am getting close to finish my project, and are looking into how to have things stored in a final way.

I have been using the driverlib drivers a lot for this project, unfortunately I needed to do a few changes to the driverlib, both the c-sources and some of the javascript.

Example of this here: Feature request SysConfig should expose more configs in defines in board.h

And here: Bug in new 4.0.0.0 C2000 ware.

Now I can of course put those changes into my code and version control. but then next time there is an update from TI of the libs, and I decide to take this update in the horror show starts. Now I have to do some merge magic to ensure i get the changes from TI, but keep the patched I added. = lot of work.

If TI exposed a git repository with the sources, I could branch of of this in my git repository, and have git keeping track of my patches vs. TI patches.making the steup to a new release so much easier. Of course I can emulate this in my own git repo by carefully maintaining a branch with TI releases including manually updated information of the release date/number a.s.o. and manually copy new releases in there and do merges but again = lot of work.

An added benefit if TI uses a platform like github or gitlab or git*** that has a concept of pull-requests, I could post changes like those from the examples above and TI could then easily decide to pull in this change or skip it.

  • Martin,

    Relgarding exposing a git repo , will have to bring this up with other stake holders including the legal team and see if we can go ahead.  Will take some time to align on this topic.

    For now, you can maintain your own repo and maintain the changes and merge it as necessary with TI released code. 

    Best Regards

    Siddharth

  • I do understand that you have to pass it by legal, i work in a larger org. too.

    But that said I don't see any legal issues here as you do not need to expose more in such git repo than you already do on the download section. Just because it is a git repo it does not mean tat it has to be the one where you also do your development work in. So you are entirely free to chose what to expose in such repo, and it does not require you to put anything in there that is not already in the download packages that you provide now.

  • Martin, 

    I understand but it will take some time to discuss with all the stake holders and seek their opinion on this. Will keep you posted.

    Best Regards

    Siddharth