The Motorola VIP Firmware is listening for only one object on the
metadata channel. The name of this object depends on the type of IP-STB.
The type of this object must always be bootcastinfo
.
This object is downloaded and the object(s) (splash screen (optional) and boot image (mandatory)) pointed out in this object are then downloaded.
After the boot image has been downloaded, the firmware passes control to the kernel in the boot image and stops executing. The firmware has no effect on the performance or behavior of the box after the third dot has been passed during the boot process.
Object | Comment | Values | Sources |
---|---|---|---|
motorola-vip<model number> |
The The model number consists of the type of box and if it has got a tuner the type of tuner will be reflected last in the string. Example 1: A VIP1920-9 with DVB-T tuner will be called motorola-vip1920-9t. Example 2: A VIP1910 will be called motorola-vip1910. The Bootcast ID for VIP19xx can also be found in the firmware menu when starting the STB. |
Infocast Type: BootcastInfo
Object Type:
Value set:
Example: |
|
kreatel-ip-stb-rev-<revision number> |
The revision number corresponds to the DBL compatibility of
the IP-STB. This can be found in the architecture and
compatibility section. The |
Infocast Type: BootcastInfo
Object Type:
Value set:
Example: |
|
<software name (generic)> | The object containing the boot image. The name of the object is the one specified in the bootcast info object. |
Infocast Type: BootcastFile
Object Type:
Value set:
Example: |
|
<splash name (generic)> | The object containing the splash image. The name of the object is the one specified in the bootcast info object. |
Infocast Type: BootcastFile
Object Type:
Value set:
Example: |
|