TMS320DM357 DVEVM v2.
IMPORTANT NOTICE Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications, enhancements, improvements, 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.
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. Persons handling the product(s) must have electronics training and observe good engineering practice standards.
FCC Warning 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. 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.
This is a draft version printed from file: pref.fm on 12/15/08 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. It is intended to be used as an introductory document for the DVEVM. Other documents provide more in-depth information.
Trademarks Trademarks The Texas Instruments logo and Texas Instruments are registered trademarks of Texas Instruments. Trademarks of Texas Instruments include: TI, DaVinci, the DaVinci logo, XDS, Code Composer, Code Composer Studio, Probe Point, Code Explorer, DSP/BIOS, RTDX, Online DSP Lab, DaVinci, TMS320, TMS320C54x, TMS320C55x, TMS320C62x, TMS320C64x, TMS320C67x, TMS320C5000, and TMS320C6000. MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation.
This is a draft version printed from file: davinci_gsgTOC.fm on 12/15/08 Contents 1 DVEVM Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1 This chapter introduces the DVEVM (Digital Video Evaluation Module). 1.1 What’s in this Kit? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 1.2 What’s on the Board? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4.4 4.5 4.6 4.7 4.8 4.9 A 4-12 4-12 4-13 4-14 4-15 4-16 4-17 Additional Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 This appendix describes optional procedures you may use depending on your setup and specific needs. A.1 A.2 A.3 A.4 A.5 A.6 viii Setting Up the Build/Development Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1 Writing a Simple Program and Running it on the EVM . . . . . . .
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? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3 1.3 What’s Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What’s in this Kit? 1.1 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. ❏ Universal Power Supply. Both U.S. and European power are supported. ❏ Cables. Serial and Ethernet cables are included to allow for host development. ❏ IR Remote Control (Phillips).
What’s on the Board? 1.2 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. IR TI JTAG MSP430 JTAG ARM JTAG SD/ MMC S1 Storage NAND DC1 (EMIF) User LEDs PWR SW I2C GPIO 3V BAT MSP430 Boot NAND CPLD DC6 I2C EMIF DDR TMS320 DM357 S3 Config DDR DC7 1.8V I/O Voltage 1.
What’s Next? 1.3 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: 1-4 ❏ Spectrum Digital website: http://support.spectrumdigital.com/boards/evmdm357 ❏ TI DaVinci Software Updates: http://www.
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 2.1 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. For reference, the numbers in the following photo of the DM357 EVM target board correspond to the steps in the procedure. 8 1 3 2 4 6 5 Important: The EVM board is sensitive to static discharges.
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. 1 2 3 4 5 6 7 8 9 10 Also on the S3 mini-dip switch, verify that position 10 selects the correct video format—NTSC or PAL. The following diagram shows the switch in the NTSC setting. 2) Connect an audio speaker to Stereo Line Out (P5) and an audio source to Stereo Line In (P3).
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.
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 Ethernet (P2) UART (P6) Power (J14) 6) (Optional) If you will be using an Ethernet connection, connect the provided Ethernet cable to the Ethernet port (P2) on the EVM board and to an Ethernet network port.
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. 2.2 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2 3.3 Running the Standalone Demos . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5 3.4 Running the Demos from the Command Line . . . . . . . . . . . . . . . .
Default Boot Configuration 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. 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. The out-of-the-box boot parameters are listed in Section A.4.1.
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.
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. To use the demos in standalone mode, follow these steps: 1) Check to make sure the batteries are installed in your IR remote.
Running the Standalone Demos 3.3 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. The Encode demo records audio/speech and video in the formats you select. The Decode demo plays audio/speech and video files you select. 2) Use the up and down arrows to change which demo is selected.
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. You can change the transparency of the OSD (overlay) while running a demo by using the left and right arrows on the remote. 9) Press "Stop" or "Pause" when you want to end or pause a demo. The first time you press "Stop", you return to the settings screen.
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; it does not encode and decode audio or speech. The supported video algorithm is H.264 (.264 file extension).
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).
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. 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.
Running the Demos from the Command Line 3.4 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. Use "lsmod" to see if they are loaded.
Running the Network Demo 3.5 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. After the EVM board has booted, connect a PC to the same network to which the EVM board is connected.
3-12
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–5 4.3 Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–6 4.4 Setting Up the Build/Development Environment . . . . . . . . . . . .
Software Overview 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 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.
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.
Software Overview 4.1.2 Software Components The following figure shows the software components used for application development in the DVEVM kit: I/O I/O I/O Application xDM API Video Codec xDM API Imaging Codec xDM API Speech Codec xDM API Audio Codec VISA API Framework Components DMAN3 User Space Codec Engine VID IMG SPH AUD Engine Linux APIs Kernel Space CMEM Driver USB 2.
Preparing to Install 4.2 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. ❏ mvl_5_0_demo_sys_setuplinux.bin (disk 1) ❏ mvl_5_0_0_demo_lsp_setuplinux_#_#_#_#.bin (disk 2) ❏ dvsdk_dm357_setuplinux_#_#_#_#.bin (disk 2) ❏ xdctools_setuplinux_#_#_#.
Installing the Software 4.3 Installing the Software Installing the software used by the DVEVM involves performing the following steps: 4.3.1 ❏ 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 ❏ Section 4.3.4, Exporting a Shared File System for Target Access ❏ Section 4.3.
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. Note: The LSP shipped with the DVSDK is a multi-platform LSP and is not configured for a particular platform.
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 previously.
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 . Substitute your user name for . If you installed in a location other than /opt/mv_pro_5.0, use your location in the cp command. host $ cp -a /opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/target/* .
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. If you have a Windows workstation, you can use HyperTerminal. If you have a Linux workstation, you might use Minicom.
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 ❏ H.264 Base Profile Decoder ❏ H.264 Base Profile Encoder ❏ G.711 Decoder (not a TI codec) ❏ G.711 Encoder (not a TI codec) These codecs are provided under a "for demonstration-only" license agreement.
Setting Up the Build/Development Environment 4.4 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. For example, in a default installation of the MontaVista LSP, you should add a definition like the following to your shell resource file (for example, ~/.
Building a New Linux Kernel 4.5 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. Make sure you have completed Section 4.4, Setting Up the Build/Development Environment and Section 4.4.
Rebuilding the DVEVM Software for the Target 7) If the kernel is configured with any loadable modules (that is, selecting 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_leINSTALL_MOD_PATH=/home//workdir/filesys modules_install 8) Use the following command to copy uImage to a place where U-Boot can use TFTP to download it to the EVM.
Building with DSPLink ■ Make sure LINUXKERNEL_INSTALL_DIR is defined as follows: LINUXKERNEL_INSTALL_DIR=/home//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//dvsdk_#_# directory, but you may have installed it elsewhere.
Booting the New Linux Kernel 4.8 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). 1) Power on the EVM board, and abort the automatic boot sequence by pressing a key in the console window (Section 2.2).
Using the Digital Video Test Bench (DVTB) 4.9 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. Using DVTB, you can configure codecs and/or peripherals before starting a data flow.
4-18
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 . . . . . . . . . . . . A–3 A.3 Setting Up a TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–5 A.4 Alternate Boot Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Video Input/Output Methods A.1 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.
Putting Demo Applications in the Third-Party Menu A.2 Putting Demo Applications in the Third-Party Menu You can add your own demos to the Third-Party Menu by following the steps in this section. Only four demos can be shown at once in the userinterface. If you add more than four demos, the first four in alphabetical order are shown. 1) Create the following files for your demo: ■ logo.jpg. This is the logo of the third party company which will be showed next to the demo description.
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. The result should say "gzip compressed data". file .tar.gz 3) Put your archive in the "thirdpartydemos" subdirectory of the target installation directory.
Setting Up a TFTP Server A.3 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. Search for "tftp-server". 2) To install TFTP, use this command, where -#.
Alternate Boot Methods A.4 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) ❏ Flash boot with NFS file system (Section A.4.3) ❏ TFTP boot with NFS file system (Section A.4.4) The subsections that follow show the environment variable settings used to enable each boot method.
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, 2025K davinci_enc_mgr.ch0_output=COMPOSITE davinci_enc_mgr.
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.
Updating/Restoring the Bootloaders A.5 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. UBL in turn loads the U-Boot bootloader program from NAND flash memory.
Updating/Restoring the Bootloaders ■ To assign a dynamic address, use the following: EVM # dhcp EVM # setenv ipaddr 2) Set the TFTP server IP address: EVM # setenv serverip 3) Save these settings to the flash memory: EVM # saveenv 4) Load U-Boot. To load U-Boot, the U-Boot image must be copied to the TFTP directory (usually /tftpboot), and the tftp command must specify both the image name and the destination address.
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. The NAND Programmer binary (NANDWriter.out) is in /home//dvsdk_#_##/PSP_#_#_#_#/bin/dm357.
Restoring the NAND Flash A.6 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. However, you must first update the kernel on the NAND flash as described in Section A.6.1. The DVSDK NAND image is included on the DVSDK (disk #2) restore directory (or the http://www.ti.
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. The YAFFS2 image should reside on the NFS Server root directory. Follow these steps: 1) Copy the dm357_flash_image_#_#_#_#.tar file from the DVSDK disk to the NFS mounted root directory. For example, /home//workdir/filesys.
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. The YAFFS2 image resides on the 2 GB SD card. An MMC/SD card reader should be used to copy the YAFFS2 image on the 2 GB SD card.
Restoring the NAND Flash 7) Execute the following commands to mount the MMC/SD and NAND partitions and populate the YAFFS2 image: EVM EVM EVM EVM EVM EVM EVM EVM EVM EVM # # # # # # # # # # mkdir /mnt/mmc mkdir /mnt/nand mount -t vfat /dev/mmcblk0 /mnt/mmc/ flash_eraseall /dev/mtd0 mount -t yaffs2 /dev/mtdblock0 /mnt/nand/ cd /mnt/nand tar xf /mnt/mmc/dm357_flash_image_#_#_#_#.tar cd umount /mnt/nand reboot The first mount command assumes you have a VFAT partition.
A-16
This is a draft version printed from file: davinci_gsgIX.
Index Encode demo 3-7 on disks 4-2 flash memory boot configuration A-6, A-7 G G.711 speech 3-8, 3-9 GNU make, version 4-15 H.
Index components 1-2, 4-4 installing 4-6 speaker 2-3 Spectrum Digital website 1-3 standalone demos 3-2 static precautions 2-2 Stereo Line In (P3) 2-3 Stereo Line Out (P5) 2-3 Stop button 3-6 SuSe Workstation 4-6 T target $ prompt 4-3 terminal session 2-6 test program 4-12 TFTP boot configuration A-7, A-8 server A-5 transfer files to board 4-16 Third-Party Menu A-3 transparency of OSD 3-6 U UART port (P6) 2-5 UBL A-9 U-Boot A-9 U-Boot utility 4-13 uImage boot file 4-16 V video-in (J12) 2-4 video-out (J8)
Spectrum Digital, Inc.
