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
12
z3_mcfw_api
This directory contains a modified version of the TI MCFW API (found in dvr-
rdk/dvr_rdk/mcfw/src_linux/mcfw_api) that is tailored to work with Z3’s hardware and use-cases. The
link setup code for Z3’s demos can be found in the usecases directory. The use-case code is called from
ti_vsys.c in the same directory.
z3
This directory contains the base code for RTP tx and rx, as well as the base code for audio capture and
output.
4.2 Z3 Application Overview
4.2.1 Application Names and Locations
For encode, there are 2 binaries in the sample code. The first is a menu-based demo (this is what comes
up in the serial terminal when the board is powered on). The second is a command line interface that is
more flexible and easier to use from a programming standpoint. The web-based interface uses the
command line interface extensively.
The menu-based demo binary can be found at:
/opt/dvr_rdk/ti816x/bin/z3_dvr_rdk_demo_mcfw_api.out
The command line interface binary can be found at:
/opt/dvr_rdk/ti816x/bin/mcfw_mcsenc
On the decode side, there is a command line interface. The binary for this can be found at:
/opt/dvr_rdk/ti816x/bin/mcfw_mcsdec
4.2.2 Application Options and Arguments
The menu-based demo uses an .ini file. This .ini file is built in the script run.sh and stored in
/tmp/encode.ini.
Once called with the .ini file, the menu-based demo presents to the user a menu of demos. Most .ini files
are geared towards a specific demo. The easiest way to get a valid .ini file is to run the script with the
settings you want and then copy the generated .ini out of /tmp and save it.
The command line interface for the encoder is set up by running:
