An IIPs file name has this structure:
<name>_<version>_<processor>_<dbl compatibility>_<boot-image
compatibility>.iip
Examples of IIP file names:
kreatv-tool-logging_4.2_vip1900.iip
kreatv-app-webkit-portal_4.2.iip
As seen, different parts of the file name are separated by an underscore character ("_"). The underscore character is thus not allowed in any of the elements building up an IIP's file name.
Element | Comment | Example |
---|---|---|
Name | The name of the IIP.
Note! The name of the IIP is not the same as the file name. |
kreatv-tool-telnet
kreatv-app-webkit-portal |
Version | This version element is generated when building the boot-image
and should have the same value as the boot-image. Note! The version of the IIP does not reflect the version of the content of the IIP. |
2.4.1 |
Processor | This reflects what processor the IIP is intended for. If omitted, the IIP is intended for all platforms. | vip1900_25 |
DBL compatibility | The IIP can only be used with KreaTV IP-STBs with this DBL (dynamic boot loader). If omitted, the IIP can be run with all DBLs. | 2 |
Boot-image compatibility | The IIP is only compatible with KreaTV IP-STBs with this boot-image. If omitted, the IIP can be run with all boot-images. | 2 |
The valid processor-, DBL- and boot-image compatibility values can be found in the architecture and compatibility section.