Ap 5131 Firmware Update

15-09-2021
 |  [RAND-100] - Comments

This repository contains the firmware updater (chromeos-firmwareupdate) that will update firmware images related to verified boot, usually AP (also known as BIOS or MAIN) and EC.

AP-5131 Symbol Access Point applet. A prompt displays confirming the logout before the applet is closed. 4.8 Updating Device Firmware Symbol periodically releases updated versions of the AP-5131 device firmware to the Symbol Web site. If the AP-5131 firmware version displayed on. This firmware update leverages the IEEE 802.11r/k standard, which enables fast roaming (r) and location-based triangulation (k) to determine the closest and strongest AP. Similar setups from other manufacturers may require expensive controller hardware and complex software configuration, but we’ve provided a Tech Service Bulletin to ensure.

Introduction

Auto update is one of the most important feature in Chrome OS. Updating firmware is one of the most complicated process, since all Chromebooks come with firmware that implemented verified boot and must be able to update in background silently.

Using Firmware Updater

The firmware updater was made as a “shellball”, a self-executable file containing updater logic (shell scripts), utility programs, and firmware images.

In all modes, updater will try to preserve few firmware data, for example the VPD sections (RO_VPD, RW_VPD), HWID and GBB flags (in GBB section).

Update manually

Usually you can find the updater in /usr/sbin/chromeos-firmwareupdate on a ChromeOS device (or the rootfs partition of a disk image).

To look at its contents (firmware images and versions):

Usually for people who wants to “update all my firmware to right states”, do:

The recovery mode will try to update RO+RW if your write protection is not enabled, otherwise only RW.

If your are not sure about write protection status but you only want RW to be updated, run:

The --wp argument will override you real write protection status.

Simulating ChromeOS Auto Update

The ChromeOS Auto Update (update_engine) runs updater in a different way - a two-step trial process.

If you want to simulate and test that, do:

Building Firmware Updater

The updater is provided by the virtual/chromeos-firmware package in Chromium OS source tree, which will be replaced and includes the chromeos-base/chromeos-firmware-${BOARD} package in private board overlays.

To build an updater locally, in chroot run:

If your board overlay has defined USE flags bootimage or cros_ec, chromeos-firwmare-${BOARD} package will add dependency to firmware and EC source packages (chromeos-bootimage and chromeos-ec), and have the firmware images in /build/${BOARD}/firmware/{image,ec}.bin. A “local” updater will be also generated in /build/${BOARD}/firmware/updater.sh so you can run it to test the locally built firmware images.

In other words, you can remove bootimage and cros_ec in branches that you don't need firmware from source, for example the factory branches or ToT, especially if there are external partners who only has access to particular board private overlays. To do that, find the make.conf in board overlay and add USE='-bootimage -cros_ec'.

Manipulating Firmware Updater Packages

The firmware updater packages lives in private board overlays: src/private-overlays/overlay-${BOARD}-private/chromeos-base/chromeos-firmware-${BOARD}/chromeos-firmware-${BOARD}-9999.ebuild. Find a template here in chromiumos-base/chromeos-firmware-null.

Usually there are few fields you have to fill:

CROS_FIRMWARE_MAIN_IMAGE

A reference to the Main (AP) firmware image, which usually comes from emerge-${BOARD} chromeos-booimage then /build/${BOARD}/firmware/image.bin.

Usually this implies both RO and RW. See CROS_FIRMWARE_MAIN_RW_IMAGE below for more information.

You have to run ebuild-${BOARD} chromeos-firmware-${BOARD}.ebuild manifest whenever you've changed the image files (CROS_FIRMWARE_*_IMAGE).

CROS_FIRMWARE_MAIN_RW_IMAGE

A reference to the Main (AP) firmware image and only used for RW sections.

If this value is set, CROS_FIRMWARE_MAIN_IMAGE will be used for RO and this will be used for RW.

CROS_FIRMWARE_EC_IMAGE

A reference to the Embedded Controller (EC) firmware image, which usually comes from emerge-${BOARD} chromeos-ec then /build/${BOARD}/firmware/ec.bin.

Technical Details

CROS_FIRMWARE_SCRIPT and packaging

The firmware updater is built by running pack_firmware.py, which collects firmware image and extra files, all files under pack_dist folder, archived by running shar, with a special bootstrap stub pack_stub.

Since the verified boot has been evolved with so much differences, we put the updating logic in different files according to the generation of firmware: pack_dist/updater*.sh. Most Chromebooks today should use updater4.sh.

Usually we will increase a “logic version” when the verified boot has been changed so much that the updater code for previous versions would almost won't work. Currently we have defined these versions (Use Developer Info page to find the mapping from board names to product names):

  • Version 1: (EOL) mario (CR48), using H2C BIOS.
  • Version 2: (EOL) alex and zgb.
  • Version 3: lumpy, stumpy, butterfly, stout, parrot.
  • Version 4: Everything after version 3 until now.
  • Version 5: Was created for vboot2, but now it's merged back to Version 4.

This will be mapped to what you should set in the CROS_FIRMWARE_SCRIPT value in ebuild files.

Updater logic

