Boot process

The ARRIS Boot Loader supports booting using several different protocols, including HTTP and Infocast. Although the exact implementation details differ slightly depending on which protocol is used, the processes are still quite similar.

The process begins with the set-top box fetching an XML manifest file from the boot server. This manifest contains information on what boot image is available for that set-top box, and the software version of that boot image. This allows the STB to make a decision; if the software version is already available in the STB flash memory, it can skip downloading the boot image and just run the version it already has.

If the versions are different, the boot loader downloads the offered boot image, and also a splash screen (loading graphic shown while the bigger boot image download and install takes place).

Since the STB requests metadata based on the STB model, it is fully possible for the boot server to support many different STB models at the same time. Furthermore, in the case of the HTTP protocol, the STB also provides its serial number and MAC address, allowing the server to provide specific boot images to an individual STB or groups of STBs. This is useful if you want to cater to a group of test-pilot users who run an experimental version of your next software release, for example.