• Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 599 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

StarterWare project creation problem

mahesh
Intellectual 670 points

Other Parts Discussed in Thread: OMAPL138, SYSBIOS, CONTROLSUITE

Hello,

I am new to the StarterWare. I run some of the ARM based example projects and found them working.

Next I want to create my own project. 

-  get errors while inclusion, CCS reports "internal errors" and  any of the source , lib, .out etc are not visible in the project explorer window.

My question is what is the best way to create my own project based upon the example projects and keep on adding the other source files.

Thank you

Yours

Mahesh

 

  • Intellectual 670 points

    In continuation to the above,

    I imported a single project say lidd_armv5 in my workspace with "copy to workspace" option unchecked. I renamed the project and CCS created a new prject for  me keeping the older one.

    I add some functionality to the code and run to succeed. But periodically CCS attempting to write .metadata but failing to do so as can be seen from the snap-shot.

    Is this fatal issue? How this going to effect my project?  What to do?

    Regards,

    Mahesh

    Observations:


    **** Build of configuration Debug for project GPP ****

    D:\ti\ccsv5\utils\bin\gmake -k all
    'Building file: D:/Program Files/Texas Instruments/OMAPL138_StarterWare_1_10_01_01/examples/evmOMAPL138/lidd/liddDisplay.c'
    'Invoking: TMS470 Compiler'
    "D:/ti/ccsv5/tools/compiler/tms470/bin/cl470" -mv5e -g --define=omapl138 --include_path="D:/ti/ccsv5/tools/compiler/tms470/include" --include_path="../../../../../../../include" --include_path="../../../../../../../include/hw" --include_path="../../../../../../../include/armv5" --include_path="../../../../../../../include/armv5/omapl138" --include_path="../../../../../../../grlib/include" --include_path="../../../../../../../usblib/include" --include_path="../../../../../../../ipclite/include" --include_path="../../../../../../../nandlib/include" --diag_warning=225 -me --abi=eabi --code_state=32 --preproc_with_compile --preproc_dependency="liddDisplay.pp"  "D:/Program Files/Texas Instruments/OMAPL138_StarterWare_1_10_01_01/examples/evmOMAPL138/lidd/liddDisplay.c"
    "D:/Program Files/Texas Instruments/OMAPL138_StarterWare_1_10_01_01/examples/evmOMAPL138/lidd/liddDisplay.c", line 101: warning: variable "INITMessage" was declared but never referenced
    'Finished building: D:/Program Files/Texas Instruments/OMAPL138_StarterWare_1_10_01_01/examples/evmOMAPL138/lidd/liddDisplay.c'
    ' '
    'Building target: liddDisplay.out'
    'Invoking: TMS470 Linker'
    "D:/ti/ccsv5/tools/compiler/tms470/bin/cl470" -mv5e -g --define=omapl138 --diag_warning=225 -me --abi=eabi --code_state=32 -z -m"GPP.map" --warn_sections -i"D:/ti/ccsv5/tools/compiler/tms470/lib" -i"D:/ti/ccsv5/tools/compiler/tms470/include" -i"../../../../../../../binary/armv5/cgt_ccs/omapl138/drivers/Debug" -i"../../../../../../../binary/armv5/cgt_ccs/omapl138/evmOMAPL138/platform/Debug" -i"../../../../../../../binary/armv5/cgt_ccs/omapl138/system_config/Debug" -i"../../../../../../../binary/armv5/cgt_ccs/omapl138/ipclib/Debug" -i"../../../../../../../binary/armv5/cgt_ccs/omapl138/usblib/Debug" -i"../../../../../../../binary/armv5/cgt_ccs/utils/Debug" -i"../../../../../../../binary/armv5/cgt_ccs/grlib/Debug" -i"../../../../../../../binary/armv5/cgt_ccs/nandlib/Debug" --reread_libs --rom_model -o "liddDisplay.out"  "./liddDisplay.obj" -l"libc.a" -ldrivers.lib -lutils.lib -lplatform.lib -lsystem_config.lib "../liddDisplay.cmd"
    <Linking>
    warning: entry-point symbol other than "_c_int00" specified:  "Entry"
    'Finished building target: liddDisplay.out'
    ' '
    D:/ti/ccsv5/utils/bin/gmake --no-print-directory post-build
    A subdirectory or file ..\..\..\..\..\..\..\binary\armv5\cgt_ccs\omapl138\evmOMAPL138\lidd\Debug already exists.
    liddDisplay.out
            1 file(s) copied.
    ' '

    **** Build Finished ****

  • in reply to mahesh
    Intellectual 670 points

    Can anybody please share a small SYSBIOS program using StartrerWare package.

    Regards

    Mahesh

     

     

  • TI__Guru**** 173310 points

    mahesh said:

    My question is what is the best way to create my own project based upon the example projects and keep on adding the other source files.


    Please see this wiki article: http://processors.wiki.ti.com/index.php/Creating_copy_of_example_project
    Although written for ControlSuite and Stellarisware, the suggestions should still be applicable.

    mahesh said:

    Can anybody please share a small SYSBIOS program using StartrerWare package.

    I'm not aware of any SYSBIOS examples using Starterware but this might be better answered by the folks in the OMAP forum, so feel free to post this question there.

  • in reply to AartiG
    Intellectual 670 points

    Iuse CCSv5.1. I could not find  ".cdtbuild" file as said in the wiki page .

    It says "

    Edit the .cdtbuild file.

    • In this file do a search/replace of the old directory name with the new directory. In this case search for "cpu_timer" and replac it with "my_project".

    could anybody help me in finding this?

    Also I am getting two .out files with original name .out and new name .out

    Regards

    Mahesh

  • in reply to mahesh
    TI__Guru**** 173310 points

    The .cdtbuild file was created with CCSv4 but is no longer created/used with CCSv5. The Starterware projects were created for CCSv5 which is why you don't see that file. You can ignore that section of the wiki page.

    I noticed that the output file name is hard-coded in the project settings, which is likely the reason why you are seeing the original name .out file. You should change this for your copied project to a different name. Then clean and rebuild the project and the original .out should no longer be there.