ARRIS Enterprises, Inc. Confidential Information

Installing the SDK

On this page the basic configuration required to get the KreaTV SDK up and running is described. The KreaTV SDK typically consists of:

One (or more) KreaTV IP-STB
The KreaTV Infocast Server software
A general-purpose STB boot image (the evaluation boot image)

Example portals and some sample pages written in HTML and Javascript

Some utilities, like the logclient tool.

The boot image building kit. It will allow you to build a custom boot image from components.

Documentation

Requirements

The SDK officially requires installation on a linux PC running a recent version of Fedora, although it may work on other distributions. Installation assumes that a number of tools are available on the development machine:

Bash is used for many scripts.
Perl is used in some scripts used when building boot images etc.

Installation procedure

It is possible to install the SDK into any directory. These install instructions refer to this directory as <sdk_root>. In these instructions, /opt/kreatv_5.0.1 is used.

It is strongly recommended to install and use the SDK as a normal user, and not as root.

Create the destination directory and unpack the SDK into it:

mkdir /opt/kreatv_5.0.1 tar zxvf kreatv-sdk-customername_5.0.1.tgz -C /opt/kreatv_5.0.1

A directory structure similar to the following is created.


/opt/kreatv_5.0.1
      | - build_scripts/
      | - dist/
      | - doc/
      | - examples/
      | - products/
      | - README
      | - tools/

You may find it useful to add the <sdk_root>/dist/bin/ directory to your path. It contains build scripts, install scripts and useful tools for working with IIP's (see IP-STB Installation package)

Installation of Infocast & RPMs

The Infocast server is distributed as RPM files. If you do not require Infocast (you will boot only with http) then you can skip the installation of the Java Runtime Environment and the Infocast RPMs. It is recommended that you install the remaining RPMs though, as they contain useful tools such as the logging client.

Download and install the Java Runtime Environment (JRE). You can find it here.

Install the desired RPMs. Replace <version> with the correct version number. For some RPMs, there is one version for 32-bit systems (i386) and one version for 64-bit systems (x86_64). Be sure to install the one for your system.

<sdk_root>/tools/linux/kreatv-infocastserver-3.<version>.rpm
<sdk_root>/tools/linux/kreatv-infocastconfig-emea-<version>.rpm
<sdk_root>/tools/linux/kreatv-example-bootimages_bcm15_vip43x2-5.0.1.rpm
<sdk_root>/tools/linux/kreatv-logtools-<version>.rpm
<sdk_root>/tools/linux/kreatv-utils-<version>.rpm
<sdk_root>/tools/linux/kreatv-wxlogclient-<version>.rpm (requires package wxPython version 2.8.8 or higher)

To install the RPMs you'll need root access. Notice, an internet connection is required for any dependencies that need to be downloaded and installed. Type as root and replace <rpm> with the rpm file for each RPM to install (alternatively, line them all up on the same line).

dnf install <rpm> (used on the latest Fedora distributions)
or
yum localinstall <rpm> (used on the older Fedora distributions)

If you just want to extract a file or files from the rpms, without actually installing the full rpm, the file unpack-rpm.sh can be used. It is found in each directory containing rpms.

Java Runtime Environment and Infocast directory

In the file /etc/infocast that is installed by the package kreatv-infocastserver*.rpm there are two variables that can be changed:

INFOCAST_JAVA - points to the java binary that should be used to start the Infocastserver.
INFOCAST_INSTALL - points to the directory where the Infocastserver is installed. Default location is /opt/infocast

If you for some reason want to change the location of the Infocastserver or use a different JRE you can change these variables. They are read by the script /etc/init.d/infocastserverd

Upgrade instructions for RPMs

To make an upgrade from an older version of the SDK you may first need to remove the old installation.

To find out what you have installed on your system type: dnf list installed | grep kreatv. You will see a listing that looks something like this:


kreatv-infocastconfig-emea.i386  1.0-01             @System                   
kreatv-infocastserver.i386       3.5-01             @System                   
kreatv-logtools.i386             1.39-1             @System                   
kreatv-utils.i386                2.2-01             @System                   
kreatv-wxlogclient.noarch        1.37-1             @System

As an example you can remove the package "kreatv-utils.i386". Type as root:

dnf remove kreatv-utils.i386

Post installation check list

Here is a list of things you need to check after the Infocast Server has been installed for the first time:

The server PC needs an IP address (preferably a static IP)
The server needs a default gateway configured, even if there is no other network connected.
You need to set up a static IP address on the IP-STB, or use an existing DHCP server in the network.
You need to make sure multicast traffic from the server to the IP-STB is let through by the network.
Check that the Infocast service is installed properly, e.g. by starting the service (service infocastserverd start) and checking that it is actually running (service infocastserverd status). You should also look at the startup log for any errors (/opt/infocast/infocast.log).
If you plan to use the Infocast Server PC as portal (web) server, check that an HTTP server is installed.

Basic Configuration

Once you have installed the Infocast server, you need to provide the STB with the metadata channel address. This is done either with DHCP options or by statically entering the values into the boot loader menu.

The Infocast server should, by default, have support for a wide range of ARRIS STBs. The STB will boot and show the example portal.