Skip navigation

Automatic STB software update (hereinafter - autoupdate) is designed to detect of new versions availability on the update server and, if needed, to update STB software.

If STB is running manufacturer’s software (Public or Factory image), autoupdate is performed from the manufacturer’s server on new version of Factory software image.

Autoupdate procedure

Autoupdate consists of two phases:

1. Analysis of new software version existence. STB periodically reads file update_list.txt from web-server with software updates. See Update file address.

2. Launch required autoupdate scenario. When existence of new version is detected, STB launch autoupdate scenario according to settings:

  • Disabled - autoupdate is not performed, info message about existence of new version is not displayed.
  • Enabled — immediate start of downloading of new software version from the update server, followed by software update and STB restart.
  • With confirmation - Software Autoupdate window is displayed on the screen with description of the current and new software versions. To start update, user must run Update (F1) command.

More detailed description of autoupdate procedure is given in developers section - Autoupdate module description.

Autoupdate scenario configuration

In the Embedded portal, autoupdate configuration is performed in the section: Settings ⇒ Software autoupdate.


To configure autoupdate:

  • Open Settings ⇒ Software autoupdate.
  • Specify Autoupdate option:
    • Disabled - autoupdate is disabled (default value);

      If autoupdate is disabled, the user is not informed via STB messages of the new software issued. This case the only way to update software is manually (HTTP, USB).

    • Enabled - autoupdate is executed as soon as new version of software is detected at server. After update start, the Software Autoupdate window is displayed on the screen, which indicates current and new software versions, as well as the status of software update in the form of a filling progress bar and comments;
    • With confirmation - autoupdate is executed in confirmation mode: when new software version is detected, an info message is displayed on the screen. The user confirmation is expected to continue updating. See description
  • Specify Update to beta versions option:
    • ON - use beta (i.e.test) version;
    • OFF- do not use beta version (the default value).

      Stability of beta version is not guaranteed.

  • In the Software Update window, click Save (OK).

The value of Autoupdate and Update to beta versions options of Software Autoupdate window is stored in STB in variables autoupdate_cond and betaupdate_cond, respectively.

Update file address

Address of update_list.tx file, which contains information about the latest software version, is stored in STB in variable autoupdateURL. In standard software version (provided by manufacturer) the following address is specified (<Model> - Basic model number):<Model>/update_list.txt

For example, for MAG254:

Every new version release (URL of imageupdate file) should be specified in update_list.txt file. Manufacturer of STB specifies the following URL:<Model>/update_list.txt

For example, for 0.2.18-r23-254 version of STB MAG254:

Autoupdate with confirmation

Autoupdate with confirmation is one of scenarios which is specified in autoupdate settings. When new software version is detected, Software autoupdate window is appeared, which indicates the Current version and New version (latest version specified in update_list.txt file).
The user should determine if update needed (after comparing the current and new versions):

  • To reject update, click Cancel (Exit on RC) in Software autoupdate window.
  • To proceed update, select Update (F1 on RC) in Software autoupdate window.


Munual update

In addition to configuring autoupdate, in SettingsSoftware autoupdate window you can also run the update manually by F1 command.

This feature is described in Update from Portal by HTTP section.

Need Help

Dave is an expert on the MAG STB and the author of this article.

Was this article helpful?

Yes No

Sorry to hear that.
How can we improve this article?

We use cookies in order to optimise our website, provide you with the best possible user experience and help us promote our products. Please read our Cookie Policy to find out how we use cookies and how you can control cookies.
By using this website or closing this message, you acknowledge our Privacy Policy and agree to our use of cookies as described in our Cookie Policy.