Texas Instruments TMS320DM357 DVEVM 2.05 Getting Started Manual
  1. Manuals
  2. Brands
  3. Texas Instruments Manuals
  4. Computer Hardware
  5. TMS320DM357
  6. Getting started manual
Texas Instruments TMS320DM357 DVEVM 2.05 Getting Started Manual

Texas Instruments TMS320DM357 DVEVM 2.05 Getting Started Manual

Hide thumbs Also See for TMS320DM357 DVEVM 2.05:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
TMS320DM357 DVEVM v2.05
Getting Started Guide
Literature Number: SPRUGH0
December 2008
Printed on Recycled Paper

Advertisement

Table of Contents
loading
Need help?

Need help?

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

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Texas Instruments TMS320DM357 DVEVM 2.05

Summary of Contents for Texas Instruments TMS320DM357 DVEVM 2.05

  • Page 1 TMS320DM357 DVEVM v2.05 Getting Started Guide Literature Number: SPRUGH0 December 2008 Printed on Recycled Paper...
  • 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 solu- tions:...
  • 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: About This Guide

    Preface About This Guide The DVEVM (Digital Video Evaluation Module) is an evaluation platform that showcases the DaVinci architecture and lets users evaluate the power and performance of DaVinci as a Multimedia engine. This guide gives you overview information about the board and the software provided with the board.
  • Page 6 Trademarks 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).
  • Page 8 Contents Setting Up the Build/Development Environment ......4-12 4.4.1 Writing a Simple Program and Running it on the EVM ....4-12 Building a New Linux Kernel .

  • Page 9: Dvevm Overview

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

  • Page 10: What's In This Kit

    What’s in this Kit? What’s in this Kit? Your TMS230DM357 DVEVM kit contains the following hardware items. Section 2.1, Setting Up the Hardware tells how to connect these components. ❏ EVM Board This board contains a DaVinci TMS320DM357 Digital Media System-on-Chip. ❏...

  • Page 11: What's On The Board

    What’s on the Board? What’s on the Board? The EVM comes loaded with peripherals your multimedia applications may need to make use of. The following block diagram shows the major hardware components. TI JTAG MSP430 User LEDs ARM JTAG JTAG Storage GPIO DC1 (EMIF)

  • Page 12: What's Next

    What’s Next? What’s Next? To get started evaluating the DVEVM kit and developing applications for the DM357, begin by using this Getting Started guide. It will step you through connecting the hardware, testing the software, and beginning to develop applications. When you are ready for more information about DaVinci Technology and the DM357 architecture, see the following: ❏...

  • 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 DVEVM kit, use the steps that follow. You may skip steps if you do not need to access a particular peripheral. For example, if you do not need to use the serial cable, skip that step.
  • Page 15 Setting Up the Hardware 1) On the S3 mini-dip switch, verify that positions 1 through 4 are configured to boot from on-board NAND as in the following figure, where the black rectangle is the switch location. Also on the S3 mini-dip switch, verify that position 10 selects the correct video format—NTSC or PAL.
  • Page 16 Setting Up the Hardware 3) Connect your video display to the composite video-out RCA connector (J8). Composite Video Out (J8) 4) Connect a video source (such as a camera or DVD player) to the composite video-in RCA connector (J12). Then power on your video input and output devices.
  • Page 17 Setting Up the Hardware 5) (Optional) If you plan to use the UART port for a console window, connect the provided RS-232 null modem cable to the EVM UART port (P6) and to a COM port on your host Linux workstation. 10/100 UART (P6) Power (J14)

  • Page 18: Connecting To A Console Window

    Connecting to a Console Window 9) You should see the initial screen of the demo software on your video display. Use the IR remote to run the software as described in Chapter 3. 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 19: 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 20: 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 21 Starting the Standalone Demos ❏ Command line. Once you have connected the EVM to a workstation and installed the necessary software (as described in Section 4.3.1, Installing the Target Linux Software), you can run the demos from the board’s Linux command line. For further information on running the demos from the command line, see the demo documentation that is linked to by the DVSDK release notes.
  • Page 22 Starting the Standalone Demos Once the EVM board has booted, your video 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; if your remote looks different, find the buttons with the same labels on your remote.

  • Page 23: 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 24: Shutting Down The Demos

    Running the Standalone Demos 8) This information overlays the video; as a result the video you see is darker than the actual video. To hide the information display so that you can better see the video, press the "Info/Select" button on the IR remote.

  • Page 25: 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. Video input comes from a source, it is encoded, then decoded, and sent to your video display. The Encode + Decode does only video processing;...
  • Page 26 Running the Standalone Demos Note that you can use only a speech encoder, not an audio encoder. The supported video algorithms are H.264 (.264 extension) and MPEG4 (.mpeg4 file extension). The supported speech algorithm is G.711 (.g711 extension). Table 3–2 IR Remote Buttons for Encode Demo IR Remote Button Mode Action Performed...

  • Page 27: About The Decode Demo

    Running the Standalone Demos 3.3.4 About the Decode Demo Note: You must run the Encode demo before you can run the Decode demo unless you have placed appropriately-named audio and video files on the EVM’s NAND flash storage device. If you see a message that says "File Not Found", please run the Encode demo.

  • Page 28: Running The Demos From The Command Line

    Running the Demos from the Command Line Running the Demos from the 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 3.2, Starting the Standalone Demos. Before running demo applications from the command line, the CMEM and accelerator kernel modules must be loaded.

  • Page 29: 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 as part of the Linux startup sequence. It configured to service requests from web browsers on the standard TCP/IP port 80.
  • Page 30 3-12...

  • Page 31: Dvevm Software Setup

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

  • Page 32: Software Overview

    Software Overview 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 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 integrated accelerators.

  • Page 33: Command Prompts In This Guide

    Software Overview 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. The base DVEVM kit includes a demonstration version. The demo version is a subset of what MontaVista provides with the full Professional Edition.

  • Page 34: Software Components

    Software Overview 4.1.2 Software Components The following figure shows the software components used for application development in the DVEVM kit: Application Imaging Video Codec Codec VISA API Framework Codec Engine Components Engine Audio Speech DMAN3 Codec Codec User Space Linux APIs Linux APIs Kernel Space CMEM...

  • Page 35: 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 1.2 GB available space. Since you can delete the installation files after installing the software, a directory like /tmp is recommended.

  • Page 36: Installing The Software

    Installing the Software Installing the Software Installing the software used by the DVEVM involves performing the following steps: ❏ Section 4.3.1, Installing the Target Linux Software ❏ Section 4.3.2, Installing the DVSDK Software ❏ Section 4.3.3, Installing the A/V Demo Files ❏...

  • Page 37: Installing The Dvsdk Software

    Installing the Software 5) Unpack the tar files (as root) by using the following commands: host $ tar zxf mvltools5.0-#######.tar.gz host $ tar zxf DaVinciLSP-#_#_#_#.tar.gz 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.

  • Page 38: Installing The A/V Demo Files

    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 A/V Demo Files The fourth disk contains the A/V files used by the demos. After following the instructions in the previous section, follow these instructions to install the A/V files: 1) Go to the demos directory in the DVSDK directory that you set up...
  • Page 39 Installing the Software 3) Switch user to " root " on the host Linux workstation. host $ su root 4) Perform the following commands to create a copy of the target file system with permissions set for writing to the shared area as <useracct>.

  • Page 40: Testing The Shared File System

    Installing the Software 4.3.5 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. host $ /sbin/ifconfig 2) Open a terminal emulation window to connect to the EVM board via RS-232 using the instructions in Section 2.2.

  • Page 41: Notes On Using Evaluation/Production Codecs

    Installing the Software 4.3.6 Notes on Using Evaluation/Production Codecs As part of the DM357 DVSDK installation, you received a number of codecs: ❏ Sequential JPEG Decoder ❏ Sequential JPEG Encoder ❏ MPEG4 Restricted Simple Profile Decoder ❏ MPEG4 Simple Profile Encoder ❏...

  • Page 42: Setting Up The Build/Development Environment

    Setting Up the Build/Development Environment 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 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 43: Building A New Linux Kernel

    Building a New Linux Kernel 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 the EVM board’s flash or by having the U-Boot utility use TFTP to boot the kernel over a network connection.

  • Page 44: Rebuilding The Dvevm Software For The Target

    Rebuilding the DVEVM Software for the Target 7) If the kernel is configured with any loadable modules (that is, selecting <M> for a module in menuconfig), use the following commands to rebuild and install these modules: host $ make ARCH=arm CROSS_COMPILE=arm_v5t_le- modules host $ make ARCH=arm CROSS_COMPILE=arm_v5t_le- INSTALL_MOD_PATH=/home/<useracct>/workdir/filesys modules_install 8) Use the following command to copy uImage to a place where U-Boot...

  • Page 45: Building With Dsplink

    Building with DSPLink ■ Make sure LINUXKERNEL_INSTALL_DIR is defined as follows: LINUXKERNEL_INSTALL_DIR=/home/<useracct>/workdir/lsp/ti-davinci/linux-2.6.18_pro500 ■ Modify the following environment variable as needed to match the location of XDCtools on your Linux host. We recommend that XDCtools be installed in the /home/<useracct>/dvsdk_#_# directory, but you may have installed it elsewhere. XDC_INSTALL_DIR=/home/<useracct>/dvsdk_#_#/xdctools_#_# 4) While in the same directory that contains Rules.make, use the following commands to build the DVSDK demo applications and put...

  • Page 46: Booting The New Linux Kernel

    Booting the New Linux Kernel Booting the New Linux Kernel After building the new kernel, in order to use it to boot the DaVinci board, you must transfer it to the board via TFTP. It is assumed you have completed the steps in Section 4.5, Building a New Linux Kernel and the boot file, uImage has been copied to /tftpboot (or some other site-specific TFTP accessible location).

  • Page 47: Using The Digital Video Test Bench (Dvtb)

    Using the Digital Video Test Bench (DVTB) Using the Digital Video Test Bench (DVTB) The Digital Video Test Bench (DVTB) is a Linux utility that was developed to execute end-to-end data flows using the DVSDK for any platform. DVTB uses the Codec Engine VISA APIs and Linux driver peripheral APIs to encode and decode video, image, audio and speech streams.
  • Page 48 4-18...

  • Page 49: 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 Changing the Video Input/Output Methods....A–2 A.2 Putting Demo Applications in the Third-Party Menu .

  • Page 50: Changing The Video Input/Output Methods

    Changing the Video Input/Output Methods Changing the Video Input/Output Methods U-Boot reads the S3 mini-dip switch, position 10 setting on boot-up and stores the results in the videostd environment variable. As long as your U-Boot bootcmd sets the video output using the videostd variable (as the example bootcmds in Section A.4, Alternate Boot Methods do), you can switch between NTSC and PAL by simply changing the S3 switch setting as shown in Section 2.1, Setting Up the Hardware.

  • Page 51: 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 52 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 53: 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 54: 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 board’s NAND flash. The following are alternate ways you may want to boot the board: ❏ TFTP boot with NAND flash file system (Section A.4.2) ❏...
  • Page 55 Alternate Boot Methods A.4.2 Booting via TFTP Using Board’s NAND Flash 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 console=ttyS0,115200n8 ip=dhcp root=/dev/mtdblock0 rw rootfstype=yaffs2 mem=232M video=davincifb:vid0=0,2025K:vid1=0, 1350K:osd0=720x576x16,...
  • Page 56 Alternate Boot Methods When you boot, look for the following lines that confirm the boot mode: ## Booting image at 80700000 ... Starting kernel ... VFS: Mounted root (nfs filesystem). A.4.4 Booting via TFTP Using NFS 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 serverip <ip addr of tftp server>...

  • Page 57: Updating/Restoring The Bootloaders

    Updating/Restoring the Bootloaders Updating/Restoring the Bootloaders The DM357 EVM board contains 2 GB of NAND flash memory. During the boot process 64 MB of NAND is used. After booting, 2 GB are used for the file system. When the EVM board is reset, the ROM bootloader (RBL) executes, initializing the board and then loading a small program called UBL (User Bootloader) from NAND flash memory into internal memory for execution.
  • Page 58 Updating/Restoring the Bootloaders ■ To assign a dynamic address, use the following: EVM # dhcp EVM # setenv ipaddr <IP address returned by dhcp> 2) Set the TFTP server IP address: EVM # setenv serverip <TFTP server IP address> 3) Save these settings to the flash memory: EVM # saveenv 4) Load U-Boot.
  • Page 59 Updating/Restoring the Bootloaders A.5.2 Updating UBL and U-Boot Bootloaders Using an Emulator and CCStudio If working U-Boot (or UBL) images are not present in flash, you will need to restore these images using Code Composer Studio (CCStudio) and an emulator. Follow these steps: 1) Find the NAND programmer utilities.

  • Page 60: Restoring The Nand Flash

    Restoring the NAND Flash Restoring the NAND Flash You can restore the contents of the DVSDK NAND flash memory on the EVM board via NFS (Section A.6.2) or via RAM Disk and an SD card (Section A.6.3). These contents include the Linux kernel and filesystem and the demo application software.
  • Page 61 Restoring the NAND Flash A.6.2 Restoring the NAND Flash Using NFS Once you have loaded the kernel binary to the corresponding NAND partition as described in Section A.6.1, you can use NFS to populate the YAFFS2 image (dm357_flash_image_#_#_#_#.tar) to the NAND partition.
  • Page 62 Restoring the NAND Flash A.6.3 Restoring the NAND Flash Using RAM Disk and a 2 GB SD Card This procedure assumes the TFTP setup in Section A.3 has been performed. Once you have loaded the kernel binary to the corresponding NAND partition as described in Section A.6.1, you can load the Ramdisk image (ramdisk.gz) to the DDR memory via TFTP.
  • Page 63 Restoring the NAND Flash 7) Execute the following commands to mount the MMC/SD and NAND partitions and populate the YAFFS2 image: EVM # mkdir /mnt/mmc EVM # mkdir /mnt/nand EVM # mount -t vfat /dev/mmcblk0 /mnt/mmc/ EVM # flash_eraseall /dev/mtd0 EVM # mount -t yaffs2 /dev/mtdblock0 /mnt/nand/ EVM # cd /mnt/nand EVM # tar xf /mnt/mmc/dm357_flash_image_#_#_#_#.tar...
  • Page 64 A-16...
  • Page 65 Index DaVinci technology community 1-4 Decode demo 3-5, 3-9 application 4-4 command line 3-10 arrow buttons 3-5 demos 3-2 audio 2-3 command line 3-10 Digital Video Test Bench (DVTB) building 4-17 documentation 4-17 disks 1-2 battery 1-3, 3-4 file contents 4-2 bin files 4-6 DISPLAY environment variable 4-5 block diagram 1-3...
  • Page 66 Index Encode demo 3-7 boot configuration A-6, A-7 on disks 4-2 restoring A-12 flash memory NAND programmer utilities A-11 boot configuration A-6, A-7 NFS server 4-8 boot configuration A-7, A-8 testing 4-10 NTSC video 2-3 G.711 speech 3-8, 3-9 GNU make, version 4-15 OSD show and hide 3-6 OSD toggle 3-6 H.264 video 3-7, 3-8, 3-9...
  • Page 67 Index components 1-2, 4-4 installing 4-6 speaker 2-3 UART port (P6) 2-5 Spectrum Digital website 1-3 UBL A-9 standalone demos 3-2 U-Boot A-9 static precautions 2-2 U-Boot utility 4-13 Stereo Line In (P3) 2-3 uImage boot file 4-16 Stereo Line Out (P5) 2-3 Stop button 3-6 SuSe Workstation 4-6 video-in (J12) 2-4...
  • Page 68 Spectrum Digital, Inc. 511458-0001B...

Table of Contents