SitaraWareEnvironmentSetup

IMPORTANT - The content of this page is due to change quite frequently and thus the quality and accuracy are not guaranteed until this message has been removed. For suggestion/recommendation, please send mail to your local FAE.

Introduction

This chapter details the settings required for IDE/tools supported by SitaraWare. This chapter tries to cover some typical steps to be followed while starting to build and/or load and execute libraries/applications packaged inside SitaraWare.

GCC from TI Code Composer Studio v5

The CCS project files enable those users who are comfortable with building the projects rather than command line invocation of make file. CCS projects are provided only for applications, which internally invoke the make files. Following steps indicate the steps to properly build an example application packaged with SitaraWare

1. Make changes to the source files and edit the makefiles accordingly
2. Launch Code Composer Studio v5 eclipse IDE
3. File menu-> Import-> CCS-> Existing CCS/CCE Eclipse Projects
4. Select search-directory . Here, browse to the required example directory. For instance if demo project is to be imported, browse to /examples/evmAM1808/demo/build/ccs and click OK. The project will be displayed.
   
5. Check (checkbox) the project and click finish
   
6. Go to project properties

     7. Select Environment setup

   8. Set LIB_PATH to point to Code Sourcery installation. Make sure the path is given in "". For Linux the typical path will be like "opt/CodeSourcery/Sourcery G++ Lite" (give the path where the Code Sourcery is installed in the host machine).

  9. Build project:Project Menu-> Build Project. This will build the selected project

TMS470 from CCS project

  This section explains how to import the CCS project (in which TMS470 is conifugred ad the compiler) which is created earlier and how to build it. Following steps indicate the steps to properly build an example application packaged with SitaraWare.

1. Launch Code Composer Studio v5 eclipse IDE
2. File menu-> Import-> CCS-> Existing CCS/CCE Eclipse Projects
3. Select search-directory. Here, browse to the required example directory. For instance if demo project is to be imported, browse to /examples/evmAM1808/demo/build/cg_ccs and click OK. The project will be displayed.
4. Check (checkbox) the project and click finish
   
5. In addition to the required project, the driver, platform and system_config projects also have to be imported. These are compiled to get the corresponding libraries which are required during linking to create the final executable. If graphics API's are used then grlib project also has to be imported. If USB API's are used then usblib project also has to be imported. The required project and all the dependent proejcts has to be compiled either in debug mode only or in release mode only. It is not advisable to compile some projects in debug mode and others in release mode.
   
6. Add the path of tiobj2bin.bat (\ccsv5\ccs_base_5.0.2.00006\utils\tiobj2bin) to the system PATH variable.
   
7. Building project: Right click on project -> Build Project. Build all the required libraries (driver, platform, system & grlib) before building the application (grlib_demo).

Build output: The executable will be placed at examples\evmAM1808\grlib_demo\cg_ccs which can be loaded on to the target.

GCC from Command Line in Linux/Cygwin

1. Export LIB_PATH

                          

   To clean and build:

                           SitaraWare$  make clean

                           SitaraWare$ make

Debugging using CCSv5

CCSv5 can be used to connect to the target (EVM), load executable binaries and debug. To connect to the target one needs to have a target configuration for the CCSv5 and this can be used to launch a debug session.

Creating a target configuration, if one doesn't exist already.

1. Launch Code Composer Studio v5 eclipse IDE
2. File menu-> New-> Other-> General ->Target Configuration File. Click Next
3. Filename : AM1808EVM. Check "Use shared location" to be available to anyone who uses the workspace. Click Finish. A window opens up which is to configure the connection details
4. Connection: Chose the host-to-target connection details. For example "Spectrum Digital XDS510 USB Emulator", if XDS510 is being used.
5. Device: Type AM1808. AM1808 should be available in the device list. Select AM1808
6. Click on "Target Configuration". "Initialization Script" for ARM9 should point to a proper GEL file that needs to be used.
7. Click Save.

    For GEL file configuration please refer here.

Launching a debug session and connecting to the target

1. Run Menu ->Debug. This will launch the debugging session for AM1808
2. Right Click on the ARM9 target and select Connect.

Loading and running a program/executable

1. Run menu ->Load ->Load Program. Here browse to the required executable and click OK
2. Run menu -> Run
   

IAR Embedded Workbench 6.10 Projects

This section explains, steps to build a SitaraWare IAR Embedded Workbench IDE Project. IAR IDE is supported only on windows.

• Launch IAR Emedded Workbench
• Go to Project->Add Existeng Project

• Select the required SitaraWare project

• Once imported the project is listed in the workspace.Select the required profile for build from the drop down (usually Debug or Release)

• Ensure that the project settings like the include paths etc are proper under, Project->Options->Compiler , Project->Options->Linker etc
• Select Project->Rebuild All

• The IDE might ask to save the workspace file. Select a directory and name to save the file (usually the build directory is used for saving the workspace files). Once the project is build succesfully, an executable project can be debugged on the target by downloading the executable as described in the next steps.

• Ensure that for an executable project, Target type is chose appropriately.

• Ensure that the Debugger type and the target initialization script (*.mac) are selected properly

• Ensure that the host and the target are connected via IAR JLINK Debugger.
• Select Project->Download and Debug

 

OMAPL1 AM1x OMAPL1x_Topic_Boot