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.

PDK project not compiling

Hi,

I was making use of PDK_1_0_0_14 with my CCS v5.  I had the PA example project imported to my workspace and was compiling code with it and making changes to the code. I upgraded my MCSDK to now have PDK_1_0_0_19 instead and I am trying to make changes to the project build setup so that it makes use of the newer PDK 19 as opposed to 14. I thought that may be better than to try and import the new pdk projects into the workspace and end up having two of each project one tied to pdk version 14 and the other version 19. Here is the outline of what I have done:

a) I went into properties -> resources->linked Resource->path variables and changed the pdk_***_14 names to pdk_****_19.

b) under properties -C/C++ build ->Settings->Tool Settings->c6000 compiler->include options it has some dirs added to #incldue search path which include

"${PASS_INSTALL_PATH}", "${PASS_INSTALL_PATH}/ti/drv/pa/example/multicoreExample"; "${PDK_INSTALL_PATH}/ti/drv/cppi" and also one for qmss

Now the values of this PASS and PDK_INSTALL_PATH is somehow set to PDK_1_0_0_14 as opposed to PDK_1_0_0_19 as I am discovering from looking through the compile log. I am taking it that these paths are not set by the path variables under "resources" but rather by the pdksetupenv.bat which configures the pdk build environment. Is that correct? If it is why is that as I would think that the environment is for the purpose of compiling the PDK libraries such as the PA LLD etc?

Also under properties ->C/C++ General->Paths and Symbols->Include, I have some include dirs that point to pdk 14 but I am not sure how I can edit them as that option is not highlighted. What is purpose of the C/C+General paths and symbols and how does that differ from the include path under settings under C/C++ Build?

How should I go about handling my compile issue?

