Skip navigation

The automatic updating module is intended to automatically and manually update STB software via HTTP from the specified URL.

Attention! Starting from STB software version 0.2.18, all customizations of the Embedded portal is necessary to make using source codes of the portal. After all customizations complete, it is necessary to make the compiling the Embedded portal. After compiling and minimization, all files of the portal could be placed in the home directory for further image-making. Source code of portal (portal-dev-*.tgz is in the directory with a current release

By default, the Autoupdate module works from the manufacturer URL if the variable autoupdateURL is not specified!!!

Example of the variable:
  • autoupdateURL - the name of the environment variable which specifies the address (URL) of the file location


  • - an example of the path to the directory (on the Web server) where the file update_list.txt is located

Stages of the update process

  1. Verification of environment variable autoupdate_cond . Status «0» - auto-update is enabled, «1» - update with confirmation, «2» - auto-update is disabled. If the variable is «0» or «1» then checkup of available updates is launched.

  2. Checkup of available updates. STB reads the update_list.txt file (specified in autoupdateURL) which contains a list of all available updates ordered by creation date from old to new so that the last/new version is at the end of the list.
  3. STB compares the date of a new/last version from the update_list with the date of a current (running in STB) version which is specified by stb.RDir(«ImageDate») function and returns environment variable Image_Date. If the current version date is newer - auto-update doesn't start.

  4. If the last version, specified in the update_list, is newer than the current STB version then STB performs an additional checkup the date of update image that is located with URL of the last record of the update_list.
  5. If the update image is newer than the current version then STB launches a checkup a type of the update image:
  • If the update image is of type release then the auto-update is started
  • If the update image is of type beta then an additional checkup of the environment variable "Betaupdate_cond" is started: status «1» - update is permitted; status «0» - update is not permitted. By default, the status is set to «1». The value of variable "Betaupdate_cond" can be changed with Update to beta versions option of Settings.
  • Autoupdate to alpha versions doesn't start.

6. Thus, If the STB software version is types of «release» or «beta», in last case with Betaupdate is permitted, and the update image is newer than current image, then the auto-update is started.

Syntax of update_list.txt file , for example:

{"name":"0.2.14-r3", "url":"", "type":"release", "date":"26 Nov 2012 23:22:19 GMT+0200", "descr":"Release"},
{"name":"0.2.14-r7", "url":"", "type":"release", "date":"30 Nov 2012 14:43:29 GMT+0200", "descr":"Release"}


  • name - name of STB software version, can contain any text (20 characters);
  • url - URL of STB software version;
  • type - a type of STB software version (release, beta or alpha);
  • date - contains a date of creation of STB software version, it must be set from the Date section of the image header, in the following format: dd Mon yyyy hh: mm: ss GMT + nnnn, for example 10 Nov 2017 20:05:35 GMT + 0200;
  • descr - brief description of the version (40 characters) that displayed when version info is requested.
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.