TMS320F28374D: Helix Perforce

David Peter1

Part Number: TMS320F28374D
Other Parts Discussed in Thread: C2000WARE, CONTROLSUITE

I am trying to use TI CCS with Helix Perforce as a project manager and multi-user tool. There are several problems I am trying to work through.

The first is delineating which files can be part of the CCS structure (such as C2000 files) and which are ones that are user owned and modified. Of particular interest are those files that I take from the CCS file structure and then modify to meet the application needs. These files now are not referenced by the standard path but now become part of the project file structure. A good example are the *.cmd files

Then, knowing what files are user modified and which ones can be from the CCS file structure, how do I

a) Set these files up in CCS to compile properly

b) Set up CCS and Perforce so that only the user modified files are under configuration control

There is a lot of documentation for CCS, and I would imagine somewhere this is addressed, but it is tough for me to find it. I would be happy to review any documentation if you could tell me where to look.

Thanks

Dave

over 5 years ago

0 Ki over 5 years ago

TI__Guru**** 480211 points

Hi Dave,

Regarding CCS project metadata files, there is an article for which such files need to be in version control:

https://software-dl.ti.com/ccs/esd/documents/sdto_ccs_source-control.html

As for which c2000 files can be modified ,etc I will defer to the C2000 experts.

Thanks

0 MatthewPate over 5 years ago in reply to Ki

TI__Guru* 84170 points

Dave,

This has been assigned to the subject expert inside the C2000 team. Due to time zone differences within the team you can expect a reply no later than tomorrow US time.

Best,

Matthew

0 Siddharth Deshpande over 5 years ago in reply to MatthewPate

TI__Mastermind 37005 points

Hi Dave,

Are you re-using files from C2000Ware in your application?

You can organize your CCS project such that all the CCS metadata files are available in separate folder and the C2000 files are organized in a separate folder. In C2000 specific folder, you can have sub folders - one for source files , one for header files and one for linker command files (*.cmd)

It's better to have all the C2000 files under version control.

Let me know if you need any additional info.

Best Regards

Siddharth

0 David Peter1 over 5 years ago in reply to Siddharth Deshpande

Intellectual 720 points

Thanks Siddarth,

There are a few example files that we use as starting points, and these are copied into the workspace with a different name. As far as I can tell, CCS needs access to the files in

C2000

ccs1010

controlSUITE

One way is to path to them (header files etc) and the other is to copy them into the workspace. I can see benefits to both approaches.

If one could put the project properties and all the user defined code under configuration control, and let the compiler use it's own non-user-defined code, that would be one approach. How would one set up such a project?

Thanks

Dave

0 Siddharth Deshpande over 5 years ago in reply to David Peter1

TI__Mastermind 37005 points

Hi Dave ,

I think it's better if you link the files instead of copying them into workspace . In a multi user environment, each user may have a different workspace path and hence if the files are copied to the workspace , it may create a problem.

You can refer to section 6.1.2.2 in the following document which describes adding/linking files to project . Also , for projects that will be shared among multiple users, use relative link paths instead of absolute path.

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_project-management.html

Best Regards

Siddharth

0 David Peter1 over 5 years ago in reply to Siddharth Deshpande

Intellectual 720 points

That is some good info Siddharth, thanks. I have been able to link to the working source code from the workspace, so far it seems to work well.

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMS320F28374D: Helix Perforce