Wiki

The Z3 codebase assumes that certain modules are installed in the Linux system. To install all the modules needed by Z3, type the following command in Ubuntu/Debian:

    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

In Fedora you would type:

   sudo yum install bison flex mtd-utils mtd-utils-ubi lzo-devel libuuid-devel pcre-devel automake \
        automake17 automake14 autoconf libtool

Yes, but it is necessary to retrieve some 32-bit libraries that are used in the Z3 codebase. In Ubuntu, you can get these modules by typing:

sudo apt-get install ia32-libs

In Fedora, you would type:

sudo yum install glibc.i686

The Z3 codebase can be built on Ubuntu 10.x or later. Most versions of Fedora should also work.

This can be solved by installing the modules described in Question (1).

The error message looks something like this:

libtool: compile:  arm_v5t_le-gcc -DHAVE_CONFIG_H -DHAVE_VERSION_H -DLIBRARY_DIR=\"/opt/webgui/lighttpd/lib\" 
-DSBIN_DIR=\"/opt/webgui/lighttpd/sbin\" -I. -I.. -D_REENTRANT -D__EXTENSIONS__ -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGE_FILES -g -O2 -Wall -W -Wshadow -pedantic -std=gnu99 -MT mod_flv_streaming.lo -MD -MP 
-MF .deps/mod_flv_streaming.Tpo -c mod_flv_streaming.c  -fPIC -DPIC 
-o .libs/mod_flv_streaming.o In file included from base.h:24,
                 from mod_flv_streaming.c:1:
array.h:9:19: error: pcre.h: No such file or directory In file included from base.h:24,
                 from mod_flv_streaming.c:1:
array.h:130: error: expected specifier-qualifier-list before 'pcre'
In file included from base.h:26,
                 from mod_flv_streaming.c:1:
keyvalue.h:56: error: expected specifier-qualifier-list before 'pcre'
keyvalue.h:61: warning: struct has no members
make[5]: *** [mod_flv_streaming.lo] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all] Error 2
make[1]: *** [lighttpd] Error 2
make[1]: Leaving directory `/home/z3/z3-dm814x/z3-centaurus-dm814x_RPS-20130829/sysapps'
make: *** [sysapps] Error 2

The first potential cause of this is not having the automake tools installed. You should make sure the command described in Question (1) was run.

If it was, this could also be an indicator that a “make clean” is needed. Try typing “make clean” and then try typing “./makeall.sh”.

The error message looks something like this:

*

* System Logging Utilities

*

syslogd (SYSLOGD) [Y/n/?] y

  Rotate message files (FEATURE_ROTATE_LOGFILE) [Y/n/?] y

  Remote Log support (FEATURE_REMOTE_LOG) [Y/n/?] y

  Support -D (drop dups) option (FEATURE_SYSLOGD_DUP) [Y/n/?] y

  Circular Buffer support (FEATURE_IPC_SYSLOG) [Y/n/?] y

    Circular buffer size in Kbytes (minimum 4KB) (FEATURE_IPC_SYSLOG_BUFFER_SIZE) [128] 128

    logread (LOGREAD) [Y/n/?] y

      Double buffering (FEATURE_LOGREAD_REDUCED_LOCKING) [Y/n/?] y

klogd (KLOGD) [Y/n/?] y

logger (LOGGER) [Y/n/?] y

etc/config.c:8: error: 'UTS_RELEASE' undeclared here (not in a function)

This is due to bison not being installed. Running the command described in Question (1) will address this.

The error message looks something like this:

/home/z3/z3-dm814x/z3-centaurus-dm814x_RPS-20130829/ezsdk/component-sources/omx_05_02_00_38/bin/
maketemp_configuro_cmd_c6xdsp.bat: -e: not found

make[3]: *** [xdc_configuro] Error 127

make[2]: *** [dm81xxdspXdc] Error 2

make[1]: *** [omx] Error 2

make: *** [ezsdk] Error 2

The problem is that /bin/sh is not linked to bash. The fix on Ubuntu is to run:

  sudo dpkg-reconfigure dash

and then select “No” when it asks if “dash” should be the system shell (this will cause /bin/sh to be linked to “bash” instead).

Hold down the space bar and power on the unit. Keep holding the “s” key. This should cause a stop in u-boot.

Hold down the “s” key and power on the unit. Keep holding the “s” key. This will cause a stop at the Z3-MIN prompt.

You can reprogram the module using BOOTP. This process involves setting up a BOOTP server on your development PC, setting some jumpers on your module, connecting the module to your development PC via the Ethernet, and then turning on the board. Detailed procedures on doing this for DM8148 modules can be found here. Details on doing this for DM8168 modules can be here. For details on doing this on other platforms, please contact Z3.

This is currently not supported.

In the 810x: 4.04.00.01

In the 814x: 4.01.00.05

In the 816x: 4.00.00.09

This can happen if you are in the process of changing between the EZSDK and RDK but only part of the system got updated. Please be sure to use the Updater in the Web GUI when doing this update. More details can also be found in the manual “Updating from the EZSDK to the RDK.”

First of all, we recommend trying the instructions in the latest User's Guide, which should have detailed instructions on setting up the TFTP server. It should be in a section titled “Method 2: Running Your Code through TFTP/NFS” (if your User's Guide does not have this section please contact Z3 Technology).

If you try that sequence and TFTP is still not working, here are items, from our experience with previous customers, that you can check:

(a) Is the Ethernet connected well to both the Z3 Module and the TFTP server (check the link lights on both)?

(b) Check the netmask of the Z3 Module set in u-boot. Is it equal to the netmask of the TFTP server? (Default value = 255.255.0.0)

(c ) Check the IP address of the Z3 Module set in u-boot. Is it one that can communicate with the TFTP server based on the netmask?

-For example, if the netmask is 255.255.0.0 and the TFTP server IP address is 192.168.0.6, then the Z3 Module can be set to an IP address of 192.168.x.y, where x.y is any value except “0.6”.

(d) Check the value of serverip in the u-boot parameters. Does it equal the IP address of the TFTP server? (Default value = 192.168.0.6).

(e) Is there anything else on the network that might have the same IP address as the Z3 Module or the TFTP server that could be causing a conflict?

(f) Is there a firewall on the TFTP server PC that is turned on? (If so, you need to turn it off).

(g) Was an “images” directory link set up and does the file uimage exist in that directory?

(h) If you take serverargs in /etc/xinetd.d/tftp and combine that with tftp_root in the u-boot arguments, does it point to the images directory?

(i) Did you start the tftp server? (In Ubuntu, this is done with a “sudo /etc/init.d/xinetd start”)

(j) If you made changes to /etc/xinetd.d/tftp, did you start the tftp server after making those changes?

(k) Is the permission of your /tftpboot directory set to “777” and the owner set to “nobody”?