Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.

StarterWare Project Creation

From Texas Instruments Wiki
Jump to: navigation, search



This page details the steps to create projects in IDEs that are supported by StarterWare.

CCS Projects

Creating a CCSv5 Project

  • In the File Menu, go to New and select CCS Project. A window shall appear where the details of the new CCS Project have to be specified.
  • Enter the Project Name.
  • The Project type can be an Executable(Application) or a Static Library. Choose the appropriate project type under Output type parameter. However if the project is neither an Executable nor a Static Library, select the 'Other' option.
  • Select the location where the project has to be created.
  • Options for Device
    • Select the Processor Family type under Family parameter. For AM335x, the family is ARM.
    • Select the Processor Variant under Variant parameter. For AM335x, the Variant is 'Generic CortexA8 Device'.
  • Options for Advanced Settings
    • Select the appropriate option for Device Endianness parameter.
    • Select the Compiler Version used for compilation. The Compiler libraries are part of the CCS Installation Package and CCS automatically selects the compiler version upon selection of the Family. However, compilers of other versions can also be used for compiling the CCS Project.
    • Select the format of the output file to be generated under Output Format option. The Output file can conform to either ELF or COFF standard file formats.
    • If the project is an Executable one, then the path to the Linker Command File should be specified under Linker Command File parameter.
    • Additionally, the Runtime Support Library parameter should be appropriately selected.
  • Options for Project templates and examples
    • Select the Empty Project option under Empty Projects parameter. This creates an empty project fully initialized for the selected device.

The image below is a snapshot of the New Project Settings for AM335x CCS Projects for applications.
New AM335x CCS Project.jpg

Linking/Adding Source Files to Project

The source files that are expected to be built should be associated with the project. These files can either be linked to the project or added to it. In the former case, the project associates itself with the specified source file but does not copy it to the project directory. Thus any changes to the source file in its parent directory gets reflected in the project. In the latter case, a copy of the source file is added to the project directory.

  • To associate source files with the project, travel to 'Project' and select 'Add Files'.

Populating the Project Properties

The newly created CCS Project has to be populated with additional properties. Some of the important Project Properties to be specified are given below.

  • Include Options

The directories containing header files to be included in the Project can be specified. To select, right-click on the Project Name in Project Explorer window and select Properties. Under the CCS Build option, select Include Options. Now specify the path(s) of Include Directory(ies) which have to be searched for header files during compilation.

  • Predefined Symbols

There is a provision to define Pre-defined symbols before compilation. To do this, under Properties, travel to CCS Build, then to Advanced Options and then select Predefined Symbols option.

  • Runtime Environment

The memory type where the executable has to be executed has to be chosen. The available options are RAM and ROM. To do this, under Properties, travel to CCS Build, then to ARM Linker, then to Advanced Options and then select Runtime Environment. Select the appropriate option for the Initialization Model.

  • Build Artifact

The path and name of the output executable has to be specified. To configure this, under Properties, travel to C/C++ Build, then to Settings and select Build Artifact. Here specify the path and name of the output executable under Artifact name.

  • Build Steps

There tool chain performs Pre-build and Post-build operations as specified in the project. To specify these operations, under Properties, travel to C/C++ Build, then to Settings and select Build Steps. Here specify the Commands and Descriptions for the Pre-build and Post-build steps, if required.


  • In the CCS Projects of AM335x applications, there is a Post-build step command which does the following two tasks:
    • Generates a Binary file from the ELF executable file (.out) that is already obtained from the Project's build.
    • Adds a TI Image Header to the Binary file.
  • The above mentioned information regarding CCSv5 Project Creation and Properties are discussed with reference to the CCS version and above.
  • From CCSv5.3 to generate binary file from ELF executable file armofd.exe and armhex.exe, present in tools\compiler\arm_5.0.X\bin, to be used. ofd470.exe and hex470.exe, present in tools\compiler\tms470\bin, used in earlier versions are not available from CCSv5.3.