• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1055 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.

CCS/LINUXEZSDK-SITARA: CCS v7 command line clean build isn't working

Ken Price97
Prodigy 40 points
Part Number: LINUXEZSDK-SITARA
Other Parts Discussed in Thread: CCSTUDIO, SYSBIOS, AM5728

Tool/software: Code Composer Studio

The examples provided on the CCS projects build/create page don't seem to work for a CCS v7 command line build.  for example the "-ccs.buildType clean" option seems to be not working.  For example:

eclipse -noSplash -data workspace_v7/ -application com.ti.ccstudio.apps.projectBuild -ccs.projects <project name> –ccs.buildType clean

that command, when provided with a legfitimate project name in the workspace, yields the following warnings:

!WARNING: Project '–ccs.buildType' was not found in the workspace! Ignoring...
NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.


!WARNING: Project 'clean' was not found in the workspace! Ignoring...
NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.

  • 0
    TI__Guru**** 173310 points

    Can you show the projectBuild command line exactly as you are invoking it (including the project name, etc)?
    Also has the project already been imported to the workspace prior to running the proejctBuild command?

  • 0 in reply to AartiG
    Prodigy 40 points
    Thanks for your quick response!

    Yes, the project was already imported into the workspace. Here is the full command line and output from CCS:

    $CCS_ECLIPSE/eclipse -noSplash -data workspace_v7/ -application com.ti.ccstudio.apps.projectBuild -ccs.projects alice_m4 –ccs.buildType clean

    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    CCS headless build starting... [Fri Jan 12 11:11:31 EST 2018]
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

    ================================================================================
    Pre processing...


    !WARNING: Project '–ccs.buildType' was not found in the workspace! Ignoring...
    NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.


    !WARNING: Project 'clean' was not found in the workspace! Ignoring...
    NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.


    ================================================================================
    Building...


    **** Build of configuration Debug for project alice_m4 ****

    /home/ken/ti/ccsv7/utils/bin/gmake -k -j 4 all -O
    gmake[1]: 'alice_m4.out' is up to date.

    **** Build Finished ****


    ================================================================================
    CCS headless build complete! 0 out of 1 projects have errors.


    And here is the ouptu without the -ccs.buildType clean option:

    $CCS_ECLIPSE/eclipse -noSplash -data workspace_v7/ -application com.ti.ccstudio.apps.projectBuild -ccs.projects alice_m4

    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    CCS headless build starting... [Fri Jan 12 11:13:13 EST 2018]
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

    ================================================================================
    Pre processing...


    ================================================================================
    Building...


    **** Build of configuration Debug for project alice_m4 ****

    /home/ken/ti/ccsv7/utils/bin/gmake -k -j 4 all -O
    gmake[1]: 'alice_m4.out' is up to date.

    **** Build Finished ****


    ================================================================================
    CCS headless build complete! 0 out of 1 projects have errors.



    Here is an abbreviated output from the clean from within CCS:

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

    /home/ken/ti/ccsv7/utils/bin/gmake -k -j 4 clean -O
    rm -rf "alice_m4.hex" "configPkg/linker.cmd" "configPkg/compiler.opt" "alice_m4.out"
    rm -rf "configPkg/"
    rm -rf <list of object files appears here>
    rm -rf <list of .d files appears here>
    Finished clean


    **** Build Finished ****
  • 0 in reply to Ken Price97
    Prodigy 40 points
    Also, here is the abbreviated output from the actual build of the project:

    **** Build of configuration Debug for project alice_m4 ****

    /home/ken/ti/ccsv7/utils/bin/gmake -k -j 4 all -O
    gmake[1]: Entering directory '/mnt/hgfs/dev/sd_alice/Bimini/branches/devel/Alice/ccs_projects/alice_m4/Debug'
    Building file: /mnt/hgfs/dev/sd_alice/Bimini/branches/devel/Alice/CortexM4/app.cfg
    Invoking: XDCtools
    "/home/ken/ti/xdctools_3_32_01_22_core/xs" --xdcpath="/home/ken/ti/edma3_lld_2_12_04_28/packages;/home/ken/ti/ipc_3_46_00_02/packages;/home/ken/ti/bios_6_46_05_55/packages;/home/ken/ti/uia_2_00_06_52/packages;/home/ken/ti/pdk_am57xx_1_0_7/packages;/home/ken/ti/ccsv7/ccs_base;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M4 -p ti.platforms.evmDRA7XX:ipu2 -r release -b "/mnt/hgfs/dev/sd_alice/Bimini/branches/devel/Alice/CortexM4/config.bld" -c "/home/ken/ti-cgt-arm_16.9.3.LTS" "/mnt/hgfs/dev/sd_alice/Bimini/branches/devel/Alice/CortexM4/app.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring app.xem4 from package/cfg/app_pem4.cfg ...
    generating custom ti.sysbios library makefile ...
    generating custom ti.sdo.utils library makefile ...
    generating custom ti.sdo.ipc library makefile ...
    Starting build of library sources ...

    <individual file builds occur here>

    Building target: alice_m4.out
    Invoking: ARM Linker
    "/home/ken/ti-cgt-arm_16.9.3.LTS/bin/armcl" -mv7M4 --code_state=16 -me --define=am5728 --define=ipu1 --define=core0 -g --rtti --diag_warning=225 --diag_wrap=off --display_error_number -z -m"alice_m4.map" --heap_size=0x800 --stack_size=0x800 -i"/home/ken/ti-cgt-arm_16.9.3.LTS/lib" -i"/home/ken/ti-cgt-arm_16.9.3.LTS/include" --reread_libs --define=CORE1=1 --define=IPU0=1 --define=MMU=1 --diag_wrap=off --display_error_number --warn_sections --xml_link_info="alice_m4_linkInfo.xml" --rom_model -o "alice_m4.out"

    <individual object files appear here>

    -l"configPkg/linker.cmd" -llibc.a
    <Linking>
    Finished building target: alice_m4.out


    **** Build Finished ****
  • 0 in reply to Ken Price97
    TI__Guru**** 173310 points

    Ken Price97 said:
    !WARNING: Project '–ccs.buildType' was not found in the workspace! Ignoring...
    NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.


    !WARNING: Project 'clean' was not found in the workspace! Ignoring...
    NOTE: use the '-ccs.autoImport' argument to automatically import projects found in the workspace root directory.

    Looking at the above output, eclipse thinks that –ccs.buildType and clean are also inputs to the -ccs.projects option. So it is not reading -ccs.buildType as an option.

    Ken Price97 said:
    $CCS_ECLIPSE/eclipse -noSplash -data workspace_v7/ -application com.ti.ccstudio.apps.projectBuild -ccs.projects alice_m4 –ccs.buildType clean

    Could you check the "-" (dash) in the -ccs.buildType option, it looks different than the others in the command line and is perhaps being treated as non-ascii. 

  • 0 in reply to AartiG
    Prodigy 40 points
    Keen eye! that was indeed the issue; thanks!