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.

CCS: Importing Legacy CCS V3.3 project to CCS V8.1

Tool/software: Code Composer Studio

I seem to be getting closer. I am getting a linker error indicating a library cannot be found. But, the library file is in a path that is included in the link command line:

 Building target: "C:/OBVP-GCBR/THAAD/CODE/Control DSP/CP_FLASH/../Debug/T4_CP_Build.out"

Invoking: C2000 Linker

"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/bin/cl2000" -v28 -ml -mt --advice:performance=all --define=_DEBUG --define=LARGE_MODEL -g --diag_wrap=off --display_error_number --c_src_interlist --asm_directory="C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug" --obj_directory="C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug" -z -m"C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/T4_CP_Build.map" --stack_size=0x400 --warn_sections -i"C:/OBVP-GCBR/THAAD/CODE/Control DSP/lib/Flash2812_API_V210/lib" -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/lib" -i"C:/OBVP-GCBR/THAAD/CODE/Control DSP/CP_FLASH" -i"C:/OBVP-GCBR/THAAD/CODE/Control DSP" -i"C:/ti/ccsv8/tools/compiler/ti-cgt-c2000_18.1.2.LTS/include" --reread_libs --diag_wrap=off --display_error_number --xml_link_info="CP_FLASH_linkInfo.xml" --rom_model -o "C:/OBVP-GCBR/THAAD/CODE/Control DSP/CP_FLASH/../Debug/T4_CP_Build.out" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_AngSpeed.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_BIT.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_FOC.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_Fault.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_HWS.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_ISR.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_MsgProcessor.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/app_PI.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_adc.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_can.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_canC.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_flash.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_isr.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_pwm.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_sci.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_spi.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_sysctrl.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/bsp_timers.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/global.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/main.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/Debug/vector.obj" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/CP_FLASH.cmd" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/lib/Flash2812_API_V210/lib/Flash2812_API_V210.lib" "C:/OBVP-GCBR/THAAD/CODE/Control DSP/lib/IQmath/v15a/lib/IQmath.lib"  -lrts2800_ml.lib -llibc.a

<Linking>

"C:/OBVP-GCBR/THAAD/CODE/Control DSP/CP_FLASH.cmd", line 66: error #10008-D: cannot find file "Flash2812_API_V210.lib"

"C:/OBVP-GCBR/THAAD/CODE/Control DSP/CP_FLASH.cmd", line 67: error #10008-D: cannot find file "Flash2812_API_V210.lib"

 

The library file “Flash2812_API_V210.lib” is located in folder “C:/OBVP-GCBR/THAAD/CODE/Control DSP/lib/Flash2812_API_V210/lib”.

  

Also, I unchecked “ XDAIS” in the Products tab and checked the “XDCtools” and I get the following warnings. Is this a problem?

 

Description         Resource             Path       Location               Type

Build-variable 'XDAIS_CG_ROOT' cannot be resolved. This project may not build as expected.    CP_FLASH                           properties           Problem

Invalid project path: Include path not found (\packages\ti\xdais).            CP_FLASH                           pathentry            Path Entry Problem

Invalid project path: Include path not found (C:\OBVP-GCBR\THAAD\CODE\include).     CP_FLASH                           pathentry            Path Entry Problem

 

Thanks for your help!

 

  • Terry,

    Does CP_FLASH.cmd have -l statements on lines 66 and 67 that are attempting to include the library?

    If so I would comment out those lines from the CP_FLASH.cmd since it looks like your build settings are including the same library directly.

    As far as the other items:
    1) Build-variable 'XDAIS_CG_ROOT' cannot be resolved. This project may not build as expected.
    Assuming you are not using XDAIS this should not be an issue.

    2) Invalid project path: Include path not found (\packages\ti\xdais).
    Assuming you are not using XDAIS you could take a look at the include paths and see if that is listed and just remove it

    3) Invalid project path: Include path not found (C:\OBVP-GCBR\THAAD\CODE\include).
    Just remove this one from the list of include paths .

    Regards,
    John
  • The CP_FLASH.cmd file is defining the memory configuration and references the library as follows:
    SECTIONS
    {
    /***********************************************************************************
    Program Areas
    ************************************************************************************/
    .text : > FLASH, PAGE = 0
    .slow : > FLASH, PAGE = 0
    .cinit : > FLASH, PAGE = 0
    .econst : > FLASH, PAGE = 0
    Flash28_API:
    {
    Flash2812_API_V210.lib(.econst)
    Flash2812_API_V210.lib(.text)
    } LOAD = FLASH,
    RUN = RAML0,
    LOAD_START(_Flash28_API_LoadStart),
    LOAD_END(_Flash28_API_LoadEnd),
    RUN_START(_Flash28_API_RunStart),
    PAGE = 0
    IQmathTables : LOAD = FLASH, PAGE = 0
    IQmathTablesRam : LOAD = FLASH, PAGE = 0
    IQmath : LOAD = FLASH, PAGE = 0
    .const : > FLASH, PAGE = 0
    .switch : > FLASH, PAGE = 0
    .reset : > FLASH, PAGE = 0 /* Branch on reset to */
    .branch : > RV, PAGE = 0 /* .text start location */
    CsmPwlFile : > CSM_PWL, PAGE = 0 /* CSM Password Locations */

    /***********************************************************************************
    Data Areas
    ************************************************************************************/
    .stack : > RAMM1, PAGE = 1
    .bss : > RAMH0, PAGE = 1
    .ebss : > RAMH0, PAGE = 1
    .sysmem : > RAMH0, PAGE = 1

    }

    Thanks for any guidance.
  • Ok.  In that case can you check the file search path options for the linker and make sure that 

    C:/OBVP-GCBR/THAAD/CODE/Control DSP/lib/Flash2812_API_V210/lib/Flash2812_API_V210.lib

    Is listed before 

    C:/OBVP-GCBR/THAAD/CODE/Control DSP/CP_FLASH.cmd

    Something like this (your options would list a lot more files, I just created this for reference).  You can use the up down arrow to change the order.

    My thought is that the library needs to be found prior to the linker command file referencing it.

    Regards,

    John

  • JohnS - I tried your suggestion to modify the "File Search Path" to include the library followed by the command file and it did not change the results. I have another simple question - how does the CCS V8.1 determine the order of the files to compile and link? There is a file in the project that builds correctly in CCS V3.3 called Debug.lkf that has the files being linked in the correct order with the CP_FLASH.cmd file being last. Thanks for ant insight you can provide.

    Terry
  • Terry,

    Link order control is different in newer CCS versions. There is the ability to control the specific order and it is worth trying here. This video shows how to access the link order control and you could try using that to see if it helps.

    www.youtube.com/watch

    Regards,
    John
  • Terry,

    Did you manage to get things going?

    John
  • Terry,

    I am going to close off this thread. I see the new thread specifically on Link order that we will continue to work on.

    Regards,
    John