GSG: Installing the Software for OMAP-L1

^ Up to main Getting Started Guide for OMAP-L138 Table of Contents

ATTENTION OMAP-L138 DEVELOPERS: The Generally Available (GA) Linux DVSDK 4.x for the OMAP-L138 device is now available here. There are various capabilities and improvements that have been added to this version. This is the recommended release kit for development which supersedes the SDK 1.00.xx Beta. The majority of the information below is only applicable to the SDK 1.00.xx Beta.

Prerequisites

To begin installing the SDK 1.00.xx.xx Beta software, make sure you have met the following system requirements:

• Host machine running a version of Linux such as RedHat Enterprise Linux WS or Ubuntu.
• OMAP-L138 EVM (this Getting Started Guide assumes that you have the Development Kit, not the eXperimenter Kit)

Software overview

OMAP-L138 DEVELOPERS - See attention note at the top of the page.

To begin developing applications, you need to install the EVM development environment. This section provides an overview of the EVM software.

Software components

The TI SDK software includes the following installers:

• OMAP-L138_setuplinux_#_#_#_#.bin This is the ARM-side SDK software for Linux workstations. It installs development software, including:
  • Linux Platform Support Package (PSP) which includes board-flashing utilities running on ARM and some Linux driver examples
  • DSP/BIOS Utilities
  • Codec Engine
  • Board-Flashing Utilities running on DSP
  • DSP Link
  • EDMA Low Level Driver (LLD) running on DSP
  • Framework Components including DMAN3
  • Linux Utilities including CMEM
  • xDAIS Algorithm Package
• bios_setuplinux_#_#_#.bin This is the DSP/BIOS installer for Linux.
• xdctools_setuplinux_#_#_#_#.bin This is the XDCtools installer for Linux. It installs XDCtools, which provides support for RTSC and is needed to build various software, including Codec Engine, Framework Components, DSP Link.
• ti_cgt_c6000_#.#.#_setup_linux_x86.bin This is the TI Code Generation Tools installer for Linux. It is needed for users to who do not already have the latest code generation tools.

Tool chain

To build the Linux kernel, you will need to download and install version 2009q1-203 of the Sourcery G++ tools from Code Sourcery, which is available here.

These command line tools are available at no cost. Code Sourcery also offers more fully featured tools for a cost. The Sourcery G++ Lite package includes all of the following components:

• CodeSourcery Debug Sprite for ARM
• GNU Binary Utilities (Binutils)
• GNU C Compiler (GCC)
• GNU C Library (GLIBC)
• GNU C++ Compiler (G++)
• GNU C++ Runtime Library (Libstdc++)
• GNU Debug Server (GDBServer)
• GNU Debugger (GDB)

Command prompts in this guide

In this guide, commands are preceded by prompts that indicate the environment where the command is to be typed. For example:

• host$

Indicates command to be typed into the shell window of the host Linux workstation.

• U-Boot>

Indicates commands to be typed into the U-Boot shell in a console window connected to the EVM board's serial port.

• target$

Indicates commands to be typed into the Linux shell in the terminal window connected to the EVM board's serial port.

Installation steps

OMAP-L138 DEVELOPERS - See attention note at the top of the page.

Installing the software used by the EVM kit involves performing the following steps:

• Downloading TI software installers
• Installing the SDK Software
• Downloading and installing the Code Sourcery tools

Downloading TI software installers

Even though the EVM Development Kit includes TI software on DVD, it is recommended that you begin by registering the kit with TI and going to the TI software download page to get the latest versions of the software used with the EVM. (The eXperimenter kit does not include software, so you will need to download it in any case.)

On a host system, follow these steps:

1. Follow the steps in the kit's Read Me 1st Card to register and download the most current software from TI's website. (If you have already registered this EVM, skip to the next step.)
2. The software is currently available here.
3. Copy the following files to a temporary location with at least 1 GB of available space. Since you can delete the installation files after installing the software, a directory like /tmp is recommended.
   • OMAP-L138_setuplinux_#_#_#_#.bin
   • bios_setuplinux_#_#_#.bin
   • xdctools_setuplinux_#_#_#_#.bin
   • ti_cgt_c6000_#.#.#_setup_linux_x86.bin
   • cs1omapl138_1_00_00-a_setup_linux.bin

Note: For this release, TI recommends choosing either the ARM Linux drivers or the DSP BIOS Drivers for execution but not both at the same time.

Installing the SDK Software

The SDK software includes Codec Engine components, DSP/BIOS Link, xDAIS and xDM header files, Framework Components, etc.

NOTE: Some installers have different default installation locations. However, we strongly recommend that you change the default installation locations to place the components together (if you have not already installed the Linux versions of these components elsewhere). This simplifies later component build setup steps.

To install the software using the Linux installer, follow these steps:

1. Log in using a user account on your Linux workstation. The user account must have execute permission for the all the installation files. Switch user to “root” on the host Linux workstation and change directories to the temporary location where you have downloaded the bin files.

   host$ su root

   host$ cd /tmp

   host$ chmod +x *.bin

   host$ exit

