CONFIDENTIAL
DOC-USR-0030-12
___________________________________________________________________________________________
Z3 Technology, LLC
♦
100 N 8
th
ST, STE 250
♦
Lincoln, NE 68508-1369 USA
♦
+1.402.323.0702
45
(3)
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-dm810x
# ln –s z3-centaurus-dm810x_sdi_rps-20141028/images images
# ln –s z3-centaurus-dm810x_sdi_rps-20141028/filesys filesys
(4)
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
7.0).
(b)
Wait for the first stage u-boot to finish and for the second stage u-boot to start.
(c)
As soon as the second stage u-boot starts, press the space bar immediately to make it stop in
the u-boot prompt.
(d)
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 “u-boot-env-
dm810x-rdk.txt” (here emacs is used – any text editor can be used).
# cd /home/z3/z3-dm810x
# cd z3-centaurus-dm810x_sdi_rps-20141028
# cd u-boot
# emacs u-boot-env-dm810x-rdk.txt
(e)
In the editor, you want to modify the values for nfsserver, serverip, gatewayip, netmask,
ipaddr, tftp_root, and nfs_root – as shown below:
Figure 38 Editing u-boot-env-dm810x-rdk.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 and nfs configuration
(see below)
Modify to match the IP address you want the
target board to be
