Summary of Contents for Texas Instruments TMS320DM6446 DVEVM v2.0
Page 1
TMS320DM6446 DVEVM v2.0 Getting Started Guide Literature Number: SPRUE66E December 2008...
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
Preface About This Guide The DVEVM (Digital Video Evaluation Module) kit is an evaluation platform that showcases the DM644x architecture and lets users evaluate the power and performance of the DM644x 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,...
Contents DVEVM Overview ............1-1 This chapter introduces the DVEVM (Digital Video Evaluation Module) kit.
Page 8
Contents 4.3.5 Exporting a Shared File System for Target Access ....4-9 4.3.6 Testing the Shared File System ....... . . 4-11 4.3.7 Configuring the Boot Setup for PAL Video Users .
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? .
Welcome! Welcome! Your new DVEVM (Digital Video Evaluation Module) kit will allow you to evaluate TI’s new DaVinci Technology DM644x architecture. This technology brings together system-solution components tailored for efficient and compelling digital video and audio.
What’s in this Kit? What’s in this Kit? Your 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 TMS320DM6446 dual- core device with an ARM9 and C64+ DSP for development of applications that use both a general-purpose processor and an accelerated DSP processor.
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 hard drive on the board also comes pre- loaded with demonstration software. The following block diagram shows the major hardware components.
What’s Next? What’s Next? To get started evaluating the DVEVM kit and developing applications for the DM644x, 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 DM644x architecture, see the following: ❏...
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 .
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 17
Setting Up the Hardware 4) Connect the red and white audio cables to the EVM Audio Output and the LCD display R/L Audio Input jacks as shown below: 5) Connect the BNC-to-RCA connector to the coax cable. Then connect the coax cable to the video camera and the EVM Video Input. 6) Connect the power jack for the video camera.
Page 18
Setting Up the Hardware 7) Connect the microphone to the EVM. 8) Connect the power cable to the EVM power jack on the board. To be ESD safe, do not plug in the other end of the cable yet. 9) If you will use the Ethernet connection, connect the Ethernet cable to the Ethernet Port on the EVM and to an Ethernet network port.
Page 19
Setting Up the Hardware 10) If you plan to use the UART port for a console window, connect the RS-232 null modem cable to the EVM UART port and a COM port on your host Linux workstation. See Section 2.2, Connecting to a Console Window for more about using 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.
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 .
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;...
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.
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.
Running the Standalone Demos 3.3.2 About the Encode + Decode Demo The Encode + Decode demo allows you to record and playback video. Video comes from the camera, is encoded, then decoded, and then sent to the LDC display. The Encode + Decode does only video processing; it does not encode and decode audio or speech.
Running the Standalone Demos 3.3.3 About the Encode Demo Like the Encode + Decode demo, the Encode demo also encodes video. In addition, it also encodes speech. The speech source is the microphone. The encoded data is written to files on the EVM’s hard disk drive. The possible filenames are demo.264, demo.mpeg4, demompeg4.g711, and demo264.g711.
Running the Standalone Demos Table 3–2 IR Remote Buttons for Encode Demo IR Remote Button Mode Action Performed Info/Select Setup Show / hide block diagram for demo Info/Select Toggle information display Left/Right Change information transparency level (There is no display for encode demo behind the information.) Pause Pause demo (press Record to resume)
Running the Demos from the Command Line The supported video algorithms are MPEG4 (.mpeg4 file extension), H.264 (.264 file extension) and MPEG2 (.m2v file extension). The supported audio algorithm is AAC (.aac file extension). The supported speech algorithm is G.711 (.g711 file extension). Table 3–3 IR Remote Buttons for Decode Demo IR Remote Button Mode...
Page 30
Running the Demos from the Command Line 3) Move to the appropriate directory on the target using the following command. (See Section 4.1.1 for the meanings of command prompts shown in this document.) Target $ cd /opt/dvsdk/dm6446 4) Before running demo applications from the command line, the CMEM and accelerator kernel modules must be loaded.
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.
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 .
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.
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 this demonstration version. The demo version is a subset of what MontaVista provides with the full Professional Edition.
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...
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.
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.
Installing the Software 4.3.2 Installing the DVSDK Software The DVSDK software includes Codec Engine components, DSP/BIOS Link, sample data files, xDAIS and xDM header files, and a contiguous memory allocator for Linux (CMEM). Note: The installers for DSP/BIOS and Code Generation Tools (codegen) have a different default installation location.
Installing the Software When the installer prompts for an installation location, do not use the default location. Instead, use the entire path to the dvsdk_#_# codegen directory. You will need to manually create the folder cg6x_6_#_#, where # represents part of the version number. For example: /home/<useracct>/dvsdk_#_#/cg6x_6_0_16 Remember to set the environment variable as directed by the...
Installing the Software 4.3.4 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 42
Installing the Software 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>. Substitute your user name for <useracct>. If you installed in a location other than /opt/mv_pro_5.0, use your location in the cp command.
Installing the Software 4.3.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. 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.
Installing the Software See Section A.4, Alternate Boot Methods for information about booting with TFTP or NFS and using flash or the EVM’s hard drive. 4.3.7 Configuring the Boot Setup for PAL Video Users You can configure the EVM to select either the NTSC or PAL video standard during the default boot sequence.
Setting Up the Build/Development Environment These codecs are provided under a "for demonstration-only" license agreement. If you wish to use these codecs in a production development environment, you can go to the DVEVM Updates web site at http://www.ti.com/dvevmupdates to download the latest production versions, along with the appropriate license agreement.
Building a New Linux Kernel 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 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...
Page 47
Building a New Linux Kernel 5) To modify the kernel options, you will need to use a configuration command such as "make menuconfig" or "make xconfig". To enable the MontaVista default kernel options, use the following command: host $ make ARCH=arm CROSS_COMPILE=arm_v5t_le- checksetconfig 6) If you want to enable Linux Trace for the SoC Analyzer, follow these substeps.
Rebuilding the DVEVM Software for the Target Rebuilding the DVEVM Software for the Target To place demo files in the /opt/dvsdk/dm6446 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.
Booting the New Linux Kernel 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. 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.
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. To build the video_copy server, follow these steps: 1) Go to /home/<useracct>/dvsdk_#_#/codec_engine_#_#/examples and open the build_instructions.html file.
Page 51
Using the Digital Video Test Bench (DVTB) 3) Copy the binaries "dvtb-d" and "dvtb-r" to /opt/dvsdk/dm6446 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: ❏...
Running The SoC Analyzer 4.10 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: ❏...
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 54
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...
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 .
Changing the Video Input/Output Methods Changing the Video Input/Output Methods The EVM can input video using the following methods: ❏ Composite [default] ❏ S-Video (best quality) In addition, there are three types of video output: ❏ Composite [default] (lowest quality) ❏...
Page 57
Changing the Video Input/Output Methods A.1.2 Using S-Video Output To switch to higher-quality S-Video output, follow these steps: 1) Unplug the composite video connector. Then, connect your S-Video connector to the S-Video output port, which is to the right of the currently-used composite video output port.
Page 58
Changing the Video Input/Output Methods A.1.3 Using Component Video Output To switch to highest-quality component video output, follow these steps: 1) Connect your component video connectors to the connectors in a square on the far left of the board. Instead of connecting one connector as with composite video, connect the YPrPb connectors as shown here.
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 60
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.
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.
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.4.2) ❏...
Page 63
Alternate Boot Methods To boot in this mode, set the following parameters after you abort the automatic boot sequence: EVM # setenv bootcmd bootm 0x2050000 setenv bootcmd nboot 80700000 0 a0000;bootm EVM # setenv bootargs video=davincifb:vid0=720x576x16, 2500K:vid1=720x576x16,2500K:osd0=720x576x16,2025K davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=$(videostd) console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/hda1 mem=120M Note: If you have flashed a new kernel to the NOR flash at an address other than 0x2050000, modify the bootcmd definition accordingly.
Page 64
Alternate Boot Methods A.4.3 Booting from Flash Using NFS File System To boot in this mode, set the following parameters after you abort the automatic boot sequence: EVM # setenv bootcmd 0x2050000 setenv bootcmd nboot 80700000 0 a0000;bootmEVM # setenv nf- shost <ip address of nfs host>...
Rebuilding DSP/BIOS Link The <root directory to mount> must match the file system that you set up on your workstation. For example, /home/<useracct>/workdir/filesys. When you boot, look for the following lines that confirm the boot mode: TFTP from server 192.168.160.71; our IP address is 192.168.161.186 Filename 'library/davinci/0.4.2/uImage'.
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 67
Restoring and Updating the EVM Hard Disk Drive For example, you can create a terminal session with HyperTerminal or TeraTerm on MS Windows, and Minicom or C-Kermit on Linux. 6) Start an NFS server on the host workstation. This document assumes the host path /home/user/workdir/filesys contains a file system that the target EVM can use for root mounting.
Page 68
Restoring and Updating the EVM Hard Disk Drive A.6.3 Restore the EVM Hard Disk Drive The EVM hard disk drive (HDD) can be restored from a target EVM HDD partition or from the host Linux workstation file system. Either method will achieve the same result.
Page 69
Restoring and Updating the EVM Hard Disk Drive 7) The script will ask for confirmation: "This will destroy all data on /dev/hda1 - are you sure?" Type yes. 8) After the HDD restore is complete, shutdown the EVM: EVM # halt 9) When the "Power down"...
Page 70
Restoring and Updating the EVM Hard Disk Drive 3) Go to the /restore directory. EVM # cd /restore 4) Set the Linux date variable to today's date. If the date is too far off, the target file system installation generates warnings for each file it installs.
Page 71
Index console window 2-6 contents of kit 1-3 CPU load 3-5 A/V files 4-8 AAC audio 3-9 application 4-4 ARM9 1-3 arrow buttons 3-4 data files 4-8 audio cables 2-3 DaVinci technology 1-2 Decode demo 3-4, 3-8 command line 3-10 demos 3-2 command line 3-9 battery 1-4, 3-3...
Page 73
Index prompts 4-3 target $ prompt 4-3 terminal session 2-6 test program 4-13 quit demo 3-5 TFTP boot configuration A-9, A-10 server A-7 transfer files to board 4-17 Third-Party Menu 3-4, A-5 rebuilding TMS320DM6446 1-3 DVEVM software 4-16 transparency of OSD 3-5 Linux kernel 4-14 Record button 3-5 Red Hat Enterprise Linux 4-6...
Need help?
Do you have a question about the TMS320DM6446 DVEVM v2.0 and is the answer not in the manual?
Questions and answers