Thanks, Aamir

  • Aamir,

    First of all, the version of pdk used by the project is set in Project->Properties->General in the RTSC tab.  You are correct the path and build variables all have to align to this as well, but check these project settings as your project is still likely set to use the other tool versions.

    Regarding the difference between and proper include procedure, have a look at this wiki.

    http://processors.wiki.ti.com/index.php/Include_paths_and_options

    Please keep us informed whether this helps clarify everything.

    Best Regards,
    Lisa

  • Lisa,

    I had forgotten to mention, under Project->Properties->CCS Build in the RTSC tab I had clicked on the PDK 19 version as opposed to 14 which was the previous ticked box but it still has pdk 14 in the include during the compile. This include is coming from the the following I believe under Properties->C/C++ Build->Settings and under the tools setting tab right clicking the "c6000 compiler" which shows:

    -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi

    I had a look at the wiki you mentioned but did not see anything that stood out to me to fix.

    I am showing the output of the compile too:

    **** Build of configuration Debug for project PA_multicoreExample_exampleProject ****

    C:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake -k all

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_example.cfg'

    'Invoking: XDCtools'

    "C:/Program Files/Texas Instruments/xdctools_3_22_01_21/xs" --xdcpath="C:/Program Files/Texas Instruments/ipc_1_23_01_26/packages;C:/Program Files/Texas Instruments/bios_6_32_04_49/packages;C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r debug -b "C:/ccsv5new/PA_multicoreExample_exampleProject/.config/xconfig_multicore_example/config.bld" -c "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_example.cfg"

    making package.mak (because of package.bld) ...

    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...

    configuring multicore_example.pe66 from package/cfg/multicore_example_pe66.cfg ...

    Warning: xdc.cfg.INCOMPATIBLE_TARGET_VERSION: current target 'ti.targets.elf.C66' [1,0,7.2,1] is not compatible with targets used to build the following packages; package ti.csl [in C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/csl/] was built using 'ti.targets.elf.C66' [1,0,7.3,1]

    ; package ti.drv.qmss [in C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/qmss/] was built using 'ti.targets.elf.C66' [1,0,7.3,1]

    ; package ti.drv.cppi [in C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/cppi/] was built using 'ti.targets.elf.C66' [1,0,7.3,1]

    ; package ti.drv.pa [in C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/] was built using 'ti.targets.elf.C66' [1,0,7.3,1]

    cle66 package/cfg/multicore_example_pe66.c ...

    'Finished building: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_example.cfg'

    ' '

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/cppi/device/cppi_device.c'

    'Invoking: C6000 Compiler'

    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi --preproc_with_compile --preproc_dependency="cppi_device.pp" --cmd_file="./configPkg/compiler.opt" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/cppi/device/cppi_device.c"

    'Finished building: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/cppi/device/cppi_device.c'

    ' '

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/cppi_qmss_mgmt.c'

    'Invoking: C6000 Compiler'

    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi --preproc_with_compile --preproc_dependency="cppi_qmss_mgmt.pp" --cmd_file="./configPkg/compiler.opt" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/cppi_qmss_mgmt.c"

    'Finished building: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/cppi_qmss_mgmt.c'

    ' '

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/cpsw_mgmt.c'

    'Invoking: C6000 Compiler'

    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi --preproc_with_compile --preproc_dependency="cpsw_mgmt.pp" --cmd_file="./configPkg/compiler.opt" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/cpsw_mgmt.c"

    'Finished building: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/cpsw_mgmt.c'

    ' '

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_example.c'

    'Invoking: C6000 Compiler'

    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi --preproc_with_compile --preproc_dependency="multicore_example.pp" --cmd_file="./configPkg/compiler.opt" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_example.c"

    'Finished building: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_example.c'

    ' '

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_osal.c'

    'Invoking: C6000 Compiler'

    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi --preproc_with_compile --preproc_dependency="multicore_osal.pp" --cmd_file="./configPkg/compiler.opt" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_osal.c"

    'Finished building: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/multicore_osal.c'

    ' '

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c'

    'Invoking: C6000 Compiler'

    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi --preproc_with_compile --preproc_dependency="pa_mgmt.pp" --cmd_file="./configPkg/compiler.opt" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c"

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 176: error: identifier "mSize" is undefined

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 448: warning: variable "coreNum" was set but never used

    >> Compilation failure

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 1188: error: identifier "pa_PATCH_OP_DELETE" is undefined

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 1163: warning: variable "rxQInfo" was declared but never referenced

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 1244: warning: variable "coreNum" was set but never used

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 1410: error: struct "<unnamed>" has no field "nUsrStats"

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 1464: warning: subscript out of range

    "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c", line 1530: warning: variable "portNum" was declared but never referenced

    3 errors detected in the compilation of "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/pa/example/multicoreExample/pa_mgmt.c".

    gmake: *** [pa_mgmt.obj] Error 1

    'Building file: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/qmss/device/qmss_device.c'

    'Invoking: C6000 Compiler'

    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv64+ -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/pa/example/multicoreExample" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/cppi" --include_path="C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_14/packages/ti/drv/qmss" --diag_warning=225 --mem_model:data=far --abi=eabi --preproc_with_compile --preproc_dependency="qmss_device.pp" --cmd_file="./configPkg/compiler.opt" "C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/qmss/device/qmss_device.c"

    'Finished building: C:/Program Files/Texas Instruments/pdk_C6678_1_0_0_19/packages/ti/drv/qmss/device/qmss_device.c'

    ' '

    gmake: Target `all' not remade because of errors.

  • Hi Aamir,

    can I also just verify that you did correct and update the path as per the wiki I sent you?   There are two places in CCS to add include paths and unfortunately only the one place will end up actually pulling in the path ...  There is a generic eclipse one (which you seem to keep referencing) and the one from CCS and our compiler tools (as shown in the wiki)

    Best Regards,

    LIsa

  • Lisa,

    I think the problem is the view I see under properties differs from those shown in the wiki pages you talk about. So I am not able to make probably the appropriate changes.

    Here is mine with the settings highlighted.

    Aamir

    I believe the issue is something to do with the macro.ini files in the project directory in the workspace that I am using.

     

  • Aamir,

    what exact version of CCS are you using?  What OS? That may be part of the problem/confusion here.

    Best Regards,

    Lisa

  • Lisa,

    My version of CCS is v5.0.1.201105110900 according to help under CCS.

    My OS on my PC is Windows XP

    I have tried creating a new workspace and interestingly enough my old workspace that was working with compiling PDK projects, I though I had imported using Import->CCS -> existing CCS/CCE legacy projects but that would then have the term "CCS" on top of the folder next to the name of the project in the project view. However, what I see in my old workspace is the term "RTSC" which is generated when one makes use of the import->general->Existing project into workspace.

    When I try using the CCS import, and try to build or cleaning the project, I get the following error:

    **** Clean-only build of configuration Debug for project PA_emacExample_exampleProject **** 

    (Cannot run program "make": Launching failed)

    Thanks, Aamir

  • Hi Aamir,

    it could be your CCS version, which is an old beta version.

    I would please

    - try the current released version, CCS v5.1.1

    - do not use the generic import.  Please make sure to use the CCS project import and a fresh workspace.

    Keep us posted how that goes.

    Best Regards,
    Lisa

  • testing  ability to post - please ignore

  • Lisa,

    I was having issues posting due to some firewall settings.

    Thanks for the reply. I upgraded my CCS to v5.1.1 as you suggested and then just went about importing the project under PDK 1_0_0_19 instead as a CCS project and ont copying the project to the workspace and got it to compile and build okay. I will try the trick of updating the project to make use of a newer version of the PDK when and if that gets updated again by TI. I did have some licensing issues first though. I previously was using a v4.0 license file with my older version of CCS v5.0.1 when I activated the license and copied the license file to my CCS directory. When I upgraded to ccs v5.1.1 I was no longer able to make use of the same license and had to then use my other license file for v5 that we had. Can you explan why?

    Thanks, Aamir

  • Hi Aamir,

    yes this is easy to explain.  CCSv5 requires a v5 license and will not work with a v4 license.  A CCSv5 license however, will work with v4 so that you can continue to use v4 as well.

    If you have an active subscription, you can upgrade to a v5 license by doing the following.  Otherwise you will unfortunately need to purchase a license or, if possible for your development, use a setup that would allow you a free license.  I have posted the licensing wiki for you as well below.

    • Go to www.ti.com/myregisteredsoftware
    • Find your row for TMDSCCS-ALLF03-v4.0
    • Click MANAGE and then click UPGRADE – GET NEW LICENSE
    • Click E-mail license - you will receive two (2) emails: Instructions and License File with attachment (.lic)
    • You MUST follow these instructions to save this new License File (.lic) before you can use your upgraded version 5.1

    http://processors.wiki.ti.com/index.php/Licensing_-_CCS

    Hope this helps.

    Best Regards,

    Lisa

  • Please ignore - just testing ability to post again.