Summary of Contents for Texas Instruments OMAP-L137 EVM
Page 1
OMAP-L137 EVM PSP User’s Guide Literature Number: SPRUGI8 February 2009...
Page 2
TI as compliant with ISO/TS 16949 requirements. Buyers acknowledge and agree that, if they use any non- designated products in automotive applications, TI will not be responsible for any failure to meet such requirements. Following are URLs where you can obtain information on other Texas Instruments products and application solutions: Products...
Page 3
EVALUATION BOARD/KIT IMPORTANT NOTICE Texas Instruments (TI) provides the enclosed product(s) under the following conditions: This evaluation board/kit is intended for use for ENGINEERING DEVELOPMENT, DEMON- STRATION, OR EVALUATION PURPOSES ONLY and is not considered by TI to be a finished end-product fit for general consumer use.
Page 4
FCC Warning This evaluation board/kit is intended for use for ENGINEERING DEVELOPMENT, DEMON- STRATION, OR EVALUATION PURPOSES ONLY and is not considered by TI to be a finished end-product fit for general consumer use. It generates, uses, and can radiate radio frequency energy and has not been tested for compliance with the limits of computing devices pursuant to part 15 of FCC rules, which are designed to provide reasonable protection against radio frequency interference.
Page 5
This document is intended for system engineers who want to get started using the Linux PSP package for OMAP-L137 EVM board. This document assumes you have knowledge of the OMAP-L137 EVM platform and have basic knowledge about installing and using software on embedded Linux platforms.
Page 6
Trademarks Trademarks The Texas Instruments logo and Texas Instruments are registered trademarks of Texas Instruments. Trademarks of Texas Instruments include: TI, DaVinci, the DaVinci logo, XDS, Code Composer, Code Composer Studio, Probe Point, Code Explorer, DSP/BIOS, RTDX, Online Lab, DaVinci,...
Chapter 1 Introduction This chapter introduces the OMAP-L137 EVM PSP. Topic Page 1.1 What is a Platform Support Product (PSP) Package? ... 1–2 1.2 About this User Guide........1–2...
Version 2.6.18) ported for OMAP-L137 EVM. The kernel is compiled with MV Pro 5.0 ToolChain based on GCC 4.2.0. ❏ U-Boot version 1.3.3 ported for OMAP-L137 EVM. The U-Boot is compiled with MV Pro 5.0 ToolChain based on GCC 4.2.0.
Chapter 2 Installing the Package This chapter describes the installation procedure for OMAP-L137 EVM Linux PSP package. Topic Page 2.1 Downloading the Release ........2–2 2.2 System Requirements.
MontaVista Pro 5.0 installed on RedHat Enterprise Linux WS release 4 and CCStudio v3.3 installed on Microsoft Windows XP Service Pack 2. ❏ Target Board. OMAP-L137 EVM ❏ Emulation Setup. Onboard emulation on OMAP-L137 EVM Only the OMAP-L137 EVM is required. Software ❏ Code Composer Studio 3.3.38...
Running the Installation Running the Installation Follow these steps to perform the necessary installations: 1) To install the PSP package, extract the release package with the following command (replace # in these commands with the release version number of your release package): tar -xzf REL_LSP_02_20_#_#.tgz The following files and directories are extracted:...
Page 14
Running the Installation 3) To install Linux kernel, mvl_5_0_0_demo_lsp_setuplinux_02_20_#_#.bin on the Linux host. This is a self-installing executable which installs a tar ball named LSP_02_20_#_#.tar.gz at the chosen location. 4) Untar the LSP_02_20_#_#.tar.gz tar ball to obtain the kernel sources. 5) Untar the PSP_02_20_#_#/board_utilities/u-boot-1.3.3.tar.gz file to obtain the U-Boot sources.
Chapter 3 Installing MontaVista Tools This chapter explains how to set up the demonstration version of the MontaVista Pro 5.0 software provided with the kit. Topic Page 3.1 Software Overview ........3–2 3.2 Preparing to Install .
❏ MontaVista Linux support package (LSP) installer. This is installed by the mvl_5_0_0_demo_lsp_setuplinux_#_#_#_#.bin file. Texas Instruments, in agreement with MontaVista Software Inc., is providing a demonstration version of the Linux Professional Edition v5.0.0 embedded operating system and development tools. The base software development kit includes a release of this demonstration version.
Preparing to Install Preparing to Install On a host system, mount the software development kit disks and copy the following .bin files to a temporary location with at least 2.3 GB available space. Since you may delete the installation files after installing the software, a directory like /tmp is recommended.
Page 18
Installing the Software To install the Linux software, follow these steps: 1) Log in as root on your host Linux workstation. This will allow you to successfully run the graphical installer to install MontaVista Linux. 2) Execute each of the following bin files (where is the current #_#_#_# version number) from the temporary location that they were copied in...
Installing the Software 3.3.2 Exporting a Shared File System for Target Access Although the EVM's flash memory can contain a Linux file system, during development it is more convenient to have the target board NFS mount a file system on a host Linux workstation. Once you have tested the application, you can store it on the EVM’s hard drive for a standalone demonstration.
Installing the Software Note: Use to re-export all directories. Use exportfs -rav to verify that the NFS status is running. /etc/init.d/nfs status 7) Verify that the server firewall is turned off: host $ /etc/init.d/iptables status If the firewall is running, disable it: host $ /etc/init.d/iptables stop 3.3.3 Testing the Shared File System...
Setting Up the Build/Development Environment Hints: You may want to use the printenv command to print a list of your environment variables. You can also save these setenv commands in a .txt file from which you can paste them in the future. 5) Save the environment so that you don't have to retype these commands every time you cycle power on the EVM board: EVM # saveenv...
Page 22
Setting Up the Build/Development Environment 3) Create a file called hello.c with the following contents: #include <stdio.h> int main() { printf("Buongiorno!\n"); return 0; 4) host $ arm_v5t_le-gcc hello.c -o hello Perform the following steps on the target board. You may use either the target's console window (Section A.4) or a telnet session.
Chapter 4 Building PSP Components This chapter explains how to build various components of the PSP. Topic Page 4.1 Building U-Boot ......... . 4–2 4.2 Building a New Linux Kernel .
The following build options can be modified: ❏ Choice of flash supported: ■ CFG_USE_SPIFLASH. When this flag is defined, U-Boot supports the SPI flash part on the OMAP-L137 EVM DSK board. The environment variables are stored on SPI flash. This option is switched on by default.
Building the SPI Flash User Boot Loader (UBL) Building the SPI Flash User Boot Loader (UBL) The following steps build the SPI Flash User Boot Loader (UBL) using CCStudio: 1) Start CCStudio v3.3. 2) From the menus, choose Project->Open. Browse to the REL_LSP_02_20_#_#/PSP_02_20_#_#/board_utilities/armubl directory and open the ubl.pjt project.
Chapter 5 Booting This chapter describes how to run the target content that is provided as a part of the PSP package. Topic Page 5.1 Booting from SPI Flash........5–2 5.2 Driver Configuration in the Linux Kernel .
Booting from SPI Flash Booting from SPI Flash Follow these steps to boot from SPI Flash: 1) Download files from http://support.spectrumdigital.com/boards/evmomapl137. Run the CCStudio Setup tool and ensure that the DSP and ARM GEL files are correctly specified. The file evmomapl137_arm.gel is the ARM side GEL file and evmomapl137_dsp.gel is the DSP side GEL file.
Driver Configuration in the Linux Kernel 6) Once the SPI flash has been written with the AIS file, switch off the board and set the SW2 switch on the DSK board as follows: Table 5–2 Final SW2 settings Pin# Position 7) Power up the board again.
Page 30
Driver Configuration in the Linux Kernel If you need to support ISO devices (such as audio), choose the following: <*> Reserve ISO Endpoint If you need to support MSC devices (such as pen drives), choose the following: --- USB Device Class drivers <*>...
Driver Configuration in the Linux Kernel 5.2.2 USB 1.1 Configuration The menus appear as follows: Device Drivers ---> USB support ---> <*> Support for Host-side USB --- Miscellaneous USB options [*] USB device filesystem --- USB Host Controller Drivers <*> OHCI HCD support If you need to support MSC devices (such as pen drives), choose the following:...
<*> Advanced Linux Sound Architecture System on Chip audio support ---> <*> ALSA for SoC audio support <*> SoC Audio support for DA830/OMAP-L137 EVM [*] DA830/OMAP-L137 McASP0 control by ARM [ ] DA830/OMAP-L137 McASP1 control by ARM [ ] DA830/OMAP-L137 McASP2 control by ARM DA830/OMAP-L137 CODEC --->...
Driver Configuration in the Linux Kernel The menus appear as follows: System Type ---> [ ] Support for NAND flash on UI board [ ] Support for NOR flash on UI board Device Drivers ---> Graphics support ---> < > Support for frame buffer devices <...
Building and Loading Kernel Modules The menus appear as follows: System Type ---> [ ] Support for NAND flash on UI board [*] Support for NOR flash on UI board Device Drivers ---> Character devices ---> < > DA830/OMAP-L137 Character LCD Support Graphics support --->...
Building and Loading Kernel Modules where the <root fs path> is the path of your root file system on the host machine. This is usually /opt/montavista/pro/devkit/arm/v5t_le/target/. On the target, use the command to get information on the modinfo module. Use the command to load the module.
Booting the Linux Kernel Using U-Boot Booting the Linux Kernel Using U-Boot Booting the kernel requires a valid kernel image (uImage) and a target filesystem. File systems of various kinds are supported by Linux kernel. A pre-built RAM Disk image can be found in your MontaVista tools installation <linux_install_dir>/pro/devkit/arm/v5t_le/images/ramdisk.gz directory.
Booting the Linux Kernel Using U-Boot 5.4.1 Booting from SDRAM Download the kernel and ramdisk image from Ethernet (using TFTP) into SDRAM. Then boot the kernel image from SDRAM. To achieve this, use the following settings (on a single line) for the U-Boot environment variables bootargs and bootcmd and reboot the DUT.
Booting the Linux Kernel Using U-Boot 5.4.3 Booting from USB Storage U-boot includes support for loading files from USB mass storage devices into memory. This section explains how to configure U-Boot to enable USB and mass storage support in U-Boot and the U-Boot commands used for initializing and loading files from mass storage devices connected to the USB 2.0 port on the EVM.
Page 39
Booting the Linux Kernel Using U-Boot same as for the command. For the optional fatload directory parameter you can specify the directory from which the contents should be listed. For example, the following command lists the contents of the first partition on the first USB storage device. U-Boot>...
Appendix A Additional Procedures This appendix describes optional procedures you may use depending on your setup and specific needs. Topic Page A.1 Loading the DSP User Bootloader into SPI-Flash Memory ..A–2 A.2 Building the SPI DSP AIS Binary ......A–3 A.3 Setting Up a TFTP Server .
Loading the DSP User Bootloader into SPI-Flash Memory Loading the DSP User Bootloader into SPI-Flash Memory Section 4.3 describes how to build the DSP User Bootloader (UBL). You can use the following steps to flash the DSP UBL into SPI-Flash using the DSP flash utility: 1) Open CCStudio 3.3 and connect to the DSP.
Building the SPI DSP AIS Binary Building the SPI DSP AIS Binary Building the DSP AIS binary requires CCStudio v3.3 and the AIS generation tool. Typically you should not need to rebuild the DSP AIS binary. In most cases, you can use the binary provided in the REL_LSP_02_20_#_#/PSP_02_20_#_#/bin directory.
Setting Up a TFTP Server Setting Up a TFTP Server You can check to see if a TFTP server is set up with the following command: host $ rpm -q tftp-server If it is not set up, you can follow these steps: 1) If you have not yet installed MontaVista Linux Demo Edition (see Section 3.3.1), you can download a TFTP server for your Linux host from many locations on the Internet.
Connecting to a Console Window Connecting to a Console Window You can open a console window that allows you to watch and interrupt EVM boot messages by following these steps: 1) Connect a serial cable between the serial port on the EVM and the serial port (for example, COM1) on a PC.
Page 47
Index DSP flash utility A-2 DSP User Bootloader, loading into SPI-Flash memory A-2 AIS generation tool A-3 audio configuration 5-6 EVM # prompt A-5 EVM (Evaluation Module) .bashrc file 3-7 boot messages, watching and interrupting A-5 build environment, setting up 3-7 file system in flash memory of 3-5 PSP package support for 1-2 system requirements for 2-2...
Page 48
SPI Flash 5-2 commands 5-10 compiling 4-2 included in PSP package 1-2 uImage kernel 5-10 OMAP-L137 EVM 1-2 USB 1.1 5-5 (see also EVM (Evaluation Module) USB 2.0 5-3 operating system requirements (see system require- usb info command 5-13...
Need help?
Do you have a question about the OMAP-L137 EVM and is the answer not in the manual?
Questions and answers