Motorola Mobility Confidential Restricted.

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)
  • The Cactus boot image (demonstration TV viewer)
  • Example portals and some sample pages written in SVG/HTML and Javascript
  • Some utilities, like the logclient tool
  • The boot image building kit (allows you to build a custom boot image from components)
  • Documentation
The SDK++ is an extension of the SDK. The following is added:
  • Resources for C++ development (header files, libs, examples etc).

Requirements

The SDK officially requires installation on a linux PC running a recent version of Fedora Core, 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 or SDK++ into any directory. These install instructions refer to this directory as <dk>. In this example /opt/sdk++ is used. It is strongly recommended to install and use the SDK as a normal user, and not as root.

Unpack the SDK (tar zxvf kreatv-kit-sdk++-<arch>_<version>.tgz). A directory structure similar to the following is created.

/opt/sdk++
      | - build_scripts/
      | - dist/
      | - doc/
      | - examples/
      | - products/
      | - test/
      | - tools/

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

Note! If you are using the SDK++ you will need to install the toolchain before you can proceed with building boot images or applications. The correct version of the toolchain for this SDK can be found in dist/<toolchain>/toolchain_dir where <toolchain> is the toolchain, e.g. st40, bcm74xx or bcm45.

Installation of RPMs

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

Install the RPMs listed below. Replace the <version> for each file to match the file supplied with your SDK.

  • <dk>/examples/eval-boot-images/kreatv-evaluation-bootimages-emea-<version>.rpm
  • <dk>/tools/linux/kreatv-infocastconfig-emea-<version>.rpm
  • <dk>/tools/linux/kreatv-infocastserver-<version>.rpm
  • <dk>/tools/linux/kreatv-logtools-<version>.rpm
    Requires package wxPython version 2.8.8 or higher to be installed
  • <dk>/tools/linux/kreatv-utils-<version>.rpm

Type as root:

rpm -Uvh <rpm>

Replace <rpm> with the rpm-file for each rpm or use a pattern like tools/linux/*.rpm.

The file unpack-rpm.sh can be used to extract the contents of an rpm package. It is found in each folder 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 (previously Starter-kit) you may first need to remove the old installation.

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

kreatv-evaluation-bootimages-emea-3.7.3.5-01
kreatv-infocastserver-3.0-01
kreatv-infocastconfig-emea-1.0-01
kreatv-logtools-1.2-01
kreatv-utils-2.2-01

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

rpm -e kreatv-utils-2.2-01

Note that some packages are dependent on others and then you have to remove them at the same time. To completely remove the Infocastserver, the config files and the bootimages as root type:

rpm -e kreatv-infocastserver-3.0-01 kreatv-evaluation-bootimages-emea-3.7.3.5-01 kreatv-infocastconfig-emea-1.0-01

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 number (preferrably static IP)
  • The server needs a default gateway configured, even if there is no other network connected.
  • You need to setup static IP 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).
  • If you plan to use the Infocast Server PC as portal (web) server, check that a HTTP server is installed.

Basic configuration

This is the configuration changes you need to do (from the default installation configuration) to get an IP-STB up and running:

  1. Install the KreaTV demo portal, or your own portal pages, on a web server (this can be the same PC as the Infocast Server).

    Note! The IP-STB can still run without a web based portal available, by using only the demo applications included in the Evaluation Kit boot image.

  2. Make sure the HTTP service is running and the pages can be reached, e.g. by using a standard web browser.
  3. Edit the file whitelisturls.xml to match the URL and path where the portal is. The IP-STB will display the first entry in this file upon startup. Check the link for further details.
  4. If the IP-STB need to use a HTTP proxy to reach the portal (or Internet), edit the file proxylist.xml to reflect this. Check the link for further details.
  5. Edit the file homepageurl.txt to match your desired www home page. The web application will start on this page when pressing the WWW button. If Internet connectivity is not available, it's recommended to set this blank (i.e. have an empty file).
  6. Edit the file channeltable.txt to match your multicast TV channels. This is used by the TV application included in the boot image. Check the link for further details.

IP-STB start up

When all the above steps are finished, do the following to start the IP-STB:

  1. Restart the Infocast service (service infocastserverd restart) to make it read the configuration changes you have made.
  2. Make sure it's running OK (service infocastserverd status)
  3. Connect the IP-STB, configure the correct IP (if using static IP) and TV output on the IP-STB.
  4. Watch the "dots" on screen, they will describe the different steps during the boot process. These are very useful for troubleshooting.
  5. Start using the IP-STB by pressing MENU key to see the different applications included in the evaluation kit boot image.