CONFIDENTIAL
DOC-USR-0014-03
___________________________________________________________________________________________
Z3 Technology, LLC
♦
100 N 8
th
ST, STE 250
♦
Lincoln, NE 68508-1369 U.S.A.
♦
+1.402.323.0702
15
The target board must be able to access the files placed in the “images” directory of the project. Since
the default u-boot variables point to /home/z3/z3-netra, it is just easier to make a symbolic link from
there to the project you are currently working on. If un-tar'ring the release created an intermediate
directory with the release name (such as "z3-dm8168-version”), then create symbolic links as shown below
so that the target default settings can find the images:
cd /home/z3/z3-netra
ln -s z3-dm8168-version/images images
ln -s z3-dm8168-version/filesys filesys
Make sure that the u-boot environment variables set on the target board match the locations of the
executables on your work directory and run the target board. By default, using the factory settings, the
target expects that the kernel image is available at z3/z3-netra/images/ (assuming that the root path set
at the TFTP server is /home) and that a root file system is available for mounting with NFS at
/home/z3/z3-netra/filesys/fs/.
It is important that you have the shell environment variables of the Linux PC you are working on set
correctly as set by the included batch file "z3-env". Every time you start a new shell you should set the
environment by running “source z3-env”. Among other things, this will set the environment variables
$PRJROOT and $ROOTFS to the appropriate paths.
