OperationsGuide0.14r.. - hinditron

Amino Set-Top Box 

Management (Multicast 

Upgrade System) 

Operations Guide 

Version 0.14.x Revision 2 

Access level: CONFIDENTIAL - NDA required 

Confidentiality: the information in this document is subject to non-disclosure agreements and must not be 

passed to other third parties without the express permission of Amino Communications Ltd. 

This document describes components that undergo continual development. The information in this document 

is subject to change without notice at any time.

About Amino 

Amino Communications (www.aminocom.com) supplies the AmiNET series of set-top boxes 

renowned for their low cost and reliability. The AmiNET range materially reduces service 

operators’ capital expenditure, whilst offering the full range of specification required; MPEG2 

and MPEG4 encoding standards, standard and high definition TV, personal video recording 

and home networking. The high performance coupled with the innovative design of Amino’s 

set-top boxes, have brought the series industry accolades and the company a leading position 

within the IPTV market. 

Approximately 700,000 AmiNET IPTV set-top boxes have been used in over 50 countries 

worldwide by more than 400 customers in commercial deployments and trials. The set-top 

boxes have also been sampled by another additional 700 customers. Amino Communications’ 

principal customers are telecommunications, broadcast and hospitality service operators. 

Generally, AmiNET products are supplied with the IntAct IPTV software stack pre-loaded. 

Amino Communications is a wholly owned subsidiary of Amino Technologies plc. listed on the 

London Stock Exchange AIM, symbol AMO. Amino is based near Cambridge, UK, and has 

offices in Atlanta Georgia and Hong Kong. 

Contact 

Information: For further information about Amino or Amino products, email: 

info@aminocom.com 

Document feedback: If you have comments on this document, please submit feedback via 

the Customer area of the Amino support site. 

CONFIDENTIAL. Copyright © Amino Communications Ltd 2007 2

Contents 

About Amino ............................................................................................................................2 

Contact ....................................................................................................................................2 

Copyright and trademarks .......................................................................................................6 

Conventions ............................................................................................................................ 6 

1 Introduction ................................................................................................................. 7 

1.1 About this document ........................................................................................... 7 

1.2 About the Multicast upgrade system................................................................... 8 

1.3 About set-top box operation.............................................................................. 10 

1.4 About set-top box configuration ........................................................................ 11 

1.5 About software builds ....................................................................................... 11 

1.6 About software images ..................................................................................... 13 

1.7 About software security .................................................................................... 13 

1.8 More about operational states .......................................................................... 15 

2 Setting up a basic Multicast upgrade system ........................................................ 20 

2.1 Overview of procedure for setting up a Multicast system ................................. 20 

2.2 Release directory contents ............................................................................... 20 

2.3 Copying files ..................................................................................................... 22 

2.4 Setting up the DHCP server ............................................................................. 23 

2.5 Setting up the Multicast server ......................................................................... 24 

2.6 To set up the Multicast server........................................................................... 24 

2.7 Creating software images ................................................................................. 25 

2.8 Starting the Multicast server ............................................................................. 28 

3 Setting up an advanced Multicast upgrade system .............................................. 29 

3.1 Configuring the Multicast system for multiple set-top box types....................... 29 

3.2 Using deployment indexes for automatic upgrade............................................ 35 

3.3 Setting set-top boxes with static network and multicast upgrade settings........ 37 

3.4 Automating Multicast server start-up ................................................................ 39 

4 Upgrading set-top box software.............................................................................. 41 

4.1 Upgrade options ............................................................................................... 41 

4.2 Using STBremoteconf to upgrade software...................................................... 42 

4.3 Using the Management pages to upgrade software ......................................... 42 

4.4 Configuring the DHCP server for multicast upgrades....................................... 42 

4.5 Using JMACX to upgrade software................................................................... 42 

5 Configuring set-top boxes ....................................................................................... 43 

5.1 Configuration options........................................................................................ 43 

5.2 Configuration areas .......................................................................................... 45 

5.3 Configuring a large deployment........................................................................ 46 

5.4 Pairing an IR remote control with a set-top box................................................ 47 

5.5 Configuring how the set-top box responds to remote control keys................... 48 

5.6 Configuring the set-top box time zone .............................................................. 48 

6 Customising a software upgrade image................................................................. 50 

6.1 Configuring image components ........................................................................ 50 

6.2 Editing the flashcontents file ............................................................................. 51 


6.3 Creating an upgrade script ............................................................................... 52 

6.4 Enabling remote log-in tools ............................................................................. 52 

6.5 Customising graphics ....................................................................................... 53 

6.6 Changing set-top box passwords ..................................................................... 54 

7 Using STBremoteconf .............................................................................................. 56 

7.1 STBremoteconf................................................................................................. 56 

7.2 Before you start ................................................................................................ 56 

7.3 Installing prerequisite Perl modules.................................................................. 56 

7.4 Sending commands with STBremoteconf......................................................... 57 

7.5 STBremoteconf command syntax..................................................................... 58 

7.6 STBremoteconf command options ................................................................... 60 

8 Using the HTML Configuration pages..................................................................... 69 

8.1 Configuration pages.......................................................................................... 69 

8.2 Getting started .................................................................................................. 69 

8.3 Using the Management pages.......................................................................... 70 

8.4 Using the Preferences pages ........................................................................... 73 

9 Using libconfig .......................................................................................................... 75 

9.1 Before you start ................................................................................................ 75 

9.2 libconfig command syntax ................................................................................ 75 

9.3 Sending commands with libconfig .................................................................... 76 

9.4 libconfig configuration areas ............................................................................. 76 

10 Set-top box configuration settings ......................................................................... 79 

10.1 settings file contents ......................................................................................... 79 

10.2 netconf file contents.......................................................................................... 85 

10.3 NOR flash - list of settings ................................................................................ 85 

10.4 Channels file contents ...................................................................................... 91 

10.5 Trusted domains file contents........................................................................... 91 

10.6 Usersettings file contents.................................................................................. 91 

10.7 Hostname file contents ..................................................................................... 92 

10.8 HTML Configuration pages - settings used ...................................................... 92 

11 Troubleshooting........................................................................................................ 98 

11.1 Set-top box LED flashing codes ....................................................................... 98 

11.2 STBremoteconf errors .................................................................................... 101 

11.3 Browser display issues ................................................................................... 101 

Appendix A:Configuration example: DHCP server and Multicast server for multiple 

types of set-top box 102 

A.1 DHCP server configuration file ....................................................................... 102 

A.2 Multicast server configuration file ................................................................... 107 

A.3 DHCP and Multicast server matching values ................................................. 108 

Appendix B:Changing from TFTP to Multicast upgrade ............................................... 110 

B.1 To change a TFTP booting set-top box to Multicast upgrade......................... 110 

Appendix C:Video output formats................................................................................... 111 

C.1 AmiNET103 .................................................................................................... 111 


C.2 AmiNET110, 110H.......................................................................................... 111 

C.3 AmiNET120 .................................................................................................... 112 

C.4 AmiNET124 .................................................................................................... 112 

C.5 AmiNET125 .................................................................................................... 112 

C.6 AmiNET130, 130H.......................................................................................... 113 

C.7 AmiNET500 .................................................................................................... 113 

Index ...................................................................................................................................115 

Document history ................................................................................................................121 


Conventions 

Copyright and trademarks 

CONFIDENTIAL. Copyright © Amino Communications Ltd 2007 

Amino, AmiNET and the Amino logo are trademarks of Amino Communications Ltd. 

All other trademarks are the property of their respective owners. 

Conventions 

The following table describes common formatting conventions used in this document. Where 

other conventions apply to a particular section, they are described in the section they are used 

in. 

Formatting Usage 

< ...> Indicates a value that you need to replace with a systemspecific 

value (except where used in HTML or XML 

examples, where it is used in tags, as normal). 

[ ...] Indicates optional parameters - for example in commands 

or functions. 

... | ... Indicates choices - for example where an input can take 

one of a number of values. 

code font Indicates input and output values (for example, at a 

command line), as well as function, configuration, 

parameter and file names. 

bold text Used for emphasis and for cross-references to other 

sections and other documents. 

grey text Commands or settings which are not in general use (for 

example, configuration settings that are reserved for 

Amino internal use). 

underlined blue 

text 

Cross-reference (this is a “clickable” hyperlink if you are 

vewing the document electronically). 


1 Introduction 

1.1 About this document 

AmiNET set-top box operation is controlled by software installed on the set-top box. This 

document describes how to set up the Multicast system for managing the software on the 

boxes, and how to customise the software for the needs of your system. It assumes you 

have a set-top box and software release. It also assumes a basic understanding of the 

technologies involved, including Linux command line. 

Many of the control and customisation options described in this document can also be 

implemented using the JMACX Javascript extensions. JMACX is not covered in this 

document - see the JMACX API Specification for details. 

Structure 

This document consists of the following chapters: 

Chapter 

Introduction 

Setting up a basic 

Multicast upgrade 

system 

Setting up an advanced 


system 

Upgrading set-top box 

software 

Configuring set-top 

boxes 

Customising a software 

upgrade image 

Using STBremoteconf 

Using the HTML 

Configuration pages 

Using libconfig 

Set-top box 

configuration settings 

Outline 

This chapter continues by introducing the 

Multicast system and giving an overview of how 

it works. 

Details how to use a software release to set up 

the Multicast system components and install 

software on a set-top box for the first time. 

Details how to set up more complex Multicast 

upgrade systems, such as configuring 

upgrades for multiple types of set-top box. 

Introduces the options available for upgrading 

the software on set-top boxes. 

Introduces the options available for configuring 

set-top boxes, and details how to configure 

certain configuration areas. 

Describes how to customise the software 

upgrade before it is signed and loaded to the 

set-top box. 

Introduces STBremoteconf and details how to 

use it to configure and control a set-top box. 

Introduces the Management pages and 

Preferences pages and details how to use them 

to configure and control a set-top box. 

Introduces libconfig and details how to construct 

commands to view and edit set-top box 

configuration. 

Lists some of the main set-top box configuration 

settings. 


Introduction 

Chapter 

Troubleshooting 

Appendices 

Outline 

Covers LED flashing codes that set-top boxes 

use to indicate errors during booting and 

upgrading software;also covers troubleshooting 

for other Multicast system components. 

Provide configuration examples and other 

supporting information. 

Quick start 

If you are already familiar with the technologies and concepts in an Amino Multicast 

system and just want to get the system running, you can proceed with Setting up a basic 

Multicast upgrade system on page 20. 

If you have already installed the Multicast system components, and want information on 

how to configure them or upgrade software, go to Configuring set-top boxes on page 43 

or Upgrading set-top box software on page 41. 

1.2 About the Multicast upgrade system 

System overview 

The Amino Multicast upgrade system provides management, control and customisation 

for set-top boxes. It works alongside other networked IPTV components such as media 

server and conditional access (CA) server. 

Remote management components 

DHCP server 

The 3rd party DHCP server handles providing an IP address and other network settings 

to the set-top boxes, and Amino vendor extensions enable booting and software upgrade 

functionality. 


Introduction 

Multicast server 

The Amino Multicast server transmits signed bootstrap and software upgrade images that 

set-top boxes can download. It works as a carousel, continually serving the images in its 

configuration. The server can transmit multiple images at once, so that a mix of set-top 

box types can be upgraded from a single Multicast server. 

STBremoteconf 

STBremoteconf provides a mechanism for remotely configuring and controlling a local 

network of AmiNET set-top boxes. It can be run on the command line by sending 

commands individually to one or more set-top boxes, or commands can be collected into 

a script to save time. Commands are signed when they are created, so that the set-top 

box can check that the command has been sent by an authorised source. 

Example functions include rebooting, modifying output modes or updating software, as 

well as viewing information about the set-top box. 

Telnet/SSH 

If required, the set-top box software can include Telnetand in some cases SSH or 

Dropbear, which enable administrators to connect directly to a set-top box and perform 

operations such as using libconfig to view and change configuration settings. This 

functionality enables administrators to trial new software configurations, and is normally 

disabled for live systems, for security reasons. 

Local management components 

How it works 

Configuration pages 

Set-top boxes with browsers include HTML configuration pages, displayed on the 

television screen, that enable local access and editing of configuration areas. The pages 

are divided into an administrator area (Management pages) and user area (Preferences 

pages). 

Preferences pages 

The set-top box Preferences pages are a simple interface that enables users to change 

basic set-top box configuration areas such as language, subtitle and keyboard set-up. 

The pages are accessed locally via an Amino IR remote control (or keyboard). The 

Preferences pages are designed for use by end-users. 

Management pages 

The set-top box Management pages are a simple interface that enables administrators to 

change set-top box configuration areas such as networking, channel list and browser setup, 

as well as initiate basic operations such as rebooting and updating software. In 

addition, read-only access is available to areas such as version and set-top box identity 

settings. The pages are password-protected and accessed locally via an Amino IR 

keyboard (limited functionality is also supported via the remote control). Management 

pages allow access to advanced configuration functions and are designed for use by 

administrators rather than end-users. 

Once the components of the system are installed and configured, a network of set-top 

boxes can be supported and managed. For details of everyday operation as part of the 

Multicast upgrade system, see About set-top box operation on page 10 and More about 

operational states on page 15. 


Introduction 

1.3 About set-top box operation 

Overview of operational states 

Set-top box operation is driven by a defined set of states: how a set-top box operates 

depends on its current state. The state a set-top box is in depends on the existence of a 

current software image in its NAND flash, or whether it can load that software 

successfully. Each time a set-top box enters a new state, it sends a DHCP request that 

includes an appropriate string to identify its current state, as defined by Amino vendor 

extensions added to the DHCP server’s configuration file. Note that operation when the 

NAND flash doesn’t contain valid software is enabled by the bootloader stored 

permanently in the NOR flash. 

Bootstrap (mboot) state 

When the set-top box is first powered, it inspects its NAND flash for valid software. If it 

doesn’t find any, it enters the Multicast bootstrap state. In this state, it can securely 

download a bootstrap image from the Multicast server. When a set-top box is in bootstrap 

state, it includes mboot state in the message it uses to communicate with a DHCP server. 

Upgrade (upgrd) state 

Once the set-top box has found and executed a valid bootstrap image, it enters the 

upgrade state. The set-top box will also enter this state in response to a manual upgrade 

request (e.g. initiated via STBremoteconf). In this state, all non-essential applications are 

closed, and the set-top box can download and execute a new software upgrade image. 

When a set-top box is in upgrade state, it includes upgrd state in the message it uses to 

communicate with a DHCP server. 

Filesystem (fisys) state 

Once the set-top box has found and executed a valid software image from the NAND 

flash, it enters the filesystem state. In this state, the set-top box is running and available 

for normal use. An administrator can initiate a software upgrade using one of the 

management tools (e.g. STBremoteconf). When a set-top box is in filesystem state, it 

includes fisys state in the message it uses to communicate with a DHCP server. 


Introduction 

Dataflow diagram: Operational states (overview) 

When a set-top box is powered, it attempts to execute software from its NAND flash. If 

this is successful, the set-top box enters its normal running state (filesystem state - see 

below); otherwise, the set-top box enters its bootstrap state. 

See also: 

About software images on page 13 

More about operational states on page 15 

1.4 About set-top box configuration 

The Multicast system offers a range of tools for configuring set-top boxes, depending on 

factors such as whether you are trialling new settings or rolling out configuration for a 

software upgrade and whether you are configuring the box remotely or locally. For an 

overview of configuration methods, see Configuring set-top boxes on page 43. For details 

of some of the configuration possibilities, see Set-top box configuration settings on page 

79. 

1.5 About software builds 

AmiNET set-top boxes can support a wide range of functionalities and platforms. The 

software enables as much user-customisation as possible, but in order to minimise the 

size of the software image loaded on a set-top box, it is built to support a particular set of 

functionalities. Once a build has been created, it is possible to customise it with customerspecific 

security keys, additional files and configuration settings, but it is not possible to 

enable some functionality that has not been compiled into the software build. For this 

reason, it can be useful to understand what is included in a software build, and what can 

be added later. 

Diagram: Software build and customisation stages 


Introduction 

Note that the Build stage shown in this diagram is internal to Amino. 

The following table shows the stage at which some of the key functionality can generally 

be added or changed: 

Stage 

Build 

Customise 

Configure 

Options 

browser and middleware support 

hardware platform 

subtitles 

bitband support 

some CA system support 

some language support 

RSA security keys 

enable/disable Telnet/SSH 

graphic shown during upgrade 

some CA system support 

some language support 

packet size and file format for 

multicast software images 

configuration settings - e.g. browser 

display, language choice, output 

format 

See also: 

Configuring set-top boxes on page 43 

About software images on page 13 

Customising a software upgrade image on page 50 


Introduction 

1.6 About software images 

The set-top box NAND flash holds two types of signed software image: 

Bootstrap image 

The bootstrap image contains the software needed to manage the download of a 

multicast upgrade image. It is a combined Linux kernel and RAM disk image with an RSA 

digital signature. 

A signed bootstrap image is generated as file called: bootstrap.signed. 

Upgrade image 

The upgrade image is a file that contains a complete software upgrade in the form of a 

file system image with an RSA digital signature. 

A signed upgrade image is normally generated as file called: mc2.mcfs. 

Making new software images available 

When the set-top box is first connected, it inspects its NAND flash, and if this contains no 

valid software, it connects to the Multicast server and downloads a software release: first 

the bootstrap image, and then the upgrade image. 

If you have not been supplied with signed software images, you will need to create and 

sign your own. To do this, you will need the bootstrap and/or upgradeimage directories 

of a software release, and the customer key and its pass phrase. Keys are normally 

provided as part of a software release, but you can also generate and use your own keys, 

as long as they are in the set-top box ROM. 

Bootstrap image: You should normally only need to sign and load a bootstrap image 

when the set-top box is supplied with a blank NAND flash (e.g. units shipped direct from 

manufacture). The bootstrap image is created from the bootstrap.unsigned file, using 

the signbootstrap script and the customer key. 

Upgrade image: Upgrade images need to be created whenever you need to upgrade settop 

boxes with a new software release. The upgrade image is created from the contents 

of the imagecomponents directory specified in the flashcontents file, using the 

signupgradeimage script and the customer key. 

The upgrade image can be downloaded automatically by a set-top box (controlled by 

deployment index mechanism) or you can initiate multicasting (or unicasting) the image 

manually from the DHCP server and Amino Multicast server, - e.g. using the 

STBremoteconf tool. If you have not been supplied with signed bootstrap and upgrade 

images, you need to create them yourself from the files supplied in the Amino software 

release. 

See also: 

About software builds on page 11 

Overview of operational states on page 10 

1.7 About software security 

The software on a set-top box is protected by a combination of security measures: 

RSA security keys 

software deployment index (DI) 

password-protected access to management tools 


Introduction 

 

software build options 

Security keys 

Software is protected by cryptographic public-private keys and digital signatures; this 

extends from initial booting through to uploading of new software images. Images and 

commands are digitally signed when they are sent to a set-top box, and the set-top box 

checks for this signature before it loads the new software or completes the operation 

requested. 

Software distributions include public keys (used by the set-top box to verify images and 

commands) and private keys (used to sign new images and commands) for the customer 

key and configuration key. The public keys are kept on the set-top box, and the private 

keys are stored off the set-top box, usually on the PC used to sign new images. The keys 

used can be either the Amino engineering keys - used for trial purposes - or customerspecific 

keys, depending on customer requirements. In some cases, the customer may 

generate their own keys if required. 

Master key 

The master key is used only by Amino, to validate the customer key. It is held securely 

and is only available to Amino. 

Customer key 

The customer key is used to verify that bootstrap and upgrade images have been signed 

by a trusted source. 

The Amino engineering customer key (KEY.private) is normally provided with a release. 

The passphrase for this Amino engineering key is markskey. 

Configuration key 

The configuration key is used to verify the validity of remote management commands sent 

to the set-top box. 

The Amino engineering configuration key (STBrc-KEY.private) is normally provided with 

a release. The passphrase for this Amino engineering key is stbrckey. 

Deployment indexes (DI) 

The deployment index or DI is a mechanism used in the Multicast upgrade system to 

ensure that set-top boxes are using the correct versions of software. An index number is 

assigned when the signed software upgrade image is created, and when a set-top box is 

instructed to upgrade, it checks the deployment index of its current software image, and 

will only upgrade if the new software image has the same or a higher deployment index 

number. Note that the deployment index in an image is signed so that it cannot be 

tampered with. 

All set-top boxes are manufactured with an initial deployment index of 0. 

Example: 

A service provider is currently running with software version 0.9.2 on all their set-top 

boxes, which include the CA vendor’s software. Software version 0.9.2 is multicast across 

the network so that set-top boxes can upgrade to it or recover their software image at any 

time. This version 0.9.2 has a deployment index of 1. During this time, a user makes an 

unauthorised copy of version 0.9.2 on their hard drive. 


Introduction 

The CA vendor discovers a fault in version 0.9.2 that allows free access to subscription 

channels. The CA vendor issues version 0.9.4 to fix this fault, and the service provider 

upgrades all their set-top boxes to this new version. This version has a deployment index 

of 2. 

Without the deployment index mechanism, the user could potentially downgrade to their 

unauthorised copy of 0.9.2, and continue to receive free channels. The deployment index 

prevents this, though: the set-top box will not downgrade to 0.9.2, because this version 

has a lower index number than 0.9.4. 

Passwords 

Access to management functionality is assigned to password-controlled users. 

The following table outlines the main password-controlled user levels and their defaults: 

User name Description 

root 

mngread 

mngwrite 

Used for Telnet / serial console access on 

development builds. 

Used for access to the set-top box management 

pages. 

Used to write back changes from the set-top box 

management pages. 

Default 

password 

root2root 

leaves 

snake 

Build options 

Various set-top box functionality is locked or disabled during a hardware build, to protect 

the set-top box from interference. This includes identity settings such as MAC address 

and serial number. Set-top boxes with this functionality enabled are referred to in this 

documentation as “development” builds (these are sometimes also called “production” - 

see note that follows); set-top boxes with the functionality locked are known as “live” 

builds. Note that software releases designed to support functionality only available during 

development include production in the name of the release version. 

1.8 More about operational states 

The sections that follow provide detail about the stset-top box operation states, including 

how set-top box operation is affected if one of the actions that the set-top box executes 

is not successful. Information about operational errors is indicated by flashing codes used 

by the LED on the set-top box. See the separate LED flashing codes section for a list of 

these errors. 

Static DHCP settings: The descriptions that follow outline operation where the set-top 

box relies on the DHCP server for its network and other settings. Where these are defined 

statically in the set-top box’s configuration, they can either be used as a fall-back - if 

communication with the DHCP server fails - or they can be used in place of DHCP 

communication. How these static settings are used depends on configuration. 


Introduction 

Operation in bootstrap (mboot) state 

During bootstrap state, the default boot logo is displayed on the screen. If this hasn’t been 

customised, it will be similar to this: 

The operational sequence on entering this state is as follows: 

If there is a failure during this state, a sequence of flashes of the LED on the set-top box 

indicates the reason. 

Send DHCP request: The set-top box sends a message to the DHCP server, including 

mboot state and a string identifying the hardware platform. The DHCP server compares 

the state and the platform string against classes defined in its configuration file. If it 

doesn’t find a class, then it can’t provide the information that the set-top box needs. 

