Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 9767 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

How does CCS decide which linker command file to use?

Tom51266
Prodigy 20 points
Other Parts Discussed in Thread: HALCOGEN

I am using CCS 4.1.2 and have created a simple project.  When the project was created it placed a sys_link.cmd file in my project directory.  I am slo using the HalCoGen tool to generate the HAL code for our TI eval board.  I put the HalCoGen code that was generated in a subdirectory under the project directory.  The HalCoGen tool also created a sys_link.cmd file. 

When I look at the files in CCS in the C/C++ Projects window, it indicates that the sys_link.cmd file produced by CCS is 'Excluded From the build'.  I have also verified that the sys_link.cmd file in the HalCoGen subdirectory is in fact the one being used.  I can't seem to find anywhere in the build settings or anywhere else that will let me configure the linker command file to use.  So as the subject states: How does CCS choose which one to use?  And can I configure a build to use a specific linker command file?

 

Thanks in Advance

Tom

  • 0
    TI__Guru**** 437691 points

    If you have multiple linker command files in your project folder, it passes all the command files to the compiler but will place the sections as specified in the first command file passed to it (at least that is what I see). However if you have memory regions defined in the different cmd files where he ranges overlap, you will get a linker error.

    You can also specify a cmd file in the CCS Build Properties (right-click on project and the select CCS Build in the left panel, then see the Linker Command File field). When you do this, it will add the cmd file to your project if it is not there already. If it is there already and there are multiple cmd files in your project, it will exclude the others in the project from the build. But afterwards, if you un-exclude the other cmd file or add new ones, then you will get the scenario I described above where all the cmd files will be passed to the compiler/linker

  • 0
    Prodigy 20 points

    Thanks- I must have never looked under the CCS Build  options, only the C/C++ Build options.

    Tom