Installing the Software for OMAP-L137

From Texas Instruments Wiki
Jump to: navigation, search

Prerequisites

To begin installing the SDK software make sure you have met the following system requirements:

  • Host machine - The SDK software is verified using MontaVista Pro 5.0 installed on RedHat Enterprise Linux WS release 4.
  • OMAP-L137 EVM

Software overview

To begin developing applications, you need to install the EVM development environment. This section outlines the steps required to load the EVM software onto the development host.

To download the most current software, please follow the steps on this page.

After following the steps on this page one time, you can go directly to myRegistered Software to download the current software.

Software components

The TI SDK software includes codec engine software, example codec servers, and SDK documentation. In addition it includes the following installers and compressed files:

  • OMAPL137_arm_setuplinux_#_#_#_#.bin - This is an installer for Linux workstations and will install the preliminary Starter Kit software for OMAP-L137 ARM-based software development.
  • bios_setuplinux_#_#_#_#.bin - This is the installer for the Linux workstation and will install the DSP/BIOS software.
  • xdctools_setuplinux_#_#_#_#.bin- This is the installer for Linux workstation and will install the XDC tool. XDC tool is needed to build various software including Codec Engine, Framework Components, Dsplink etc.
  • LPTB-#_#_#_#-beta.bin - This is an installer for Linux driver performance test bench.
  • ti-cgt-C6000_#.#.#_setup_linux_x86.bin - This is the installer for the Linux workstation and will install the TI code generation tool. It is needed for users to who do not have the up-to-date code generation tool.

In addition, the following software installer is available for download.

  • mvl_5_0_#_demo_sys_setuplinux.bin - This is an installer for Linux workstations and will install a demonstration version of the MontaVista Professional Edition v5.0 system and target tools.

