Skip navigation

Purpose of service button

The service button (FN button) is located on the side panel of the STB near USB sockets. It is designed to emergency change STB boot mode. In normal state, after reboot, STB automatically loads software image from one of the memory banks NAND1 / NAND2, access to System Recovery Utility menu is available. If STB fails to load and there is no access to System Recovery Utility menu, the s ervice button is used.

Emergency boot modes

Three emergency boot modes are supported. They are signaled by means of LED indication:
  • Mode 1 Selecting alternative NAND (LED white, slow blinking - about 1 time per second). If for some reason (for example, after updating software that failed), software loading from the current memory bank does not complete, Mode 1 switches the loading from the alternative flash memory bank;
  • Mode 2 Reset to factory settings (LED red, quick blinking - about 3 time per second). STB software loading can be failed by reason of inconsistent STB settings. You may need to reset STB settings;
  • Mode 3 Emergency startup (LED red, lights constantly). If STB not booted after modes 1 and 2, this mode is used. Emergency startup implies download in STB a Bootstrap file that contains System Recovery Utility enabling user to perform recovery operations.

Selecting emergency boot mode

To select certain emergency boot mode press and hold service button before the power supplied. The current mode is signaled by means of LED: each mode has a unique indication. After expiration of decision interval (you should keep hold the button), the system automatically switches to the next boot mode. To activate certain boot mode you must stop pressing the button during the required mode lasts.Procedure for selecting the emergency boot mode:
  • Unplug the STB.
  • Press and hold Service button.
  • Swith the STB power on.
  • Wait for changing LED indication:
    • Mode 1 Selecting alternative NAND (LED white, slow blinking - about 1 time per second). In case the button released, STB boots in mode 1. If button not released, STB will pass to mode 2.
    • Mode 2 Reset to factory settings (LED red, quick blinking - about 3 time per second). In case the button released, STB boots in mode 2. If button not released (continue to be holded), STB will pass to mode 3.
    • Mode 3 Emergency startup (LED red, lights constantly).In case the button released, STB boots in mode 3. If continue to hold will result in standart booting (from active NAND).

Mode 1. Selecting alternative NAND

Mode 1 Selecting alternative NAND (LED white, slow blinking - about 1 time per second) leads to switching software load from alternative memory bank (NAND).
NAND1 or NAND2 - banks of internal non-volatile reprogrammable memory of STB. They are intended to store and load from them STB software. The use of two banks of memory improves reliability of software update process.  If the operation fails, user can load software from the alternative bank.

Mode 2. Reset to factory settings

Mode 2 Reset to factory settings (LED red, quick blinking - about 3 time per second) leads to reset STB to factory values. After resetting STB to the factory, the environment variables are returned to the initial values (set by the Manufacturer).

Mode 3. Emergency startup

Mode 3 Emergency startup (LED red, lights constantly) leads to download in STB Bootstrap file that contains System Recovery Utility enabling user to perform recovery operations.
Emergency startup is used if STB does not correctly load. It is applied to download in STB Bootstrap file containing the Linux kernel and System Recovery Utility. Bootstrap file may be tramsmitted in STB from USB-drive or over network from DHCP/TFTP server. After Bootstrap loaded, the System Recovery Utility menu is opened and user may take recovery actions. To download Bootstrap file, USB device is verified first (if the USB device is readable and required file is available). If first verification is failed, STB goes to receiving data by DHCP/TFTP protocol.

Emergency startup and System recovery. Bootstrap loads from USB-drive

At the PC (USB drive preparing)

  • USB-drive must have FAT32 file system
  • Download Bootstrap<model> file from release of MAG<model>, where <model> - the number value of STB (422 or 424);
  • Rename file to Bootstrap;
  • At the USB drive create mag<model > directory (it should be located in the root directory of the USB drive)
  • At the USB drive put the Bootstrap file in the mag<model number> directory;

At the STB

  • Unplug power supply of STB;
  • Connect USB-drive to any USB socket;
  • Press service button, plug the power supply and wait until mode 3 (LED red, lights constantly);
  • Release the button - Emergency startup is selected;
  • Wait for System Recovery Utility menu appearing on the TV screen;
  • In System Recovery Utility menu start recovery action:
    • load from alternative NAND;
    • reset ro factory;
    • update STB software.

Emergency startup and System recovery. Bootstrap loads from DHCP/TFTP server

Example of TFTP server configuring is given in 'DHCP server configuration. Loading and updating STB software' section, TFTP server. Installation, setup. Bootstrap file should be given from required release.
Example of DHCP server configuring (see section "MAG<model>_boot" on example MAG322) is considered in 'DHCP server configuration. Loading and updating STB software' section, Loading OS kernel (Bootstrap / uImage) via TFTP on Emergency mode.
Emergency startup and recovery actions at the STB are similar to described for Bootstrap loading from USB-drive (excepting USB drive connect).

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.