CONFIDENTIAL
Z3-DM816X-VI-RPS RDK V2.00.04a
___________________________________________________________________________________________
Z3 Technology, LLC
♦
100 N 8
th
ST, STE 250
♦
Lincoln, NE 68508-1369 USA
♦
+1.402.323.0702
11
4.
Code Overview
4.1 Directory Structure
Once you have untarred the code, you will see the following top-level directories:
build-tools
Config files and scripts for building the codebase
dvr-rdk
A modified version of the TI RDK code
factory
Factory testing scripts (the user can disregard these)
filesys
The base filesystem for release
kernels
Kernel code for release
sysapps
Various supporting applications
toolchain
The ARM toolchain for building the codebase
u-boot
u-boot code for release
z3apps
Z3 demo application code and scripts
The Z3 demo code that comes with the Z3-DM816X-VI-RPS is run from the run.sh script in dvr-
rdk/dvr_rdk/bin/ti816x. This code calls the z3_dvr_rdk_demo_mcfw_api.out binary, which initializes and
runs the encoder. This binary is built from the dvr-rdk directory. The code for the binary resides in
z3apps/rdk/rdk_demo. The z3apps/rdk directory is described in more detail in the next section.
4.1.1 The z3apps/rdk directory
There are 3 main subdirectories: rdk_demo, z3_mcfw_api, and z3 (
Note: Source code is available for
customers that have licensed RPS-SRC. For licensees of RPS, binaries of the applications are available
).
rdk_demo
This directory contains the code for the various modes that Z3’s boards are able to run in. The encoder
setup is done in demo_vcap_vdis.c. The decoder setup is done in demo_vdec_vdis.c. The passthrough
setup is done in demo_vcap_vdis.c.
The file demo_rtptx.c is responsible for setting the output mode of the encoder. Output to file, RTP, and
MPEG2-TS are handled here.
The file demo_mcsenc.c contains the implementation of the command line interface. This can be run
using the following command:
#
source /opt/mcsenc/mcsenc.sh