2. Execute the ARM-side SDK installer that you previously downloaded in a temporary directory.

   For example:

   host$ cd /tmp

   host$ ./OMAP-L138_setuplinux_#_#_#_#.bin

   NOTE: If you do not have a graphical display, you may use console installation with the following command.

   host$ ./OMAP-L138_setuplinux_#_#_#_#.bin --mode console

   Path Information - This installs the SDK in /home/<useracct>/OMAPL138_arm_#_#_#_#. For more about the contents of the PSP in this installation, see About the PSP package.

3. Execute the XDCtools installer. For example:

   host$ cd /tmp

   host$ ./xdctools_setuplinux_#_#_#.bin

   NOTE: If you do not have a graphical display, you may use console installation with the following command.

   host$ ./xdctools_setuplinux_#_#_#.bin --mode console

   Path Information - When you are prompted, do not use the default installation location. Instead, install the software in the directory created in Step 2. For example, /home/<useracct>/OMAPL138_arm_#_#_#_#.

4. Execute the DSP/BIOS installer. For example:

   host$ ./bios_setuplinux_#_#_#.bin

   NOTE: If you do not have a graphical display, you may use console installation with the following command.

   host$ ./bios_setuplinux_#_#_#.bin --mode console

   Path Information - When you are prompted, do not use the default installation location. Instead, install the software in the directory created in Step 2. For example, /home/<useracct>/OMAPL138_arm_#_#_#_#.

   NOTE: For DSP/BIOS 5.33.06, please also execute the following command:

   host$ su root

   host$ chmod 555 /home/<useracct>/OMAPL138_arm_#_#_#_#/bios_5_33_06/xdctools/*

   host$ exit

5. Execute the Code Generation Tools installer. For example:

   host$ ./ti-cgt-C6000_#.#.#_setup_linux_x86.bin

   NOTE: If you do not have a graphical display, you may use console installation with the following command.

   host$ ./ti-cgt-C6000_#.#.#_setup_linux_x86.bin --mode console

   Path Information - When the installer prompts for an installation location, do not use the default location. Instead, use the entire path to the OMAPL138_arm_#_#_#_# codegen directory. You will need to manually create the folder "cg6x_#_#_#" (or equivalent folder name for the CGtool version).

   For example:

   /home/<useracct>/OMAPL138_arm_#_#_#_#/cg6x_6_1_9

   Remember to set the environment variable as directed by the installer. For example:

   export C6X_C_DIR="/home/<useracct>/OMAPL138_arm_#_#_#_#/cg6x_#_#_#/include;

   /home/<useracct>/OMAPL138_arm_#_#_#_#/cg6x_#_#_#/lib"

   NOTE: The above line should be entered on one line with no carraige return.

   NOTE: To set this environment variables for all terminal sessions and between reboots you should add the line above to the ~/.bashrc file. You can then source the ~/.bashrc file using the following command to pick up this setting.

   host $ source ~/.bashrc

6. Execute the codec server installer. For example:

   host $ ./cs1omapl138_1_##_##-a_setup_linux.bin.bin

   NOTE: This installer requires your linux host to have a graphical display.

   Path Information - When the installer prompts for an installation location, you can install it in the default installation directory or specify your own directory, i.e. /home/<useracct>/OMAPL138_arm_#_#_#_#/cs1omapl138_#_#.

7. If you have not already done so, follow the installation instructions provided with the Logic CD that is included with the Development Kit. In addition to software from Logic, this CD provides TI's Code Composer Studio v3.3, which you should install on a Microsoft Windows host.

Downloading and installing the Code Sourcery tools

To set up the ARM development and build environment, follow these steps:

• Go the CodeSourcery web site and download the Sourcery G++ Lite 2009q1-203 for ARM tools:
• Download the IA32 GNU/Linux Installer package to your Linux workstation.
• Make the downloaded file executable

host$ chmod +x arm-2009q1-203-arm-none-linux-gnueabi.bin

• Run the installer and follow the steps it presents to install the package.

host$ ./arm-2009q1-203-arm-none-linux-gnueabi.bin

Note: On ubuntu it might fail as it uses 'dash' as a shell (the Debian shell). To reconfigure for the bash shell, use the following command:

host$ sudo dpkg-reconfigure -plow dash

If you are using 64-bit Linux host, ensure that ia32-libs are installed

host$ sudo apt-get install ia32-libs

If you installed in the default path, you can find the files at /home/<user>/CodeSourcery. Ensure the Code Sourcery tools are in the path by adding the following

host$ export PATH=/home/<user>/CodeSourcery/Sourcery_G++_Lite/bin:$PATH

to the ~/.bashrc file. You can then source the ~/.bashrc file with the following command or restart the bash shell

host$ source ~/.bashrc

About the PSP package

OMAP-L138 DEVELOPERS - See attention note at the top of the page.

The Linux Platform Support Package (PSP) provides support for Linux kernel, U-Boot, UBL and utilities to flash boot software on the EVM.

The PSP package is available as part of the SDK OMAP_L138_arm_#_#_#_#.tar.gz installation in the DaVinci-PSP-SDK-#.#.#.# directory under the main installation directory.

What's next?

Now that you have installed the SDK software, please continue on to the OMAP-L1 Setting up target file system or the AM18x Setting up target file system section of the Getting Started Guide.