Skip navigation

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

Attention! Beginning from STB software version 0.2.18, all customizations of embedded portal is necessary to make using source codes of portal. After all customizations complete, it is necessary to make compiling and minimization of source code
of portal. After compiling and minization, all files of portal could be placed in home directory for further image making. Source code of portal (portal-dev-*.tgz is in directory with current release http://soft.infomir.com)

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

Example of the variable:
autoupdateURL=http://example.com/update_list.txt
  • autoupdateURL - the name of the environment variable which specifies the address (URL) of locationof the file

update_list.txt

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

Stages of update process

  1. Verification environment variable autoupdate_cond , status «0» - autoupdate option, «1» - update with confirmation, «2» - autoupdate is disabled. If the variable is «0» or «1» than the necessaty of update initialized.

  2. Reading the file (update_list.txt) which contains a list of all available updates. The listed update items are sorted by date from old to new (the last/new record in the end).
  3. Date comparing from the new/last record with image making date which is specified by stb.RDir(«ImageDate») function and returns environment variable Image_Date. In case of image making date is newer - autoupdate doesn't start.

  4. If the image date that is pointed in the update list (update_list.txt) is newer than the date of image that is in STB then additional checking of image date is started. The checking is concerning to the image which URL is pointed in update file update_list.txt.
  5. If the result of checking is that update image is newer than current one then check of update image type is started. Autoupdate to alpha versions doesn't start. Autoupdate to beta versions startes in case if option Update to beta versions in Settings is enabled. This option sets the environment variable "Betaupdate_cond": Status «1» - «update is permitted», «0» - «update is not permitted». By default the satus is set to «update is permitted».
  6. If the STB software version has type «release» or «beta» and the option «Update to beta versions» is set and the update image date is newer than date of current image, then autoupdate is started.

Syntax of update_list.txt file , example:

[
{"name":"0.2.14-r3", "url":"http://example.com/250/imageupdate214r3", "type":"release", "date":"26 Nov 2012 23:22:19 GMT+0200", "descr":"Release"},
{"name":"0.2.14-r7", "url":"http://example.com/250/imageupdate214r7", "type":"release", "date":"30 Nov 2012 14:43:29 GMT+0200", "descr":"Release"}
]

where:

  • name - name of STB software version, can contain any text (20 characters);
  • url - url of STB software version;
  • type - type of STB software version (release, beta or alpha);
  • date - contains 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.