• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 14035 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.

Unable to add custom linker.cmd file to CCS4 DSP/BIOS project

chandrashekhar mishra
Intellectual 915 points

Hi,

I need to define custom DATA_SECTION to my DSP/BIOS project for that I need to define custom sections in linker.cmd file but when I am trying to add and compile the code I get "unrecognised file" error.

I was trying to add the linker.cmd file to by right click on project and using "Add files to project option " but it pops up message box with error "Can not Add: linker.cmd".

Is I am missing anything ?

Regards,

Chandra Shekhar Mishra

 

  • 0
    TI__Mastermind 32475 points

    Chandra,

    What versions of CCS and BIOS are you using?

    Judah

  • 0 in reply to judahvang
    Intellectual 915 points

    Hi,

    I am using CCS version 4.1.3.00038 and DSP/BIOS version 5.41.03.17.

     

    Thanks

    Chandra Shekhar Mishra

  • 0 in reply to chandrashekhar mishra
    TI__Mastermind 32475 points

    Chandra,

    Unfortunately you can't add a linker command file into your project.  I believe in newer versions of CCS this is possible but not in CCS 4.1.x.

    The way to get around this is to do the following.  Note:  I'm doing this with CCS 4.2 but I think it should be very similar if not the same.

    1.  Assuming that you added your own linker.cmd file name mylink.cmd into the project directory.

    2.  The file will show up in the CCS project window as one of your sources.  You need to right click it and select "Exclude File(s) from Build"

    3.  Next Select "Project Properties"

    4.  It will bring up the Properties for your project and select "C/C++ Build".  You should see a "Tool Settings" tab.

    5.  Expand the "Linker" options.  You should see "File Search Path".

    6.  Add your "mylink.cmd" to the "Included library file or command file ..."

    7.  Add "${PROJECT_ROOT}" to the "library search path...".  Then click Apply.

    The linker command file should be included in the build.

    Judah

  • 0 in reply to judahvang
    Intellectual 915 points

    Hi Judah,

    I followed the method described by you in previous post but unable to compile the code. I am getting follwing error,

    -------------------------------------------------------------------

    'Building target: DSPFirmware.out'

    'Invoking: Linker'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -@"ccsLinker.opt" -o "DSPFirmware.out"

    <Linking>

    fatal error: unrecognized file:

    "F:/DashLite/CCS_Workspace/DSPFirmware/ccs4/linker.cmd"

     

    >> Compilation failure

    C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** [DSPFirmware.out] Error 1

    C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: Target `all' not remade because of errors.

    Build complete for project DSPFirmware

    ------------------------------------------------------

    Please advise.

    Regards,

    Chandra Shekhar Mishra

  • 0 in reply to chandrashekhar mishra
    TI__Mastermind 32475 points

    Chandra,

    Did you specify to "excluded from build" the linker.cmd?  Because it seems like the project is still trying to build this file.

    Could you paste the whole linker command in your build console.  Mine looks something like this.  Notice the "mytest.cmd" is added to the link step.

    'Building target: bios5_test1.out'
    'Invoking: Linker'
    "C:/Program Files/Texas Instruments/ccsv4.2.3/ccsv4/tools/compiler/c6000/bin/cl6x" -mv64+ -g --diag_warning=225 --abi=coffabi -z -m"bios5_test1.map" --stack_size=800 --heap_size=800 --warn_sections -i"C:/Documents and Settings/a0783947/My Documents/workspacev4.2.3/bios5_test1" -i"C:/Program Files/Texas Instruments/ccsv4.2.3/ccsv4/tools/compiler/c6000/lib" -i"C:/Program Files/Texas Instruments/ccsv4.2.3/ccsv4/tools/compiler/c6000/include" -i"C:/Program Files/Texas Instruments/ccsv4.2.3/bios_5_41_10_36/packages/ti/rtdx/lib/c6000" -i"C:/Program Files/Texas Instruments/ccsv4.2.3/bios_5_41_10_36/packages/ti/bios/lib" --reread_libs --rom_model -o "bios5_test1.out" -l"./semaphorecfg.cmd"  "./semaphorecfg_c.obj" "./semaphorecfg.obj" "./semaphore.obj" -l"libc.a" -l"mytest.cmd"
    <Linking>

    I've attached an image below which shows my project settings:

  • 0 in reply to judahvang
    Intellectual 915 points

    Hi Judah,

    I also attached image below which shows my project settings. You can see in left hand side, I excluded linker.cmd file from build.

     

    2654.linker.rar

    I zipped and attched  linker .cmd and image file for your reference.

    Thanks and Regards,

    Chandra Shekhar Mishra

     

     

  • 0 in reply to chandrashekhar mishra
    TI__Mastermind 32475 points

    Could you paste your build command for the linker from your build console?

    I'm not sure what else could be causing the problem.

    I might recommend to move this posts to the CCS forum because its more a CCS project issue at this point.

    Judah

  • 0 in reply to judahvang
    TI__Guru**** 161575 points

    Adding more than one linker command file to a project is possible in CCSv4.1.3.  I just verified this.  You can right click on a project and select "Add Files to Project..."  You can select a cmd file and it will add it to the project.

    You can also do it from the build options like judahvang showed in his screen capture.

    Note that in the screen capture you sent you have it added both ways.  You have linker.cmd added to your project (but excluded) and you have it specified in your build options.  So it is not actually excluded.   Any cmd files that are part of your project CCS will pass to the linker unless then are excluded but it will also pass the ones that are listed in your build options.

     

    John

  • 0 in reply to judahvang
    Intellectual 915 points

    Hi Judah,

    I dumped full buid console option in text file and attached it for reference.

    0624.Build_console.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    **** Build of configuration Release for project DSPFirmware ****
    C:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake -k all
    'Building file: ../DSPFirmware.tcf'
    'Invoking: TConf Script Compiler'
    "C:/Program Files/Texas Instruments/xdctools_3_16_02_32/tconf" -b -Dconfig.importPath="C:/Program Files/Texas Instruments/bios_5_41_09_34/packages;" "../DSPFirmware.tcf"
    'Finished building: ../DSPFirmware.tcf'
    ' '
    'Building file: F:/DashLite/CCS_Workspace/DSPFirmware/src/CAbortHandler.cpp'
    'Invoking: Compiler'
    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6740 -g -O3 --define=CHIP_C6748 --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="C:/c674x-dsplib_1_03_00_01/include" --include_path="C:/C6748_dsp_1_00_00_11/pspdrivers_01_30_01/packages" --include_path="F:/DashLite/CCS_Workspace/DSPFirmware/ccs4/../bsl/inc" --include_path="F:/DashLite/CCS_Workspace/DSPFirmware/ccs4/../inc" --include_path="F:/DashLite/CCS_Workspace/DSPFirmware/ccs4/Release" --include_path="C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/bios/include" --include_path="C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/rtdx/include/c6000" --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --diag_warning=225 --preproc_with_compile --preproc_dependency="CAbortHandler.pp" "F:/DashLite/CCS_Workspace/DSPFirmware/src/CAbortHandler.cpp"
    'Finished building: F:/DashLite/CCS_Workspace/DSPFirmware/src/CAbortHandler.cpp'
    ' '
    'Building file: F:/DashLite/CCS_Workspace/DSPFirmware/src/CAnalogModuleInterfaceHandler.cpp'
    'Invoking: Compiler'
    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/bin/cl6x" -mv6740 -g -O3 --define=CHIP_C6748 --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --include_path="C:/c674x-dsplib_1_03_00_01/include" --include_path="C:/C6748_dsp_1_00_00_11/pspdrivers_01_30_01/packages" --include_path="F:/DashLite/CCS_Workspace/DSPFirmware/ccs4/../bsl/inc" --include_path="F:/DashLite/CCS_Workspace/DSPFirmware/ccs4/../inc" --include_path="F:/DashLite/CCS_Workspace/DSPFirmware/ccs4/Release" --include_path="C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/bios/include" --include_path="C:/Program Files/Texas Instruments/bios_5_41_09_34/packages/ti/rtdx/include/c6000" --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c6000/include" --diag_warning=225 --preproc_with_compile --preproc_dependency="CAnalogModuleInterfaceHandler.pp" "F:/DashLite/CCS_Workspace/DSPFirmware/src/CAnalogModuleInterfaceHandler.cpp"
    "F:/DashLite/CCS_Workspace/DSPFirmware/src/CAnalogModuleInterfaceHandler.cpp", line 2034: warning: variable "ucSlaveAddress" was set but never used
    "F:/DashLite/CCS_Workspace/DSPFirmware/src/CAnalogModuleInterfaceHandler.cpp", line 2035: warning: variable "arrucCommand" was set but never used
    'Finished building: F:/DashLite/CCS_Workspace/DSPFirmware/src/CAnalogModuleInterfaceHandler.cpp'
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

     Regards,

    Chandra

  • 0 in reply to JohnS
    Intellectual 915 points

    Hi John,

    Now I removed linker.cmd file from project properties and added by right click on project and selected "Add Files to Project..."   but the problem is same. while compiling I am getting same error whatever way I add i.e.

    fatal error: unrecognized file: "../linker.cmd"

    Regards,

    Chandra

  • 0 in reply to chandrashekhar mishra
    TI__Guru**** 161575 points

    What does the ccsLinker.opt file look like?  In that console output file I see paths that have <path>../<more path> I think it is the ../ that is messing things up.  If the linker.cmd is at the root of the project it is not going to find it if there is ../linker.cmd

  • 0 in reply to JohnS
    Intellectual 915 points

    Hi John,

    Earlier I tried putting the linker.cmd file inside ${PROJECT_ROOT}  folder at that time also I got the same error. Later I moved that file to one folder out side to avoid automatic inclusion of linker.cmd file.

    Regards,

    Chandra

     

  • 0 in reply to chandrashekhar mishra
    Intellectual 915 points

    Hi Judah/John,

    I have resolved "unrecognised file" problem. Actually I was editing linker.cmd file by notepad editor instead of by ccs4. This was creating the problem. This problem was explained in below link

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/35531.aspx?PageIndex=2

    Thanks for your support.

    Regards,

    Chandra

     

  • 0 in reply to judahvang
    Prodigy 20 points

    how to exclude? select all?