GSG: OMAP35x DVEVM Software Setup for Graphics SDK

^ Up to main OMAP35x Graphics SDK Getting Started Guide Table of Contents

This chapter describes the host platform requirements as well as the installation dependencies and procedures for getting started with the development on Graphics

Requirements

The following are the requirements for software setup:

• PC Linux Host
  • Root login or liberal sudo privileges
  • Most Linux Distributions should work with this Graphics SDK
  • This Graphics SDK has been tested on
    • Red Hat Enterprise Linux, Workstation V4, x86 32 bit
• Linux Support Package for OMAP35x EVM – This graphics SDK package has been built and tested with TI PSP GIT release version as specified in the readme.pdf file

Preparing to Install

Download the following installers to the temp folder /tmp from the OMAP3 software update site as mentioned here

• OMAP35x-PSP-SDK-setuplinux-##.##.##.##.bin
• OMAP35x_Graphics_SDK_setuplinux_#_##_##_##.bin

The # refers to the version numbers
The OMAP35x Graphics SDK contains the pre-built graphics drivers and kernel modules that are already built with the appropriate version of the OMAP35x-PSP-SDK-setuplinux-##.##.##.##.bin. Make sure that this dependency is maintained and the user uses the kernel image built from the correct version of the OMAP35x SDK as mentioned in readme.pdf

Ensure all the .bin files are set with executable permissions.

host $ chmod 777 *.bin

Installing the Software

Installing the software used by the OMAP35x EVM involves performing the following steps.

1. Installing the Target Linux Software
2. Installing the Graphics SDK Software
3. Installing the toolchain

Installing the Target Linux Software

Refer OMAP35x DVEVM Getting Started Guide: Installing_the_Target_Linux_Software

Installing the Graphics SDK Software

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

1. Log in using a user account. In the following steps, we refer to the home directory as "~".
2. Execute the OMAP35x Graphics SDK installer that you previously downloaded from the extranet location. For example:

   host $ ./OMAP35x_Graphics_SDK_setuplinux_#_##_##_##.bin
   

   The installer will start as a GUI application. Follow the instructions in the dialog boxes. You’ll be asked to agree to the End User License Agreement.

   When you are prompted for an installation location, use the default installation location, that points to /home/<user_account>/OMAP35x_Graphics_SDK_#.##.##.##. This location will be used as the OMAP35x Graphics SDK installation folder through out this document.

3. You can now delete the .bin files that you loaded into the temporary directory.

Note: You can uninstall these components by using the uninstall file in the respective installation directories. For example:

host $ cd /home/<user_account>/OMAP35x_Graphics_SDK_#_##_##_##
host $ ./uninstall

Installing the Toolchain

This guide assumes use of the LITE version of the CodeSourcery toolchain. See CodeSourcery documentation if you are using the evaluation version that comes with this EVM or for other cases. The toolchain used is ARM GNU/Linux EABI 2007q3. It can be downloaded via the following URL:

http://www.codesourcery.com/gnu_toolchains/arm/releases/2007q3

Select the following options: Target Platform: ARM GNU/Linux Host Platform: IA32 GNU/Linux

To install the toolchain, follow the sequence below. These are to be executed on the Linux host platform.

$ mkdir –p /home/<user_account>/toolchain
$ cp arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 /home/<user_account>/toolchain
$ cd /home/<user_account>/toolchain
$ tar -jxvf  arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
$ rm arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar

Setting up the Build/Development Environment

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

1. Log in to your user account (and not as root) on the Linux host system, where the OMAP35x Graphics SDK is installed.
2. Add the /host/<user_account>/toolchain/arm-2007q3/bin directory to your path. This is typically done by adding an additional line to your shell resource file (~/.bashrc). For the path given above, the line to add to your .bashrc file is:

   PATH="/home/<user_account>/toolchain/arm-2007q3/bin:$PATH"

   This adds the CodeSourcery tools to your path and allows you to execute the tools using arm-none-linux-gnueabi-gcc (or other tools in the tool chain) from any directory.

3. Remember to use the following command after modifying your .bashrc file:

   host $ source .bashrc

4. You can test that the toolchain is installed correctly by starting a new shell and using the following command:

   host $ arm-none-linux-gnueabi-gcc –v

   When you execute this command, you will get an output like the one shown below.

   Using built-in specs.
   Target: arm-none-linux-gnueabi
   Configured with: /scratch/paul/lite/linux/src/gcc-4.2/configure --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu --target=arm-none-linux-
   gnueabi --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --with-gnu-as --with-gnu-ld --enable-
   languages=c,c++ --enable-shared --enable-symvers=gnu --enable-__cxa_atexit --with-pkgversion=CodeSourcery Sourcery G++ Lite 2007q3-51 --with-
   bugurl=https://support.codesourcery.com/GNUToolchain/ --disable-nls --prefix=/opt/codesourcery --with-sysroot=/opt/codesourcery/arm-none-linux-
   gnueabi/libc --with-build-sysroot=/scratch/paul/lite/linux/install/arm-none-linux-gnueabi/libc --enable-poison-system-directories --with-build-
   time-tools=/scratch/paul/lite/linux/install/arm-none-linux-gnueabi/bin --with-build-time-tools=/scratch/paul/lite/linux/install/arm-none-linux-
   gnueabi/bin
   Thread model: posix
   gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)