DHCP response: When the DHCP server identifies an appropriate class, it responds to 

the set-top box with network settings and the vendor extensions defined in that class. 

These vendor extensions are normally an IP address and port for retrieving a bootstrap 

image that is being transmitted by the Multicast server. 


Introduction 

If the set-top box doesn’t receive a response from the DHCP server, it retries sending the 

DHCP request a number of times (the number of retries is specified in the code). If this is 

still not successful, it either uses values from its configuration (if these have been set) or 

reboots itself, returning to the initial powered state. 

Download image: The set-top box connects to the multicast carousel with the details it 

has received and downloads the packets for a bootstrap image. If the set-top box doesn’t 

manage to download an image from the Multicast server within a defined timeout, it 

reboots itself, returning to the initial powered state. 

Assemble, verify and execute image: The set-top box verifies the new bootstrap image 

by using the public customer key it holds to check the digital signature that the image is 

signed with. If the software is successfully verified, the set-top box executes it and stores 

it in its NAND flash. 

If the set-top box can’t verify or execute the software it has downloaded, the software is 

reset and the set-top box reboots itself 

Operation in upgrade (upgrd) state 

During upgrade state, the loading screen is displayed, which contains just the word 

Loading.... 

The operational sequence on entering this state is as follows: 

If there is a failure during this state, a sequence of flashes of the LED on the set-top box 

indicates the reason. 

Send DHCP request: Once the set-top box has successfully loaded a bootstrap image, 

it enters the upgrade state.The set-top box also enters this state if a manual upgrade 

request is initiated (e.g. via STBremoteconf). The set-top box sends a message to the 

DHCP server, including upgrd state and a string identifying the hardware platform. 


Introduction 

DHCP response: The DHCP server compares the state and the platform string against 

classes defined in its configuration file. When the DHCP server identifies an appropriate 

class, it responds to the set-top box with network settings and the vendor extensions 

defined in that class. These vendor extensions are normally an IP address and port for 

retrieving an upgrade image that is being transmitted by the Multicast server. If it doesn’t 

find a class, then it can’t provide the information that the set-top box needs. 

If the set-top box doesn’t receive a response from the DHCP server after a number of 

retries, it tries to move to the next stage using the settings in its configuration (i.e. using 

null values for the multicast IP address and port, if these have not been set in the 

configuration - so the download will not succeed). 

Download image: The set-top box connects to the multicast carousel with the details it 

has received and downloads the packets for an upgrade image. If it doesn’t manage to 

download the image within a defined timeout, it reboots, and returns to the initial powered 

state. 

Assemble, verify and execute image: The set-top box verifies the new image by using 

the public customer key it holds to check the digital signature that the image is signed 

with. It also compares the deployment index (DI) of the software against its current index. 

If the software is successfully verified, the set-top box stores it in its NAND flash and 

executes it. 

If the software is not successfully verified and executed, then the set-top box resets itself. 

How it behaves at this stage, depends on what stage of the verification process it failed 

at: it can either reboot or re-enter the upgrade state. 

Note that at this point the NAND flash could potentially be corrupted by a power outage 

or other failure. If this happens, the set-top box will detect it and return to the bootstrap 

state. 

Operation in filesystem (fisys) state 

In filesystem state, normal operation is enabled. When the set-top box first enters this 

state, it shows the page defined as the default home page. For example, for a standard 

Amino build with the ANT Fresco browser, a screen similar to the following is displayed: 

The operational sequence on entering this state is as follows. If there is a failure during 

this state, a sequence of flashes of the LED on the set-top box indicates the reason. 

Send DHCP request: When the set-top box successfully loads both a bootstrap and 

software upgrade image, it enters the filesystem state. The set-top box sends a message 

to the DHCP server, including fisys state and a string identifying the hardware platform. 

The DHCP server compares the state and the platform string against classes defined in 

its configuration file. If it doesn’t find a class, then it is unable to supply the information 

that the set-top box needs. 


Introduction 

DHCP response: When the DHCP server identifies an appropriate class, it responds to 

the set-top box, with network settings and any vendor extensions defined in that class. 

For the filesystem state, vendor extensions are optional, but they can include an IP 

address and port for retrieving an upgrade image that is being transmitted by the Multicast 

server as well as other options such as middleware server details and minimum software 

deployment index (DI) that the set-top box must be running. 

If the set-top box doesn’t receive a response from the DHCP server after a number of 

retries, it reboots, returning to its initial powered state. 

Initiate upgrade or Normal use: If the minimum deployment index supplied is greater 

than the set-top box’s current index, the set-top box enters the upgrade state, to 

download a new software version. The set-top box must have been supplied with 

multicast IP address and port in order for this upgrade to be successful. If the upgrade 

fails, then the set-top box returns to normal operation, using its current software version. 

If the set-top box receives an upgrade instruction from an external application, the set-top 

box enters the upgrade state, using the multicast IP address and port supplied in the 

upgrade instruction. Again, if the upgrade fails, the set-top box returns to normal 

operation without upgrading its software. 

Otherwise, the set-top box is available for normal operation. 


2 Setting up a basic Multicast upgrade 

system 

The instructions in this section describe how to set up a basic Multicast system on your 

machine for the first time - for example, to connect to a single set-top box as a trial or to 

familiarise yourself with the components. These sections detail the minimum set-up and 

configuration required; for information on setting up equipment for more complex 

systems, see Setting up an advanced Multicast upgrade system on page 29. 

2.1 Overview of procedure for setting up a Multicast system 

Prerequisites 

The instructions here assume you have a compressed Amino release and a computer 

with Linux and a DHCP server installed. They also assume familiarity with basic Linux 

command line functionality. If you intend to use STBremoteconf for remote control and 

communication with set-top boxes, then you will need Perl on the PC you are installing 

these components on. To complete the installation, you will also need to be able to find 

out settings for the network that the set-top box is connected to. 

Note: You must log in as root in order to complete the Multicast system set-up and use 

the remote configuration tools. 

Steps 

To set up a Multicast system for the first time, you need to complete the following steps: 

1. Copy files. 

2. Set up the DHCP server. 

3. Set up the Multicast server. 

4. Create software images. 

5. Start the Multicast server. 

Once you have completed these steps, your set-top box will be able to automatically 

connect and download software. 

2.2 Release directory contents 

The compressed standard release file supplied by Amino unzips to the following directory 

structure shown in the table below. The actual contents of the directories vary depending 

on the release - for example, CA-specific files and browser-specific files will be included 

with some releases; certain releases may not include keys or the full set of management 

utilities. The table below shows the location of the main files described in the 

documentation. 


Setting up a basic Multicast upgrade system 

Note: In the following table, bold text indicates a directory. 

File / subdirectory 

bootstrap 

bootstrap.unsigned 

signbootstrap 

romupgrade 

tftpboot 

server 

dhcpd.conf 

mcastbootd 

mcastbootd.conf 

upgradeimage 

flashcontents 

signupgradeimage 

imagecomponents 

config.txt 

fkeys.conf 

loading.gif 

mcnfg.tar 

netconf 

opera.ini 

settings 

splash.gif 

bin 

utils 

commands 

imgcfg 

STBremoteconf 

keys 

amino 

KEY.private 

KEY.public 

Description 

Directory containing the components needed to create a 

signed bootstrap image. 

The unsigned bootstrap image. 

The script to use to create a signed bootstrap image. 

Directory containing files needed to upgrade a TFTP booting 

set-top box to use the Multicast upgrade system. 

TFTP to Multicast upgrade files. 

Directory containing files for setting up the Multicast upgrade 

system on the server. 

Configuration file containing settings that you need to edit 

and add to your DHCP server’s configuration file. 

Amino Multicast server binary file. 

Multicast server configuration file. 

Directory that contains the components needed to create a 

signed upgrade image. 

File that lists the files to use to create the software upgrade 

image (i.e. the imagecomponents files). 

The script to use to create a signed software upgrade image. 

Directory containing the files to be used as the contents of a 

software upgrade image. 

Browser configuration file (Fresco). 

Configuration file defining actions associated with IR remote 

control and keyboard keys. You are not recommended to edit 

this file directly. 

Graphic shown on screen when the set-top box is loading a 

new software upgrade image via TFTP (not used for 

Multicast upgrade). 

Tar file containing HTML used to display the set-top box 

Configuration pages. 

Configuration file containing network settings. 

Browser configuration file (Opera). 

Configuration file containing general set-top box settings. 

Graphic shown on screen when the set-top box is booting. 

Directory containing set-top box software binary files. 

Directory containing management utilities. 

File containing commands used by STBremoteconf. 

Utility that enables remote configuration of set-top boxes. 

Directory containing the private keys used to sign and verify 

software images and STBremoteconf commands. 

The Amino engineering keys. 

The private customer key. 

The public customer key. 



File / subdirectory 

Master.public 

STBrc- 

KEY.private 

STBrc-KEYpublic 

Description 

The public master key. 

The private configuration key. 

The public configuration key. 

2.3 Copying files 

The steps here detail what you need to do to set up a basic Multicast system for the first 

time. 

To copy files 

In the following instructions, stands for the full path to the directory that 

contains your Amino software release. If you follow the example instructions below, this 

is: /usr/local/amino/releases/ 

1. Create an amino directory, with two subdirectories, called releases and 

images. 

For example: 

cd /usr/local 

mkdir amino 

cd amino 

mkdir releases 

mkdir images 

2. Unzip the Amino software release to the releases directory. 

For example: 

tar xvfs 

/usr/local/amino/releases/ 

3. Copy the Multicast server binary to a directory in the system path. 

For example: 

cp /server/mcastbootd /usr/local/bin 

4. Copy the contents of the utils directory to the same location. 

For example: 

