Setting up the boot image

The last step in this tutorial is to provide a boot image to the STB. Here we use the SDK to build a boot image. A more detailed tutorial on building boot images is provided here.

$ cd <sdk_root>/build_scripts
$ ./build_vip43x2.sh --version testVersion1 example.config

This should build a boot image, giving it the version "testVersion1". Copy the resulting .bin file to the root of the HTTP server:

$ sudo cp bi/kreatv-bi-example.config_kreatv-version_bcm15_vip43x2.bin /var/www/html/

Also copy a signed splash screen from the SDK to the root of the HTTP server:

$ sudo cp <sdk_root>/examples/splash/ARRIS_splash.bmp.sec /var/www/html

You should now be able to download the boot image using your web browser just by going to http://webserver.ip.address/kreatv-bi-example.config_kreatv-version_bcm15_vip43x2.bin

Editing the manifest file

The final step for setting up the boot image is to edit the manifest file, and update the URL and version. Change the version to "testVersion1" and the URL to http://server.ip.address/kreatv-bi-example.config_kreatv-version_bcm15_vip43x2.bin. You also need to update the URL to the splash screen to http://server.ip.address/ARRIS_splash.bmp.sec. The version can be set arbitrarily.

Booting

This time, as the STB boots, you should be able to observe from the ARRIS Boot Loader log and the HTTP server log that the STB first requests the XML manifest file, then requests kreatv-bi-example.config_kreatv_version_bcm15_vip43x2.bin. Another request will be sent for the splash screen, which will fail, as we have not configured one. Let's do that in the next section.

>> Continue to set up the splash screen.