![Z3 Technology Sitara Z3-AM572x-RPS User Instructions Download Page 20](http://html.mh-extra.com/html/z3-technology/sitara-z3-am572x-rps/sitara-z3-am572x-rps_user-instructions_916592020.webp)
20
CONFIDENTIAL
DOC-USR-0089-03
____________________________________________________________________________________
Z3 Technology, LLC
♦
100 N. 8th St. STE 250
♦
Lincoln, NE 68508-1369 USA
♦
+1.402.323.0702
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 NFS if it is not already installed:
# sudo apt-get install nfs-kernel-server
(b)
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):
/home/z3/z3-am57xx 192.168.0.6/255.255.0.0(no_root_squash,insecure,nohide,rw,async)
(c)
Create symbolic links in your top-level directory to allow access to your filesys and images
directory. Actual directory name may be different depending on your specific release:
# cd /home/z3/z3-am57xx
# ln –s z3-AM572x-RPS-20160217/images images
# ln –s z3-AM572x-RPS-20160217/filesys filesys
(d)
Start the NFS server
# sudo service nfs-kernel-server restart
(7)
Make sure the Z3-AM572x-RPS is connected to your DHCP-capable network.
*Note:
If you want to use a static IP, follow the static IP example in Section 8.0.
(8)
Power on the Z3-AM572x-RPS.
9.4
U-Boot Start Up Sequence
Besides booting from NAND and TFTP/NFS, there are other boot configurations that are possible. Below
are the possible options provided in the Z3 u-boot environment:
bootcmd=if test ${dofastboot} -eq 1; then echo Boot fastboot requested, resetting dofastboot ...;setenv
dofastboot 0; saveenv;echo Booting into fastboo
t ...; fastboot;fi;run
findfdt
; run
mmcboot
;setenv mmcdev 1; setenv bootpart 1:2; setenv mmcroot
/dev/mmcblk0p2 rw; run mmcboot;
In normal operation the
bold
commands will be run.
The
findfdt
command attempts to identify the board, and select the proper Device Tree file (with a .dtb
extension) so that the Linux kernel knows what hardware to expect. The expected file is set in the
fdtfile
environment variable.