Here's a detailed list of how each updater mode works:

  • --mode=autoupdate: Invoked by update_engine when a payload is installed.

    1. Check if WP is enabled.
    2. If WP is enabled, update RW / inactive and exit. After system reboot. The update_engine will invoke chromeos-setgoodfirmware after 60 secs, which will update or mark booted RW firmware to active.
    3. If WP is disabled, check if the RO section is same as CROS_FIRMWARE_MAIN_IMAGE. If yes, go 2. Otherwise, do --mode=recovery.

  • --mode=recovery: Invoked by recovery shim after installed.

    1. Check if WP is enabled.
    2. If WP is enabled, update both RW/A, RW/B and exit.
    3. If WP is disabled, update whole image except reserved sections (GBB, VPD). This includes RO, RW/A, and RW/B.

  • --mode=factory_install: Used for factory initial imaging.

    1. Check if WP is enabled, and exit with failure if enabled.
    2. Update whole image except reserved sections (GBB, VPD). This includes RO, RW/A, and RW/B.

For the Firebox to update the firmware for paired APs, you must download AP firmware images to the Firebox from WatchGuard servers.

AP firmware updates are downloaded from WatchGuard servers to the Firebox over HTTPS port 443.

These instructions apply to APs managed with a Gateway Wireless Controller. For APs managed by Wi-Fi Cloud, see the WatchGuard Wi-Fi Cloud Help.

See the Current Firmware Version

Ap-5131 Firmware Upgrade

From the Gateway Wireless Controller, you can see information about the installed and available versions of AP firmware. This includes:

Ap 5131 Firmware Update Windows 10

  • The Access Point Firmware section shows the version of Access Point firmware that is available on the Firebox. This is the version of firmware the Firebox can install on a paired AP.
  • On the Access Points tab, the Version column shows the currently installed firmware version on each paired access point.

For more information about the Gateway Wireless Controller in the Fireware Web UI Dashboard pages or Firebox System Manager, see Monitor AP Status.

Manage AP Firmware

You can get the latest AP firmware from WatchGuard servers directly from the Gateway Wireless Controller.

Ap-5131 Firmware Update

To manage AP firmware, from Fireware Web UI:
  1. Select Dashboard > Gateway Wireless Controller.
  1. Click Manage Firmware.
    The Access Point Firmware dialog box appears.
  1. Review the Installed Version and Available Version for each of your AP models.
  2. To remove all AP firmware versions from your Firebox, click Remove All Firmware.
  3. To get the latest firmware for a specific AP model, adjacent to the model, click Download.
To manage AP firmware, from Firebox System Manager:
  1. Select the Gateway Wireless Controller tab.
  1. Click Manage Firmware.
    The Access Point Firmware dialog box appears.
  1. Review the Installed Version and Available Version for each of your AP models.
  2. To remove all AP firmware versions from your Firebox, click Remove All Firmware.
  3. To get the latest firmware for a specific AP model, adjacent to the model, click Download.

Motorola Ap-5131 Firmware Update

Update AP Firmware on the Gateway Wireless Controller with a Component File Package

If the Firebox that manages your APs cannot contact WatchGuard servers or uses a slow Internet connection, you can manually download a firmware update package for an AP and upload it to the Firebox. The AP firmware will then be available from the Gateway Wireless Controller to upgrade your APs.

You can download individual AP firmware updates from the WatchGuard Support Center. The zip file includes the AP firmware as a .wgpkg-dl component package file. You can upload this file to your Firebox to make the firmware update available in the Gateway Wireless Controller.

To install the component software package from Fireware Web UI:
  1. Select System > Upgrade OS.
  2. Select the I have an upgrade file option.
  3. Click Browse.
  4. Select the .wgpkg-dl file you downloaded, then click Upgrade.
To install the component software package from Policy Manager:

Ap 5131 Firmware Update Download

  1. Select File > Upgrade.
  2. Click Browse.
  3. Select the .wgpkg-dl file you downloaded, then click Upgrade.

Make sure the file browser type is set to 'all files' to be able to see any .wgpkg-dl files.

After you install the component package on the Firebox, you can install the firmware on the AP from the Gateway Wireless Controller.

To install the AP firmware from Fireware Web UI:
  1. Select Dashboard > Gateway Wireless Controller.
  2. Select the Access Points tab.
  3. Select an AP.
  4. From the Action drop-down button, select Upgrade.
  5. Click Yes to confirm.
To install the AP firmware from Firebox System Manager:Ap 5131 Firmware Update
  1. Select the Gateway Wireless Controller tab.
  2. Select the Access Points tab.
  3. Select an AP.
  4. From the Actions drop-down button, select Upgrade.
  5. Click Yes to confirm.

Options for AP Firmware Updates

There are several ways that you can upgrade the firmware on your APs:

Enable automatic firmware updates

You can configure the Gateway Wireless Controller to automatically upgrade firmware for all paired APs whenever a new version is available on the Firebox. For more information, see Configure Gateway Wireless Controller Settings.

Automatic firmware upgrades occur from 00:00 (midnight) to 04:00 based on the local time of the Firebox.

Send a firmware update to a single AP

From Fireware Web UI, you can update the firmware for APs from the Gateway Wireless Controller Dashboard page.

  1. Select Dashboard > Gateway Wireless Controller.
  2. Select the Access Points tab.
  3. Select an AP.
  4. From the Action drop-down button, select Upgrade.
  5. Click Yes to confirm.

From Firebox System Manager, you can update the firmware for APs from the Gateway Wireless Controller tab.

  1. Select the Gateway Wireless Controller tab.
  2. Select the Access Points tab.
  3. Select an AP.
  4. From the Actions drop-down button, select Upgrade.
  5. Click Yes to confirm.

Do not interrupt the power to the AP while the firmware upgrade is in progress. Interruption of power during a firmware upgrade can cause the AP to start in failsafe mode. When the AP is in failsafe mode, the Access Point web UI provides a single option that enables you to upgrade the device firmware. For more details about AP failsafe mode and recovery, see the WatchGuard Knowledge Base.