Texas Instruments OMAP35 DVEVM Series Getting Started Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Motherboard
  5. OMAP35 Series
  6. Getting started manual
Texas Instruments OMAP35 DVEVM Series Getting Started Manual

Texas Instruments OMAP35 DVEVM Series Getting Started Manual

Hide thumbs Also See for OMAP35 DVEVM Series:
Table of Contents

Advertisement

Quick Links

Download this manual
OMAP35x DVEVM
Getting Started Guide
Literature Number: SPRUFZ7
Sept 23, 2009

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the OMAP35 DVEVM Series and is the answer not in the manual?

Questions and answers

Related Manuals for Texas Instruments OMAP35 DVEVM Series

Summary of Contents for Texas Instruments OMAP35 DVEVM Series

  • Page 1 OMAP35x DVEVM Getting Started Guide Literature Number: SPRUFZ7 Sept 23, 2009...
  • Page 2 TI product or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements. Following are URLs where you can obtain information on other Texas Instruments products and application solutions:...
  • Page 3 Date Sept 23, 2009 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, DEMONSTRATION, OR EVALUATION PURPOSES ONLY and is not considered by TI to be a finished end-product fit for general consumer use.
  • Page 4 TI products or services might be or are used. Mailing Address: Texas Instruments Post Office Box 655303 Dallas, Texas 75265 Copyright © 2008, Texas Instruments Incorporated FCC Warning...
  • Page 5 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Preface About This Guide The OMAP35x EVM is an evaluation platform that showcases the OMAP architecture and lets users evaluate the power and performance of OMAP as a flexible general purpose platform.
  • Page 6 Trademarks The Texas Instruments logo and Texas Instruments are registered trademarks of Texas Instruments. Trademarks of Texas Instruments include: TI, OMAP, the OMAP logo, XDS, Code Composer, Code Composer Studio, Probe Point, Code Explorer, DSP/BIOS, RTDX, Online DSP Lab, OMAP, TMS320, TMS320C54x, TMS320C55x, TMS320C62x, TMS320C64x, TMS320C67x, TMS320C5000, and TMS320C6000.

  • Page 7: Table Of Contents

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Table of contents Overview.............................. 10 What’s in the kit?........................10 What’s on the board? ......................11 What’s next? ........................... 12 Updates & Further information....................13 EVM Hardware Setup.......................... 14 Processor Module SW1 ......................
  • Page 8 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.4.2 Installing the DVSDK Software ..................... 32 4.4.3 Installing the A/V Demo Data....................34 4.4.4 Installing the Toolchain ......................35 4.4.5 Exporting a Shared File System for Target Access.............. 36 4.4.6 Testing the Shared File System....................
  • Page 9 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 7.5.3 Booting via TFTP Using Board’s NAND Flash File System..........64 7.5.4 Booting via TFTP using NFS file system ................65 Working With 256MB Micron mDDR Memory ................ 66 Additional Procedures .........................

  • Page 10: Overview

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 1 Overview This Chapter introduces the OMAP35x DVEVM (Digital Video Evaluation Module). 1.1 What’s in the kit? The OMAP35x DVEVM kit comes with the following hardware items. EVM Hardware Setup tells how to connect these components.

  • Page 11: What's On The Board

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 1.2 What’s on the board? The following block diagram shows the major hardware components. Micron Camera Provision for LI-3M02CM Camera Connector Module LI Camera Selection Connector Installed Header EHCI-USB2 Video...

  • Page 12: What's Next

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 1.3 What’s next? To get started evaluating the DVEVM kit and developing applications for the OMAP35x, begin by using this Getting Started guide. It is suggested that the user follow the sequence described in the document. The sequence is outlined below.

  • Page 13: Updates & Further Information

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 1.4 Updates & Further information Please be sure to register your EVM at: http://www.ti.com/omapregistration Once registered you will be able to find software and documentation updates at: http://www.ti.com/omapsoftwareupdates A wiki based information site is available.

  • Page 14: Evm Hardware Setup

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 2 EVM Hardware Setup This section will guide you through the process of setting up the EVM hardware for the purpose of running the supplied demo application. The information is the same as in the supplied Setup Guide. Step Section OMAP35x EVM Board Bottom...
  • Page 15 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Step Section OMAP35x EVM Board Top...

  • Page 16: Processor Module Sw1

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 2.1 Processor Module SW1 The DIP switch on the processor module controls various signal routing choices. Please be sure it matches the above diagram for normal operation. SW1 must be configured differently to use a JTAG emulator with the EVM.

  • Page 17: Uart1

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Note: Switch OFF == logic 1 and Switch ON == logic 0. 2.3 J8 Jumper J8 controls which OMAP UART is connected to the UART1/2 board connector. Make sure it selects UART1 as shown.

  • Page 18: Power Cable

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Note: This switch is not intended to be a power switch. It should be set to DC and left in that position. An external switch can be used to control the AC input to the power adapter if an adapter is desired. 2.9 Power Cable After all other steps are performed, ensure the power adapter is unplugged and then insert the adapter’s DC plug into P19.
  • Page 19 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 To create a new configuration for the serial port, run minicom as follows under root: # minicom -c on -s Command line options used above enable color (-c on) and start the setup procedure (-s). From the setup menu configure the serial port name and parameters - "Serial port setup"...

  • Page 20: Running The Demonstration Software

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 3 Running the Demonstration Software This chapter explains how to run the software demos provided with the OMAP35x DVEVM. 3.1 Default Boot Configuration Out of the box, the EVM boots from flash and starts the demos automatically after a few seconds when you power up the board.

  • Page 21: Starting The Standalone Demos

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 3.2 Starting the Standalone Demos When you connect the EVM hardware, the pre-loaded examples run automatically on your video display. These examples decode audio and video. There are two ways to use the demos: Standalone.

  • Page 22: Running The Standalone Demos

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 3.3 Running the Standalone Demos 1. Press "OK" on the keypad to move from the keypad interface diagram to the main menu screen, which looks like this: Decode Third Party Menu RIGHT...

  • Page 23: About The Decode Demo

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 3.3.1 About the Decode Demo The Decode demo plays audio and video files you select. You can select a source video file and a source audio file. Use the left and right arrow buttons to choose from the demo files and the files created by the encode example, which are stored on the EVM’s NAND flash.

  • Page 24: Running The Demos From Command Line

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 3.4 Running the Demos from Command Line You can run the demo applications from the Linux shell in a terminal window connected to the EVM board’s serial port. These are the same demos described in Section Starting the Standalone Demos. If the demos are currently running you should stop them using the S15 key until you see the "Quiting demo interface..."...

  • Page 25: Running The Video Encode Examples

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 3.5 Running the Video Encode examples The video encode examples are not available as standalone applications, but can be executed from command line. The current encode examples only support file based encode. If you wish to run the video encode examples, perform the following steps.

  • Page 26: Running The Image Encode Example

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Options MPEG4 SP Encode H.264 BP Encode Name of the codec to use (-c | -- codec) mpeg4enc h264enc As specified in the test As specified in the test parameters configuration parameters configuration Resolution (-r | --resolution)

  • Page 27: Running The Audio, Video And Image Decode Examples

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 -c | --codec Name of codec to use -e | --engine Codec engine containing specified codec -h | --help Print usage information (this message) -i | --input_file Name of input file to decode and perform cache maintenance.
  • Page 28 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 host $ chmod +x /home/<useracct>/workdir/filesys/opt/dvsdk/omap3530/video_decode_io2_omap3530.x470MV host $ chmod +x /home/<useracct>/workdir/filesys/opt/dvsdk/omap3530/audio_decode_io1_omap3530.x470MV host $ chmod +x /home/<useracct>/workdir/filesys/opt/dvsdk/omap3530/image_decode_io1_omap3530.x470MV 4. Use the –h option to determine the usage of the decode example applications and execute the decode example applications with the necessary parameters target $ ./video_decode_io2_omap3530.x470MV –h target $ ./audio_decode_io1_omap3530.x470MV –h...

  • Page 29: Omap35X Dvevm Software Setup

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4 OMAP35x DVEVM Software Setup 4.1 Software Overview To begin developing applications, you need to install the DVEVM development environment. This section outlines the steps required to load the DVEVM software onto the development host. You will need to download the files from the Download page to get started.

  • Page 30: Requirements

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 NOTE: The document lists down various commands that needs to be executed on the target or on the u-boot prompt for various operations required through out the document. Kindly note that a direct copy and paste of these commands might result in insertion of lines for a single command.

  • Page 31: Installing The Software

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.4 Installing the Software Installing the software used by the OMAP35x EVM involves performing the following steps. Installing the Target Linux Software Installing the DVSDK Software Installing the A/V demo files Installing the toolchain Exporting a Shared File System for Target Access Testing the Shared File System...

  • Page 32: Installing The Target Linux Software

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.4.1 Installing the Target Linux Software This section explains how to install Linux for use on the target board. Note that separate versions of Linux are used by the target and your host Linux workstation. The following Linux host operating systems are supported for use with the OMAP35x DVEVM.
  • Page 33 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 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/<useracct>/dvsdk_#_##_##_##.

  • Page 34: Installing The A/V Demo Data

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.4.3 Installing the A/V Demo Data The TI DVSDK software installer, by itself does not contain the media files used by the demos. You can download the data files from DVSDK download page or copy it from the DVD 2. Please use the steps mentioned below for extracting the media files into the desired location.

  • Page 35: Installing The Toolchain

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.4.4 Installing the Toolchain The CD-ROM contains the evaluation version of the CodeSourcery 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.

  • Page 36: Exporting A Shared File System For Target Access

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 To install the toolchain, follow the sequence below. These are to be executed on the Linux host platform. $ mkdir –p /home/<useracct>/toolchain  $ cp arm‐2008q1‐126‐arm‐none‐linux‐gnueabi‐i686‐pc‐linux‐gnu.tar.bz2 /home/<useracct>/toolchain  $ cd /home/<useracct>/toolchain  $ tar ‐jxvf  arm‐2008q1‐126‐arm‐none‐linux‐gnueabi‐i686‐pc‐linux‐gnu.tar.bz2  $ rm arm‐2008q1‐126‐arm‐none‐linux‐gnueabi‐i686‐pc‐linux‐gnu.tar.bz2  4.4.5 Exporting a Shared File System for Target Access Although the board’s NAND flash contains a file system, during development it is more convenient to have the target board NFS mount a file system on a host Linux workstation.
  • Page 37 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Alternatively, if you want to have permissions to write or create folders within the target file system that you want to export as NFS, perform the following command host $ chown ‐R <useracct> /home/<useracct>/workdir/filesys ...

  • Page 38: Testing The Shared File System

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.4.6 Testing the Shared File System To test your NFS setup, follow these steps: 1. Get the IP address of your host Linux workstations as follows. Look for the IP address associated with the eth0 Ethernet port.

  • Page 39: Notes On Using Production Codecs

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.4.7 Notes on using production codecs As part of the OMAP35x DVSDK installation, you received a number of codecs: MPEG4 Simple Profile Decoder. This decoder is compliant with IVIDDEC2 Interface H.264 Base Profile Decoder.

  • Page 40: Setting Up The Build/Development Environment

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4.5 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 OMAP3530 DVSDK is installed.
  • Page 41 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 #include <stdio.h>    int main() {  printf("Welcome to OMAP35x World!\n");  return 0;  4. Build the new C file: host $ arm‐none‐linux‐gnueabi‐gcc hello.c ‐o hello  Perform the following steps on the target board. You may use either the target's console window (see Setup Terminal Program) or a telnet session.

  • Page 42: Updating/Restoring The Flash Image

    1. Ensure that the host PC is connected to the board via UART as mentioned in Section 2.4. 2. Power On the board. Once you power on the board, the following will be printed on the hyperterminal or teraterm. Texas Instruments X-Loader 1.41 Detected Samsung MuxOneNAND1G Flash Starting OS Bootloader...

  • Page 43: Downloading U-Boot Via The Uart Downloader

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 LAN9x18 (0x01150002) detected. Setting mac address: 00:50:c2:7e:85:66 start Auto negotiation... (take ~2sec) Auto negotiation complete, 100BaseTX, full duplex 3. Stop the boot process by pressing the Enter key on the development PC keyboard. The u-boot prompt will appear.
  • Page 44 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Download in progress Download Complete NOTE: If you do not get the uboot prompt on pressing "Enter" after connecting the serial port cable to UART1, check if you have followed all the above steps properly. If the problem persists, your NAND could be corrupted.

  • Page 45: Using U-Boot To Update The Flash Memory

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 5.4 Using U-boot to Update the Flash Memory Now that U-boot is running on the target, you can use it to update any or all of the software in flash. The steps provided here will use the Ethernet connection with the TFTP protocol to transfer the files.

  • Page 46: Running The Re-Flash Procedure

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 PumpKIN Options Dialog 5.4.2 Running the Re-flash Procedure 1. Ensure that the terminal program is configured with ~ 100 ms of delay after sending each line as described in Section Setup Terminal Program 2.
  • Page 47 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 4. Check the IP settings OMAP3EVM # ping $(serverip)       (expect “x.x.x.x is alive”)  5. Use the terminal program to send the text file reflash.txt file to the EVM Make sure you know if your board has Samsung or Micron memory parts See Section Identifying Board Variations path: OMAP35x-PSP-SDK-##.##.##.##/scripts/ reflash-micron.txt (for Micron memory boards)
  • Page 48 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 setenv rf_ub          run rf_unlock\; run rf_blank_ram\; run rf_er_uboot\; run rf_get_uboot\; run  rf_wr_uboot  setenv rf_kn          run rf_unlock\; run rf_blank_ram\; run rf_er_kernel\; run rf_get_kernel\; run  rf_wr_kernel  setenv rf_rd          run rf_unlock\; run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_ramdisk\; run  rf_wr_ramdisk  setenv rf_min_rd      run rf_unlock\; run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_min_rd\; run  rf_wr_ramdisk  setenv rf_fs          run rf_unlock\; run rf_blank_ram\; run rf_er_fs\; run rf_get_fs\; run rf_wr_fs  setenv rf_all_rd      run rf_xl\; run rf_ub\; run rf_kn\; run rf_rd  setenv rf_all_min_rd  run rf_xl\; run rf_ub\; run rf_kn\; run rf_min_rd  setenv rf_all_fs      run rf_xl\; run rf_ub\; run rf_kn\; run rf_fs  printenv  echo done   echo Make sure to set MAC address  If you need to re-flash the target file systems that contains the demos that come along with the OMAP3530 DVSDK, or your own target file systems, refer section Flashing the Pre-built/rebuilt NAND Flash File System For HyperTerm use Transfer / Send Text File …...
  • Page 49 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 setenv bootargs_fs     mem=88M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2  omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y  setenv bootargs_nfs    mem=88M console=ttyS0,115200n8 noinitrd ip=dhcp rw root=/dev/nfs  nfsroot=<nfsserver_ip>:/home/<useracct>/workdir/filesys,nolock omapfb.rotate=1 omapfb.rotate_type=1  omap_vout.vid1_static_vrfb_alloc=y   The bootargs for DVSDK releases from 3.00.02.44 are as given below setenv bootargs_rd     mem=99M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,16M  ramdisk_size=40960 mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1  omap_vout.vid1_static_vrfb_alloc=y  setenv bootargs_fs     mem=99M console=ttyS0,115200n8 noinitrd root=/dev/mtdblock4 rw rootfstype=jffs2  mpurate=600 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y  setenv bootargs_nfs    mem=99M console=ttyS0,115200n8 noinitrd ip=dhcp rw root=/dev/nfs  nfsroot=<nfsserver_ip>:/home/<useracct>/workdir/filesys,nolock mpurate=600 omapfb.rotate=1  omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y   If the script is not used, use the above appropriate command (depending on ramdisk, NAND flash or NFS file system) to set the bootargs by using the following command For Ramdisk: setenv bootargs ‘bootargs_rd’ ...

  • Page 50: Rebuilding The Software

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 6 Rebuilding the Software This section describes how to rebuild pieces of the software delivery. Ensure that the toolchain setup and install has been completed (see section Installing the Toolchain). 6.1 Rebuilding U-boot Rebuilding the U-boot is described in more detail in the LSP User’s Guide available at OMAP35x-PSP-SDK-##.##.##.##/docs/UserGuide-##.##.##.##.pdf...

  • Page 51: Rebuilding The Linux Kernel

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 6.2 Rebuilding the Linux Kernel Rebuilding the kernel is described in more detail in the User’s Guide available at OMAP35x-PSP-SDK- ##.##.##.##/docs/UserGuide-##.##.##.##.pdf Note that building the kernel requires using mkimage, a host side utility built by the u-boot makefile. If you have not already done so please build u-boot using the instructions in the Rebuilding U-Boot section.

  • Page 52: Rebuilding The Dvsdk Software For The Target

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 6.3 Rebuilding the DVSDK Software for the target To place demo files in the /opt/dvsdk directory, you need to rebuild the DVSDK software. To do this, follow these steps: 1.
  • Page 53 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Make sure CODEC_INSTALL_DIR is defined as follows. (If you have installed it in a different location, ensure you set the correct path). CODEC_INSTALL_DIR=/home/<useracct>/dvsdk_#_##_##_##/cs1omap3530_#_##_##  Change the path of the CSTOOL_DIR to point to the location where you have installed the CodeSourcery tool-chain.

  • Page 54: Rebuilding The Initial Nand X-Loader

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 Note:Certain components have dependency on other components.So please make sure you have executed the make all command before proceeding for individual component build. host $ make help  NOTE: The dependencies for indivdual component builds are not addressed in the top level DVSDK Makefile.

  • Page 55: Rebuilding The Target-Side Uart Loader

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 6.5 Rebuilding the Target-side UART Loader Copy the UART loader dnld_util_target.tar.bz2 file from OMAP35x-PSP-SDK-##.##.##.##/src/utils directory into your working directory. host $ cd ~  host $ mkdir –p workdir/opt  host $ cp dnld‐util‐target.tar.bz2 ~/workdir/opt/. Un-tar the UART loader by performing the following command. host $ tar ‐jxvf dnld_util_target.tar.bz2 ...

  • Page 56: Rebuilding The Full Ramdisk Image

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 host $ sudo make –f targetfs_make clean_nfs DVSDKVER=<your version number #_##_##_##> For any clarification about the procedure please perform the below command host $ make –f targetfs_make help  Executing above command requires the users to have sudo access. The linux host would prompt for the user password and the user needs to enter his password for the make to continue.

  • Page 57: Rebuilding The Dsp Side Server Executables

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 NOTE: Also ensure that you have copied the overlay_dvsdk_#_##_##_##.tar.gz file to your /home/<useracct>/dvsdk_#_##_##_##/targetfs folder. Clean the old file system images: host $ cd /home/<useracct>/dvsdk_#_##_##_##/targetfs  host $ sudo make –f targetfs_make clean_old_rootfs DVSDKVER=<your version number #_##_##_##>  Create the JFFS2 Image (This requires building the NFS image to create the JFFS2 image from): host $ cd /home/<useracct>/dvsdk_#_##_##_##/targetfs ...
  • Page 58 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 C64P.rootDir=java.lang.System.getenv("CODEGEN_INSTALL_DIR");   cd /home/<useracct>/dvsdk_#_##_##_##/cs1omap3530_#_##_##  host $ make clean  host $ make rebuilt server executable found /home/<useracct>/dvsdk_#_##_##_##/cs1omap3530_#_##_##/packages/ti/sdo/server/bin directory and is named cs.x64P. The DSP side server executables can also be built from the DVSDK installation directory itself by following the below commands.

  • Page 59: Evm Operation

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 7 EVM Operation 7.1 Using Telnet The initialization file (/etc/init.d/rcS) starts a telnet server. If your development host is in the same sub-net as the EVM, you can telnet to it using the IP address assigned in the U-boot environment. $ telnet 192.168.1.10 ...
  • Page 60 Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 The bootargs for DVSDK releases from 3.00.00.36 up to and including 3.00.01.42 are as given below OMAP3EVM  #  setenv  bootargs  mem=88M  console=ttyS0,115200n8  noinitrd  root=/dev/mtdblock4  rw  rootfstype=jffs2 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y  The bootargs for DVSDK releases from 3.00.02.44 onwards are as given below OMAP3EVM ...

  • Page 61: Flashing The New Linux Kernel

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 7.2.3 Flashing the New Linux Kernel The Linux kernel can also be flashed on the NAND and then could be used for the boot. Perform the following steps for flashing the new or rebuilt Linux Kernel 1.

  • Page 62: Changing Options In U-Boot

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 OMAP3EVM # nandecc sw  OMAP3EVM # nand write.i 0x81600000 780000 6000000  Once the image is flashed, refer to section Booting From Flash using Board’s NAND Flash File System or section Booting via TFTP Using Board’s NAND Flash File System for booting using the NAND flash file system 7.4 Changing Options in U-boot If you use the environment provided by the initenv.txt script you have several choices for boot options.

  • Page 63: Alternate Boot Methods

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 OMAP3EVM # run rf_fs          (update just the JFFS image)  Note 1: The two ramdisk images and JFFS are all mutually exclusive in Flash as they occupy the same partition. (Running ramdisk from tftp does not require flash space). Note 2: The current U-boot only allows 40 environment variables.

  • Page 64: Booting From Flash Using Nfs File System

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 7.5.2 Booting from Flash Using NFS File System Make sure that the kernel image is flashed. To boot in this mode, set the following parameters after you abort the automatic boot sequence: For Micron NAND EVM: OMAP3EVM # setenv nand_kernel nand read.i 0x80000000 280000 300000  ...

  • Page 65: Booting Via Tftp Using Nfs File System

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 The bootargs for DVSDK releases from 3.00.00.36 up to and including 3.00.01.42 are as given below OMAP3EVM  #  setenv  bootargs      mem=88M  console=ttyS0,115200n8  noinitrd  ip=dhcp  root=/dev/mtdblock4  rw  rootfstype=jffs2 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y ...

  • Page 66: Working With 256Mb Micron Mddr Memory

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 7.6 Working With 256MB Micron mDDR Memory In case the EVM that you have has ES3.1 silicon and 256MB Micron memory part, and you wish to utilize the entire 256MB, the bootargs need to be changed to create a memory hole.

  • Page 67: Additional Procedures

    Name the tar file using <company>_<demoname>.tar.gz (with no spaces in the file name) as the convention. For example, a video phone demo created by Texas Instruments would be named ti_videophone.tar.gz. The name must be unique since all demos are installed in the same directory.

  • Page 68: Changing The Output Display To Dvi

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 /opt/dvsdk/omap3530/thirdpartydemos. Do not extract the contents of the archive in this location. Extraction is performed behind-the-scenes each time the demo is run. 8.2 Changing the Output Display to DVI The output display is set by default as LCD.You can change it to DVI either through Boot Mode Argument for the kernel or command line arguments once the kernel has booted.

  • Page 69: Enabling Audio Capture For Speech Encode

    Document OMAP35x DVEVM Getting Started Guide Document Number SPRUFZ7 Date Sept 23, 2009 target $ echo "gfx e:0" > /sys/devices/platform/omapfb/overlays  target $ echo "lcd e:0" > /sys/devices/platform/omapfb/displays  target $ echo "lcd t:none" > /sys/devices/platform/omapfb/managers  target $ echo "dvi e:1" > /sys/devices/platform/omapfb/displays  target $ echo "lcd t:dvi" > /sys/devices/platform/omapfb/managers  /* Set the Frame buffer parameters like xres, xres_virtual, y_res, yres_virtualagain before running below command. For example for 720P as DVI resolution setxres=1280 yres=720 xres_virtual=1280 yres_virtual=1440.*/ target $ echo "gfx e:1" > /sys/devices/platform/omapfb/overlays  ...

Table of Contents