CONFIDENTIAL
Z3-DM8169-VI-RPS
___________________________________________________________________________________________
V1.03.00
Z3 Technology, LLC ♦ 100 N 8
th
ST, STE 250 ♦ Lincoln, NE 68508-1369 U.S.A. ♦ +1.402.323.0702
25
system using NFS and present a "#" prompt. If not, then troubleshoot the connections, IP addresses
and server settings. Look in the .../images directory and make sure that the code is there. The root
file system for the target will be at .../filesys/fs
9.1 U-boot Startup Scripts
The following u-boot startup scripts are available. Each set up the u-boot variables for a specific behavior. To
make the settings permanent, run 'saveenv'.
setenv bootcmd run boot-nfs
Obtains root file system from NFS, kernel from TFTP
setenv bootcmd run nand_boot_nfs
Obtains root file system from NFS, kernel from NAND
setenv bootcmd run nand_boot_jffs2
Obtains root file system from NAND (JFFS2 format), kernel from NAND
setenv bootcmd run nand_boot_ramdisk Obtains root file system from ramdisk, kernel from NAND
setenv bootcmd run nand_boot_ubifs
Obtains root file system from NAND (UBIFS format), kernel from NAND
9.2 U-boot Update Scripts
The following u-boot update scripts are available. These scripts just update the images - you must also set the
bootcmd above to use the proper image.
run update-uboot Update U-Boot bootloader in NAND
run update-kernel Update Linux kernel image
run update-env Update U-Boot environment settings
run update-ramdisk Update root filesystem ramdisk
run update-jffs2 Update jffs2 image (requires mtd-utils on host)
run update-ubifs Update jffs2 image (requires ubi utils on host)
10.
Building the Code
Instructions to setup and build the full code base for the Z3-DM8169-MOD.
You will need sudo privileges in order to build the code. Make sure that the user account you are working from
is in the /etc/sudoers file and that you have the password.
The various variables of the system are all set up by default as if you are using the user account "z3". If you
create a "z3" account and use it to build the code then you will be able to execute the results of your build
without changing paths in the target system or elsewhere. It is not necessary to do so, but starting at the right
place can shorten the startup time.
First create a work directory (if you have not already done so) and cd to it.
