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

Texas Instruments TMS320DM6467 DVEVM Getting Started Manual

V2.0
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
TMS320DM6467 DVEVM v2.0
Getting Started Guide
Literature Number: SPRUF88E
April 2009

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Related Manuals for Texas Instruments TMS320DM6467 DVEVM

Summary of Contents for Texas Instruments TMS320DM6467 DVEVM

  • Page 1 TMS320DM6467 DVEVM v2.0 Getting Started Guide Literature Number: SPRUF88E April 2009...
  • Page 2 IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, im- provements, and other changes to its products and services at any time and to discontinue any product or service without notice. Customers should obtain the latest relevant information before placing orders and should verify that such information is current and complete.
  • 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 Preface About This Guide The DVEVM (Digital Video Evaluation Module) kit is an evaluation platform that showcases the DM646x architecture and lets users evaluate the power and performance of the DM646x as a multimedia engine. This guide gives you overview information about the board and the software provided with the board.
  • Page 6 Trademarks Texas Instruments logo 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 DSP Lab, DaVinci, TMS320,...

  • Page 7: Table Of Contents

    Contents DVEVM Overview ............1-1 This chapter introduces the DVEVM (Digital Video Evaluation Module) kit.
  • Page 8 Contents 4.3.4 Installing the A/V Demo Files ........4-9 4.3.5 Installing the SoC Analyzer .

  • Page 9: Dvevm Overview

    Chapter 1 DVEVM Overview This chapter introduces the DVEVM (Digital Video Evaluation Module) kit. Topic Page 1.1 Welcome! ..........1–2 1.2 What’s in this Kit? .

  • Page 10: Welcome

    Welcome! Welcome! Your new DVEVM (Digital Video Evaluation Module) kit will allow you to evaluate TI’s new DaVinci Technology DM646x architecture. This technology brings together system-solution components tailored for efficient and compelling digital video and audio. What’s in this Kit? A DVEVM (DaVinci Evaluation Module) is a physical kit that includes the DVSDK software bundle, a demonstration version of MontaVista Linux Pro, the EVM board, and other hardware items.

  • Page 11: What's On The Board

    What’s on the Board? The DVEVM kit also comes with the following software. Information about how to use the software components is provided in Chapter 4. ❏ DaVinci Digital Video Evaluation Kit. ❏ TI DaVinci Demonstration Version of MontaVista Linux Pro v5.0 Target ❏...

  • Page 12: Registering The Software And Downloading Updates

    Registering the Software and Downloading Updates Registering the Software and Downloading Updates To download software updates and to register to receive notifications about future updates, follow these steps: 1) Go to http://www.ti.com/activatesoftware. ■ If you do not already have a my.TI login and password, you will be asked to create one.

  • Page 13: Evm Hardware Setup

    Chapter 2 EVM Hardware Setup This chapter tells you how to set up the EVM hardware. Topic Page 2.1 Setting Up the Hardware ........2–2 2.2 Connecting to a Console Window .

  • Page 14: Setting Up The Hardware

    Setting Up the Hardware Setting Up the Hardware To set up the hardware provided with the EVM, use the steps in the sections that follow. You may skip sections if you do not need to access a particular peripheral. For example, if you do not need to use the serial cable, skip that section.
  • Page 15 Setting Up the Hardware 3) Verify that the EVM board’s SW3 boot/muxing configuration switch is correctly set. The BM1, BM2, and BM3 switches should be set to On. These switch settings, which are shown in the following figure, enable the following: ■...
  • Page 16 Setting Up the Hardware 5) Connect a video source (for example, a camera or DVD player) to the component input video connectors (J1, J2, J3). Note: To run the demos described in Chapter 3, you will need to have an HD (720p) video source connected to the EVM board's component input connectors.
  • Page 17 Setting Up the Hardware 7) Connect an audio speaker to the headphone connector (P4). 8) Connect an audio source to the microphone connector (P8). EVM Hardware Setup...
  • Page 18 Setting Up the Hardware 9) If you plan to use the UART port for a console window, connect the RS-232 null modem cable to the EVM UART port (P1) and to the COM port of your host workstation. 10) Power on your video input and output devices. 11) Connect the power cable to the EVM power jack on the board.

  • Page 19: Connecting To A Console Window

    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 21: Running The Demonstration Software

    Chapter 3 Running the Demonstration Software This chapter explains how to run the software demos provided with the DVEVM kit. Topic Page 3.1 Default Boot Configuration....... . . 3–2 3.2 Starting the Standalone Demos .

  • Page 22: Default Boot Configuration

    Default Boot Configuration 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. It does not require an NFS mount or a TFTP server to run the standard demos. Note: The default U-Boot bootargs definition sets "ip=off", which disables the Ethernet connection.
  • Page 23 Starting the Standalone Demos running. Otherwise you will see error messages raised when device drivers fail to open. Once the EVM board has booted, the display should show a picture of the remote control. You use the IR remote to control the demos. The order of the buttons on the actual remote may be different from the picture;...

  • Page 24: Running The Standalone Demos

    Running the Standalone Demos Running the Standalone Demos 1) Press "Play" or "OK" on the remote to move from the remote control diagram to the main menu screen, which looks like this: The Encode + Decode demo allows you to record and playback video.

  • Page 25: Shutting Down The Demos

    Running the Standalone Demos 5) Use the left and right arrows to cycle through the options until the setting you want is shown. 6) Press "Play" to begin the Encode+Decode and Decode demos. Press "Rec" (record) twice to begin the Encode demo. 7) While the demo runs, data about the settings, processor load, and rates are shown.

  • Page 26: About The Encode + Decode Demo

    Running the Standalone Demos 3.3.2 About the Encode + Decode Demo The Encode + Decode demo allows you to record and playback video. from an HD video source connected to the EVM board's component input connectors, is encoded, then decoded, and then sent to a display connected to the EVM board's component video output connectors.

  • Page 27: About The Encode Demo

    Running the Standalone Demos The application runs on the ARM using Linux. The video signal is passed to video encoders and decoders on the DSP by the Codec Engine. Shared memory is used when passing data. To use this demo from the command line, see Section 3.4, Running the Demos from the Command Line.
  • Page 28 Running the Standalone Demos The supported video algorithm is H.264 (.264 file extension). The supported speech algorithm is G.711 (.g711 extension). The supported audio algorithm is AAC (.aac extension). Table 3–2 IR Remote Buttons for Encode Demo IR Remote Button Mode Action Performed Up/Down...

  • Page 29: About The Decode Demo

    Running the Standalone Demos 3.3.4 About the Decode Demo The Decode demo plays audio/speech and video files you select. You can select a source video file and a source audio or speech file. Use the left and right arrow buttons to choose from the demo files and the files created by the Encode demo, which are stored on the EVM’s hard disk drive.

  • Page 30: About The Third Party Menu

    Running the Demos from the Command Line Table 3–3 IR Remote Buttons for Decode Demo IR Remote Button Mode Action Performed Left/Right Change information transparency level Pause Pause demo (press Play to resume) Stop Setup / Run Return to previous screen The application runs on the ARM using Linux.
  • Page 31 Running the Demos from the Command Line 4) Before running demo applications from the command line, the CMEM and accelerator kernel modules must be loaded. ■ Use "lsmod" to see if they are loaded. You should see output similar to the following: Target $ lsmod Module Size...

  • Page 32: Running The Network Demo

    Running the Network Demo Running the Network Demo As an example of standard TCP/IP networking support, the DVEVM examples include a small HTTP web server. This web server is started on the GPP-side as part of the Linux startup sequence. It configured to service requests from web browsers on the standard TCP/IP port 80.

  • Page 33: Dvevm Software Setup

    Chapter 4 DVEVM Software Setup This chapter explains how to use the software provided with the DVEVM kit. Topic Page 4.1 Software Overview ........4–2 4.2 Preparing to Install .

  • Page 34: Software Overview

    Software Overview Software Overview To begin developing applications, you need to install the DVEVM development environment. This chapter outlines the steps required to load the DVEVM software onto the development host. You will need the distribution disks or the files they contain to get started. The DaVinci software approach provides interoperable, optimized, production-ready video and audio codecs that leverage DSP and integrated accelerators.

  • Page 35: Command Prompts In This Guide

    Section 1.4. After installing the DVSDK software in Section 4.3.2, you will install the codec servers in Section 4.3.3. Texas Instruments, in agreement with MontaVista Software Inc., is providing a demonstration version of the Linux Professional Edition v5.0 embedded operating system and development tools.

  • Page 36: Software Components

    Software Overview 4.1.2 Software Components The following figure shows the software components used for application development with the DVEVM kit: Application V-Node V-Node I-Node I-Node Video-Task Video-Task Image-Task Image-Task DMAI Imaging Imaging Video Video VISA API Codec Codec Codec Codec Codec Engine Engine Operating System...

  • Page 37: Preparing To Install

    Preparing to Install Preparing to Install On a host system, mount the DVEVM demonstration DVD 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.

  • Page 38: Installing The Target Linux Software

    Installing the Software 4.3.1 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. Note that separate versions of Linux are used by the target and your host Linux workstation.

  • Page 39: Installing The Dvsdk Software

    Installing the Software This creates the MontaVista directory structure under the /opt/mv_pro_5.0/montavista/ directory. Note that unpacking these tar files will overwrite any existing files that were previously installed. Note: The LSP shipped with the DVSDK is a multi-platform LSP; it is not configured for a particular platform.
  • Page 40 Installing the Software This installs the DVSDK in /home/<useracct>/dvsdk_#_#. 3) Execute the XDC installer that you previously copied from the DVSDK DVD. For example: host $ ./xdctools_setuplinux_#_#_#_#.bin 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>/dvsdk_#_#.

  • Page 41: Installing The Codec Servers

    Installing the Software Note: You can uninstall these components by using the rm -rf command on its directory. You should ignore the uninstall files created by the installer. 4.3.3 Installing the Codec Servers This release of the DVSDK does not install the codec servers when the DVSDK is installed.

  • Page 42: Installing The Soc Analyzer

    Installing the Software 4.3.5 Installing the SoC Analyzer SoC Analyzer is a graphical tool that runs on a Windows development host and uses data collected from Linux, DSP/BIOS, and Codec Engine to provide system-level execution and performance analysis for debugging and profiling DVEVM software execution. Follow these instructions to install SoC Analyzer: 1) Insert the TI DVSDK software disk into the Windows development host PC.

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

    Installing the Software 4.3.7 Exporting a Shared File System for Target Access Although the board’s hard drive 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. Once you have tested the application, you can store it on the board’s hard drive for a standalone demonstration.

  • Page 44: Testing The Shared File System

    Installing the Software 6) Still as root, use the following commands to make the NFS server aware of the change to its configuration and to invoke an NFS restart. host $ /usr/sbin/exportfs -av host $ /sbin/service nfs restart Note: Use to re-export all directories.

  • Page 45: Notes On Using Evaluation/Production Codecs

    Installing the Software 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 46: Setting Up The Build/Development Environment

    Setting Up the Build/Development Environment Setting Up the Build/Development Environment To set up the GPP-side development and build environment, follow these steps: 1) Log in to your user account (and not as root) on the NFS host system. 2) Set your PATH so that the MontaVista tool chain host tools and cross compiler (arm_v5t_le-gcc) can be found.

  • Page 47: Building A New Linux Kernel

    Building a New Linux Kernel Perform the following steps on the target board. You may use either the target's console window (Section 2.2) or a telnet session. 1) target $ cd /opt/hello 2) Run ./hello. The output should be: Buongiorno DaVinci! Building a New Linux Kernel If you modify the target’s Linux kernel sources, you will need to rebuild it and then boot it up by either replacing the kernel that comes installed on...
  • Page 48 Building a New Linux Kernel 6) If you want to enable Linux Trace for the SoC Analyzer, follow these substeps. Otherwise, skip to Step 7. a) Use this command to go to the configuration menu for the ARM: host $ make ARCH=arm CROSS_COMPILE=arm_v5t_le- menuconfig b) Navigate to Device Drivers->Filesystems->Pseudo Filesystems.

  • Page 49: Rebuilding The Dvsdk Software For The Target

    Rebuilding the DVSDK Software for the Target Rebuilding the DVSDK Software for the Target To place demo files in the /opt/dvsdk/dm6467 directory, you need to rebuild the DVSDK software. To do this, follow these steps: 1) If you have not already done so, rebuild the Linux kernel as described in Section 4.5.

  • Page 50: Booting The New Linux Kernel

    Booting the New Linux Kernel the resulting binaries on the target file system specified by EXEC_DIR. host $ make clean host $ make host $ make install 5) You can test the rebuilt DVEVM software by booting your NFS file system and running the demos from the command line as described in Section 3.4.

  • Page 51: Testing The Build Environment

    Testing the Build Environment Testing the Build Environment To test your DVSDK software installation, you can build one of the Codec Engine servers. This server is a DSP-side application. Building it tests the installation of DSP-side development components. You must have also installed the codec servers as described in Section 4.3.3.

  • Page 52: Configuring And Compiling The Linux Performance Test Bench

    Configuring and Compiling the Linux Performance Test Bench 3) Copy the binaries "dvtb-d" and "dvtb-r" to /opt/dvsdk/dm6467 on the device’s target filesystem and run it there. It must be in the same directory as the DSP executables. For further details on the DVTB, see the following documents: ❏...

  • Page 53: Running The Soc Analyzer

    Running The SoC Analyzer 4.11 Running The SoC Analyzer Built upon Texas Instruments' eXpressDSP data visualization technology (DVT), the SoC Analyzer simplifies debugging, analysis, and optimization of DVEVM applications. It collects execution, interaction, and resource utilization logs from Linux, DSP/BIOS, Codec Engine, and drivers and presents system-level analysis and graphical visualization such as: ❏...

  • Page 54: Documentation For Dsp-Side Development

    Documentation for DSP-Side Development To run the SoC Analyzer, double-click the SoC Analyzer icon on the Windows Desktop or select it from the Windows Start menu under Texas Instruments. The SoC Analyzer comes with online help, which can be accessed from the SoC Analyzer Help menu (choose Help->Help Contents).
  • Page 55 Documentation for DSP-Side Development Table 4-1. Documentation for DVSDK Components Component Title Location Section 4.9, Using the Digi- this document tal Video Test Bench (DVTB) Codec Engine Codec Engine Application /home/<useracct>/dvsdk_#_#/codec_engine_#_#/docs Developer User's Guide (SPRUE67) Codec Engine Server /home/<useracct>/dvsdk_#_#/codec_engine_#_#/docs Integrator User's Guide (SPRUED5) Codec Engine Algorithm /home/<useracct>/dvsdk_#_#/codec_engine_#_#/docs...
  • Page 56 4-24...

  • Page 57: Additional Procedures

    Appendix A Additional Procedures This appendix describes optional procedures you may use depending on your setup and specific needs. Topic Page A.1 Putting Demo Applications in the Third-Party Menu ... . A–2 A.2 Setting Up a TFTP Server .

  • Page 58: Putting Demo Applications In The Third-Party Menu

    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 59 Putting Demo Applications in the Third-Party Menu uses relative references to access them. For example, the following directory structure might be used in the archive: |-- app.sh |-- data |-- datafile1 `-- datafile2 |-- logo.jpg `-- readme.txt To check the format of the file you create, execute the following command in Linux.

  • Page 60: Setting Up A Tftp Server

    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 4.3.1), you can download a TFTP server for your Linux host from many locations on the Internet.

  • Page 61: Alternate Boot Methods

    Alternate Boot Methods Alternate Boot Methods The default configuration for the EVM is to boot from flash with the file system on the EVM’s hard drive. The following are alternate ways you may want to boot the board: ❏ TFTP boot with hard drive file system (Section A.3.2) ❏...

  • Page 62: Booting Via Tftp Using The Evm's Hard Drive File System

    Alternate Boot Methods A.3.2 Booting via TFTP Using the EVM’s Hard Drive File System To boot in this mode, set the following parameters after you abort the automatic boot sequence: EVM # setenv bootcmd 'dhcp;bootm' EVM # setenv bootargs mem=120M console=ttyS0,115200n8 root=/dev/hda1 rw noinitrd ip=dhcp davincihd_capture.channel0_numbuffers=4 EVM # setenv serverip <tftp server ip address>...

  • Page 63: Rebuilding Dsp/Bios Link

    Rebuilding DSP/BIOS Link Rebuilding DSP/BIOS Link If you want to rebuild the DSP/BIOS Link package, follow these steps (assuming you are using the bash shell): 1) Edit davinci_mvlpro5.0.mk file, which /home/<useracct>/dvsdk_#_#/dsplink_#/packages/dsplink/make/Linux/ directory, to make sure the BASE_BUILDOS and BASE_CGTOOLS variables correctly point to the correct locations. For example: BASE_BUILDOS := /home/<useracct>/workdir/lsp/ti-davinci/linux-2.6.18_pro500 BASE_CGTOOLS := /opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin 2) Define the DSPLINK environment variable to be the absolute path to...

  • Page 64: Restoring And Updating The Evm Hard Disk Drive

    Restoring and Updating the EVM Hard Disk Drive Restoring and Updating the EVM Hard Disk Drive This section describes how to restore and update all the files on the EVM hard disk drive (HDD), including the Linux file system and the demos. Using these restore procedures, you can return your board to a known state if anything happens to the data on the EVM board’s HDD.
  • Page 65 Restoring and Updating the EVM Hard Disk Drive 4) Change directory to /mnt/restore: EVM # cd /mnt/restore 5) Add execute permissions for the script: EVM # chmod +x restore-hdd 6) Run the restore script: EVM # ./restore-hdd 7) The script will ask for confirmation: "This will destroy all data on /dev/hda1 - are you sure?"...

  • Page 66: Restoring From Host Linux Workstation File System

    Restoring and Updating the EVM Hard Disk Drive A.5.2 Restoring From Host Linux Workstation File System Follow these steps to restore the HDD from the host Linux workstation restore directory: 1) On your host workstation, copy the restore directory from the TI DVSDK disk to /home/<useracct>/workdir/filesys/restore.
  • Page 67 Index CPU load 3-5 A/V files 4-9 AAC audio 3-9 application 4-4 data files 4-9 ARM9 1-2 DaVinci technology 1-2 arrow buttons 3-4 Decode demo 3-4, 3-9 command line 3-11 demos 3-2 command line 3-10 Digital Video Test Bench (DVTB) battery 3-3 building 4-19, 4-22 bin files 4-6...
  • Page 68 Index boot/muxing configuration switch 2-3 component video 2-4 JTAG 2-2 EMU0/1 select switch 2-2 Ethernet port 2-3 headphone connector (P4) 2-5 microphone connector 2-5 UART port 2-6 kit contents 1-2 EVM # prompt 2-7, 4-3 examples 3-2 exit demo 3-5 exports file 4-11 Link, DSP/BIOS 4-4 Linux 4-4...
  • Page 69 Index prompts 4-3 target $ prompt 4-3 terminal session 2-7 test program 4-14 quit demo 3-5 TFTP boot configuration A-6 server A-4 transfer files to board 4-18 Third-Party Menu 3-4, A-2 rebuilding TMS320DM6467 1-2 DVSDK software 4-17 transparency of OSD 3-5 Linux kernel 4-15 Record button 3-5 Red Hat Enterprise Linux 4-6...
  • Page 70 Index--4...
  • Page 72 Spectrum Digital, Inc. 509538-0001F...

Table of Contents