A boot image is a binary file containing the software which is downloaded to the IP-STB. A boot image is built from a number of parts:
All different kind of parts are each stored in an IP-STB Installation Package (IIP). When building a boot image all the parts are put together as one binary.
The HAL abstracts differences between different types of hardware so layers on top of HAL don't have to handle it themselves. The operating system (Linux) is also included in the HAL.
Typical IIP name: kreatv-hal-...
The platform consists of the platform services.
Typical IIP name: kreatv-platform-...
An application registration package contains the files needed for the application to be handled correctly by the platform. The application property file is included in the application registration package.
Application registration packages have an execution dependency to the application installation package. This means that the application installation package will be installed into the boot image automatically. This dependency can however be ignored, making in possible to dynamically download and install the application installation package after boot. This is a part of the KreaTV Dynamic Download, which the KreaTV IP-STB system provides. See an example of such a boot image configuration here.
It is possible to share an installation package between several registration packages. An example of this is the browser application, which can be registered both as web browser and as portal browser.
Typical IIP name: kreatv-app-...
An application installation package contains the application binary and libraries.
Typical IIP name: kreatv-inst-...
Examples of options are:
Typical IIP name: kreatv-option-...
Examples of tools are:
Typical IIP name: kreatv-tool-...
The build_boot_image command is used to build boot images.
For information on how to distribute a boot image to a KreaTV IP-STB, see the Booting section of the manual.