NOTE: In previous versions, there were 2 files (mvl_5_0_#_demo_sys_setuplinux.bin and mvl_5_0_#_demo_target_setuplinux.bin). In the beta software version, the contents of the file mvl_5_0_#_demo_target_setuplinux.bin are included in the file mvl_5_0_#_demo_sys_setuplinux.bin.

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.
  • EVM #
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.

Preparing to Install

On a host system, download the software and copy the following files to a temporary location with at least 2.3 GB available space. Since you can delete the installation files after installing the software, a directory like /tmp is recommended.

  • OMAPL137_arm_setuplinux_#_#_#_#.bin
  • bios_setuplinux_#_#_#.bin
  • xdctools_setuplinux_#_#_#.bin
  • LPTB-#_#_#_#-beta.bin
  • mvl_5_0_#_demo_sys_setuplinux.bin
  • ti-cgt-C6000_#.#.#_setup_linux_x86.bin

To download the most current software, please follow the steps on this page.

After following the steps on this page one time, you can go directly to myRegistered Software to download the current software.

Installation steps

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

  • Installing the SDK Software
  • Installing the LSP
  • Installing the Target Linux Software

Installing the SDK Software

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


NOTE: The installers can have a different default installation location. 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 the build setup steps.


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

  1. Log in using a user account . 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. Once you have changed the execute permissions you can go back to a normal user.
    host $ su root
    host $ cd /tmp
    host $ chmod +x *.bin
    host $ exit
  2. Execute the SDK installer that you previously downloaded from the OMAP-L137 Software Download page in a temporary directory.
    For example:
    host $ cd /tmp
    host $ ./OMAPL137_arm_setuplinux_#_#_#_#.bin
    NOTE: If you do not have a graphical display, you may use console installation with the following command.
    host $ ./OMAPL137_arm_setuplinux_#_#_#_#.bin --mode console
    Path Information - This installs the DVSDK in /home/<useracct>/OMAPL137_arm_#_#_#_#
  3. Execute the XDC installer. For example:
    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>/OMAPL137_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>/OMAPL137_arm_#_#_#_#.
    NOTE: For DSP/BIOS 5.33.05, please also execute the following command:
    host $ su root
    host $ chmod 555 /home/<useracct>/OMAPL137_arm_#_#_#_#/bios_5_33_05/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 OMAPL137_arm_#_#_#_# codegen directory. You will need to manually create the folder "cg6x_#_#_#" (or equivalent folder name for the CGtool version).
    For example:
    host $ mkdir $HOME/OMAPL137_arm_#_#_#_#/cg6x_6_1_9
    Remember to set the environment variable as directed by the installer. For example:
    export C6X_C_DIR="/home/<useracct>/OMAPL137_arm_#_#_#_#/cg6x_#_#_#/include;
    /home/<useracct>/OMAPL137_arm_#_#_#_#/cg6x_#_#_#/lib"
    NOTE: The above line should be entered on one line with no carriage 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

Installing the LSP

Follow these steps to perform the necessary installations:

  1. If you followed the steps in Installing the SDK Software section, you will already have the LSP installed in the OMAPL137_arm_1_00_00_07/REL_LSP_02_20_#_# directory.

    Please notice that the version of the LSP that comes with the SDK has been tested to work with the SDK software. This might not be the case for the newest version. If you want to use the LSP version that comes with the SDK, skip to step 2.

    The latest standalone LSP package can be downloaded from this page. You need a ti.com ID to access this page. Click on the link LSP 2.20 OMAP-L137 and DA830 MontaVista Linux based Platform Support to download the file REL_LSP_02_20_#_#.tgz. Place the file in the OMAPL1_arm_#_#_#_# folder.
    To install the LSP package, extract the release package with the following command (replace # in these commands with the release version number of your release package):
    host $ tar -xzf REL_LSP_02_20_#_#.tgz
  2. Move (cd command) to the REL_LSP_02_20_#_# directory.
    This is the directory structure:
    • REL_LSP_02_20_#_#
    • mvl_5_0_0_demo_lsp_setuplinux_02_20_#_#.bin
    • PSP_02_20_#_#
    • bin
    • lsp_psp_02_20_#_#_release_notes.html
    • psp_license_agreement.html
    • psp_software_manifest.html
    • examples
    • docs
    • board_utilities
    • u-boot-1.3.3.tar.gz
    • flash_writers
    • tools
    • armubl
    • dspubl
  3. The installation of the Linux Kernel (mvl_5_0_0_demo_lsp_setuplinux_02_20_#_#.bin) is covered in the next section Installing the Target Linux Software.
  4. Untar the PSP_02_20_#_#/board_utilities/u-boot-1.3.3.tar.gz file to obtain the U-Boot sources:
    host $ cd PSP_02_20_#_#/board_utilities
    host $ tar -xzf u-boot-1.3.3.tar.gz
  5. Flash writer sources and CCStudio projects are provided in the PSP_02_20_#_#/board_utilities/flash_writers directory.
  6. Pre-compiled binaries for U-Boot, Linux kernel and Flash writers are provided in the PSP_02_20_#_#/bin directory.

Installing the Target Linux Software

This section explains how to install Linux for use on the target board. This is a demonstration version of MontaVista Linux Pro v5.0.

To install the Linux software, follow these steps:

  1. Switch user to "root" on your host Linux workstation. You will need to be root to install to the /opt/mv_pro_5.0 directory.
    host $ su root
  2. Execute the following bin files (where # is the current version number) in order to extract the installers for Linux tools, the file system, and Linux kernel.

    • mvl_5_0_#_demo_sys_setuplinux.bin (in /tmp directory)
    • mvl_5_0_0_demo_lsp_setuplinux_#_#_#_#.bin (in OMAPL137_arm_#_#_#_#/REL_LSP_02_20_#_# directory)

    The file mvl_5_0_#_demo_sys_setuplinux.bin (which you should have previously downloaded and copied to the /tmp directory) and the file mvl_5_0_0_demo_lsp_setuplinux_#_#_#_#.bin will be in the OMAPL137_arm_#_#_#_#/REL_LSP_02_20_#_# folder after you intall the SDK software. If a bin file does not run, make sure these files are executable (use chmod +x *.bin). Instead of the default directory, we suggest that you install in the /opt/mv_pro_5.0 directory.
    host $ cd /tmp
    host $ ./mvl_5_0_#_demo_sys_setuplinux.bin
    host $ cd /home/<useracct>/OMAPL137_arm_#_#_#_#/REL_LSP_02_20_#_#
    host $ ./mvl_5_0_0_demo_lsp_setuplinux_#_#_#_#.bin
    NOTE: If you do not have a graphical display, you may use console installation with the following commands.
    host $ ./mvl_5_0_#_demo_sys_setuplinux.bin --mode console
    host $ ./mvl_5_0_0_demo_lsp_setuplinux_#_#_#_#.bin --mode console
    NOTE: In previous version, there were 3 files (mvl_5_0_#_demo_sys_setuplinux.bin, mvl_5_0_#_demo_target_setuplinux.bin, and ./mvl_5_0_0_demo_lsp_setuplinux_#_#_#_#.bin). In the beta software version, the contents of the file mvl_5_0_0_demo_target_setuplinux.bin are included in the file mvl_5_0_#_demo_sys_setuplinux.bin.
  3. Go to the location where you will unpack the tar files. For example:
    host $ cd /opt/mv_pro_5.0
  4. After you execute these .bin files, make sure the following files are located in /opt/mv_pro_5.0 (or in the /mv_pro_5.0 subdirectory of the directory you chose in place of the default):
    • mvltools5_0_#_update.tar.gz
    • LSP_02_20_#_#.tar.gz
  5. Unpack the tar files (as root) by using the following commands:
    host $ tar zxf mvltools5_0_#_update.tar.gz
    host $ tar zxf LSP_02_20_#_#.tar.gz

    This creates the MontaVista directory structure under the /opt/mv_pro_5.0/montavista/ directory.

    NOTE: unpacking this tar file will overwrite any existing files that were previously installed.
  6. Exit out of root. This should switch you back to user:
    host $ exit
  7. You can now delete the .bin files that you loaded into the temporary directory.
    NOTE: You can uninstall these components by using the "rm -rf" command on its directory. You should ignore the _uninstall directories created by InstallShield

Adding MV Tools to Environment

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

  1. As user (not as root) on the host system set your PATH so that the MontaVista tool chain host tools and cross compiler (arm_v5t_le-gcc) can be found. For example, in a default installation of the MontaVista LSP, you should add a definition like the following to your shell resource file (for example, ~/.bashrc):

    PATH="/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin:/opt/mv_pro_5.0/montavista/pro/bin:/opt/mv_pro_5.0/montavista/common/bin:$PATH"

    NOTE: If you installed in a location other than /opt/mv_pro_5.0, use your own location in the PATH.
  2. Remember to use the following command after modifying your .bashrc file:
    host $ source ~/.bashrc

What's Next?

Now that you have installed the SDK software, please proceed to the Restoring/Flashing Bootloaders section of the Getting Started Guide.