Z3 Technology Z3-DM368-ZDVR User manual

User’s Guide
Player and Recorder Application
High Definition Video Processor Module
DM368-ZDVR Rapid Prototyping System
Model Name: Z3-DM368-ZDVR
DOC-USR-0044-01
Manual Version 1.03.01
Software Version 1.03.01
December 13, 2013
Before attempting to connect or operate this product, please read these
instructions carefully and save the manual for future use.
This document contains proprietary and confidential information of Z3 Technology, LLC ("Z3"). This document may
not be used, reproduced, disclosed, or disseminated to anyone without the prior written approval of an authorized
representative of Z3.

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
2
Revision History
Version
Date
Change Note
Author
0.00.01
01/17/2010
Initial draft
BM
0.00.02
01/17/2010
Minor changes, JW feedback
BM
0.01.00
03/03/2011
Merge player and recorder along with helper commands. Simplify API.
Change product name to Z3-DVR to reflect rec/pb capability.
0.02.00
05/30/2011
Adjust per implementation
BM
0.03.00
06/03/2011
Continue to adjust as implemented
BM
0.04.00
10/31/2011
Edited document layout
CH
0.05.00
01/31/2013
Address update. Minor update.
PS
0.06.00
02/08/2013
Updated Section 7.2
PS
0.07.00
02/08/2013
Formatting, grammar review
MC
1.03.01
12/13/2013
Changed version number to reflect software version number, made some
formatting changes, added sections on untarring and building the code, added
more step-by-step instructions on doing a record and playback, added OSD
overlay details, added details on setting up TFTP/NFS, added example of boot
log, added to Troubleshooting.
RC

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
3
TABLE OF CONTENTS
1. General Description ......................................................................................... 5
2. Features ....................................................................................................... 7
2.1 Supported Input Resolutions ......................................................................... 7
2.2 Supported Output Resolutions ....................................................................... 7
3. Untarring and Building the Sample Code................................................................. 8
3.1 Preparing the Linux Environment ................................................................... 8
3.2 Making the Directories and Running the Make Script............................................. 8
4. Code Overview ..............................................................................................10
4.1 Software Overview....................................................................................10
4.2 Software Architecture................................................................................11
4.3 Software Interface....................................................................................11
5. Encoding and Playing Back a File.........................................................................12
5.1 Set up the Audio/Video Source .....................................................................12
5.2 Connect the Board....................................................................................12
5.3 Set up the Terminal Window........................................................................13
5.4 Power on the board...................................................................................13
5.5 Encode a stream ......................................................................................14
5.6 Play back a stream ...................................................................................14
5.7 Play stream on Windows Media Player ............................................................14
5.8 Option 1: Invoking the OSD overlay ...............................................................15
6. Running The Code You Built on the Board ..............................................................16
6.1 Method 1: Updating the Image File using an SD card...........................................16
6.2 Method 2: Running Your Code through TFTP/NFS...............................................18
6.3 Other available u-boot commands .................................................................22
7. ZDVR Command Summary .................................................................................23
7.1 Command Structure ..................................................................................23
7.2 prompt <string> .......................................................................................24
7.3 storage <block_device> | RELEASE.................................................................24
7.4 media ...................................................................................................25
7.5 space....................................................................................................25
7.6 record [file=<filename>] [time=<time_limit>] [vrate=<bit_rate>] ...........................26
7.7 play [file=]<filename>...............................................................................28
7.8 (File management commands)......................................................................29
Appendix A: Example of Successful Boot Log and Sample Run...........................................30
Appendix B: Troubleshooting..................................................................................33

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
4
LIST OF FIGURES
Figure 1 Z3-DM368-MOD......................................................................................... 5
Figure 2 Z3-DM368-ZDVR App Board .......................................................................... 6
Figure 3 Sample Content of Images Directory after Successful Build..................................... 9
Figure 4 ZDVR Software Architecture........................................................................11
Figure 5 Demo Connections for Z3-DM368-RPS .............................................................12
Figure 6 ZDVR Startup Message .............................................................................13
Figure 7 Graphics shown on screen as an overlay..........................................................15
Figure 8 Graphics with encoded video overlayed ..........................................................15
Figure 9 The ZWriter Main Menu.............................................................................16
Figure 10 Selecting the .img file .............................................................................17
Figure 11 Editing uboot_envDM368.txt .....................................................................20
Figure 12 Minicom Terminal Settings ........................................................................21
Figure 13 Minicom Paste File Selection......................................................................21
Figure 14 Example of Successful u-boot Configuration ...................................................22

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
5
1. General Description
Measuring only 44x68mm, the Z3-DM368-MOD is the most compact production-ready DM368 based video
encoder / decoder system-on-module on the market. The module has on-board high definition analog
component output, standard definition NTSC/PAL composite video input and output, as well as stereo
audio input and output. It also includes a micro-SD card socket, USB 2.0, Ethernet, a real-time clock, and
an IR sensor.
The Z3-DM368-MOD features a unique edge connector design which supplies all interfaces native to the
DM368 to an application board mate, including I2C, SPI, LCD, USB, Serial, SD/MMC/MS, digital video, digital
audio, analog composite and component video. Figure 1 below shows the Z3-DM368-MOD:
An application board, the Z3-DM365-APP, is included with the Z3-DM368-RPS.This application board uses
the I/O expansion capability of the Z3-DM368-MOD to implement additional functions not present in the
base module. The Z3-DM365-APP application board has 2 HDMI inputs, 2 YPbPr component inputs, 2 analog
stereo audio inputs, an SD card jack and 2 bi-color LEDs. Figure 2 on the next page shows the Z3-DM365-
APP application board.
A Linux-based SDK, additional design services, and support are available from Z3 Technology. Please
contact Z3 at http://www.z3technology.com or e-mail at [e-mail].
68 mm
44 mm
Figure 1Z3-DM368-MOD

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
6
Figure 2Z3-DM368-ZDVR App Board
Component In
Component Out
Composite In
Composite Out
Headphone Out
Serial
5V Power
MicroSD
GPIOs
HDMI Out
Ethernet
SD Card
USB

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
7
2. Features
!H.264 video encode and decode up to 1080p30
!On-board standard definition video ADC with 2 composite inputs or 1 S-Video input
!On-board standard definition composite and high definition component inputs
!On-board stereo audio ADC/DAC with 6 line level inputs and 4 outputs
!Low power consumption
!Built-in Ethernet MAC, on-board PHY
!USB 2.0 OTG support
!Edge Connector Expansion:
oDigital Video input interface for use with CMOS sensors or other devices
oDigital Video output interface for use with LCD or other devices
oComposite Video input/output
oComponent Analog Video output
oStereo Audio input (3 sets of stereo inputs)
oStereo Audio output, line level plus independent output for headphones
oFast Ethernet I/O
oTwo MMC/SD card ports (one with support for Memory Stick)
oTwo UARTs for serial interface
oGeneral Purpose I/O
oSPI and I2C ports
2.1 Supported Input Resolutions
Composite: 480i29.97, 576i25
Component: 720p50, 720p60, 1280x768, 1280x800, 1080i50, 1080i60, 1080p25, 1080p30
2.2 Supported Output Resolutions
Composite: 480i29.97, 576i25
Component: 720p50, 720p60, 1280x768, 1280x800, 1080i50, 1080i60, 1080p25, 1080p30

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
8
3. Untarring and Building the Sample Code
3.1 Preparing the Linux Environment
Prior to building the Z3 sample code, certain modules are required. In Ubuntu 10.x or later, the following
command can be used to get the required modules:
sudo apt-get install bison flex mtd-utils liblzo2-dev uuid-dev zlib1g-dev
libpcre3-dev autoconf autoconf-archive automake automake1.9 automake1.9-doc
libtool libtool-doc gstreamer-tools libglib2.0-dev mono-gmcs gperf
In Fedora, the command would be:
sudo yum install bison flex mtd-utils mtd-utils-ubi lzo-devel libuuid-devel
pcre-devel automake automake17 automake14 autoconf libtool gstreamer-tools
glib2-devel mono-core gperf
If you are running a 64-bit OS, it may be necessary to install some 32-bit libraries for the cross-compiling
toolchain. You can determine whether your OS is 64-bit by using the “uname –p” command. A 64-bit OS
will return “x86_64,” while a 32-bit OS will return “i386”, “i586”, or “i686”.
For 64-bit Ubuntu, you can get the necessary libraries by typing:
# sudo apt-get install ia32-libs
For 64-bit Fedora, you can type:
# sudo yum install glibc.i686
3.2 Making the Directories and Running the Make Script
The software provided will allow you to re-create the pre-installed software of the Z3-DM368-RPS starting
from the included source code.
On a PC running Linux, create a directory where the released materials are going to be located:
# mkdir /home/z3/z3-dm368
Copy the released tar archive to that directory (note: could also be RPS-SRC, name may slightly vary).
# cp SW-3D2-00123-01_DM368-ZDVR-20131211.tar.bz2 /home/z3/z3-dm368
Untar the archive (name of tar file may slightly vary):
# tar -xvjf SW-3D2-00123-01_DM368-ZDVR-20131211.tar.bz2
Note: Untarring could take 5 to 10 minutes.
Then go into the directory just created and run the build script (directory name may slightly vary):
# cd z3-dm368-ZDVR-20131211
# ./makeall

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
9
Note: Building can take around 30-40 minutes. You will also need to type in the sudo password a few
times towards the end of the build.
The outcome of the build process should be newly created image files in the images directory. You can
confirm this by doing the following:
# cd images
# ls -alt
The result should be something like the following. Note that actual filenames, dates, and times will differ.
Figure 3 Sample Content of Images Directory after Successful Build

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
10
4. Code Overview
Once you have untarred the code, you will see the following top-level directories:
build-tools Config files and scripts for building the codebase
dvsdk The DM368 DVSDK from TI with changes for Z3 Technology hardware
filesys The root file system for the DM368 target
flash_utils The UBL and a tool to write it into the board’s NAND flash
kernels The kernel source tree, with added support for the Z3-DM368-MOD
sysapps Source code for the system applications placed in the basic root file system
toolchain ARM compilers, binutils and other build tools
u-boot The u-boot source tree, with support for the Z3-DM368-MOD
z3apps Z3 demo applications, drivers, and utilities
4.1 Software Overview
The ZDVR consists of player and recorder applications. Both player and recorder accept simple, high level
commands in plain text from the serial port or console and provide relevant status information in return.
The command set allows for the quick configuration of elements such as capture resolution, encoding bit
rate, file names, etc., and should be sufficient for implementing most video playback and recording
applications. Both player and recorder are command-line driven applications designed so that they can be
executed via console commands or be set up to be automatically started when the system boots. The
simple nature of the command set makes it the ideal component to use in applications where the video
module is driven by another processor, typically the controller of the end application.
The player application provides a simple interface to playback previously recorded media files, allowing
the user to fast forward and reverse through the files at different speeds, move to the beginning of the
file, pause, resume and query playback information.
The recorder application effectively allows the use of advanced audio and video capture, compression and
storage without any knowledge of the many details of the media processing engine -- therefore enabling
quick time-to-market of media-enabled end systems.
Users of recorder are able to create files with compressed and synchronized audio and video into SD cards
or other external media with simple commands.

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
11
4.2 Software Architecture
The player and recorder applications provide an abstraction layer for the operation of a larger
multimedia system.
Figure __ shows the overall architecture used of the Z3 Technology recorder. The player application has
a similar architecture.
The recorder application sits on top of gstreamer, which provides the basic building blocks needed
to implement the recording functions offered. A variety of other services are provided by the
underlying components, such as audio and video capture, audio and video codecs, and file format
constructors and parsers.
4.3 Software Interface
The player and recorder command line applications each have a command-response type interface,
where the user sends commands and the application returns the status or other relevant information.
Commands are executed one at a time, with a command being accepted only when the previous
commanded has completed. Some commands will allow input of sub-commands or options during its
execution, others will not accept any input until they are completed.
Communication with the application’s command interpreter can be started using any standard stream, such
as serial ports and stdin/stdout. The exact communications channel to be used must be specified when
invoking player and recorder. By default, the stdin/stdout path will be used.
Figure 4ZDVR Software Architecture

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
12
5. Encoding and Playing Back a File
This section gives step-by-step instructions on taking the Z3-DM368-ZDVR and using it to write a 1 minute
.mp4 file encoding from composite in and playing back on composite out (or with Windows Media Player on
a PC). It also describes how to show OSD support and passthrough support.
5.1 Set up the Audio/Video Source
(1) Select a source with a composite output, such as a DVD or Blu-ray player.
-Power on the Source
-Connect composite out of the Source to a monitor
-Make sure the Source is set to NTSC output (the default for most DVD/Blu-ray players in North
America and Japan)
-Select content you would like to record
5.2 Connect the Board
For these steps, please refer to Figure 5.
(2) Connect the supplied 2.5mm serial cable and NULL modem adapter to your PC.
(3) Connect the video and 2 audio signals to your Audio/Video Source and connect the other end to “A/V
In” (J15) of the board.
(4) Connect “A/V Out” (J12) to the A/V input of a monitor.
The next step is to set up a terminal to view the activity of the board …
Figure 5Demo Connections for Z3-DM368-RPS
Composite A/V In
Serial
5V Power
Composite A/V Out

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
13
5.3 Set up the Terminal Window
(5) If you are running from a Windows PC, run TeraTerm. Select “Setup – Serial Port” and set the
following:
Port: Whichever serial port the port is connected to
Baud Rate: 115200
Data: 8-bit
Parity: None
Stop: 1-bit
Flow Control: None
(6) If you are running from Linux, type:
# sudo minicom –s
And then configure by doing the following:
-Select “Serial Port Setup”
-Ensure the right Serial Device is specified (typically “/dev/ttyUSB0”)
-Set option E (“Bps/Par/Bits”) to 115200 8N1
-Press <return>
-Select “Exit”
5.4 Power on the board
(7) Connect the 5V power supply and turn on the switch. If all is configured properly, you should see the
board booting up within the terminal window. After about a minute, you will see the app load up and
the words “Preloading gstreamer components” – once you see that, the ZDVR app is ready to go.
Figure 6ZDVR Startup Message

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
14
5.5 Encode a stream
(7) You are now in the ZDVR command environment (denoted by a prompt of “=”). In this environment, set
up composite encode:
= echo COMPOSITE > /sys/class/davinci_display/ch0/output
(8) Next, insert a standard-size SD card into the SD card slot on the board.
(9) Set up the input to be “NTSC” and the output media to be the SD card:
= standard ntsc
= storage mmc
(10) Now you can begin encode. To record 1 minute of .mp4, type:
= record vpassthru=true ntsc1.mp4
(11) ZDVR will respond with “+Recording”. You should start hearing the audio being encoded and, a few
seconds later, see video on the passthrough monitor.
5.6 Play back a stream
(12) When ZDVR is done, it will return “+End recording” and “+OK.” To play back the stream you just
recorded, type:
= play ntsc1.mp4
(13) Press the “H” and “L” keys to rewind and fast-forward through the stream.
(14) Playback stops on the last frame. Press the “E” key to exit playback mode. You can also press “E”
earlier to exit playback early.
5.7 Play stream on Windows Media Player
(15) First you should unmount the SD card. Type:
= storage release
= sync
(16) Put the SD card in a PC with Windows Media Player. Drag “ntsc1.mp4” to Windows Media Player.

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
15
5.8 Invoking the OSD overlay
(17) First of all, if you had taken the SD card out to run the stream on Windows Media Player, put the SD
card back in the board and remount it in ZDVR:
= storage mmc
(18) Type the following example app to invoke the OSD overlay example:
= cd /opt/dvsdk
= ./interface &
(19) You should see a sample picture on the screen:
(20) Now try an encode command with passthrough:
= record vpassthru=true ntsc1.mp4
(21) You should see the content being encoded overlapped with the original picture:
The source code for “interface” can be found at:
$PRJROOT/dvsdk/dvsdk_2_10_00_17/dvsdk_demos_2_10_00_17/dm365/interface
Figure 7Graphics shown on screen as an overlay
Figure 8Graphics with encoded video overlayed

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
16
6. Running The Code You Built on the Board
There are 2 ways to take the image files you built in Section 3 and run them on the board: (1) Updating
the image file using an SD card, and (2) Setting up NFS/TFTP to link to your development PC.
6.1 Method 1: Updating the Image File using an SD card
It is possible to update the firmware of the Z3-DM368-ZDVR using an SD card. The process requires a
Windows PC, an SD card, and the ZWriter tool (included with ZDVR). The process for updating via SD card
is as follows:
(1) Locate the img update file you want to update to (either received from Z3 or built in your
environment) and copy it to your Windows computer.
(2) Place an SD card into your Windows computer.
(3) Open the ZWriter Windows program provided by Z3. The main menu should appear.
-Note: It may be necessary to right-click on ZWriter and select “Open as Administrator” to
get ZWriter to run.
(4) Click on “Open File”. This will bring up the Windows File Browser. Use that to select the
.img file you want to upgrade to:
Figure 9The ZWriter Main Menu
Click here

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
17
(5) Click on “Open”. This takes you back to the Main Menu. There, click on the “Select SD
Card” window and choose the drive with the SD card you want to write to.
Important note: Do NOT make a mistake on this. This will cause wherever you specify to
be overwritten. There is no recovery once you hit “Write Device.”
(6) When ZWriter is finished, eject the SD card from your computer.
(7) Place the SD card in the socket on the Z3-DM368-ZDVR.
(8) Power on the system, viewing the terminal output via your PC.
(9) You should be able to see the system updating the flash.
(10) Once the update is complete, the system will automatically reboot.
(11) Power off the Z3-DM368-ZDVR.
(12) Remove the SD card
Note: This is important – otherwise another update will occur when you reboot.
(13) Turn the system back on.
The update should then be finished.
Figure 10 Selecting the .img file
Click here

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
18
6.2 Method 2: Running Your Code through TFTP/NFS
(1) Set up a TFTP server on your Linux PC and configure it to read from your “images” directory.
This will vary depending on the Linux setup you have. As an example, here is a set of steps that would
be run from Ubuntu 10.x or later (these are in gray to denote they can vary from system to system):
(a) Get tftp if it is not already installed:
# sudo apt-get install xinetd tftpd tftp
(b) Create the file /etc/xinetd.d/tftp . Set “server_args” to “/home”. An example of a tftp file would
be:
service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = nobody
server = /usr/sbin/in.tftpd
server_args = /home
}
(c) Make a tftpboot directory
# sudo mkdir /tftpboot
# sudo chmod –R 777 /tftpboot
# sudo chown –R nobody /tftpboot
(d) Start tftp
# sudo service xinetd start
(2) Enable NFS on the Linux PC. The target system will mount the root file system using NFS.
This, like TFTP, will also vary depending on the Linux setup you have. As an example, here is a set of
steps that would be run from Ubuntu 10.x or later (these are in gray to denote they can vary from
system to system):
(a) Get nfs if it is not already installed:
# sudo apt-get install nfs-kernel-server
(b) Create /export/users and set it up:
# mkdir –p /export/users

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
19
# mount –bind /export/users /home/users
(c) Add the following line to /etc/fstab:
/home/users /export/users none bind 0 0
(d) Add an entry for the file system directory in /etc/exports. For example, the line would be
something like (here, 192.168.0.6 is the IP address of the PC, and 255.255.0.0 is the netmask):
/home/z3/z3-dm368/filesys/fs 192.168.0.6/255.255.0.0(no_root_squash,insecure,nohide,rw,async)
(e) Create symbolic links in your top-level directory to allow access to your filesys and images directory
(note: actual directory name may be different depending on your specific release):
# cd /home/z3/z3-dm368
# ln –s z3-dm368-ZDVR-{date}/images images
# ln –s z3-dm368-ZDVR-{date}/filesys filesys
(f) Start the NFS server
# sudo service nfs-kernel-server restart
(3) Configure u-boot on your board to match your system configuration settings
(a) Reboot the board with minicom or TeraTerm setup on your PC (see Steps (5) and (6) in Section 6).
(b) As soon as u-boot starts, press the space bar immediately to make it stop in the u-boot prompt.
(c) The next step is to prepare the environment variable script to match your own environment
settings. Go to the u-boot directory in the release directory and edit the file
“uboot_envDM368.txt” (here emacs is used – any text editor can be used)
# cd /home/z3/z3-dm368
# cd z3-dm368-ZDVR-{date}
# cd u-boot
# emacs uboot_envDM368.txt
(d) In the editor, you want to modify the values for nfsserver, serverip, gatewayip, netmask, ipaddr,
tftp_root, and nfs_root – as shown in the figure below:

CONFIDENTIAL Z3-DM368-ZDVR V1.03.01
___________________________________________________________________________________________
Z3 Technology, LLC ♦100 N 8th ST, STE 250 ♦Lincoln, NE 68508-1369 USA ♦+1.402.323.0702
20
The value for tftp_root, when combined with the value of “server_args” in your /etc/xinetd.d/tftp
file (see step (1b)), should point to the images link you set up in step (2e).
The value of nfs_root should point to the fs subdirectory within the filesys link you set up in step
(2e).
(e) Save your changes and then copy this file to your home directory (this will make it easy to transfer
from minicom later).
# cp uboot_envDM368.txt /home/z3
Figure 11 Editing uboot_envDM368.txt
Modify to match the IP address of your Linux PC
Modify to match the netmask of your Linux PC
(should be same as Target netmask)
Modify to match the IP address of router
Modify to match your TFTP configuration (see below)
Modify to match the IP address you want the target
board to be
Modify to match your NFS configuration (see below)