cp /utils/* /usr/local/bin 

Note that the keys subdirectory isn’t copied over by this command (it is not 

needed here). 

5. Copy the Multicast server configuration file to the /etc directory. 

For example: 

cp /server/mcastbootd.conf /etc 

6. If you are using a dedicated DHCP server (only for this Multicast system), then 

copy the sample configuration file from the software release to the etc directory. 

For example: 

cp /server/dhcpd.conf /etc 

If you are using a DHCP server that is already set up, then you will be able to 



copy settings from the sample file to your existing file when you set up the 

DHCP server. 

All the files needed to run the Multicast system have now been copied to the locations 

they are needed in. You will also still need to access some of the other files in the software 

release directory. 

2.4 Setting up the DHCP server 

For a first set-up of a Multicast system (e.g. for trial purposes), you are recommended to 

set up a DHCP server that will only be used for this Multicast system, in order to keep 

configuration simple while you are getting to know the system’s functionality. A sample 

configuration file is supplied with the software release, and you can either edit this file or 

copy the settings from this file to your DHCP server’s configuration file. 

To set up the DHCP server 

1. Open the sample DHCP server configuration file dhcpd.conf in a text editor. If 

you copied the file over when you copied the binaries, then this is located in 

/etc. Otherwise, it is in the /server/ directory. If you are adding 

settings to an existing DHCP server configuration file, you will also need to open 

the configuration file for your DHCP server, and in the following instructions you 

will need to copy the settings from the sample file to you DHCP server’s 

configuration file, before editing them. 

2. The following settings from the sample configuration file need to be in the DHCP 

server configuration file that you want to use. If you are copying files from the 

sample file to your existing DHCP configuration file, then you should copy these 

unchanged: 

Misc dhcp options 

allow bootp; 

ddns-update-style ad-hoc; 

filename=”AMINET.txt”; 

Extra Options for Amino option space 

option space AMINO; 

option AMINO.address code 1 = ip-address; 

... 

option AMINO.middleware2 code 17 = ip-address; 

3. For each set-top box type that you want to multicast to, you will need classes 

that specify how set-top boxes can get software images when they are in boot 

state mboot class), upgrade state (upgrd class) and normal boot state (fisys 

class). These are as follows in the sample file: 

AmiNET Configuration section(s) 

class “AmiNET mboot” ... 

class “AmiNET upgrd” ... 

class “AmiNET fisys” ... 

Use these classes exactly as they are shown in the sample file, and edit just the 

following options in the mboot and upgrd classes, to use a unique IP address 

for each class. 

option AMINO.address ; 

option AMINO.port ; 



4. You will also see the following lines in the fisys classes in the file: 

option AMINO.middleware ; 

option AMINO.mw_port ; 

If you have Minerva middleware on the set-top box type, edit these lines with IP 

address and port values for the middleware server. For all other sections, 

comment out these lines by adding a # character to the start of each line. 

5. Make a note of the multicast IP addresses and ports you have specified for each 

set-top box type, as you will need to use the same values when you set up the 

Multicast server. 

6. Edit the subnet declaration with settings for your network. As a minimum, you 

will need to edit the following lines: 

subnet netmask { 

option routers ; 

options subnet-mask ; 

pool{ 

range dynamic-bootp 192.168.1.50 192.168.1.100; 

range 192.168.1.101 192.168.1.200; 

} 

Note that in the pool declaration, range dynamic-bootp is the range for TFTPbooting 

set-top boxes; the other range (just range) is the range of IP addresses 

for multicast booting and upgrades. 

7. Make any further settings you require for your system. Note that from 0.13.0 you 

can add User Class options to the configuration file if required, and they will be 

passed to the set-top box in the DHCP response. Refer to your DHCP server’s 

documentation for general configuration information. 

8. Save your changes, then reboot the DHCP server with the following command: 

/etc/init.d/dhcpd restart 

The minimum DHCP server set-up for a Multicast system is now complete. 

2.5 Setting up the Multicast server 

The following instructions describe the minimum steps that you need to complete to set 

up a working Multicast server that provides software images for a single type of set-top 

box (for example, as part of a trial system). 

2.6 To set up the Multicast server 

The instructions that follow assume that you have already installed, configured and 

started your DHCP server, and that you have copied the files from your software release 

to the example locations. 

9. Open the Multicast server configuration file mcastbootd.conf in a text editor. 

This is normally located in the /etc directory. 

10. In the [Image bootstrap.signed] section, edit the following settings to specify 

the IP address and port for multicasting the bootstrap image. 

MulticastIPAddress 

MulticastUDPPort 

These must be the same values as specified in the DHCP server configuration 



file’s mboot class. 

11. In the same section, check that the FileName setting lists the directory that you 

will be copying signed bootstrap images to and has the correct file name. If you 

have used the recommended settings, this is 

/usr/local/amino/images/bootstrap.signed. 

12. In the [Filesystem mc2] section, edit the following settings to specify the IP 

address and port for multicasting the bootstrap image. 

MulticastIPAddress 

MulticastUDPPort 

These must be the same values as specified in the DHCP server configuration 

file’s upgrd class. 

13. In the same section, check that the ImageName setting lists the directory that you 

will be copying signed software upgrade images to and has the correct name for 

the image. If you have used the recommended settings, this is 

/usr/local/amino/images. 

14. If you are setting up the Multicast server to transmit software for multiple set-top 

box types, you will need to add separate [Image ] and 

[Filesystem ] sections for each of the types of set-top box. The 

and must be unique, and must match the name of the 

bootstrap and upgrade images for that type of set-top box. (To set this up, you 

will also need to rename the software images you create, so that the image 

name for each type of set-top box is unique.) This is not necessary if you have 

only configured the DHCP server for a single type of set-top box. 

The Multicast server is now set up. You should now create software images and copy 

them to the directory specified in the configuration file before you start the Multicast 

server. 

2.7 Creating software images 

About software images 

The set-top box NAND flash holds two types of signed software image: 

Bootstrap image 

The bootstrap image contains the software needed to manage the download of a 

multicast upgrade image. It is a combined Linux kernel and RAM disk image with an RSA 

digital signature. 

A signed bootstrap image is generated as file called: bootstrap.signed. 

Upgrade image 

The upgrade image is a file that contains a complete software upgrade in the form of a 

file system image with an RSA digital signature. 

A signed upgrade image is normally generated as file called: mc2.mcfs. 

Making new software images available 

When the set-top box is first connected, it inspects its NAND flash, and if this contains no 

valid software, it connects to the Multicast server and downloads a software release: first 

the bootstrap image, and then the upgrade image. 



If you have not been supplied with signed software images, you will need to create and 

sign your own. To do this, you will need the bootstrap and/or upgradeimage directories 

of a software release, and the customer key and its pass phrase. Keys are normally 

provided as part of a software release, but you can also generate and use your own keys, 

as long as they are in the set-top box ROM. 

Bootstrap image: You should normally only need to sign and load a bootstrap image 

when the set-top box is supplied with a blank NAND flash (e.g. units shipped direct from 

manufacture). The bootstrap image is created from the bootstrap.unsigned file, using 

the signbootstrap script and the customer key. 

Upgrade image: Upgrade images need to be created whenever you need to upgrade settop 

boxes with a new software release. The upgrade image is created from the contents 

of the imagecomponents directory specified in the flashcontents file, using the 

signupgradeimage script and the customer key. 

The upgrade image can be downloaded automatically by a set-top box (controlled by 

deployment index mechanism) or you can initiate multicasting (or unicasting) the image 

manually from the DHCP server and Amino Multicast server, - e.g. using the 

STBremoteconf tool. If you have not been supplied with signed bootstrap and upgrade 

images, you need to create them yourself from the files supplied in the Amino software 

release. 

Creating a signed bootstrap image 

The following steps detail how to create a signed bootstrap image. This is generated as 

a file called bootstrap.signed. 

To create a signed bootstrap image 

The steps outlined here assume that you have set up a Multicast server and you have 

logged in as root. The Amino software release normally contains the engineering 

customer key that you will need for creating the bootstrap image. If you are using your 

own keys, then you will need to know the pass phrase for your key. 

Note: In the following steps, stands for the full path to the directory that 

contains your Amino software release. If you used example settings when you copied the 

files to your machine, this is: /usr/local/amino/releases/. 

1. Set the CUSTOMER_KEY environment variable by entering a command in the 

following format: 

export CUSTOMER_KEY=/utils/keys/amino/KEY.private 

2. Navigate to the bootstrap directory: 

cd /bootstrap 

3. Run the signbootstrap script by entering the following command: 

./signbootstrap 

You will be prompted to enter the pass phrase for the key. For the Amino 

engineering key, the pass phrase is markskey 

4. The script generates a bootstrap.signed file in the bootstrap directory. Copy 

this file to the images directory specified by the FileName setting in the [Image 

] section of the Multicast server configuration file 

(mcastbootd.conf). 

For example: 

cp bootstrap.signed /usr/local/amino/images 



When the Multicast server is started, the new image will be multicast automatically and 

the set-top box will download it next time it needs to upgrade its software. If the Multicast 

server is already running, you will need to restart it in order for it to transmit the new 

image. 

Creating a signed upgrade image 

The following steps detail how to use the signupgradeimage script to create a signed 

software upgrade image. This is image is normally called mc2.mcfs. 

To create a signed upgrade image 

The steps outlined here assume that you have set up a Multicast system and you have 

logged in as root. The Amino software release contains the engineering customer key that 

you will need for creating the signed software upgrade image. If you are using your own 

keys, then you will need to know the pass phrase for your customer key. 

Note: In the following steps, stands for the directory that contains your Amino 

software release. If you used example settings when you copied the files to your machine, 

this is: /usr/local/amino/releases/. 

1. Configure the files that will form the release and add any extra files to the 

flashcontents file. If you are setting up a system to familiarise yourself with the 

components, then you don’t need to perform any configuration at this stage. 

2. Set the CUSTOMER_KEY environment variable by entering a command in the 


export CUSTOMER_KEY=/utils/keys/amino/KEY.private 

3. Navigate to the upgradeimage directory: 

cd //upgradeimage 

4. Run the signupgradeimage script by entering a command in the following 

format: 

./signupgradeimage [-hvwz] [-s


Example command (recommended for a trial installation): 

./signupgradeimage -z 0 

You will be prompted to enter the pass phrase for the key. For the Amino 

engineering key, the pass phrase is markskey. 

5. The script generates an upgrade image in the current directory. It is normally 

called mc2.mcfs (or mc2.tgz if you ran the script with the -w argument). Copy 

this file to the images directory specified by the ImageName setting in the 

[Filesystem mc2] section of the Multicast server configuration file 

(mcastbootd.conf). 

For example: 

cp mc2.mcfs /usr/local/amino/images 

If you have multiple [Filesystem ] sections in the Multicast server 

configuration file, you will need to change the name of the file to the 

for the appropriate section, and then copy the file, as above. 

When the Multicast server is started, the new image will be multicast automatically and 

the set-top box will download it next time it needs to upgrade its software. Alternatively, 

you can force the set-top box to upgrade to a specified version. If the Multicast server is 

already running, you will need to restart it in order for it to transmit the new image. 

2.8 Starting the Multicast server 

These instructions assume you have set up and configured the DHCP server and 

Multicast server, and copied signed bootstrap and software upgrade images to the 

location specified in the Multicast server configuration file. 

To start the Multicast server 

1. Navigate to the directory in which software images are located. 

For example: 

cd /usr/local/amino/images 

2. Enter the following command: 

mcastbootd -D 

The Multicast server starts in debug mode, and details of its operation are 

echoed to the console. This is useful to monitor its operation in a trial 

installation. (Run the command without -D to start the Multicast server in normal 

mode.) 

The Multicast server continuously transmits the software images as a carousel, and when 

a set-top box needs to install a bootstrap or upgrade image, it joins the carousel and 

retrieves and installs the files it needs. 


3 Setting up an advanced Multicast 

upgrade system 

The instructions in Setting up a basic Multicast upgrade system detail how to set up a 

simple Multicast upgrade system that enables you to familiarise yourself with the 

available functionality using a single type of set-top box. The sections in this chapter 

provide additional recommendations on how to expand this simple implementation to 

handle multiple types of set-top box and to automate some of the steps. 

See also: 

 

 

for information about further configuration options for set-top boxes, see 

Configuring set-top boxes on page 43 

for information about how to control software upgrades, see Upgrading set-top 

box software on page 41 

3.1 Configuring the Multicast system for multiple set-top box types 

The sample configuration file supplied with a software release only contains sections to 

define a single bootstrap and upgrade image to transmit. In many deployments, it is likely 

that there will be more than one type of set-top box installed, each needing different 

software images. To implement this, you need to change the DHCP server and Multicast 

server configuration, and ensure that software images for different set-top box types are 

uniquely identifiable (either give them different names or store them in separate 

directories). 

To configure the DHCP server for multiple set-top box types 

The sample configuration file supplied with a software release includes examples of these 

classes for all the set-top box types. You can copy these sections into your configuration 

file for the set-top box types you want to support or add the classes yourself. 

The steps that follow assume you already have a DHCP server configuration file that 

contains configuration for a single type of set-top box. 

1. Navigate to the /etc directory, and open the following file in a text editor: 

dhcpd.conf 

2. For each set-top box type that you want to support, add an mcast, upgrd and 

fisys class. (See example after step 3.) Note that the name of the set-top box 

type that the class matches must be the same as is sent by the set-top box when 

it sends its DHCP request. 

3. Add Amino vendor options to each class, as required. As a minimum, you will 

normally need AMINO address and AMINO port in the mcast and upgrd 

classes; if you are setting up automatic upgrade with the deployment index 

mechanism, you will also need the following settings in the fisys class: AMINO 

address, AMINO port, AMINO dindex_min . 


Setting up an advanced Multicast upgrade system 

Example of completed classes for the AmiNET 110: 

class "AmiNET110 mboot" 

{ 

match if (option vendor-classidentifier="aminoAMINET11xmboot1.31") 

or ((substring(option vendor-encapsulated-options, 2, 

9)="AMINET11x") 

and (substring(option vendor-encapsulated-options, 13, 

5)="mboot")); 

} 

vendor-option-space AMINO; 

option AMINO.address 225.50.50.52; 

option AMINO.port 11111; 

class "AmiNET110 upgrd" 

{ match if (option vendor-classidentifier="Aminoaminet110upgrd") 

or ((substring( option vendor-encapsulatedoptions,2,9)="aminet110") 

and (substring( option vendor-encapsulatedoptions,13,5)="upgrd")); 

} 




class "AmiNET110 fisys" 

{ match if (option vendor-classidentifier="Aminoaminet110fisys") 

or ((substring( option vendor-encapsulated-options, 2, 

9)="aminet110") 


5)="fisys")); 


} 

4. When you have added all three classes for each set-top box type that you are 

supporting, save your changes then reboot the DHCP server with the following 

command: 

/etc/init.d/dhcpd restart 

For full configuration file examples, see Configuration example: DHCP server and 

Multicast server for multiple types of set-top box on page 102, which shows a DHCP server 

server configuration file for several types of set-top box. The example also includes a 

table that shows the settings that need to correspond in the Multicast server and DHCP 

server configuration files. 



To configure the Multicast server for multiple set-top box types 

The sample Multicast server configuration file supplied with a software release defines 

one bootstrap and upgrade image. 

The steps that follow assume you have already set up the Multicast server as detailed in 

Setting up a basic Multicast upgrade system on page 20, and the configuration files 

contains settings for a single set-top box, with the specified software images stored in the 

specified directories. 

1. Navigate to the /etc directory, and open the following file in a text editor: 

mcastbootd.conf 

2. Add the Image and Filesystem sections for each type of set-top box. Note that 

each section must be named uniquely. The software images for each set-top 

box type must be unique (they can either be stored in separate directories or 

named uniquely by renaming the image files you have created). 

Example Image sections (contains two Image sections that specify bootstrap 

images for two platforms; note that the images are named uniquely - 

bootstrap.110 and bootstrap.130): 

[Image bootstrap.110] 

MulticastIPAddress=239.255.230.52 

MulticastUDPPort=11111 

FileName=bootstrap.110 

Description=Linux bootstrap image 

ImageType=1 

SerialNumber=1 

PacketSize=1456 

CycleTime=0 






ImageType=1 



CycleTime=0 

See To use symbolic links to reduce Multicast server configuration when you add 

new images on page 33 for details of how to set up an image directory structure 

that identifies current images directly without the need to keep updating the 

Multicast server’s configuration. 



Example Filesystem sections (for transmitting software upgrade images for 

the same platforms as in the Image section examples above; again the upgrade 

images are named uniquely - mc110 and mc130): 

[Filesystem mc110] 



ImageName=mc110 

Description=upgrade filesystem 


DirsPerCycle=128 

DataRate=256 








DataRate=256 

Important: The Multicast server configuration file must contain a Filesystem 

section called mc2. If this section is removed, the signupgradeimage script can’t 

create new software upgrade images successfully. If you want to name sections 

appropriately for each set-top box type, then you should leave this section in the 

file as a dummy section, and add new sections for each of the set-top box types 

that you want to support. If there is no software upgrade image at the location 

specified in this dummy section, the Multicast server will generate errors on 

start-up, but will still run. 

Example [Filesystem mc2] section (this can be a dummy section, as described 

above): 




ImageName=mc2 




DataRate=256 

For full configuration file examples, see Configuration example: DHCP server and 

Multicast server for multiple types of set-top box on page 102, which shows a Multicast 

server configuration file that transmits images for several types of set-top box. The 

example also includes a table that shows the settings that need to correspond in the 

Multicast server and DHCP server files. 



To use symbolic links to reduce Multicast server configuration when you add new images 

If you are implementing a system in which you will be updating the software image that a 

set-top box needs to download (e.g. to provide images that use new software versions), 

it can be useful to put in place an image directory structure that uses symbolic links, so 

that you don’t need to edit the Multicast server configuration file for every new software 

image. The following instructions outline how to put this in place. 

The steps that follow assume you have already set up the Multicast server as detailed in 

Setting up a basic Multicast upgrade system on page 20. 

1. Create a directory structure with a separate directory for each type of set-top 

box that you are supporting, each with a subdirectory for the current version. 

For example, if you’re supporting the AmiNET110 and AmiNET500, and you are 

currently using software version 0.13.0 for both, create the following directories: 

/A110/0.13.0 

/A500/0.13.0 

2. Create the bootstrap and upgrade images for each software version, and copy 

them into the appropriate directories. Note that there is no need for the images 

for each set-top box type to have different names from each other, as they are 

already uniquely identified by their directory location. The configuration 

example below assumes both bootstrap images are called bootstrap.signed, 

and both upgrade images are called mc2. 

3. Create symbolic links called current for each of these directories. 

Example: 

ln -s /A110/0.13.0 /A110/current 

ln -s /A500/0.13.0 /A500/current 

4. Edit the Multicast server configuration file to include sections for each image, 

using the same Multicast IP addresses and ports as specified in the DHCP 

server configuration. Instead of giving the image location directory by version 

number, use the current symbolic links that you just created. Note that you’ll 

also need to keep the original mc2 section with dummy settings. 

Example configuration file: 

# Configuration file: Tue Sep 19 10:25:51 2006 

[Server] 

LogLevel=4 

MulticastTTL=5 

ImageDir=/usr/local/amino/images 

[Image A110Bootstrap] 



FileName=110/current/bootstrap.signed 


ImageType=1 



CycleTime=0 



[Image A500Bootstrap] 



FileName=A500/current/bootstrap.signed 


ImageType=1 



CycleTime=0 




ImageName=mc2 

Description=DUMMY upgrade filesystem 



DataRate=512 

[Filesystem A110Upgrade] 



ImageName=A110/current/mc2 




DataRate=512 

[Filesystem A500Upgrade] 



ImageName=A500/current/mc2 




DataRate=512 

5. Save your changes and restart the Multicast server. 

Next time you need to add a new software image for the platforms you’ve set up: 

6. Create a subdirectory with the new version number. 

For example, if you’re adding images for version 0.13.8, for the AmiNET110, 

create the following directory: 

/A110/0.13.8 

7. Change the current symbolic link to this new directory instead of the 0.13.0 

one: 

ln -s /A110/0.13.8 /bootstrap/A110/current 



8. The Multicast server configuration sections already point to the current 

directory, so all you need to do to start transmitting the new images is restart the 

Multicast server. 

3.2 Using deployment indexes for automatic upgrade 

In normal operation, the set-top box downloads new software from the Multicast server 

when there is a problem with its current software or when an upgrade command instructs 

it to (e.g. from STBremoteconf, the Management pages or a JMACX call). Using the 

deployment index, it is also possible to configure the Multicast upgrade system to force 

set-top boxes to upgrade to a particular software version (as identified by the software’s 

deployment index). 

How it works 

The set-top box stores the deployment index of its current software version in the NOR 

flash. 

A new deployment index is specified when a new signed software upgrade image is 

created (with the signupgradeimage script). The deployment index is an integer between 

0 and 65535. 

When the set-top box receives the new software version, it checks the deployment index 

against the number in its NOR flash, and accepts the software upgrade if the new number 

is the same or greater, and changes the deployment index in its NOR flash accordingly. 

Otherwise it rejects it. 

For trial versions and for early stages of a project, we recommend you use a deployment 

index of 0 all the time. This means that you don’t need to specify the deployment index 

when you create a new upgrade image. Once the deployment is live, the service provider 

should increase the deployment index by 1 when asked to produce a new version by the 

software provider (e.g. the CA or middleware vendor). 

Deployment indexes and software versioning 

The deployment index mechanism is completely separate from software version 

numbers. This means that if necessary a service provider can downgrade from a current 

software version to an older one, as long as they create a software upgrade image with 

a higher deployment index than the current software version has. 

Migrating from pre-DI to DI-capable software 

All set-top boxes are manufactured with an initial deployment index of 0 in their NOR 

flash. All you need to do to start using the deployment index mechanism in a system that 

currently doesn’t implement this control, is to increase the deployment index to 1 in the 

next software upgrade image that you create. 

Setting up automatic upgrade to minimum deployment index 

The deployment index mechanism can be used to force set-top boxes to upgrade to a 

specified minimum deployment index, using Amino DHCP vendor extensions. The 

minimum index number is added to the DHCP configuration. When the set-top box boots 

up and contacts the DHCP server, the DHCP server includes this deployment index in its 

response, along with the multicast upgrade address and port for the upgrade image. The 

set-top box checks this index against the deployment index in its NOR flash, and 

upgrades immediately if its index is lower than the specified value. 



To implement automatic upgrading 

Automatic upgrading to a specified minimum deployment index is set up in the DHCP 

server. The following steps outline how to implement this system. 

Note: The following steps assume you have already set up a Multicast upgrade system 

and the software image is in the location specified in the Multicast server’s configuration. 

1. Open the DHCP server configuration file (dhcpd.conf). 

2. Find the Amino options (under option space AMINO;) and ensure that the 

following line is included (add it if it is not there already): 

option AMINO.dindex_min code 10=integer 32; 

3. Find the fisys class for the set-top box type that you want to force to upgrade, 

and under vendor-option-space AMINO; add a line in the following format: 

option AMINO.dindex_min ; 

For example, if you want set-top boxes to be running software with the minimum 

deployment index of 5, the line should be as follows: 

option AMINO.dindex_min 5; 

4. Also ensure that the following lines are present, and specify the correct 

multicast IP address and port: 

option AMINO.address ; 

option AMINO.port ; 

The fisys class you are editing should now look similar to the following: 

class “110 normal” 

{ 

match if (substring( option vendor-encapsulated-options, 2, 

9)=”aminet110”) and (substring( option vendorencapsulated-options, 

13, 5)=”fisys”); 


option AMINO.dindex_min 5; 



} 

5. Save your changes and restart the DHCP server. Also ensure the Multicast 

server is running. 

The system is now set up. Next time a set-top box of the configured type boots, it will 

compare its current deployment index with the one you specified, and will upgrade to the 

specified software image if its current deployment index is lower than the one in the DHCP 

server configuration. 

To test automatic upgrading 

Once you have implemented automatic upgrading using a specified minimum deployment 

index to force upgrades, you can test the system. The following steps assume that Telnet 

(or other remote log-in client) is enabled in the set-top box. 

1. Check the deployment index number of set-top box you’re going to test with. 

You can do this from the command line by Telnetting to the set-top box and 

entering the following command (the current number must be lower than the one 

you want to upgrade to): 

libconfig-get NORFLASH.DI 



2. Power up (or reboot) the set-top box. 

The loading screen is displayed (the default image has Loading followed by 

Upgrading, do not unplug! 

3. When the upgrade is finished, you can check that the set-top box is now running 

the new software version and you can check the deployment index, as in step 

1 (it should now have the deployment index specified in the DHCP server 

configuration file). 

See also: 

Using libconfig on page 75 

Enabling remote log-in tools on page 52 

3.3 Setting set-top boxes with static network and multicast upgrade 

settings 

Some DHCP servers don’t support the addition of the vendor extensions that this 

Multicast upgrade system uses to tell set-top boxes the IP address and port to use for 

booting and retrieving software images (e.g. AMINO.address and AMINO.port). In these 

cases, the DHCP server can be used just to assign an IP address to the set-top box, and 

you can configure the addresses and ports to use for software upgrades as static values 

in the set-top box’s configuration. 

In other installations, it may be useful to set all network settings statically, rather than 

retrieving them from the DHCP server. 

In both cases, the static values are normally defined in the NOR flash, which you can edit 

in the following ways: 

libconfig commands in upgrade script (recommended method) 

libconfig commands via remote log-in tool (e.g. Telnet) 

via the Management pages (Network Configuration page) 

JMACX calls in HTML page (not generally recommended, for security reasons) 

In some cases, the settings may be defined in the netconf file. See the Set-Top Box 

Configuration Guide for more information. 

The recommended way to set static multicast upgrade and network values for multiple 

set-top boxes is to add libconfig commands to the upgrade script that is included as part 

of a software image. The script executes automatically when the new software image is 

loaded to the set-top box, and is then deleted. 

Network and multicast upgrade configuration settings 

To set static network and multicast upgrade settings, you need to edit settings in the NOR 

flash. These settings can be accessed via various configuration tools (e.g. libconfig 

commands in an upgrade.sh script or over Telnet, JMACX calls, Management pages). 

For more information on these settings, see Set-Top Box Configuration Guide. For 

details of how to use the tools available to change settings, see the JMACX API 

Specification and Set-Top Box Configuration Pages Administrator Guide. 

The NOR flash settings that configure static network and multicast upgrade values are 

listed in the following sections. 

Note: In some cases, these settings may be defined in the netconf file. See the Set-Top 

Box Management Configuration Guide for more information. 



To configure whether the set-top box uses static network values by default: 

DHCP 

Set this to “N” (i.e. disable), to configure set-top boxes to always use static network 

values. 

To set static multicast upgrade values: 

MULTICAST_BOOTSTRAP_GROUP 

MULTICAST_BOOTSTRAP_PORT 

MULTICAST_UPGRADE_GROUP 

MULTICAST_UPGRADE_PORT 

MULTICAST_FILESYSTEM_GROUP 

MULTICAST_FILESYSTEM_PORT 

Note: The bootstrap, upgrade and filesystem groups must be set with a valid multicast 

addresses in order for multicast upgrades to work. From version 0.14.4, if an address is 

invalid, the set-top box tries to retrieve an IP address via DHCP; if this is not successful 

- or if the address that the set-top box retrieves via DHCP is also invalid - the set-top box 

reboots. 

To set a static IP address: 

IPADDR 

Other network settings: 

NETMASK 

GATEWAY 

DNS 

TIME_SERVER 

Required vs. optional settings 

The list of values that must be defined statically depends on what functionality your DHCP 

server supports. The following guidelines apply: 

 

 

Required multicast upgrade settings: If the DHCP server is being used to 

provide network settings, but not the multicast upgrade settings (i.e. the DHCP 

server doesn’t support the Amino vendor extensions), the bootstrap and 

upgrade settings are required. The filesystem settings are normally optional, 

although this will depend on the functionality you want to enable in the system. 

Required network settings: If the DHCP server is not being used to provide 

network settings, then most of the values listed are required; only DNS and 

TIME_SERVER are optional. 

Example upgrade.sh script to set static multicast upgrade values 

The recommended way to set static network and multicast upgrade values for multiple 

set-top boxes is to add libconfig commands to the upgrade script that is added to the 

image components used to create a software upgrade image. When the new upgrade 

image is loaded to the set-top box, the script executes automatically, and is then deleted. 

Important: The software image containing this upgrade script must be installed on the 

set-top boxes before they are installed on a network that requires the static settings. This 

is because the set-top box requires these network settings in order to retrieve the new 

software image. 



The following script uses libconfig commands to set values for some of the multicast 

upgrade settings (bootstrap and upgrade ports and IP addresses) in the NOR flash: 

#!/bin/sh 

libconfig-set NOFLASH.MULTICAST_BOOTSTRAP_GROUP 239.255.1.1 

libconfig-set NORFLASH.MULTICAST_BOOTSTRAP_PORT 11111 

libconfig-set NOFLASH.MULTICAST_UPGRADE_GROUP 239.255.1.2 

libconfig-set NORFLASH.MULTICAST_UPGRADE_PORT 11111 

For more information on the libconfig-set command, the NOR flash settings and upgrade 

script, see the Set-Top Box Configuration Guide. 

See also: 

Using libconfig on page 75 

Creating an upgrade script on page 52 

Set-top box configuration settings on page 79 

3.4 Automating Multicast server start-up 

By default, the Multicast server doesn’t start when you start the server it is installed on. 

You can enable automatic start-up by creating an mcastbootd script in /etc/init.d, and 

running the following command to start the service:chkconfig mcastbootd on. The 

Multicast server will be started automatically on the next reboot. 

The following example start script works with Redhat Linux. 

#!/bin/bash 

# 

# chkconfig: 2345 55 25 

# description: Amino Multicast Daemon 

# processname: mcastbootd 

# config: /etc/mcastbootd.conf 

# Source function library. 

[ -f /etc/rc.d/init.d/functions ] || exit 0 

. /etc/rc.d/init.d/functions 

# getting the Mcastbootd options 

. /etc/sysconfig/mcastbootd 

RETVAL=0 

start() { 

echo -n $"Starting Mcastbootd server services: " 

mcastbootd $MCASTBOOTD_ARGS 

RETVAL=$? 

echo 

[ $RETVAL -eq 0 ] && touch /var/lock/subsys/mcastbootd 

return $RETVAL 

} 



stop() { 

echo -n $"Stopping Mcastbootd server services: " 

killproc mcastbootd 

RETVAL=$? 

[ $RETVAL -eq 0 ] && rm -f /var/lock/subsys/mcastbootd echo 

return $RETVAL 

} 

# See how we were called. 

case "$1" in 

start) 

start ;; 

stop) 

stop ;; 

status) 

status mcastbootd ;; 

restart|reload) 

stop start ;; 

condrestart) 

if [ -f /var/lock/subsys/mcastbootd ]; then 

stop 

start 

fi 

;; 

*) 

echo $"Usage: $0 

{start|stop|status|restart|reload|condrestart}" 

exit 1 

esac 

exit $RETVAL 


4 Upgrading set-top box software 

4.1 Upgrade options 

The Amino Multicast upgrade system offers various means of instructing set-top boxes to 

replace their software images: 

 

 

STBremoteconf - remote configuration tool that enables you to send 

commands such as changing basic configuration settings or initiating software 

upgrade. 

Management pages - local configuration pages, using an Amino IR keyboard 

and television display to change configuration settings and simple commands 

such as rebooting and initiating software upgrades. 

DHCP server configuration - DHCP server configuration specifies where settop 

boxes “go” to retrieve software images transmitted by the Multicast server; 

it can also be configured to force upgrades by specifying minimum deployment 

index numbers for software versions that the set-top box must be running. 

DHCP server and Multicast server together also enable the set-top box to 

connect and retrieve new software images when required (e.g. if the software 

on the set-top box is corrupted). 

In addition to these means, the JMACX API offers functions for controlling a range of settop 

box operational areas, including software upgrades. See the JMACX API 

Specification for more information. 

As detailed in the table below, the various upgrade mechanisms are each suited to 

particular circumstances and contexts. For example, making images available by defining 

upgrade groups and ports in the DHCP server configuration enables automatic upgrades 

when the set-top box requires them, but STBremoteconf can be used to force an upgrade 

at a required time. 

Note: In the table, “reflash” refers to deleting all the contents of the NAND flash and 

replacing both the bootstrap and the main software image, “upgrade” refers to replacing 

just the main software image. 

STBremoteconf 

Management 

pages 

Contexts 

remote y y 

local 

y 

single STB y y 

large deployment 

y (not 

recommended: 

requires all STBs 

to be powered) 

y 

test set-up y y 

automatic 

manual y y 

DHCP server 

config. 

y 


Upgrading set-top box software 

STBremoteconf 

Management 

pages 

DHCP server 

config. 

Operations 

upgrade y y y 

reflash y y 

upgrade to min. DI number 

(min. version 0.12.0 on 

A110/A500 platforms) 

y 

upgrade to min. version 

number 

. 

y 

4.2 Using STBremoteconf to upgrade software 

The UPGRADEMCAST and UPGRADEMCAST_VER commands enable you to instruct a set-top 

box to upgrade. See Using STBremoteconf on page 56 for details. 

4.3 Using the Management pages to upgrade software 

You can instruct a set-top box to upgrade or reflash from the Update Software 

Management page. See Using the HTML Configuration pages on page 69 for details. 

4.4 Configuring the DHCP server for multicast upgrades 

The DHCP server and Multicast server enable the set-top box to retrieve software 

upgrades when it needs them. You can also configure the DHCP server so that the settop 

box automatically upgrades to a specific software version, even if its current software 

is running normally. See Setting up a basic Multicast upgrade system on page 20 and 

Setting up automatic upgrade to minimum deployment index on page 35 for details of how 

to enable automatic upgrades. 

4.5 Using JMACX to upgrade software 

You can call the following JMACX function to instruct a set-top box to upgrade or reflash: 

ASTB.Upgrade 

See the JMACX API Specification for details. 


5 Configuring set-top boxes 

5.1 Configuration options 

Amino set-top box management offers various means of editing/reading configuration 

and controlling basic set-top box operation (e.g. initiate software upgrade or reboot): 

 

 

 

STBremoteconf - remote configuration tool that enables you to commands 

such as changing basic configuration settings or initiating software upgrade. 

Configuration pages - local configuration pages, using an Amino IR keyboard 

and television display to change configuration settings and simple commands 

such as rebooting and initiating software upgrades. This includes both the 

Management pages and the User Preferences pages. 

image components - set of files that a software upgrade image is built from; 

these include configuration files and graphics files (e.g. used in the display to 

show that the set-top box is loading new software). In the table below, changing 

image components means editing the contents of the image components 

directory before creating and signing a new upgrade image. 

Telnet/SSH/Dropbear - remote log-in tools enable you to interact with set-top 

box configuration remotely, using libconfig commands; note that these are 

usually disabled during manufacture to improve security, so they will need to be 

added to the software image installed on the set-top box if you want to use them. 

In addition to these means, the JMACX API offers a full set of functions for controlling a 

range of set-top box operational areas via Javascript embedded in web pages. See the 

JMACX documentation for more information. 

As detailed in the table below, the various configuration mechanisms are each suited to 

particular circumstances and contexts. For example, the Configuration pages offer local 

configuration, while STBremoteconf enables remote configuration; editing image 

component files before the software is upgraded enables the same configuration to be set 

on multiple set-top boxes, whereas changes via Telnet can only apply to a single set-top 

box. 

STBremote 

conf 

Config. 

pages 

image 

components 

Contexts 

before software loaded 

y 

after software loaded y y y 

remote y y y 

local 

y 

Telnet/SSH/ 

Dropbear + 

libconfig 


Configuring set-top boxes 

single STB y y y (not generally 

recommended: 

unless 

performing 

operation that 

can’t be done in 

another way - 

e.g. adding a 

client program) 

large deployment 

STBremote 

conf 

y (not 

recommended: 

settings only 

received if STB 

is powered) 

Config. 

pages 

image 

components 

test settings y y y 

y 

Telnet/SSH/ 

Dropbear + 

libconfig 

y 

Operations 

read configuration y y y y 

write configuration y y y y 

reboot y y 

upgrade software (see 

upgrading comparison 

table) 

y 

y 

reflash (see upgrading 

comparison table) 

y 

y 

Configuration areas 

general STB settings 

(e.g. language, volume 

ranges, keyboard 

settings) 

y y y 

channels list y y y 

network configuration y y y 

IR remote key functions 

y 

NOR flash settings y y y y 

browser configuration 

y 

graphics displayed 

during loading 

y 

include additional files 

(e.g. to enable Telnet) 

pre-OTP STBs 

only 

See also: 

Using STBremoteconf on page 56 

Using the HTML Configuration pages on page 69 

Using libconfig on page 75 (for information on using Telnet/SSH/Dropbear) 

y 



 

 

 

Customising a software upgrade image on page 50 (for information on how to 

configure a set-top box by editing the image components) 

Enabling remote log-in tools on page 52 (for information on how to enable 

Telnet/SSH/Dropbear) 

Set-top box configuration settings on page 79 (for a list of the main configuration 

settings and their allowed values) 

5.2 Configuration areas 

Configuration that persists through set-top box reboots is generally stored in configuration 

files that can be read or edited either directly or via the administration tools; the exception 

is the NOR flash, which can only be configured via the administration tools. 

settings file 

The settings file contains various set-top box settings, such as languages, volume 

ranges and keyboard configuration. 

netconf file 

The netconf file contains network configuration settings. In some cases, the set-top box 

reads these settings from the NOR flash instead of from this file. 

HOSTNAME file 

The HOSTNAME file contains just a single setting, that specifies the name of the set-top box. 

usersettings file 

The usersettings file contains settings that the set-top box user controls (i.e. through 

the Preferences pages). These override the values specified for the same settings in the 

settings file. 

NOR flash configuration 

The NOR flash contains settings required by the ROM. In some cases, this can include 

static network settings (these would otherwise be set in the netconf file). 

fkeys.conf file 

The fkeys.conf file sets the default actions associated with the buttons on the IR remote 

control. This file should not normally be edited directly (use JMACX functions instead). 

chnls.txt file 

The chnls.txt file contains a list of channel numbers and the media stream URL for the 

channel. 

trsdmns.txt file 

The trsdmns.txt file defines trusted domains and specfies whether Javascript and 

Macrovision are enabled for each. 

config.txt and opera.ini files 

Software releases will normally include the configuration file for the browser. For Fresco, 

this is called config.txt; for Opera it is opera.ini. In some builds, the set-top box reads 

some of its settings from these files. 



DHCPC settings 

The dynamic network and multicast upgrade settings retrieved from the DHCP server are 

stored in a file called dhcpcd-eth0.info. These values are only set if the set-top box uses 

dynamic network and Multicast upgrade settings; otherwise, the static values are defined 

in the NOR flash or the netconf file. The DHCPC values are read-only. 

5.3 Configuring a large deployment 

It is possible to configure software before deploying it to a large number of set-top boxes. 

The following steps describe recommendations on how this can be done for both the 

initial set-top box configuration and for future upgrade images. 

Prerequisites 

The configuration procedure outlined here assumes you already have a set-top box with 

a valid software image installed. This must include one of the remote log-in tools 

(Telnet/SSH/Dropbear). 

Steps 

1. Configure the software on the box (e.g. via the Management pages), and test 

the configuration to ensure the set-top box now operates as intended. 

2. When you are happy with the configuration, use the remote log-in tool to 

connect to the set-top box. 

3. Copy the contents of the files that have been modified. The configuration files 

are in /mnt/nv, and you will need to copy them to the 

/upgradeimage/imagecomponents directory on your PC. If you’re 

not sure which files have been modified, then copy all the contents of the 

directory. 

4. If you’ve added any new files that need to be included in the upgrade image, 

add them to the flashcontents file in the /upgradeimage/ 

directory. 

5. Create a new signed upgrade image (and add it to the directory specified in the 

Multicast server’s configuration file). Ensure that the new image has an 

incremented deployment index, if you are using deployment indexes to control 

software versions installed on the set-top box (not recommended for a trial 

system). 

6. Upgrade the software on a single set-top box with this new upgrade image (e.g. 

by using STBremoteconf). 

7. Check that the new software loads and works as expected. If changes need to 

be made, repeat steps 1 - 6 until the configuration is correct. 

8. Instruct all set-top boxes on your network to upgrade to this new image. (e.g. 

use deployment index mechanism to force automatic upgrade). 

See also: 

Configuring image components on page 50 

Editing the flashcontents file on page 51 

Setting up an advanced Multicast upgrade system on page 29 



5.4 Pairing an IR remote control with a set-top box 

You can program an Amino IR remote control so that it can only control a set-top box that 

is configured to respond to it. 

How it works 

The Amino IR remote control prefixes a number to each set-top box command. This 

number is set to 0 by default, but you can program it to be another number in the range 

1 - 15. 

All AmiNET set-top boxes respond to commands prefixed with 0 but you can configure 

them to respond to commands prefixed with another number as well. 

For example, a remote control is set to prefix commands with 3, and a set-top box is 

configured to respond to commands prefixed with 3. 

 

 

The remote control can only control set-top boxes that expect 3 as a command 

prefix. 

The set-top box will respond to commands prefixed with 3 and also continues to 

respond to commands prefixed with 0 (so that all set-top boxes respond to the 

default Amino remote control. 

To pair a remote control with a set-top box 

The following steps use the HTML Configuration pages to set the IR brand code. See the 

Configuration pages documentation for more information. This can also be set with the 

other configuration tools. See the Configuration pages and other separate documentation 

for details. 

On the Amino remote control: 

1. Hold down the STB and OK buttons until the STB button lights up permanently. 

2. Enter the number that you want to set as the prefix code for this remote control. 

This must be a three-digit number in the range 000 - 015. 

For example: 

008 

The remote control will now prefix all set-top box commands with this code. 

Note: To revert to the default code (i.e. to unpair the remote control and set-top box), 

repeat these steps and set the code to 000. 

To configure the set-top box: 

3. From the IR keyboard, press Alt-M and then enter the Management password 

(leaves by default), to access the Management pages. 

4. Open the Infra-Red Configuration page. 

5. Enter the same three-digit code as you programmed the remote control with. 

6. Save the changes (the default password here is snake). 

The remote control is now paired to the set-top box. 



5.5 Configuring how the set-top box responds to remote control keys 

The fkeys.conf file specifies how the set-top box responds to remote control keys. If 

you want to change the configuration, you are not recommended to edit this file directly. 

Instead, you should use the JMACX SetKeyFunction and SaveKeyFunction commands. 

See the JMACX API Specification for details of how to use these commands. 

5.6 Configuring the set-top box time zone 

Time zone support 

Set-top boxes support time zone handling through an NTP client. 

The time zone can be set in one of the following ways: 

Dynamic configuration, using the DHCP server 

Static configuration, in the netconf file 

In both cases, time zone strings can be in the following formats: 

 

 

 

Fully specified Posix 1003.1 time zone string (e.g. GMT0BST-1, M3.5.0/01, 

M10.5.0/02:00 

Unix-style definition in the format Region/City (e.g. Europe/London) 

Commonly used alias (e.g. GB-Eire) 

To set the time zone over DHCP 

If the set-top box retrieves its settings dynamically from the DHCP server, you can include 

the time zone in the settings that it retrieves. 

1. Open the DHCP server configuration file (dhcpd.conf) in a text editor. This file 

should be stored in the following location: 

/etc 

2. Add the following to the list of Amino vendor extensions (if it isn’t already there): 

option AMINO.timezone code 16=text; 

3. In the subnet declaration in the configuration file, add a line that specifies the 

time zone you want to set. 

Example: 

option AMINO.timezone “Europe/Stockholm”; 

The subnet declaration will now look something like the following: 

subnet 10.172.0.0 netmask 255.255.0.0 { 

option routers 10.172.0.1; 

option subnet-mask 255.255.0.0; 

option domain-name "aminocom.com"; 

option domain-name-servers 10.171.22.7,10.171.22.9; 

option AMINO.timezone “Europe/Stockholm”; 

pool { 

range 10.172.230.50 10.172.230.100; 

} 

} 



4. Save your changes and restart the DHCP server. 

Next time the set-top box sends a DHCP request (e.g. when it is rebooted), the time zone 

will be included in the information that the DHCP server sends. 

To set the time zone in the netconf file 

If you want to set the set-top box’s time zone statically, you can do it with the following 

setting in the netconf file: 

TIME_ZONE 

See for details of the options for editing network configuration settings. 

Note: If the set-top box receives a time zone value from the DHCP server, it uses this 

value in preference to the one in the netconf file. 

See also: 

 

 

 

for options for editing network configuration settings, including the time zone, 

see Configuration options on page 43 

for details of the main settings in the netconf file, see netconf file contents on 

page 85 

for more information on configuring set-top boxes to use static network settings, 

see Setting set-top boxes with static network and multicast upgrade settings on 

page 37 


6 Customising a software upgrade image 

You can customise software before it is loaded to a set-top box by configuring the image 

components used to create the software upgrade image. The sections in this chapter 

describe how to configure the image components and provide additional information on 

some of the important image components that you may need to use. 

6.1 Configuring image components 

Configuring image components enables you to customise the files used to create a 

software upgrade image. When the signupgradeimage script creates a new image, it 

includes the files that are listed in the flashcontents file and stored in the 

imagecomponents subdirectory of the software release. You can edit these files or add 

new ones in order to customise the software upgrade image to your requirements. 

For example, you can: 

edit configuration files before they are made available to set-top boxes 

add files needed to enable Telnet, SSH or Dropbear 

add/edit an upgrade.sh script file that the set-top box will execute when it 

installs the new software upgrade image 

replace graphics (displayed during the boot stages) with customised versions - 

e.g. the “splash.gif” graphic 

Note: All files in the imagecomponents directory must be listed in the flashcontents file; 

otherwise, the signupgradeimage script will fail. 

To configure image components 

The general procedure for editing image components is as follows: 

Note: In the following instructions, stands for the full path of the directory that 

contains your Amino software release. If you used example settings during installation, 

this is: /usr/local/amino/releases/ 

1. Open the file that you want to edit. The image component files are in the 

following location: 

/upgradeimage/imagecomponents 

Alternatively, you can add a new file to this location - such as a chnls.txt file 

you have copied from a pre-configured set-top box or an upgrade.sh file that 

contains libconfig commands to set NOR flash values. 

2. Edit the file, and save your changes. 

3. Open the flashcontents file, and ensure that the file you have added/edited 

is listed there. This file is in the following location: 

/upgradeimage 

The flashcontents file lists the files that will be included in a software upgrade 

image, and defines permissions for the file. 

4. Use the signupgradeimage script to create the software image, as usual. 


Customising a software upgrade image 

The new software upgrade image includes your new or edited files, and you can use it to 

upgrade your set-top boxes. 

See also: 

To create a signed upgrade image on page 27 

Upgrading set-top box software on page 41 

Configuration areas on page 45 for a list of the configuration that can be edited 

Release directory contents on page 20 for a list of the main files included in the 

imagecomponents directory 

Editing the flashcontents file on page 51 

6.2 Editing the flashcontents file 

You are only recommended to edit the flashcontents file if you are adding new files to 

the image components used to create a software image, and the files are not currently 

listed in the flashcontents file. It is supplied in the following location in a software 

release /upgradeimage 

flashcontents file 

The flashcontents file lists the files that can be included in a software upgrade image, 

and defines the permissions associated with these files when the software image is 

installed on the set-top box. 

flashcontents file contents 

The file contains a list of file names and the permission associated with them, in the 


Example: 

 

R AMINET.img 

Permissions. The permissions are as follows: 

Permission 

R 

W 

E 

File cannot be altered by the set-top box (e.g. kernel 

module, application). If files with R permission are deleted, 

the set-top box detects an error and reboots. 

File can be altered by the set-top box (e.g. configuration 

file). If these files are deleted from the set-top box, it will 

not cause an error. 

File is read-only and can be deleted after it is executed 

without affecting set-top box operation (e.g. upgrade.sh 

script). 

 

Executable image component files must be listed as either R or E, otherwise the 

signupgradeimage script will fail to create the software upgrade image. 

All files in the imagecomponents directory must be listed in the flashcontents 

file; otherwise, the signupgradeimage script will fail. If a file is listed in the 

flashcontents file but is not present in the imagecomponents directory, it will 

not affect the signupgradeimage script. 

Note: The E permission was introduced in version 0.12.0. 



File naming. Files names must not be longer than 12 characters. 

6.3 Creating an upgrade script 

upgrade.sh 

An upgrade script upgrade.sh contains commands that the set-top box executes when a 

new software upgrade image is installed. The script is created and installed on the settop 

box as part of a software image, and is only executed once, then deleted. 

To use an upgrade script 

The upgrade.sh script is not normally supplied as part of a software release, but you can 

create you own and add the commands you want the set-top box to execute. For example 

you can add libconfig commands to set static multicast values. Add the file to the image 

components used to create a software upgrade image; ensure that the script is listed in 

the flashcontents file, with its permission set to E. 

The script is executed automatically when this software image is installed on the set-top 

box. 

See also: 

Editing the flashcontents file on page 51 for details of how to add the files 

required to the imagecomponents 



Using libconfig on page 75 for details of libconfig commands you can add to the 

script 

6.4 Enabling remote log-in tools 

Telnet, SSH or Dropbear can be included in the software installed on a set-top box (the 

tool available depends on the platform), in order to enable remote log-in - e.g. to access 

configuration via libconfig commands. 

Remote log-in tool availability 

The remote log-in tools (Telnet/SSH/Dropbear) are not included as part of a standard 

software build or software image (version 0.13.0 onwards), for security reasons. If you 

want to enable these on the set-top box, you can do so by adding them to the image 

components used to create a new software upgrade image. 

For the following platforms, Telnet, SSH and Dropbear are all available: 

A103 

A110 

A110H 

A210 

A500 

For other platforms, only Telnet is available. 



To add Telnet/SSH/Dropbear to a software image 

To complete these steps, you will need a copy of the files required for the applications you 

want to enable. The files can then be added to the image components used to create a 

software upgrade image, and then installed on the set-top box by upgrading its software 

with this new image. 

See also: 

Configuring image components on page 50 for details of how to add the files 

required to the imagecomponents 



6.5 Customising graphics 

You can replace the graphic displayed during set-top box booting. For TFTP booting settop 

boxes, it is also possible to replace the graphic shown during software upgrades. 

Graphics used by set-top box 

The following default graphics are supplied with a software release: 

splash.gif This is the graphic shown on screen when the set-top box is booting. 

loading.gif This is the graphic shown on screen when the set-top box is upgrading via 

TFTP. Note that Multicast upgrades shows a graphic with just the word Loading... at this 

stage, which is part of IntactOS rather than part of the image components supplied with 

a software release. 

To replace default graphics with your own 

You can replace the default graphics with your own by replacing the GIF files in the image 

components used to build a new software upgrade image, then upgrading the software 

on a set-top box to use this new software image. 

Note: The loading graphic shown during Multicast upgrades (“Loading...”) is part of 

IntactOS, and can’t be customised. 

Each graphic must be a GIF with the same name as the file you are replacing. Other 

recommendations are: 

Animated GIFs are not supported (using an animated GIF will prevent the settop 

box from booting) 



Recommended size for GIFs is 640 x 400 pixels. If the GIF is larger than the 

screen dimensions, it will not be displayed. 

Transparent GIFs are not supported, but if you set the transparent colour to 0, 

the background colour will be undefined. 

Note that the graphic is always centred on the screen when it is displayed. 

See also: 

Configuring image components on page 50 for details of how to add the files 

required to the imagecomponents used to create a software upgrade image 



6.6 Changing set-top box passwords 

You can customise the passwords used to access to a set-top box by editing the shadow 

file supplied with a software release, and then generating a new software upgrade image 

that includes the updated shadow file. In some builds it is also possible to customise 

passwords once software is installed on a set-top box, using STBremoteconf. See the 

STBremoteconf documentation for more information on this. 

Passwords 

Access to management functionality is assigned to password-controlled users. 

The following table outlines the main password-controlled user levels and their defaults: 


root 

mngread 

mngwrite 




pages. 



Default 

password 

root2root 

leaves 

snake 

shadow file 

The shadow file defines the passwords for set-top box management users. Each line in 

the file specifies password information for a user, beginning with the user name. 

To change passwords in the shadow file 

Note: The following steps assume you have already set up a Multicast upgrade system 

and the software release is in the location specified in the set-up instructions. 

1. At a Linux command line, generate a new password hash with a command in 

the following format: 

perl -e ‘print crypt(“”, )’ 

( is the new password you want to set, and is any two 

alphabetical characters.) 

Example: 

perl -e ‘print crypt(“admin”, Ap)’ 

The command returns a hash for the password admin (for example 

ApC4fVgseQ63w). 



2. Open the shadow file. If you used the recommended settings when you set up 

the Multicast upgrade system, you will find the file in the following location: 

/usr/local/amino/releases//upgradeimage/imagecompone 

nts 

3. The shadow file has a line for each password that can be changed. Find the line 

for the password you want to change, and replace the current password hash 

with your new one. The password hash is the string between colons after the 

user name. 

For example, if you want to change the password for root, find the line that 

looks similar to the following: 

root:kUCfiRdXdzJSM:10596:0:99999:7:-1:-1:0 

Replace the password hash string, so that the line now looks like this: 

root:ApC4fVgseQ63w:10596:0:99999:7:-1:-1:0 

4. Repeat these steps for any other passwords you want to change, then save your 

changes. 

Once you have changed the passwords as required, you will need to create a new 

software upgrade image that includes the edited shadow file, and load it to your set-top 

boxes. 

See also: 




7 Using STBremoteconf 

7.1 STBremoteconf 

7.2 Before you start 

This section describes how to use the main STBremoteconf commands. For full 

information, see the separate STBremoteconf Administration Guide. 

STBremoteconf provides a mechanism for remotely configuring and controlling a local 

network of AmiNET set-top boxes. It can be run on the command line by sending 

commands individually to one or more set-top boxes, or commands can be collected into 

a script to save time. Commands are signed when they are created, so that the set-top 

box can check that the command has been sent by an authorised source. 

Example functions include rebooting, modifying output modes or updating software, as 

well as viewing information about the set-top box. 

The instructions in this section assume that STBremoteconf and other components are 

installed as part of a Multicast system. You will need the following: 

 

 

 

You will need to know the pass phrase for the configuration key that you will be 

using to sign commands. For the Amino engineering key this is stbrckey. 

To send commands via STBremoteconf, you will need to know the IP address 

of individual set-top boxes, or the address for a multicast group. Set-top boxes 

must be powered and connected to the network. 

For some of the commands (e.g. Multicasting commands), the DHCP server 

and Multicast server must be running, and appropriate upgrade images must be 

available. 

You will need to log in as root or have sudo rights to send commands via 

STBremoteconf. 

Note: STBremoteconf commands are time-stamped, and the set-top box will reject 

commands that are more than 30 seconds old. (This prevents encrypted commands 

being snooped and recorded, then re-sent to the set-top box at a later time.) For this 

reason, the set-top box and the PC that the STBremoteconf client is installed on must use 

the same date and time settings. 

7.3 Installing prerequisite Perl modules 

The STBremoteconf client has dependencies on various external Perl modules. You can 

either install these before you start installing STBremoteconf, or try using STBremoteconf 

and then install the Perl modules required only if errors are reported. 



To install Perl modules required by STBremoteconf: 

The following procedure assumes that you have the Perl CPAN module installed and 

have internet connectivity. You must be logged in as root or have sudo rights. 


sudo perl -MCPAN -e shell 

2. If the cpan> prompt isn’t displayed, then you are asked to manually 

configure it. Answer no to force an auto-configuration for CPAN. 

3. If you are prompted to install any modules, enter yes. 


install Bundle::CPAN 

If you are prompted to install dependencies, enter yes. 


install Date::Manip 



install MIME::Base64 



install File::Copy 



install IO::Socket::Multicast 



quit 

You now have all of the required Perl modules installed and your STBremoteconf client 

should now work. 

7.4 Sending commands with STBremoteconf 

The following steps outline an example command line interaction with STBremoteconf. 

STBremoteconf commands can alternatively be embedded in a script so that a group of 

commands can be sent together. 



To send a command at the command line: 

In the following steps, stands for the full path for the directory that contains 

your Amino software release. If you have used the example settings during set-up of the 

Multicast system, this is: /usr/local/amino/releases/. The steps 

assume you have not copied the STBremoteconf files to a directory in the system path 

(e.g. /usr/local/bin); if you have done this, you don’t need to navigate to the directory 

that the STBremoteconf file is stored in, and you don’t need to enter ./ at the start of each 

command. 

1. Set the STBKEY environment variable by entering a command in the following 

format: 

export STBKEY=/utils/keys/amino/STBrc-KEY.private 

2. Navigate to the directory that the STBremoteconf file is located in. 

For example: 

cd /utils 

3. Enter a command in the following format: 

./STBremoteconf [] 

For example, enter the following command to find out the software version on 

the set-top box with the IP address 123.4.5.67: 

./STBremoteconf -p 110,120 123.4.5.67 GETVERSION 

4. You are prompted to enter the pass phrase for the configuration key. For the 

Amino engineering configuration key this is stbrckey. 

If the command syntax and IP address(es) entered are valid, the client 

command is sent, and for non-multicast operations (i.e. commands sent to a 

single set-top box) a confirmation message is displayed which includes a status 

code returned by the set-top box. For multicast operations there is no return 

channel so confirmation is not sent. 

You can now enter further commands, as required. 

7.5 STBremoteconf command syntax 

STBremoteconf is operated by entering commands with the following syntax: 

./STBremoteconf [-p ] [-e ] [-t 

] [-P ] 

Argument 

Usage 

-p A comma-separated list of product codes that you 

want the command to apply to. For example: 

-p 110,120,110h 

-e Length of time to message expiry (in seconds). If you 

don’t include this argument, it defaults to 30 seconds. 

-t Network time-to-live value for the message. 

-P Port to send the command on. 

 

The host argument that specifies where the command 

will be sent or enables you to save the command for 

use later. See below for more information. 



Argument 

 

Usage 

The command that will be executed. 

Alternatively, you can enter the command ./STBremoteconf without any arguments to 

display help at the command line. 

Note: If you have copied the STBremoteconf to a directory in the system path (e.g. 

/usr/bin), you can enter the commands without the ./ at the start. 

argument 

The argument must be included in all commands. It can be set with one of the 

following types of value, depending on where you want the command to be sent: 

 

To send the command to all set-top boxes listening on a particular multicast group, enter 

the IP address of the group (for example, as defined in the DHCP server configuration or 

in the set-top box’s configuration).f no group has been configured on the set-top box, the 

default address 225.10.10.10 is used. 

Note that there is no return channel for status messages to be returned when 

multicasting, so no confirmation will be received, and many commands that request 

information such as version or status cannot be sent to a multicast group. 

 

To send the command to a single set-top box listening on the network, enter the IP 

address for the box. Alternatively, you can enter a valid name (which has a DNS entry). 

You should send commands to a single box in this way if you want to configure settings 

for a single box, or if the command returns information such as status or version. 

If the IP address is invalid, then the following error is returned: 

Couldn’t convert to internet address: Resource temporarily 

unavailable. 

If the IP address is valid, but the set-top box doesn’t respond to the command (e.g. the 

set-top box is not connected or the address has not been allocated by the DHCP server), 

then the following error is returned: 

SAVE 

Couldn’t connect: Connection refused 

To sign a command and save it for multicasting or unicasting later, replace with 

SAVE. This is useful as it allows you to collect multiple signed commands together to be 

transmitted altogether later, or to give a signed command to a third party that it is not 

appropriate to give keys to. 

STBremoteconf saves the signed command to a SAVEFILE.msg file in the current 

directory, and you can send it later using the SIGNEDCMD command option. 

argument 

The argument must be included in all commands, and specifies the 

operation you want to execute. Some options also require additional parameters. See the 

command options overview for a list of available options. 



7.6 STBremoteconf command options 

STBremoteconf commands enable you to configure or control a single or multiple set-top 

boxes and to request current configuration and status information from a single set-top 

box. In addition, you can view help and version information about STBremoteconf itself. 

Overview of command options 

You can add one of the following to the STBremoteconf command. Alternatively, enter the 

command without adding any options to view STBremoteconf version information and a 

full list of available commands at the command line. In the following table, commands 

marked in grey are not for general use (see the full command list for details of when they 

should be used), and you should only use these if you are fully aware of the implications 

on your set-top box. 

Command 

ACAPS_CS_IP_SET 

ACAPS_CS_PORT_SET 

ACAPS_ENABLE 

CHANGEPAGE 

CHANGE-PWORD 

CHANNEL 

DEFAULT_VOLUME 

DELETECUSTKEY 

EAS 

ETHERNET 

FETCHFILE 

 

GETVERSION 

HWINFO 

LOADKEY-CONF 

LOADKEY-CUSTOMER 

LOADKEY-OPERATOR 

LOCK 

LOGREAD 

MACADDRESS 

MCASTADDR 

OUTFMT 

Usage 

Development use only. 



Displays the page specified on the set-top box 

browser. (Set-top boxes running Fresco web 

browser only.) 

Changes set-top box user passwords. 

Changes the channel of one or more set-top boxes. 

Sets the default volume level on a set-top box. 

Deletes the customer key on a set-top box. 

Sends an EAS (Emergency Alert System) 

message. 

Sets the Ethernet speed. 

Retrieves a file from the set-top box and stores it on 

a local PC. 

Returns the current software version on the set-top 

box. 

Returns information about the set-top box 

hardware. 

Uploads a new public configuration key to the settop 

box. 

Uploads new public customer key to the set-top 

box. 

Uploads new operator key to the set-top box. 

Locks the NOR flash. 

Returns last few entries from syslog. 

Sets the set-top box’s MAC address. 

Changes the Multicast address that the set-top box 

listens on. 

Sets the output format of the set-top box. 



Command 

PING 

 

PROC 

REBOOT 

REFLASH 

RFMODE 

SAVEFILE 

 

SERIALID 

SIGNEDCMD 

STATS 

SYSLOG 

TVSYSTEM 

UPGRADEMCAST 

 

UPGRADMCAST_VER 

 

 

VOD 

Usage 

Instructs set-top box to send ICMP echo (ping) 

requests to a remote host. 

Sends specified proc entry to the set-top box. 

Reboots the set-top box. 

Wipes the NAND flash on the set-top box, then 

download new software. 

Enables/disables or resets the RF modulator on the 

set-top box (if there is one). 

Uploads a file from a local PC to the specified 

destination location on the set-top box file system. 

Sets the set-top box’s serial number. 

Sends a pre-prepared signed command to the settop 

box. 

Returns status information about the set-top box. 

Redirects the set-top box’s syslog to the specified 

new host. 

Sets the TV standard to be used. 

Instructs set-top box to upgrade to software 

available at Multicast group specified. 

Instructs set-top box boxes running different 

software versions to upgrade to the specified 

version. 

Executes video on demand operations. 

List of commands 

In the following list, commands marked Restricted are not for general use and may have 

irreversible effects. You should only use these if you are recommended to do so by Amino, 

and you are fully aware of the implications on your set-top box. 

ACAPS_CS_IP_SET, ACAP_CS_PORT_SET, ACAPS_ENABLE 

Restricted: Commands for development use only. 

CHANGEPAGE 

Usage: 

CHANGE-PWORD 

Usage: 

./STBremoteconf CHANGEPAGE 

Instructs software versions running the Fresco web browser to go to a specific URL. This 

command is only valid in software with this browser. Whatever the user is viewing at the 

time will be interrupted, including video. 

Example: 

./STBremoteconf 123.4.5.67 CHANGEPAGE 

“http://www.aminocom.com” 

./STBremoteconf CHANGE-PWORD 



Changes the specified user password on the set-top box. Note that this option only works 

with set-top box software versions that have been set up to allow it; this is not enabled in 

standard releases. 

You are prompted to enter the new password twice (to catch any typing error, as the 

password you type is not echoed to the display). An error is returned if the user name 

doesn’t exist or password-changing is not supported in the set-top box. 

The following users are recognised: 


root 

mngread 

mngwrite 




pages. 



Default 

password 

root2root 

leaves 

snake 

Example: 

./STBremoteconf 123.4.5.67 CHANGE-PWORD mngread 

Example response interaction: 

Enter new password for user 'mngread’: 

Retype new password for user 'mngread’: 

Unicasting... 

Passphrase (for key ): 

Signed image written to '/tmp/TMPFILE.signed' 

Got back: OK 

CHANNEL 

Usage: 

./STBremoteconf CHANNEL 

Changes the current channel of a single or multiple set-top boxes. 

Example: 

./STBremoteconf 123.4.5.67 CHANNEL 123 

DEFAULT_VOLUME 

Restricted: Not for use with OTP set-top boxes. 

DELETECUSTKEY 

Restricted: Internal use only. 

EAS 

Usage: 

./STBremoteconf EAS 

Sends an EAS (Emergency Alert System) message. It is the responsibility of the 

middleware running on the set-top box to act on this message and perform any required 

operations. 



Example: 

./STBremoteconf 123.4.5.67 EAS “This is a 

message” 

ETHERNET 


FETCHFILE 


GETVERSION 

Usage: 

./STBremoteconf GETVERSION 

Returns the software version of a box. This command is only useful via unicast. 

Example: 

./STBremoteconf 123.4.5.67 GETVERSION 

Example response: 

Got back: 0.12.1-aminet-frescoj27-1 

HWINFO 

Usage: 

./STBremoteconf HWINFO 

Returns the product , board revision and ROM type of the set-top boxes. 

Example: 

./STBremoteconf 123.4.5.67 HWINFO 

Example response: 

aminet110 (revision 2) ROM type: 0xc222-SS-S4 

LOADKEY-CONF, LOADKEY-CUSTOMER, LOADKEY-OPERATOR 


LOCK 


LOGREAD 

Usage: 

./STBremoteconf LOGREAD 

Returns the last few entries from syslog. 

Example: 

./STBremoteconf LOGREAD 

MACADRESS 




MCASTADDR 


OUTFMT 

PING 

PROC 

REBOOT 

REFLASH 


Usage: 

./STBremoteconf PING 

 

Instructs the set-top box to send a number of ICMP echo (ping) requests to a remote host. 

In a network with multiple set-top boxes, this command can be multicast and then the 

network can be monitored for replies, to determine which set-top boxes received the 

message. 

specifies the number of echo requests to send. 

specifies how long to wait before sending the first request (in seconds). 

If you specify a backoff parameter of zero, the set-top box sends the ICMP echo requests 

as soon as it receives the message. If backoff is greater than zero, the set-top box waits 

a random time interval between zero and backoff seconds before sending the first ICMP 

echo; followed by one second between each request. 

Example: 

Usage: 

./STBremoteconf 123.4.5.67 PING 139.255.1.1 10 0 

./STBremoteconf PROC 

Queries the set-top box for the value of the specified proc entry - e.g. to query memory 

usage. 

Example: 

Usage: 

./STBremoteconf 123.4.5.67 PROC meminfo 

./STBremoteconf REBOOT 

Triggers a reboot of the set-top box, which is most useful when restarting the device after 

making configuration changes. The command returns a status code indicating whether 

the command was accepted. 

Note: The set-top box automatically reboots after some commands, such as a 

MCAST_UPGRADE. 

Example: 

Usage: 

./STBremoteconf 123.4.5.67 REBOOT 

./STBremoteconf REFLASH 



Requests an update of the software loaded on a TFTP-booting set-top box. The update 

is done by formatting the flash memory and reloading it from the appropriate TFTP boot 

server. Before using this command, ensure that valid software exists in TFTP boot, and 

that no attempt is made to interact with the device (disconnect mains power etc.) during 

the update process. This command wipes any persistent setting stored in the NAND flash 

(/mnt/nv). It should not be used to trigger a multicast upgrade, instead see the 

UPGRADEMCAST command. 

Example: 

./STBremoteconf 123.4.5.67 REFLASH 

RFMODE 

Usage: 

./STBremoteconf RFMODE 

Enables or disables the RF modulator (if present) and/or changes the current RF channel. 

The following options are available: 

Example (sets the RF channel to 38 and enables the RF modulator): 

./STBremoteconf 123.4.5.67 RFMODE 38 ENABLE 

SAVEFILE 


SERIALID 

SIGNEDCMD 

Usage: 

STATS 


./STBremoteconf SIGNEDCMD 

Sends a pre-prepared signed command out. This requires a file generated by 

STBremoteconf using the SAVE command and allows the user to send out a command 

without needing a password or a private key, so it can be useful to allow untrusted parties 

to submit commands. 

Example: 

Usage: 

./STBremoteconf 123.4.5.67 SIGNEDCMD SAVEFILE.msg 

./STBremoteconf STATS 

Returns a set of status values for the set-top box. 

Example: 

./STBremoteconf 123.4.5.67 STATS 



Example of some of the types of values returned: 

MACADDRESS: xx:xx:xx:xx:xx:xx 

URL: 

SKIPS: (last total_in_movie total) t, n, n 

SERRORS (last total_in_movie, total) t, n, n 

TIME (timestamp_movie_start, time) t, t 

AUDBUF: 

VIDBUF: 

ERFLOW_TIMESTAMP 

VIDPTS 

EthInfo 

MemInfo 

SYSLOG 

Usage: 

./STBremoteconf SYSLOG 

Redirects the set-top box's syslog to the new host you specify. Syslog handles logging of 

various event and debug messages on the set-top box. You can redirect the output to an 

alternative host, such as a local PC. (Please refer to syslog documentation available online 

for more information about syslog set-up.) 

Example: 

./STBremoteconf SYSLOG 123.4.5.67 

TVSYSTEM 

Usage: 

./STBremoteconf TVSYSTEM 

Changes the TV standard to one of a predefined set of values. 

The following options are available: 

PAL-I 

PAL-M 

PAL-N 

PAL-G 

PAL-B 

PAL-H 

NTSC-J 

NTSC-M 

SD 

108i59 

108i50 

720p59 

720p50 

576p50 

480p59 



Example (along with text returned which indicates a valid response): 

./STBremoteconf TVSYSTEM PAL-I 

UPGRADEMCAST 

Usage: 

Got back: OK 

./STBremoteconf UPGRADEMCAST 

Instructs one or more set-top boxes to upgrade to the software offered on a particular 

multicast group. This command is only valid for software versions supporting multicast 

upgrade (it is not valid for TFTP booting software versions). A software version must be 

multicasting on the specified group when the command is sent. Once the upgrade is 

complete, the set-top box will automatically reboot into the new version; you can use the 

GETVERSION command to check that the new software version is in use. 

This command retains various persistent settings files held in the flash, such as settings 

and netconf. 

Example: 

UPGRADEMCAST_VER 

Usage: 

VOD 

./STBremoteconf 123.4.5.67 UPGRADEMCAST 239.255.1.1 12345 

./STBremoteconf UPGRADEMCAST_VER 

 

Instructs set-top boxes to upgrade to a specified software version. It is only valid for 

software versions supporting multicast upgrade (it is not valid for TFTP booting software 

versions). The command takes three parameters: a numeric multicast address, a port 

number and the full software version string. A software version must be multicasting on 

this group when the command is sent. The set-top box compares its current software 

version string with the upgrade version string specified, and only upgrades if the strings 

are different. Once the upgrade is complete, the set-top box will automatically reboot into 

the new version. 

This command retains various persistent settings files held in the flash, such as settings 

and netconf. 

Example: 

Usage: 

./STBremoteconf 123.4.5.67 UPGRADEMCAST_VER 2 255.50.50.51 

11111 0.12.1-aminet110-frescoj27-1 

./STBremoteconf VOD 

Allows remote video on demand operations to be executed. For example, a PAUSE 

operation may be required before you can send another command. 



The following video on demand operations are supported: 

Example: 

PLAY 

PAUSE 

STOP 

FF 

RW 

./STBremoteconf 123.4.5.67 VOD PAUSE 

Note: VOD PLAY should only be used to resume from a PAUSE state. To initiate a new video 

on demand session remotely, use the CHANGEPAGE command to point to the required video 

on demand resource. 


8 Using the HTML Configuration pages 

8.1 Configuration pages 

This section provides an overview of functionality. For full information, see the separate 

Set-Top Box Configuration Pages Administration Guide. 

Set-top boxes with browsers include HTML configuration pages, displayed on the 

television screen, that enable local access and editing of configuration areas. The pages 

are divided into an administrator area (Management pages) and user area (Preferences 

pages). 

Preferences pages 

The set-top box Preferences pages are a simple interface that enables users to change 

basic set-top box configuration areas such as language, subtitle and keyboard set-up. 

The pages are accessed locally via an Amino IR remote control (or keyboard). The 

Preferences pages are designed for use by end-users. 


The set-top box Management pages are a simple interface that enables administrators to 

change set-top box configuration areas such as networking, channel list and browser setup, 

as well as initiate basic operations such as rebooting and updating software. In 

addition, read-only access is available to areas such as version and set-top box identity 

settings. The pages are password-protected and accessed locally via an Amino IR 

keyboard (limited functionality is also supported via the remote control). Management 

pages allow access to advanced configuration functions and are designed for use by 

administrators rather than end-users. 

8.2 Getting started 

Before you start 

The instructions in this section assume that the set-top box you want to communicate with 

is powered and connected to the network. 

To use the Management pages, you will need the following: 

An Amino IR keyboard (optionally also a remote control) 

You will need to know the password for the mngread and mngwrite user names 

on the set-top box. These are leaves and snake respectively if you haven’t 

changed the defaults. 

If you are using a production set-top box and want to change identity settings, 

you will also need to know the password for the identity user. If the default 

hasn’t been changed, this is tiger. Note that these settings and functionality 

are locked during manufacture, and access is read-only in most set-top boxes. 

To use the Preferences pages, you will need the following: 

An Amino remote control or IR keyboard 


Using the HTML Configuration pages 

Using the keyboard and remote control with the configuration pages 

Although the actual functionality enabled is slightly different, the general ways of 

communicating with the Management and Preferences pages are similar, and the table 

below shows some of the remote control buttons and keyboard keys that enable 

important functionality: 

In general, the Management pages require the use of a keyboard; the Preferences pages 

are designed for use with just the remote control. 

8.3 Using the Management pages 

Functionality Remote control Keyboard 

Move around the items on the page. arrow buttons arrow keys 

Select an option / press a button on OK button Enter key 

the page. 

Delete text you have entered. LAST CH button Back Space key 

Close Management/Preferences Home button Escape key 

pages 

Display Preferences pages MENU button Alt-P key 

combination 

Display Management pages 

Alt-M combination 

Getting started 

The Management pages are divided into separate areas according to configuration and 

control functionalities. Some areas allow you to view and edit configuration, some only 

allow you to view configuration and others allow you to perform software upgrades and 

reboot the set-top box. 

When you first access the pages, a menu that lists the available areas is displayed. The 

settings available depend on the software build, but the menu can include the following 

items: 

Area 

Browser Setup 

Channels 

Proxy Setup 

Trusted Domains 

Video Setup 

Network Configuration 

Hardware Information 

Software Version 

Update Software 

Identity 

Allows you to: 

View and edit browser configuration and 

change keyboard layout. 

View and edit the channel URLs. 

View and edit HTTP and HTTPs proxies. 

View and edit settings for trusted domains. 

View and edit video display and timeout 

settings. 

View and edit static address information; also 

view DHCP lease details. 

View set-top box hardware details. 

View set-top box software version. 

Initiate a software upgrade (multicast) or 

reflash. 

View set-top box identity information. In 

production boxes, it is also possible to edit 

these settings; the settings are locked during 

manufacture. 



Area 

See also: 

For more detail on these settings on these pages, see the Set-Top Box 

Configuration Pages Administrator Guide. 

Navigation - using the keyboard 

Once the Management pages are displayed, you can use either the keyboard or remote 

control to navigate around the pages and change settings. However, the Management 

pages require the use of a keyboard to display them and enter text, so the usage 

instructions here all specify what keys to press on the keyboard. It is also possible to use 

equivalent remote control options in many cases. 

Use the arrow keys to move up or down the menu page, then press the Enter 

key to select the page you want to view. 

Once the page you want is displayed, you can use the arrow keys to move 

around it, make changes if required and then move to the Back to Main Menu 

button and press Enter to return to the menu. 

Viewing and editing configuration 


Infra-Red Configuration Pair the set-top box with an IR remote control. . 

TVI Configuration Set the protocol to use for controlling the 

television. 

Reboot 

Reboot the set-top box. 

To view configuration 

1. Open the page for the configuration area you want to view. The current 

configuration settings are displayed. 

2. To return to the menu page, move to the Back to Main Menu button (usually at 

the bottom of the page) and press Enter. 

To change configuration settings 

Note that not all configuration settings can be changed. If a page doesn’t have a Save 

Changes button, then the settings are all read-only. 

1. Open the page for the configuration area you want to view. 

2. Use the arrow keys to move to the setting you want to change. As you move 

around the page, the current setting that you have currently selected is 

highlighted. 

3. Make the changes you require: 

To change a text field, use the Back Space key to delete the current value, then 

type the new value. 

To change a check box, press the Enter key to check or uncheck the box. 

To select values from a drop-down list, press the Enter key to display the 

choices, use the up and down arrow keys to move to the value want, then press 

Enter again to select the new value. 

4. When you are happy with your changes, move to the Password field and type 

the password. If you have not changed the default password, this is snake. Next, 

move to the Save Changes button, and press Enter. There will be a short delay 

while the changes are written to the set-top box’s configuration (the set-top 



box’s LED will flash during this time). Alternatively, you can use the Reset button 

to undo your changes to the page and return to the values set when you 

displayed the page. 

5. If you saved your changes, a new page confirms the changes. If you didn’t make 

any changes, the page doesn’t change. From both pages, you can return to the 

main menu by navigating to the Back to Main Menu button and pressing Enter. 

For many configuration settings, you will now need to reboot the set-top box for the 

changes to take effect. 

Rebooting the set-top box 

To reboot the set-top box via the Management pages 

1. On the main menu, move to the Reboot option, then press the Enter button. 

2. The set-top box reboots immediately. 

Updating set-top box software 

To initiate a software upgrade via the Management pages 

Before you initiate a software upgrade, you will need to ensure that new software is 

available. In most cases, this means that the Multicast system must be set up, with the 

Multicast server transmitting appropriate new software images. 

1. On the main menu, move to the Update software option, the press the Enter 

button. The Update software page is displayed. 

2. You can either upgrade just the main software image or you can reflash the settop 

box (i.e. delete the contents of the NAND flash and reload both a new 

bootstrap and a new software upgrade image). When the set-top box performs 

a software upgrade, it tests the new software and can revert to the old software 

if there is a problem. When the box reflashes, it wipes its current software before 

installing new software so it may not be able to revert to the old software if there 

is a problem. 

To upgrade the main set-top box image: 

In the Address field, enter the IP address for the multicast image (this is the IP 

address specified in the Multicast server configuration). 

In the Port field, enter the port for accessing the multicast image (again, as 

specified in the Multicast server configuration). 

In the Password field, enter the password. If you haven’t changed the default, 

this is snake. 

Move to the CLICK HERE button and press Enter to start the upgrade. 

Note: Because of memory limitations, the AmiNET120 does not use the 

Address and Port values you enter; instead it uses values retrieved from the 

DHCP server (or set in configuration, if static DHCP values are used). You still 

need to specify dummy address and port values, though - otherwise the 

command forces a reflash instead of a software upgrade (see below). 

 

 

To reflash the set-top box: 

Leave the Address and Port fields blank. 

In the Password field, enter the password. If you haven’t changed the default, 

this is snake. 



3. Move to the CLICK HERE button and press Enter to start the upgrade or 

reflash. 

Closing the Management pages 

To close the Management pages 

When you have finished, press the Escape key to close the Management pages 

and return to the main television display. 

8.4 Using the Preferences pages 

Getting started 

The Preferences pages are divided into separate areas according to configuration and 

control functionalities you can view and edit. 

When you first access the pages, a menu that lists the available areas is displayed. The 

actual settings available depend on the software build, but the menu can include the 

following items: 

Area 

Keyboard settings 

TV system and audio 

settings 

Subtitle settings 

Exit preferences 


View and edit keyboard configuration. 

View and edit TV, video and audio language setup. 

View and edit subtitle configuration. 

Close the preferences pages 

See also: 

For more detail on these settings on these pages, see the Set-Top Box 

Configuration Pages Administrator Guide. 

Navigation - using the remote control 

Once the Preferences pages are open, you can use either the keyboard or remote control 

to navigate around the pages and change settings. The Preferences pages are designed 

to be able to be used with just the Amino remote control, so the usage instructions all 

specify what buttons to press on this remote control. It is also possible to use equivalent 

keyboard options. 

Use the arrow buttons to move up or down the menu page, then press the OK 

button to select the page you want to view. 

Once the page you want is displayed, you can use the arrow buttons to move 

around it, make changes if required and then move to the Back to Main Menu 

button and press OK to return to the menu. 

Viewing and editing configuration 

To view configuration 

1. Open the page for the configuration area you want to view. The current 

configuration settings are displayed. 



2. To return to the menu page, move to the Back to Main Menu button and press 

OK. 

To change configuration settings 

1. Open the page for the configuration area you want to view. 

2. Use the arrow buttons to move to the setting you want to change. As you move 

around the page, the current setting that you have currently selected is 

highlighted. 

3. Make the changes you require: 

To change a text field, use the LAST CH button to delete the current value, then 

type the new value. 

To change a check box, press the OK button to check or uncheck the box. 

To select values from a drop-down list, press the OK button to display the 

choices, use the up and down arrow buttons to move to the value want, then 

press OK again to select the new value. 

4. When you are happy with your changes, move to the Save Changes button, and 

press OK. There will be a short delay while the changes are written to the settop 

box’s configuration (the set-top box’s LED will flash during this time). 

Alternatively, you can use the Reset button to undo your changes to the page 

and return to the values set when you displayed the page. 

5. If you saved your changes, a new page confirms the changes. If you didn’t make 

any changes, the page doesn’t change. From both pages, you can return to the 

main menu by moving to the Back to Main Menu button and pressing OK. 

Closing the Preferences pages 

To close the Preferences pages 

When you have finished, navigate to the main menu, then move to the Exit 

preferences option and press OK. Alternatively, press the Home button on the 

remote control. 


9 Using libconfig 

9.1 Before you start 

libconfig enables you to interact with set-top box configuration. In most cases, you can 

retrieve or set any of the available configuration settings. See HTML Configuration pages 

- settings used on page 92 for a list of the main settings; also see the separate Set-Top 

Box Management Configuration Guide for a more detailed list of settings. 

The instructions in this documentation assume that the set-top boxes you want to 

communicate with are powered and connected to the network. You will need the following: 

 

 

To send commands via libconfig, you will need to know the IP address of 

individual set-top boxes that you want to communicate with. 

You will need to know the password for the root user on the set-top box. This 

is root2root if you haven’t changed the default. 

The set-top box will need to be running software with Telnet enabled if you want 

to follow the instructions here on using Telnet to send libconfig commands. Note 

that both Telnet and SSH are normally disabled for roll-out, so you will probably 

need to enable it by adding it to the software image on the set-top box. 

See also: 

9.2 libconfig command syntax 

 

 

For details of how to enable Telnet or SSH, see Enabling remote log-in tools on 

page 52 

For details of how to add commands to an upgrade script, see Creating an 

upgrade script on page 52 

The libconfig commands for setting and querying set-top box configuration have similar 

syntax: 

libconfig-set 

libconfig-get 

Argument 

 

 

Usage 

Key formed from a prefix that relates to the 

configuration area and the name of the setting. For 

example, for the DEFAULT_VOLUME setting in the 

settings file, the key is 

SETTINGS.DEFAULT_VOLUME. 

Specifies the new value for the configuration 

setting. Only required for the libconfig-set 

command. If this value contains any spaces, it must 

be enclosed in quotation marks (for example: 

“file name.txt”); otherwise, the quotation marks 

are not required. 



Example (libconfig-get): 

libconfig-get SETTINGS.DEFAULT_VOLUME 

Example (libconfig-set): 

libconfig-set SETTINGS.DEFAULT_VOLUME 80 

9.3 Sending commands with libconfig 

Libconfig commands can be sent in the following ways: 

Telnet to the set-top box and enter commands on the command line 

Embed commands in a script (particularly useful if you need to use set values 

in multiple set-top boxes - for example, to set static DHCP settings) 

Using the JMACX API - STB.SetConfig/ASTB.GetConfig functions in the 

JMACX API call libconfig functions ( see JMACX documentation for more 

information) 

The following steps outline how to send libconfig commands via Telnet (note that this is 

usually only enabled for production set-top boxes, and is disabled for roll-out, for security 

reasons). 

To send a command via Telnet 

1. From a console window, Telnet to the set-top box. 

For example, if your set-top box’s IP address is 123.4.5.67, enter the following 

command: 

telnet 123.4.5.67 

2. You are prompted to enter log-in details. The user name to log in as is root; the 

password is root2root (unless you have changed the password for the root 

user). 

3. Enter libconfig commands, as required. 

Example command (get-config): 

libconfig-get SETTINGS.DELAY_FACTOR 

This command returns the DELAY_FACTOR setting from the SETTINGS file on the 

set-top box, and displays it in the console; if you request a setting for which no 

value is set, then no return value is displayed. 

Example command (set-config): 

libconfig-set SETTINGS.DELAY_FACTOR 5 

The new value (5) is confirmed in the console, followed by a note of the value 

you replaced: 

Setting 'SETTINGS.DELAY_FACTOR'='5' 

SETTINGS.DELAY_FACTOR currently '4' 

4. When you have finished, exit Telnet by typing the following command: 

quit 

9.4 libconfig configuration areas 

libconfig can be used to access various areas of configuration, using a unique prefix for 

each area. In most cases, libconfig can read or write settings, but there are a few 

exceptions for which libconfig access is read-only. 



NOR flash settings 

“Settings” settings 

Hostname setting 

Netconf settings 

Usersettings settings 

NOR flash configuration 

The NOR flash contains settings required by the ROM. In some cases, this can include 

static network settings (these would otherwise be set in the netconf file). 

libconfig prefix 

To create the key for use in libconfig commands, prefix the setting name with NORFLASH. 

For example, for the DI setting, the libconfig key is NORFLASH.DI. 

settings file 

The settings file contains various set-top box settings, such as languages, volume 

ranges and keyboard configuration. 


To create the key for use in libconfig commands, prefix the setting name with SETTINGS. 

For example, to access the RTSPSERVER setting, the libconfig key is 

SETTINGS.RTSPSERVER. 

hostname file 

The hostname file contains just a single setting, that specifies the name of the set-top box. 


To create the key for use in libconfig commands, prefix the setting name with HOSTNAME. 

For the HOSTNAME setting, the libconfig key is HOSTNAME.HOSTNAME. 

netconf file 

The netconf file contains network configuration settings. In some cases, the set-top box 

reads these settings from the NOR flash instead of from this file. 


To create the key for use in libconfig commands, prefix the setting name with NETCONF. 

For example, to access the DHCPTIMEOUT setting, the libconfig key is 

NETCONF.DHCPTIMEOUT. 

usersettings file 

The usersettings file contains settings that the set-top box user controls (i.e. through 

the Preferences pages). These override the values specified for the same settings in the 

settings file. 



dhcpc settings 


To create the key for use in libconfig commands, prefix the setting name with 

USERSETTINGS. For example, for the PREFERRED_LANG setting, the libconfig key is 

USERSETTINGS.PREFERRED_LANG. 

DHCPC settings 

The dynamic network and multicast upgrade settings retrieved from the DHCP server are 

stored in a file called dhcpcd-eth0.info. These values are only set if the set-top box uses 

dynamic network and Multicast upgrade settings; otherwise, the static values are defined 

in the NOR flash or the netconf file. The DHCPC values are read-only. 


To create the key for use in libconfig commands, prefix the setting name with DHCPC. For 

example, for the DNS setting, the libconfig key is DHCPC.DNS. 

See also: 

For a list of settings available in each of these configuration areas, see Set-top 

box configuration settings on page 79 


10Set-top box configuration settings 

The following sections list the main settings needed to customise set-top boxes, including 

the settings that can be HTML Configuration pages (see HTML Configuration pages - 

settings used on page 92 for a list of the configuration settings that can be accessed via 

the Configuration pages in Fresco and Opera builds). 

See also: 

10.1settings file contents 

 

See the Set-Top Box Management Configuration Guide for a complete list of 

the settings available, and for more information on how to access and edit them. 

The following table describes the settings available in the settings file. Note that whether 

these values are used depends on the software and hardware build. 

Default values listed here are used if no value is supplied. Default values are often buildspecific 

though, so may not be as listed here. 

The examples show how to enter the setting if you are editing the settings file directly (note 

that the values are all enclosed in quotation marks). See the appropriate documentation for 

information on how to enter values using other means (e.g. JMACX, libconfig via Telnet). 

Setting Allowed values Description 

BROWSER_HELPPAGE URL 

BROWSER_HOMEPAGE URL 

Sets the help page. This is the URL for the page 

that the browser goes to when the Help key is 

pressed. 

Example: 

BROWSER_HELPPAGE=”http://www.aminocom.co 

m/help” 

Sets the home page. This is the URL for the page 

that the browser goes to when the Home key is 

pressed and when the set-top box has booted 

successfully. 

Default: “about:/start.htm” 

BROWSER_ENABLECO 

OKIES 

Y enable 

N disable 

Example: 

BROWSER_HOMEPAGE=”http://www.aminocom.co 

m” 

Enables or disables cookies. 

Note: This setting can’t be accessed via 

libconfig. 

Default: Y 

Example: BROWSER_ENABLECOOKIES=”N” 


Set-top box configuration settings 


BROWSER_MARGIN_L 

EFT 

BROWSER_MARGIN_R 

IGHT 

BROWSER_MARGIN_T 

OP 

BROWSER_MARGIN_B 

OTTOM 

1 - 100 Sets the browser margins as a percentage of the 

graphics plane size. 

Note: You are not recommended to set these 

values to 100, as this would set the margins to 

cover the entire graphics plane. 

Example: BROWSER_MARGIN_LEFT=”20” 

RTSP_SCALE 1 - 6 The default fast forward and rewind multiplier. 

Default: 6 

FULLSCREEN 

IME 

SUBTITLES 

Y full screen 

N not full screen 

el Greek 

ge German 

ru Russian 

sl Slovenian 

”” no IME 

Y subtitles on 

N subtitles on 

Example: RTSP_SCALE=”2” 

Enables or disables full screen mode. 

In full screen mode, the graphics plane is set to 

100% of the video plane. 

In non-full-screen mode, the graphics plane is set 

to 90% (safe area), so that the entire plane will be 

visible on all televisions. 

Default: N 

Example: FULLSCREEN=”Y” 

Specifies which built-in IME (input method editor) 

to use. 

By default no IME is enabled. 

Default: ““ 

Example: IME=”ru” 

Enables or disables subtitle display. 

Available in subtitle builds only. 

Default: N 

SUBTITLES_OPTION ““ standard 

H subtitles on for 

hearing-impaired 

(dependant on 

build) 

Example: SUBTITLES=”Y” 

Sets how subtitles are displayed, if enabled (with 

SUBTITLES setting). 


Example: SUBTITLES_OPTION=”H” 




IR_BRAND 0 - 15 Sets the IR brand code, used to link the set-top 

box to certain Amino remote controls. 

Set 0 for the set-top box to respond to all remote 

controls. Set other values for the set-top box to 

respond only to remote controls configured with 

the same number. 

See the Set-Top Box Management Operations 

Guide for details of how to pair a remote control 

with a set-top box. 


IGMP_START_TIMEO 

UT 

Example: IR_BRAND=”10” 

0 - 30 Sets the number of seconds before a no-video 

event is raised for multicast video. 

Set 0 for never timeout. 

Default: 30 

IGMP_END_TIMEOUT 0 - 30 

Example: IGMP_START_TIMEOUT=”15” 

Sets the number of seconds before an end-ofmedia 

event is raised for multicast video. 


Default: 30 

RTSP_START_TIMEO 

UT 

Example: IGMP_END_TIMEOUT=”15” 

0 - 30 Sets the number of seconds before a no-video 

event is raised for RTSP video. 


Default: 4 

RTSP_END_TIMEOUT 0 - 30 

Example: RTSP_START_TIMEOUT=”15” 

Sets the number of seconds before an end-ofmedia 

event is raised for RTSP video. 


RTSP_SERVER 

ncube 

mediabase 

oracle 

concurrent 

bitband 

infovalue 

seachange 

eona 

smartvision 

Default: 6 

Example: RTSP_END_TIMEOUT=”15” 

Sets the default video server type. 

Default: ncube 

Example: RTSP_SERVER=”mediabase” 




HTTP_PROXY_IGNOR 

E 

HTTPS_PROXY 

List of sites to ignore if HTTP proxy is enabled. 

Opera browser only. 


Example: 

HTTP_PROXY_IGNORE=”http://www.bbc.co.uk” 

Sets the proxy server for HTTPS transactions. 

Enter the IP address and port in the format 

host:port; for example: 123.4.5.67:1234 


HTTP_PROXY 

USE_PROXY 

DISPLAY_MODE 

Y enable 

N disable 

panscan 4:3 pan 

and scan 

letterbox 4:3 

letterbox 

widescreen 16:9 

widescreen 

Example: HTTPS_PROXY=”123.4.5.67:1234” 

Sets the proxy server for HTTP transactions. 

Enter the IP address and port in the format 

host:port; for example: 123.4.5.67:1234 


Example: HTTP_PROXY=”123.4.5.67:1234” 

Enables or disables the use of HTTP, HTTPs and 

FTP proxy servers. 

Opera browser only. For Fresco and Escape, this 

is set in the browser’s settings file. 

Example: USE_PROXY=”Y” 

Configures how the video is formatted for the TV. 

Select panscan for televisions that can’t do 

automatic aspect ratio switching, and you want 

the video image to fill the full 4:3 screen. In this 

mode, 4:3 content fits the screen correctly, and 

any 16:9 video content is cropped on the left and 

right sides. 

Select letterbox for televisions that can’t do 

automatic aspect ratio switching, and you want to 

display the full 16:9 content. In this mode, 4:3 

content fits the screen correctly, and any 16:9 

content is displayed in full, with black bars above 

and below it. 

Select widescreen for televisions that can do 

automatic ratio switching. In this mode, the 

television switches between 4:3 and 16:9 

depending on the video content, and full content 

is displayed for both. 

Default: panscan 

Example: DISPLAY_MODE=”widescreen” 




AUTO_SD_SWITCH 

Y automatically 

switch to NTSC-M 

output 

N maintain aspect 

ratio by 

pillarboxing the 

image within the 

HDTV video 

signal (720 or 

1080) 

Sets how 4:3 SDTV video channels are handled 

when the set-top box is set to an HDTV output 

type (i.e. with NOR flash TVSYSTEM). 

For 4:3 HD televisions, if TVSYSTEM is set to 720 or 

1080 and AUTO_SD_SWITCH is set to N, the 4:3 

SDTV video image is displayed in the centre of 

the screen, with black borders all around it. Set 

AUTO_SD_SWITCH to Y to get a 4:3 image that fills 

the whole screen on these televisions. 

Default: N 

SUBTITLES_PREF_L 

ANG 

SUBTITLES_SECOND 

_LANG 

ISO 639-2 

language code 

ISO 639-2 

language code 

PREFERRED_LANG ISO 639-2 

language code 

SECONDARY_LANG ISO 639-2 

language code 

Example: AUTO_SD_SWITCH=”Y” 

Sets the primary language for default subtitle 

display. 

Example: SUBTITLES_PREF_LANG=”fra” 

Sets the secondary language for default subtitle 

display. 

Example: SUBTITLES_SECOND_LANG=”fra” 

Sets the primary language for the default audio 

stream selection. 

Set ““ for automatic language selection. 

Example: PREFERRED_LANG=”fra” 

The secondary language for the default audio 

stream selection. 

Set ““ for automatic language selection. 

DELAY_FACTOR 

REPEAT_RATE 

1 16cs 

2 32cs 

3 64cs 

4 96cs 

0 off 

2 - 30 repeat rate 

(in cs) 

Example: SECONDARY_LANG=”fra” 

Sets the length of time that a user holds a key 

down on an IR input device (e.g. the keyboard) in 

order to make it repeat. 

Default: 2 

Example: DELAY_FACTOR=”1” 

Sets the key repeat rate in centi-seconds, to 

control the number of characters per second that 

a user can enter via an IR input device (e.g. the 

keyboard). “0” indicates no key repeat. "2", "4", 

"6" … "30" indicate number of centi-seconds of 

repeat. 

Default: 8 

Example: REPEAT_RATE=”0” 

MAXIMUM_VOLUME 0 - 100 Sets the maximum volume. 

Default: 100 

Example: MAXIMUM_VOLUME=”100” 




MINIMUM_VOLUME 0 - 100 Sets the minimum volume. 

Default: 0 

RFBOOST_MPEG 

RFBOOST_DOLBY 

TEXT_ENTRY 

ENABLE_TRUSTED_D 

OMAINS 

Y enable 

N disable 

Y enable 

N disable 

1 enable 

0 disable 

Y enable 

N disable 

Example: MINIMUM_VOLUME=”20” 

Sets whether RF audio level boosting is enabled 

or disabled. 

A110-BGA only. 

Default: N 

Example: RFBOOST_MPEG=”Y” 

Sets whether Dolby audio level boosting is 

enabled or disabled. 

A110-BGA only. 

Default: N 

Example: RFBOOST_DOLBY=”Y” 

Enables or disables remote text entry via the 

remote control. If text entry is enabled, the user 

enters text by holding down the appropriate 

number key. Note that REPEAT_RATE must be set 

to zero in order for remote text entry to be 

enabled. 

Example: TEXT_ENTRY=”1” 

Enable or disable use of trusted domains. If the 

use of trusted domains is enabled, pages that use 

Javascript or Macrovision are checked against 

the list of trusted hosts. If trusted domains is 

disabled, then Javascript and Macrovision calls 

are executed from any web page. Note that if 

trusted domains is set, only URLs listed can 

execute Macrovision calls. 

Opera and Escape browsers only. 

Note: This setting can’t be accessed via 

libconfig. 

Default: N 

TVI_TYPE 

NTPCLIENT_TIMEOU 

T 

0 Philips 

1 Zenith 

2 LG 

3 Mate 

(Sony/Panasonic) 

Example: ENABLE_TRUSTED_DOMAINS=”Y” 

Configures which TV type the TVI interface needs 

to use on the PIC. 

Hospitality platforms only. 

Example: TVI_TYPE=”0” 

Sets the NTP client timeout (in seconds). 

Example: NTPCLIENT_TIMEOUT=”10” 



10.2netconf file contents 

The following table describes the settings available in the netconf file. Note that whether 


Default values listed here are used if no value is supplied. In many cases, the default value 

is build-specific, so may not be as specified here. 

The examples show how to enter the setting if you are editing the netconf file directly (note 

that the values are all enclosed in quotation marks). See the appropriate documentation for 

information on how to enter values using other means (e.g. JMACX, libconfig via Telnet). 


DOMAIN 

Specifies a domain for the set-top box. 

TIME_ZONE 

PACKET_ORDERING 

Y enable 

N disable 

Example: DOMAIN=”aminocom.com” 

Sets the time zone. 

Example: TIME_ZONE=”GMT” 

Enables or disables using packet ordering. 

Example: PACKET_ORDERING=”Y” 

10.3NOR flash - list of settings 

The following table describes the settings available in the NOR flash. Note that whether 


Default values listed here are used if no value is supplied. Note, though, that in many cases 

the actual default is build-specific, so may not be as specified here. 

Setting Values Description 

DI 

Specifies the deployment index (DI) of the 

software image loaded on the set-top box. 

Read-only. 

LOCK 

0 not locked 

1 locked 

Specifies the lock state of the NOR flash. 

If this is set to 1, values such as the MAC address, 

serial number and some CA settings that identify 

an individual set-top box cannot be changed. 

Read-only, except in production builds. 

MAC_ADDRESS aa:bb:cc:dd:ee: Sets the unique MAC address of the set-top box. 

ff format 

If the MAC address is changed, then the set-top 

box needs to be rebooted for the new value to 

take effect. 


SERIAL_ID 

Configures the unique serial ID of the set-top box. 



IDENT 

The NOR flash model identity string value. 

Read-only. 




BOARDREV 00, 01, 02, 16, 17, 

32 - 47 

TVSYSTEM 

see separate 

Board revision 

numbers list for 

meanings 

PAL-B e.g. 

Australia, Ghana 

PAL-G e.g. Europe 

PAL-H e.g. 

Belgium 

PAL-I e.g. UK 

PAL-M e.g. Brazil 

PAL-N e.g. South 

America 

PAL-CN e.g. 

Argentina 

NTSC-J e.g. 

Japan 

NTSC-M e.g. US 

The following 

values are for the 

AmiNET120 only: 

SD set from HD 

back to SDTV 

1080i59 HDTV 

1080i 59Hz 

refresh 

1080i50 HDTV 

1080i 50Hz 

refresh 

720p59 HDTV 

720p 59Hz refresh 

720p50 HDTV 

720p 50Hz refresh 

576p50 50Hz 

refresh PAL SDTV 

resolution (but 

progressive scan) 

480p59 59Hz 

refresh NTSC 

SDTV resolution 

(but progressive 

scan) 

Specifies the board type (relates to the region that 

the set-top box is designed to work in and 

indicates board features). 

Read-only. 

Sets the TV system that the set-top box will 

operate in. 

Note: after the value has been altered the set-top 

box has to be rebooted for the change to take 

effect. 




RFMOD_CHAN 

RFMOD_ENABLE 

RFMOD_FREQTABLE 

OUTFMT 

Y enable 

N disable 

BROADCAST 

CABLE 

CVBS-RGBOFF 

Composite 

CVBS-RGBON 

Composite + RGB 

LC-RGBOFF S- 

video 

LC-RGBON” S- 

video + RGB 

CVBS-LC 

Composite + S- 

video 

CVBS-LBR 

Composite + 

Component 

LBR-CVBS-LC 

Component + 


video 

RGB-CVBS-LC 


video + RGB 

PPP_USERNAME max. 20 

characters 

PPP_PASSWORD max. 20 

characters 

PPP_DIALUP 

max. 32 digits; no 

spaces 

Sets the RF channel for boards that have an RF 

tuner. 


Enables or disables the RF tuner for boards that 

have one. 

Configures whether the RF tuner is cable or 

broadcast. 

Configures the output format for the set-top box to 

use. 

Configures the user name to use in PPP builds. 

PPP builds only. 


Configures the password to use in PPP builds. 



Configures the dial up phone number for PPP 

builds. 






MULTICAST_BOOTST 

RAP_GROUP 

MULTICAST_BOOTST 

RAP_PORT 

valid multicast IP Configures a static multicast bootstrap group. 

address in range Enter a valid IP address for the group, and set 

224.0.0.0 - MULTICAST_BOOTSTRAP_PORT with the port to use. 

239.255.255.255 

This value is used: 

 

as a fall-back bootstrap group when the 

group and port specified by DHCP 

cannot be found 

for deployments where booting 

information is not held on a DHCP 

server 

If this is not set with a valid multicast IP address, 

the set-top box tries to retrieve a valid IP address 

via DHCP. If this is not successful, the set-top box 

reboots. 

Note: The set-top box always tries to use a value 

served from a DHCP in preference to the 

statically defined value, unless DHCP is set to N. 

Default: 0.0.0.0 

0 - 65535 Configures a static multicast bootstrap port. You 

will also need to set 

MULTICAST_BOOTSTRAP_GROUP with the IP 

address to use. 


 

as a fall-back bootstrap group when the 

group and port specified by DHCP 

cannot be found 



server 




Default: 0 




MULTICAST_UPGRAD 

E_GROUP 

MULTICAST_UPGRAD 

E_PORT 

MULTICAST_FILESY 

STEM_GROUP 

valid multicast IP Configures a static multicast upgrade group. 

address in range Enter a valid IP address for the group, and set 

224.0.0.0 - MULTICAST_UPGRADE_PORT with the port to use. 

239.255.255.255 




server 




reboots. 





0 - 65535 Configures a static multicast upgrade port. You 

will also need to set MULTICAST_UPGRADE_GROUP 

with the IP address to use. 


valid multicast IP 

address in range 

224.0.0.0 - 

239.255.255.255 



server 




Default: 0 

Configures a static multicast file system group. 

Enter a valid IP address for the group, and set 

MULTICAST_FILESYSTEM_PORT with the port to 

use. 




server 




reboots. 

Note: the set-top box always tries to use a value 

served from a DHCP in preference to the statically 

defined value, unless DHCP is set to N. 





MULTICAST_FILESY 

STEM_PORT 

SUBTITLES 

ETHERNET 

DHCP 

0 - 65535 Configures a static multicast file system port. You 

will also need to set 

MULTICAST_FILESYSTEM_GROUP with the IP 

address to use. 


Y enable 

N disable 

AUTO auto-detect 

10HD 10Mbit/s half 

duplex 

10FD 10Mbit/s full 

duplex 

100HD 100Mbit/s 

half duplex 

100FD 100Mbit/s 

full duplex 

Y always use 

DHCP 

N do not use 

DHCP 



server 

Note: the set-top box always tries to use a value 

served from a DHCP in preference to the statically 

defined value, unless DHCP is set to N. 

Default: 0 

Enable or disable the subtitle display when 

playing video that contains subtitles. 

Subtitle builds only. 

Sets the default speed for the main ethernet port. 

Default: AUTO 

Configures if and how configuration information is 

used from a DHCP server. This value is used if 

USE_NOR is set to Y in the netconf file. Note that if 

you set “N”, the multicast upgrade values and 

other settings are read from the settings listed in 

this table (e.g. the MULTICAST_ settings). 

IPADDR valid IP address Configures the static IP address of the set-top 

box. This is the value used if DHCP is set to N. 

NETMASK valid IP address Specifies the static netmask for the set-top box. 

This is the value used if DHCP is set to N. 

GATEWAY valid IP address Specifies the gateway for the set-top box. This is 

the value used if DHCP is set to N. 

DNS valid IP address Specifies the IP address of the DNS that the settop 

box should be using. This is the value used if 

DHCP is set to N. 

TIME_SERVER valid IP address Specifies the location of the time server for the 

set-top box to use. This is the value used if DHCP 

is set to N. 

TFTP_SERVER valid IP address Specifies a static TFTP server IP address. 

Only used for systems that use the TFTP upgrade 

mechanism instead of DHCP. 



10.4Channels file contents 

The file contains just a list of channel numbers and the URL for them, in the following 

format: 

Example: 

 

123 http: igmp://239.255.250.2:11111 

Channel numbers can be in the range 0 - 999, and they do not have to run consecutively or 

start at zero (e.g., you could just configure channels 100 - 199). 

10.5Trusted domains file contents 

The file contains a list of trusted domains, each one on a separate line, with a code that 

indicates what is enabled. The format for each line is as follows: 

 

 

Code that indicates what is enabled for the specified domain. 

Values can be as follows: 

0 neither Macrovision nor Javascript enabled 

1 Macrovision enabled, Javascript disabled (unlikely to need 

setting) 

2 Javascript enabled, Macrovision disabled 

 

3 both Javascript and Macrovision enabled 

URL for the trusted domain. This can use asterisks as wildcards. 

Example: 

3 *.aminocom.com 

Important: The rules specified in the trsdmns.txt file are applied in the order they are 

stated, so you need to take care when adding domains to ensure that the rules are applied 

as intended. 

For example, in the following file, 3 specifies that Macrovision and Javascript are enabled 

for the macrovision.aminocom.com domain, and 2 specifies that only Javascript is 

enabled for any other aminocom.com domain: 

3 macrovision.aminocom.com 


In the following alternative example - with the same settings re-ordered - only Javascript is 

enabled for any aminocom.com domain, and so Macrovision is not enabled for 

macrovision.aminocom.com, even though 3 would normally enable Macrovision - since 

Macrovision for this domain has already been ruled out in the previous line: 

10.6Usersettings file contents 


3 macrovision.aminocom.com 

The usersettings file can contain any of the settings normally specified in the settings file. 

Software builds for some browsers write certain settings to the usersettings file. 



10.7Hostname file contents 

The following table describes the settings available in the HOSTNAME file. 

Default values listed here are used if no value is supplied. 

The example shows how to enter the setting if you are editing the hostname file directly 

(note that the values are all enclosed in quotation marks). See the appropriate 

documentation for information on how to enter values using other means (e.g. JMACX, 

libconfig via Telnet). 

Setting Default value Description 

HOSTNAME 

The set-top box’s host name. 

10.8HTML Configuration pages - settings used 

The main settings needed to configure the set-top box can be accessed via the 

Configuration pages. Which configuration area these settings are read from (i.e. 

configuration file or NOR flash) depends on the software build. The following table shows 

which area the Configuration pages read and write settings to for the Fresco and Opera 

browsers (the setting is specified with the file name (or “NOR flash”) on the first line and 

the setting name on the next line). 

You may need this information if you want to trial settings via the Configuration pages and 

then copy the new configuration to the image components used to create a new software 

image. 


Area Fresco Opera 

Browser Setup page 

Home page 

config.txt 

settings 

Help page 

Use proxy 

Accept Cookies 

Disk Cache 

RAM Cache 

larch.document.default 

settings 

BROWSER_HELPPAGE 

config.txt 

access.proxy.http.on 

config.txt 

access.cookie.enable 

config.txt 

access.cache.size 

config.txt 

BROWSER_HOMEPAGE 

settings 

BROWSER_HELPPAGE 

settings 

USE_PROXY 

settings 

BROWSER_ENABLECOOKIES 

not used 

not used 

access.ramcache.size 

Channels page 

0-999 chnls.txt chnls.txt 

Proxy Setup page 

HTTP proxy host / port config.txt 

settings 

access.proxy.http 

HTTP_PROXY 




Secure proxy host / port config.txt 

settings 

FTP proxy host / port 

Don’t use proxy (list) 

Trusted Domains page 

Enable trusted domains 

Domain n URL 

Domain n Macrovision? 

Domain n Javascript? 

Video Setup page 

Default Video Server 

TV Standard 

Output Format 

Video Trick-play Scale 

No RTSP event timeout 

RTSP End of media event 

timeout 

No IGMP event timeout 

IGMP End of media event 

timeout 

No UDP event timeout 

UDP End of media event 

timeout 

access.proxy.https 

config.txt 

access.proxy.ftp 

config.txt 

access.proxy.http.igno 

re 

config.txt 

amino.trusted.domains 

trsdmns.txt 

(URL on line n) 

trsdmns.txt 

(Macrovision enabled if 

value on line n is 1 or 3) 

trsdmns.txt 

(Javascript enabled if value 

on line n is 2 or 3) 

settings 

RTSP_SERVER 

NOR flash 

TVSYSTEM 

NOR flash 

OUTFMT 

settings 

RTSP_SCALE 

settings 

RTSP_START_TIMEOUT 

settings 

RTSP_END_TIMEOUT 

settings 

IGMP_START_TIMEOUT 

settings 

IGMP_END_TIMEOUT 

settings 

UDP_START_TIMEOUT 

settings 

UDP_END_TIMEOUT 

HTTPS_PROXY 

not used 

settings 

HTTP_PROXY_IGNORE 

settings 

ENABLE_TRUSTED_DOMAINS 

trsdmns.txt 

(URL on line n) 

trsdmns.txt 

(Macrovision enabled if 

value on line n is 1 or 3) 

trsdmns.txt 

(Javascript enabled if value 

on line n is 2 or 3) 

settings 

RTSP_SERVER 

NOR flash 

TVSYSTEM 

NOR flash 

OUTFMT 

settings 

RTSP_SCALE 

settings 

RTSP_START_TIMEOUT 

settings 

RTSP_END_TIMEOUT 

settings 

IGMP_START_TIMEOUT 

settings 

IGMP_END_TIMEOUT 

settings 

UDP_START_TIMEOUT 

settings 

UDP_END_TIMEOUT 




Full screen mode 

settings 

settings 

Left Margin 

Right Margin 

Top Margin 

Bottom Margin 

MPEG RF Audio Boost 

Dolby RF Audio Boost 

FULLSCREEN 

config.txt 

fe_generic.display.mar 

gin.left 

config.txt 


gin.right 

config.txt 


gin.top 

config.txt 


gin.bottom 

settings 

RFBOOST_MPEG 

settings 

FULLSCREEN 

settings 

BROWSER_MARGIN_LEFT 

settings 

BROWSER_MARGIN_RIGHT 

settings 

BROWSER_MARGIN_TOP 

settings 

BROWSER_MARGIN_BOTTOM 

settings 

RFBOOST_MPEG 

settings 

RFBOOST_DOLBY 

Network Configuration page 

Ethernet Link 

NOR flash 

RFBOOST_DOLBY 

NOR flash 

DHCP Info 

Hostname 

IP Address 

Gateway 

Netmask 

Domain 

DNS 

Time Server 

ETHERNET 

NOR flash 

DHCP 

hostname 

HOSTNAME (or in netconf file, 

depending on build) 

NOR flash 

IPADDR (or in netconf file, 


NOR flash 

GATEWAY (or in netconf file, 


NOR flash 

NETMASK 

netconf 

DOMAIN 

NOR flash 

DNS 

NOR flash 

TIME_SERVER 

ETHERNET 

NOR flash 

DHCP 

hostname 

HOSTNAME (or in netconf file, 


NOR flash 

IPADDR (or in netconf file, 


NOR flash 

GATEWAY (or in netconf file, 


NOR flash 

NETMASK 

netconf 

DOMAIN 

NOR flash 

DNS 

NOR flash 

TIME_SERVER 




Time Zone 

netconf 

netconf 

TIME_ZONE 

Multicast Bootstrap Address NOR flash 

TIME_ZONE 

NOR flash 

Multicast Bootstrap Port 

Multicast Upgrade Address 

Multicast Upgrade Port 

Multicast Filesystem 

Address 

Multicast Filesystem Port 

NTP Client timeout 

TFTP Server 

TFTP Load File 

Packet Ordering 

PPP Username 

PPP Password 

MULTICAST_BOOTSTRAP_GR 

OUP 

NOR flash 

MULTICAST_BOOTSTRAP_PO 

RT 

NOR flash 

MULTICAST_UPGRADE_GROU 

P 

NOR flash 


NOR flash 

MULTICAST_FILESYSTEM_G 

ROUP 

NOR flash 

MULTICAST_FILESYSTEM_P 

ORT 

settings 

NTPCLIENT_TIMEOUT 

NOR flash 

TFTP_SERVER 

NOR flash 

TFTP_LOADFILE 

netconf 


NOR flash 

PPP_USERNAME 

NOR flash 

MULTICAST_BOOTSTRAP_GR 

OUP 

NOR flash 

MULTICAST_BOOTSTRAP_PO 

RT 

NOR flash 

MULTICAST_UPGRADE_GROU 

P 

NOR flash 


NOR flash 

MULTICAST_FILESYSTEM_G 

ROUP 

NOR flash 

MULTICAST_FILESYSTEM_P 

ORT 

not used 

NOR flash 

TFTP_SERVER 

NOR flash 

TFTP_LOADFILE 

netconf 


NOR flash 

PPP_USERNAME 

NOR flash 

PPP_PASSWORD 

PPP_PASSWORD 

Hardware Information page 

Product hard coded hard coded 

Processor hard coded hard coded 

SDRam hard coded hard coded 

Flash hard coded hard coded 

Processor Speed hard coded hard coded 

Board Revision hard coded hard coded 

Software version page 

Version /etc/version /etc/version 




Identity page 

MAC Address 

NOR flash 

NOR flash 

Serial Number 

Infra-Red Configuration 

IR brand code 

TVI Configuration 

TVI protocol 

User Preferences pages 

MAC_ADDRESS 

NOR flash 

SERIAL_ID 

settings 

IR_BRAND 

settings 

TVI_TYPE 

MAC_ADDRESS 

NOR flash 

SERIAL_ID 

settings 

IR_BRAND 

settings 

TVI_TYPE 


Keyboard settings page 

Repeat delay 

settings 

settings 

Repeat rate 

Enable remote text entry 

DELAY_FACTOR 

settings 

REPEAT_RATE 

settings 

DELAY_FACTOR 

settings 

REPEAT_RATE 

settings 

TEXT_ENTRY 

TV system and audio settings page 

Frequency table 

NOR flash 


RF Channel / Use RF output NOR flash 

TEXT_ENTRY 

NOR flash 


NOR flash 

Volume Minimum 

Volume Maximum 

TV display format 

Video output format 

Audio - Primary Language 

RFMOD_CHAN 

settings 

MINIMUM_VOLUME 

settings 

MAXIMUM_VOLUME 

settings 

DISPLAY_MODE 

NOR flash 

TVSYSTEM 

settings 

PREFERRED_LANG (or 

usersettings file if the file 

exists) 

RFMOD_CHAN 

settings 

MINIMUM_VOLUME 

settings 

MAXIMUM_VOLUME 

settings 

DISPLAY_MODE 

NOR flash 

TVSYSTEM 

usersettings 

PREFERRED_LANG / (in 

settings file instead in some 

builds) 




Audio - Secondary 

Language 

Subtitles page 

Enable (check box) 

settings 

SECONDARY_LANG (or 


exists) 

NOR flash 

usersettings 

SECOND_LANG / (in settings 

file instead in some builds) 

NOR flash 

Subtitle selection 

Primary Language 

Secondary Language 

SUBTITLES 

settings 

SUBTITLES_OPTION 

settings 

SUBTITLES_PREF_LANG (or 


exists) 

settings 

SUBTITLES_SECOND_LANG 

(or usersettings file if the file 

exists) 

SUBTITLES 

settings 

SUBTITLES_OPTION 

settings 

SUBTITLES_PREF_LANG 

settings 

SUBTITLES_SECOND_LANG 


11Troubleshooting 

11.1 Set-top box LED flashing codes 

About flashing codes 

LED flashing codes 

The LED on the front of AmiNET set-top boxes indicates operational information such as 

errors during booting. A sequence of short and long flashes communicates the general 

type of information and the detail of the error. 

The flashing codes indicate 2 main groups of errors - information and fatal errors. 

Information errors: Information errors are indicated by shorter flashes. These errors 

generally require a reboot of the set-top box, but there are exceptions - for example if the 

set-top box can’t execute a command sent by STBremoteconf, it continues normal 

operation rather than rebooting. The following table shows the number of flashes that 

indicates the major groups of information errors. 

Major no. Error type 

of flashes 

1 Not full functionality 

2 Code upgrade failure 

3 Security/cryptographic issue (boot loader) 

4 Security/cryptographic issue (OS) 

5 Miscellaneous errors 

Fatal errors: Fatal errors are indicated by longer flashes. When the set-top box detects 

these errors, it flashes the LED error in an endless loop. Rebooting the set-top box in 

these cases may cause it to stop responding permanently, particularly after a NOR flash 

write failure. For this reason, the set-top box should not be rebooted until all diagnostics 

have been completed. The following table shows the number of flashes that indicates the 

major groups of fatal errors. 

Major no. Error type 

of flashes 

8 Cryptographic failure 

9 Hardware failure 

List of LED flashing codes 

Major Minor Error Set-top box behaviour Reboot 

1 Not full functionality 

1 1 No network connection. Repeats 3 times. Continues 

booting. 

No 




1 2 DHCP look-up failure. Repeats 3 times. Continues 

booting. 

1 3 I2C communication failure. Repeats 3 times. Continues 

booting. 

No 

No 

2 Code upgrade failure 

2 1 TFTP download failure. !poweron file is not saved. 

Reboots. 

2 2 BOOTP server not found. !poweron file is not saved. 

Reboots. 

2 3 Multicast group not found. Retries 3 times. If still 

unsuccessful, reboots. 

2 4 Multicast download timeout. Retries 3 times. If still 


2 5 product file missing from 

running software. 

2 6 bin/products file missing from 

downloaded software upgrade 

image. 

2 7 bin/products file doesn’t 

match set-top box product (i.e. 

the software upgrade image is 

not suitable for this platform). 

2 8 Failed to load new NOR flash 

driver. 

Uses reflash (upgrade system is 

broken) then reboots. 

Reboots. 

Reboots. 

Reboots. 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

3 Security/cryptographic issue (boot loader) 

3 1 Verification of download image 

failed. 

3 2 Signature check of 

listfile.sig failed. 

Deletes the image if saved in 

the flash. Retries 3 times. If still 

unsuccessful, STB reboots. 



unsuccessful, STB reboots. 

3 3 listfile.sig is missing. Erases the flash (assumed to be 

unsafe) and reboots. 

3 4 Missing file in the NAND flash 

(according to listfile.sig). 

3 5 File check against 

listfile.sig failed. 

3 6 File found in the NAND flash is 

not in listfile.sig. 

3 7 Unable to decode the customer 

public key on the STB. 

Erases the flash (assumed to be 






Reboots. 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

4 Security/cryptographic issue (OS) 




4 1 Verification of download image 

failed 

4 2 Signature check of 

listfile.sig failed 

4 3 listfile.sig is missing or 

corrupted 

4 4 Software upgrade image DI 

(deployment index) is less than 

set-top box DI 












4 5 Set DI failed. Deletes the code contents of the Yes 

flash, then reboots. 

4 6 STBremoteconf key not found. Ignores command. No 

4 7 STBremoteconf key failed to Ignores command. 

No 

verify. 

4 8 MD5 sum failure. Rejects software upgrade 

image. 

No 

4 9 Number of entries in 

listfile.sig doesn’t match 

files downloaded. 

Rejects software upgrade 

image. 

4 10 No DI found. Reboots. Yes 

Yes 

Yes 

Yes 

Yes 

No 

5 Miscellaneous errors 

5 1 NAND flash corruption. Reformats the NAND flash and 

reboots. 

5 2 PID mismatch when upgrading Reboots. 

the ROM. 

5 3 Failed to remove files on Reboots and retries. 

upgrade. 

5 4 Failed to set execute/start Clears the NAND flash. 

address in the NAND flash. 

5 5 Kernel panic / no root FS. Reboots (can’t clear the NAND 

flash). 

5 6 Invalid type of GIF file saved on Deletes the file. 

NAND flash. 

5 7 Failed to write files to NAND Clears the NAND flash 

flash. 

5 8 Failed to gunzip the boot ROM Rejects image and reboots. 

image. 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

Yes 

8 Cryptographic failure 

8 1 No master key found. Flashes in endless loop No 

8 2 No customer key found. Flashes in endless loop No 

8 3 Signature check of customer 

key failed. 

Flashes in endless loop No 




8 6 Verification of IntactOS code 

failed. 

Flashes in endless loop No 

9 Hardware failure 

9 1 Page write to ROM failed. Flashes in endless loop No 

9 2 NAND flash hardware / format Flashes in endless loop No 

failure. 

9 3 SDRAM access failure. Flashes in endless loop No 

9 4 Communication to Ethernet chip Flashes in endless loop No 

failed. 

11.2 STBremoteconf errors 

When using the STBremoteconf client, the following error messages may be displayed in 

response to sending a command: 

Message: Couldn’t convert to internet address: Resource temporarily unavailable. 

Explanation: The IP address specified was not in a valid format. IP addresses must be in 

the format aaa.bbb.ccc.ddd, where aaa and so on are numeric values (e.g. 10.0.0.1). 

Message: Couldn’t connect: Connection refused. 

Explanation: The set-top box IP address entered is not the address of a set-top box. Check 

that the address you entered is a set-top box address - e.g. check the address allocations 

in the DHCP server’s configuration file (subnet declaration). 

11.3 Browser display issues 

Issue: Video is visible around the edges of browser pages 

Explanation: In non-fullscreen mode, the browser renders graphics in a safe screen area 

that occupies around 90% of the full screen resolution, so that browser content is visible on 

all televisions. 

A side-effect of this is that if video is playing behind the graphics plane, it can be see around 

the edges of the browser pages. 

Solution: Enable fullscreen mode (e.g. via the set-top box Management pages - Video 

Setup page). 

The browser now fills the graphics plane, but may render content off the edge of the screen. 

To adjust this, re-set the browser’s margins (e.g. via the set-top box Management pages 

again). 

These margins define an area that the browser won’t draw HTML elements in. To render 

this area the same as the current background colour or image, the following tag will need 

to be added to the web pages that the browser is displaying: 

Appendix A:Configuration example: 

DHCP server and Multicast server for 

multiple types of set-top box 

A.1 DHCP server configuration file 

The following dhcpd.conf file contains settings for transmitting bootstrap and upgrade 

images for three different platforms. 

### Misc dhcp options 

allow bootp; 

ddns-update-style ad-hoc; 

filename="AMINET.txt"; 

max-lease-time 360000; 

default-lease-time 360000; 

### Extra Options for AMINO option space (used for multicast) 

option space AMINO; 

option AMINO.address code 1 = ip-address; 

option AMINO.port code 2 = integer 16; 

option AMINO.product code 3 = text; 

option AMINO.option code 4 = text; 

option AMINO.version code 5 = text; 

option AMINO.middleware code 6 = ip-address; 

option AMINO.mw_port code 7 = integer 16; 

option AMINO.homepage code 8 = text; 

option AMINO.dindex code 9 = integer 32; 

option AMINO.dindex_min code 10 = integer 32; 

option AMINO.dindex_page code 11 = text; 

### 

### AmiNET110 Configuration Section 

### 

### Class "AmiNET110 mboot" 

# AmiNET110 - response to bootrom request for a bootstrap image 


Configuration example: DHCP server and Multicast server for multiple types of set-top box 


{ 

match if (option vendor-classidentifier="aminoAMINET11xmboot1.31") 

or 

((substring(option vendor-encapsulated-options, 2, 

9)="AMINET11x") 


5)="mboot")); 

} 




### Class "AmiNET110 upgrd" 

# AmiNET110 - response to bootstrap request for a main upgrade 

image 


{ 

match if (option vendor-classidentifier="Aminoaminet110upgrd") 

or 

((substring( option vendor-encapsulatedoptions,2,9)="aminet110") 


} 




### Class "AmiNET110 fisys" 

# AmiNET110 - response when booting in normal boot state 


{ 

match if (option vendor-classidentifier="Aminoaminet110fisys") 

or 

((substring( option vendor-encapsulated-options, 

2, 9)="aminet110") 


5)="fisys")); 

} 


option AMINO.middleware 239.255.5.5; 



### 


### 




{ 

match if (option vendor-classidentifier="aminoAMINET130mboot") 

or 

((substring(option vendor-encapsulated-options, 

2, 9)="AMINET130") 


5)="mboot")); 

} 






image 


{ 


or 



} 









{ 


or 


2, 9)="aminet130") 


5)="fisys")); 

} 


### 


### 




{ 

match if (option vendor-classidentifier="aminoAMINET5xxmboot") 

or 

((substring(option vendor-encapsulated-options, 

2, 9)="AMINET5xx") 


5)="mboot")); 

} 






image 




{ 


or 



} 







{ 


or 


2, 9)="aminet500") 


5)="fisys")); 

} 


### 

### Subnet Declaration 

### 

subnet 10.172.0.0 netmask 255.255.0.0 { 

option routers 10.172.0.1; 

option subnet-mask 255.255.0.0; 

option domain-name "aminocom.com"; 

option domain-name-servers 10.171.22.7,10.171.22.9; 

option time-offset 0; # Eastern Standard Time 

pool { 

range 10.172.230.50 10.172.230.100; 

} 

} 



A.2 Multicast server configuration file 

The following mcastbootd.conf file contains settings for transmitting bootstrap and 

upgrade images for three different platforms, as also configured in the DHCP 

configuration file. In this example, all the bootstrap images are stored in the same 

location, but named differently (e.g. bootstrap.110, bootstrap.130); the same method 

is used to uniquely identify the upgrade images. Note that the [Filesystem mc2] section 

here is a dummy section, required in order for the Multicast server to start successfully. 

[Server] 

LogLevel=4 

MulticastTTL=5 






ImageType=1 



CycleTime=0 






ImageType=1 



CycleTime=0 






ImageType=1 



CycleTime=0 






ImageName=mc2 




DataRate=256 








DataRate=256 








DataRate=256 








DataRate=256 

A.3 DHCP and Multicast server matching values 

For each set-top box type set up in the DHCP server, the multicast values that the 

configuration specifies must match the values that the Multicast server uses for 

transmitting software images. The following table shows the equivalent settings in the 

example DHCP server and Multicast server configuration files shown here. 

DHCP server configuration 


Multicast server configuration 




DHCP server configuration 

Multicast server configuration 

option AMINO.address 239.255.230.52; MulticastIPAddress=239.255.230.52 









Example configuration file contains no 

settings for retrieving upgrade image in fisys 

state, but it could use the same values as in 

the [Filesystem mc110] section (e.g. if 

using deployment index for automatic 

upgrades). 






















Appendix B:Changing from TFTP to 


Amino software releases include the files needed to change TFTP-booting set-top boxes 

over to using the Multicast upgrade system instead. To make the change, the files need 

to be supplied to the set-top box via TFTP. 

B.1 To change a TFTP booting set-top box to Multicast upgrade 

The following steps assume you have a TFTP bootrom and a recent software release for 

that includes a tftpboot directory. The steps also assume you have set up a Multicast 

upgrade system and have suitable software bootstrap and upgrade images available via 

the Multicast server. 

Note: Note that in the following steps, stands for the full path to an Amino 

software release. If you followed examples during installation of the Multicast upgrade 

system, this is /usr/local/amino/releases/ 

1. Log in as root. 

2. Delete the contents of your TFTP server’s directory. 

Example: 

rm -f /tftpboot/* 

3. Copy the contents of the tftpboot directory of the software release to your 

TFTP server’s directory. 

Example: 

cp //romupgrade/tftpboot* /tftpboot 

4. Update the set-top box using the normal TFTP procedure. 

The set-top box will wipe its NAND flash and download a new multicast-aware 

boot loader . It will then reset itself and enter the Multicast bootstrap state, and 

contact the DHCP server for Multicast bootstrap group settings. 


Appendix C:Video output formats 

C.1 AmiNET103 

The following sections show the output format possibilities for each set-top box platform, 

depending on the cables connected. The output format is normally set as part of 

configuration (e.g. via the Management pages or libconfig), but in some cases it is 

selected automatically - as detailed in the tables for each platform. The name of the 

setting or command used to change the output format depends on which tool you are 

using - see the documentation for the tool for details. Note that in the following tables 

Composite is the same as CVBS and Component is the same as YPbPr. 

C.2 AmiNET110, 110H 

Part no. Cables Output format 

configuration options 

RCA to SCART 

Composite 

RCA to RCA 

Composite 



502-418 10 pin Mini DIN to SCART Composite 


S-video 

Composite + S-video 

502-594 10 pin Mini DIN to S-video Composite + S-video 

and Composite 

502-523 10 pin Mini DIN to Composite Composite 

(3RCA) 

002-596 10 pin Mini DIN to 

Component (5RCA) 

(obsolete) 

Composite + Component 

502-419 10 pin Mini DIN to 6RCA 

Component video and 

Composite 

Note that Sync is on Yellow 

(Sync on Green is not 

supported). 

10 pin Mini DIN to S-video 

(obsolete) 

Composite 




S-video 

S-video 


C.3 AmiNET120 

With the AmiNET120, you don’t need to select output format in configuration - it is 

selected automatically. The following table shows the output format possibilities. 

C.4 AmiNET124 




and Composite 

002-726 10 pin mini DIN to 



Note that Component video output is not supported on older AmiNET124 hardware (US 

board revision number 17; EU board revision number 02). 

C.5 AmiNET125 








and Composite 


(3RCA) 

002-596 

obsolete 

10 pin Mini DIN to 




Composite 


Composite 











C.6 AmiNET130, 130H 



502-594 10 pin Mini DIN to S-video 

and Composite 

502-523 10 pin Mini DIN to Composite 

(3RCA) 

002-596 

obsolete 

10 pin Mini DIN to 


(obsolete) 



Composite 


Composite 


Composite 




Note that when the HDMI cable is connected, the HD type is selected automatically. 

C.7 AmiNET500 








and Composite 


(3RCA) 



Composite 

Composite 




510-885 HDMI Composite + Component 

Any combination of the following cables: 


Part no. Cables Output Configuration options 

(output format) 

002-777 Composite 

(RCA) 

Composite 

002-776 S-video S-video 

002-775 Component Component 

(3RCA) 

Depends on cables used. 

E.g. if S-video and 

Composite cables are 

connected, you can set 

Composite + S-video or just 

S-video or just Composite; if 

all three cables are 

connected, you can set 

Composite + Component + 

S-video - or any combination 

of the formats. 


Index 

A 

ACAPS_CS_IP_SET (STBremoteconf) 63 

ACAPS_ENABLE (STBremoteconf) 63 

Amino key 14 

See also Keys 

AUTO_SD_SWITCH (settings file) 85 

B 

BOARDREV (NOR flash) 88 

Bootstrap 

See also software images 13, 25 

bootstrap directory 21 

Bootstrap image 13, 25 

Distributing 13, 26 

Bootstrap state 10 

DHCP request 16 

DHCP response 16 

Operation 16 

bootstrap.unsigned 21 

Browser configuration files 45 

Browser Setup (Management pages) 72, 

95 

BROWSER_ENABLECOOKIES (settings 

file) 81, 95 

BROWSER_HELPPAGE (settings file) 81 

BROWSER_HElPPAGE (settings file) 95 

BROWSER_HOMEPAGE (settings file) 

81, 95 

BROWSER_MARGIN_BOTTOM (settings 

file) 82, 97 

BROWSER_MARGIN_LEFT (settings file) 

82, 97 

BROWSER_MARGIN_RIGHT (settings 

file) 82, 97 

BROWSER_MARGIN_TOP (settings file) 

82, 97 

Build options 

Development builds 15 

Live builds 15 

C 

CHANGEPAGE (STBremoteconf) 63 

CHANGE-PWORD (STBremoteconf) 63 

CHANNEL (STBremoteconf) 64 

Channels (Management pages) 72, 95 

chnls.txt 45, 95 

Contents 93 

commands file 21 

config.txt 21, 45, 95–96 

config.txt file 97 

Configuration 

Set-top box (overview) 11 

Configuration key 14 

See also Keys 

Configuration pages 9, 71 

Configuring set-top box 43 

Controlling with keyboard 72 

Controlling with remote control 72 

mcnfg.tar 21 

Prerequisites 71 

Configuring 

Set-top box 43 

Browser configuration file 45 

chnls.txt 45 

config.txt 45 

Configuration pages 43 

Dropbear 43 

fkeys.conf file 45 

hostname file 45, 79 

Image components 43 

Management pages 95 

Multiple set-top boxes 46 

netconf file 45, 79 

NOR flash settings 45, 79 

opera.ini 45 

Options 43 

Pairing remote control 47 

Preferences pages 99 

Remote control keys 48 

settings file 45, 79 

SSH 43 

STBremoteconf 43 

Telnet 43 

trsdmns.txt 45 

usersettings file 45, 79 

Using Management pages 73 

Set-top boxes 


Customer key 14 

See also Keys 

D 

DEFAULT_VOLUME (STBremoteconf) 64 

DELAY_FACTOR (settings file) 85, 99 

DELETECUSTKEY (STBremoteconf) 64 

Deployment index 14 

Development build 

Build options 15 

DHCP (NOR flash) 92, 97 

DHCP request 


Filesystem state 18 

Upgrade state 17 

DHCP response 





DHCP server 8 

DHCP settings 

Dynamic 46, 80 

DHCPC settings 46, 80 

dhcpd.conf 21 

DI 

See Deployment index 

DI (NOR flash) 87 

DISPLAY_MODE 84 

DISPLAY_MODE (settings file) 99 

DNS (NOR flash) 97 

DOMAIN (netconf file) 87, 97 

Dropbear 9 


Dynamic DHCP settings 46, 80 

E 

EAS (STBremoteconf) 64 

ENABLE_TRUSTED_DOMAINS (settings 

file) 86, 96 

ETHERNET (NOR flash) 92, 97 

ETHERNET (STBremoteconf) 65 

F 

FETCHFILE (STBremoteconf) 65 

Files 

Software release directory contents 

20 




Operation 18 

fisys 

see Filesystem state 

fkeys.conf 21, 45 

flashcontents file 21 

FULLSCREEN (settings file) 82, 96 

G 

GATEWAY (NOR flash) 92, 97 

GETVERSION (STBremoteconf) 65 

Graphic 

splash.gif 16 

Graphics 

loading.gif 21 

splash.gif 21 

H 

Hardware Information (Management 

pages) 72 

Hardware information (Management 

pages) 98 

HOSTNAME (hostname file) 94, 97 

hostname file 45, 79 

Contents 94 

HOSTNAME 94, 97 

HTML Configuration pages 

see Configuration pages 9, 71 

HTTP_PROXY (settings file) 84, 95 

HTTP_PROXY_IGNORE (settings file) 84, 

96 

HTTPS_PROXY (settings file) 84, 95 

HWINFO (STBremoteconf) 65 

I 

IDENT (NOR flash) 87 

Identity (Management pages) 72, 98 

IGMP_END_TIMEOUT (settings file) 83, 

96 

IGMP_START_TIMEOUT (settings file) 

83, 96 

Image components 


imagecomponents directory 21 

IME (settings file) 82 

imgcfg file 21 

Infra-Red Configuration (Management 

pages) 73, 99 

Installing 

Perl modules for STBremoteconf 58 

IPADDR (NOR flash) 92, 97 

IR_BRAND (settings file) 83, 99 

K 

Keyboard 

Using with Configuration pages 72 

Using with Management pages 73 

Keyboard settings (Preferences pages) 99 

Keys 

Amino engineering keys 

keys directory 21 

Security Keys 10, 14 

keys directory 21 

L 

LED 

Flashing codes 101 

List 101 

Live build 

Build options 15 

loading.gif 21 

LOADKEY-CONF (STBremoteconf) 65 

LOADKEY-CUSTOMER (STBremoteconf) 

65 


LOADKEY-OPERATOR (STBremoteconf) 

65 

Local management 9 

LOCK (NOR flash) 87 

LOCK (STBremoteconf) 65 

LOGREAD (STBremoteconf) 65 

M 

MAC_ADDRESS (NOR flash) 87, 99 

MACADDRESS (STBremoteconf) 65 

Management pages 9, 71 

Browser Setup 72 

Channels 72 

Configuration settings used 95 

Browser Setup 95 

Channels 95 

Hardware information 98 

Identity 98 

Infra-Red 99 

Network 97 

Proxy Setup 95 

Software version 98 

Trusted Domains 96 

TVI 99 

Video Setup 96 

Controlling with keyboard 73 

Editing configuration 73 

Hardware Information 72 

Identity 72 

Infra-Red Configuration 73 

List of pages 72 

Network Configuration 72 

Overview 72 

Proxy Setup 72 

Reboot 73 

Rebooting set-top box 74 

Software Version 72 

Trusted Domains 72 

TVI Configuration 73 

Update Software 72 

Using 72 

Video Setup 72 

Viewing configuration 73 

MAXIMUM_VOLUME (settings file) 85, 99 

mboot 

see Bootstrap state 

MCASTADDR (STBremoteconf) 66 

mcastbootd binary file 21 

mcastbootd.conf 21 

mcnfg.tar 21 

MINIMUM_VOLUME (settings file) 86, 99 

Multicast server 8–9 

Multicast system 

Copying release files 22 

Diagram (overview) 8 

Overview of procedure 20 


Setting up 20 

MULTICAST_BOOTSTRAP_GROUP 

(NOR flash) 90, 98 

MULTICAST_BOOTSTRAP_PORT (NOR 

flash) 90, 98 

MULTICAST_FILESYSTEM_GROUP 

(NOR flash) 91, 98 

MULTICAST_FILESYSTEM_PORT (NOR 

flash) 92, 98 

MULTICAST_UPGRADE_GROUP (NOR 

flash) 91, 98 

MULTICAST_UPGRADE_PORT (NOR 

flash) 91, 98 

N 

netconf file 21, 45, 79 

DOMAIN 87, 97 

PACKET_ORDERING 87, 98 

TIME_ZONE 87, 97 

NETMASK (NOR flash) 92, 97 

Network Configuration (Management 

pages) 72, 97 

NOR flash 

BOARDREV 88 

DHCP 92, 97 

DI 87 

DNS 97 

ETHERNET 92, 97 

GATEWAY 92, 97 

IDENT 87 

IPADDR 92, 97 

LOCK 87 

MAC_ADDRESS 87, 99 

MULTICAST_BOOTSTRAP_GROU 

P 90, 98 

MULTICAST_BOOTSTRAP_PORT 

90, 98 

MULTICAST_FILESYSTEM_GROU 

P 91, 98 

MULTICAST_FILESYSTEM_PORT 

92, 98 

MULTICAST_UPGRADE_GROUP 

91, 98 


91, 98 

NETMASK 92, 97 

OUTFMT 89, 96 

PPP_DIALUP 89 

PPP_PASSWORD 89, 98 

PPP_USERNAME 89, 98 

RFMOD_CHAN 89, 99 

RFMOD_ENABLE 89 

RFMOD_FREQTABLE 89, 99 


SERIAL_ID 87, 99 

SUBTITLES 92, 100 

TFTP_LOADFILE 98 

TFTP_SERVER 92, 98 

TIME_SERVER 92, 97 

TVSYSTEM 88, 96, 99 

NOR flash settings 45, 79 

NTP 

see Time zone 

NTPCLIENT_TIMEOUT (settings file) 86, 

98 

O 

opera.ini 21, 45 

OUTFMT (NOR flash) 89, 96 

OUTFMT (STBremoteconf) 66 

P 

PACKET_ORDERING (netconf file) 87, 98 

Passwords 15, 56 

shadow file 56 

PING (STBremoteconf) 66 

PPP_DIALUP (NOR flash) 89 

PPP_PASSWORD (NOR flash) 89, 98 

PPP_USERNAME (NOR flash) 89, 98 

Preferences pages 9, 71 

Configuration settings used 99 

Keyboard 99 

Subtitles 100 

TV and audio 99 

Controlling with the remote control 

75 

PREFERRED_LANG (settings file) 85 

PREFERRED_LANGUAGE (settings file) 

99 

Prerequisites 

Configuration pages 71 

Configuring multiple set-top boxes 

46 

Setting up Multicast system 20 

STBremoteconf 58 

Installing Perl modules 58 

PROC (STBremoteconf) 66 

Procedure 

Configuring multiple set-top boxes 

46 

Pairing remote control with set-top 

box 47 

Sending STBremoteconf commands 

59 

Setting up Multicast system 20 

Production build 

see Development build 

Proxy Setup (Management pages) 72, 95 

R 

Reboot (Management pages) 73 

REBOOT (STBremoteconf) 66 

Rebooting set-top box 

Using Management pages 74 

REFLASH (STBremoteconf) 66 

Remote control 

Configuring how set-top box 

responds to keys 48 

Pairing with set-top box 47 

Using with Configuration pages 72 

Using with the Preferences pages 

75 

Remote log-in 9 

Remote management 8 

REPEAT_RATE (settings file) 85, 99 

RFBOOST_DOLBY (settings file) 86, 97 

RFBOOST_MPEG (settings file) 86, 97 

RFMOD_CHAN (NOR flash) 89, 99 

RFMOD_ENABLE (NOR flash) 89 

RFMOD_FREQTABLE (NOR flash) 89, 99 

RFMODE (STBremoteconf) 67 

romupgrade directory 21 

RTSP_END_TIMEOUT (settings file) 83, 

96 

RTSP_SCALE (settings file) 82, 96 

RTSP_SERVER (settings file) 83, 96 

RTSP_START_TIMEOUT (settings file) 

83, 96 

S 

SAVEFILE (STBremoteconf) 67 

SECONDARY_LANG (settings file) 85 

SECONDARY_LANGUAGE (settings file) 

100 

Security 

Amino key 14 

Configuration key 14 

Customer key 14 

Deployment index 

Keys 10, 14 

Overview 13 

Passwords 15, 56 

see also Bootstrap state 16 

see also Configuration pages 9 

SERIAL_ID (NOR flash) 87, 99 

SERIALID (STBremoteconf) 67 

server directory 21 

settings file 21, 45, 79 

AUTO_SD_SWITCH 85 

BROWSER_ENABLECOOKIES 81, 

95 

BROWSER_HELPPAGE 81, 95 

BROWSER_HOMEPAGE 81, 95 


BROWSER_MARGIN_BOTTOM 

82, 97 

BROWSER_MARGIN_LEFT 82, 97 

BROWSER_MARGIN_RIGHT 82, 

97 

BROWSER_MARGIN_TOP 82, 97 

Contents 81 

DELAY_FACTOR 85, 99 

DISPLAY_MODE 84, 99 

ENABLE_TRUSTED_DOMAINS 

86, 96 

FULLSCREEN 82, 96 

HTTP_PROXY 84, 95 

HTTP_PROXY_IGNORE 84, 96 

HTTPS_PROXY 84, 95 

IGMP_END_TIMEOUT 83, 96 

IGMP_START_TIMEOUT 83, 96 

IME 82 

IR_BRAND 83, 99 

MAXIMUM_VOLUME 85, 99 

MINIMUM_VOLUME 86, 99 

NTPCLIENT_TIMEOUT 86, 98 

PREFERRED_LANG 85 

PREFERRED_LANGUAGE 99 

REPEAT_RATE 85, 99 

RFBOOST_DOLBY 86, 97 

RFBOOST_MPEG 86, 97 

RTSP_END_TIMEOUT 83, 96 

RTSP_SCALE 82, 96 

RTSP_SERVER 83, 96 

RTSP_START_TIMEOUT 83, 96 

SECONDARY_LANG 85 

SECONDARY_LANGUAGE 100 

SUBTITLES 82 

SUBTITLES_OPTION 82, 100 

SUBTITLES_PREF_LANG 85, 100 

SUBTITLES_SECOND_LANG 85, 

100 

TEXT_ENTRY 86, 99 

TVI_TYPE 86, 99 

UDP_END_TIMEOUT 96 

UDP_START_TIMEOUT 96 

USE_PROXY 84, 95 

Set-top box configuration 

Overview 11 

Set-top box operation 


Detail of operational states 15 

Diagram (overview) 11 


Operational states 10 

Overview 10 


shadow file 56 

signbootstrap script 21 

SIGNEDCMD (STBremoteconf) 67 

signupgradeimage script 21 

Software builds 11 

Software images 13, 25 

Bootstrap 13, 25 

Deployment index 


Signing 10, 14 

Upgrade 13, 25 

Software release 

Directory contents 20 

software builds 11 

Software security 

Overview 13 

Software Version (Management pages) 72 

Software version (Management pages) 98 

splash.gif 16, 21 

SSH 9 


Static DHCP serttings 15 

STATS (STBremoteconf) 67 

STBremoteconf 9, 58 

ACAPS_CS_IP_SET 63 

ACAPS_ENABLE 63 

CHANGEPAGE 63 

CHANGE-PWORD 63 

CHANNEL 64 

Command syntax 60 

Commands 62 

List 63 

Overview 62 


DEFAULT_VOLUME 64 

DELETECUSTKEY 64 

EAS 64 

ETHERNET 65 

FETCHFILE 65 

GETVERSION 65 

HWINFO 65 

LOADKEY-CONF 65 

LOADKEY-CUSTOMER 65 

LOADKEY-OPERATOR 65 

LOCK 65 

LOGREAD 65 

MACADDRESS 65 

MCASTADDR 66 

OUTFMT 66 

PING 66 


Installing Perl modules 58 

PROC 66 

REBOOT 66 

REFLASH 66 

RFMODE 67 

SAVEFILE 67 

Sending commands 59 

Syntax 60 


SERIALID 67 

SIGNEDCMD 67 

STATS 67 

SYSLOG 68 

TVSYSTEM 68 

UPGRADEMCAST 69 

UPGRADEMCAST_VER 69 

VOD 69 

STBremoteconf file 21 

SUBTITLES (NOR flash) 92, 100 

SUBTITLES (settings file) 82 

Subtitles settings (Preferences pages) 100 

SUBTITLES_OPTION (settings file) 82, 

100 

SUBTITLES_PREF_LANG (settings file) 

85, 100 

SUBTITLES_SECOND_LANG (settings 

file) 85, 100 

Syntax 

STBremoteconf commands 60 

SYSLOG (STBremoteconf) 68 

T 

Telnet 9 


TEXT_ENTRY (settings file) 86, 99 

TFTP_LOADFILE (NOR flash) 98 

TFTP_SERVER (NOR flash) 92, 98 

tftpboot directory 21 

Time zone 

formats 48 

TIME_SERVER (NOR flash) 92, 97 

TIME_ZONE (netconf file) 87, 97 


LED flashing codes 101 

List 101 

trsdmns.txt 45, 96 

Contents 93 

trsdmns.txt file 96 

Trusted Domains (Management pages) 

72, 96 

TV and audio settings (Preferences pages) 

99 

TVI Configuration (Management pages) 

73, 99 

TVI_TYPE (settings file) 86, 99 

TVSYSTEM (NOR flash) 88, 96, 99 

TVSYSTEM (STBremoteconf) 68 

U 

UDP_END_TIMEOUT (settings file) 96 

UDP_START_TIMEOUT (settings file) 96 

unsigned bootstrap image 21 

Update Software (Management pages) 72 

Upgrade image 13, 25 


See also Software images 




Operation 17 

upgradeimage directory 21 

UPGRADEMCAST (STBremoteconf) 69 

UPGRADEMCAST_VER (STBremoteconf) 

69 

Upgrarde image 

See also Upgrading software 

upgrd 

see Upgrade state 

USE_PROXY (settings file) 84, 95 

User preferences pages 

see Preferences pages 9 

usersettings file 45, 79 

Contents 93 

utils directory 21 

V 

Video Setup (Management pages) 72, 96 

VOD (STBremoteconf) 69 


Document history 

Revision Name Date Changes 

0.1 - 14Feb 2005 Initial draft 

0.2 - 25Jul 2006 Updated for 0.9.4 release changes 

0.3 - 27Jul 2006 STBremoteconf Perl Updates 

0.4 - 13Jun 2006 DHCP and Ntpclient (0.12.0) 

0.12.x rev0 R.Potts 9Aug 2006 Added updated STBremoteconf 

appendix (Linux v1.6); added xref to 

signing images instructions from 

multicast system set-up procedure;minor 

format fixes 

0.13.x rev0 R.Potts 1Sept 2006 Added updated “setting up mulitast 

system”, overview pages. New section 

“Including additional files in image”. New 

libconfig appendix, example DHCP 

configuration file and Multicast server 

configuration file appendices. 

0.13.x rev1 R.Potts 5Oct 2006 Updated Configuring set-top boxes 

section; added Upgrading set-top boxes 

section; moved all STBremoteconf 

content to appendix; added advanced 

multicast system set-up section, added 

new DHCP&Multicast server 

configuration example for complex 

system. 

0.14.x rev0 R.Potts 12Oct 2006 Major rework of format. New content - 

added note on User Class options, new 

“Customising set-top box upgrade 

image” chapter, chapter covering main 

config settings. Removed HTTP upgrade 

section; JMACX function keys example 

moved to JMACX doc. Removed out-ofdate 

video cables list (temporarily). 

0.14.x rev1 R.Potts 14Nov 

2006 

Added Video output formats appendix 

and references to it in STBremoteconf 

and Config chapters 


Revision Name Date Changes 

0.14.x rev2 R.Potts 20/2/2007 Updated “Introduction” and 

“Customising...” chapters to clarify use of 

loading.gif vs. image shown during 

multicast upgrade. 

Added references to documents that 

provide more detail in many sections. 

Added section on changing passwords 

(in “Customising...” chapter). 

Added to “Advanced Multicast Upgrade” 

chapter, “static network and multicast 

upgrade settings” section: note on 

behaviour if invalid static IP addresses 

set (new functionality from 0.14.4). 

Corrected error in file path example in 

2.5 (Signing image) section

OperationsGuide0.14r.. - hinditron

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?