Impinj Inc. XARRAY 사용자 설명서
Speedway Revolution Installation and Operations Guide Octane 4.11
Chapter 4: Upgrading Firmware
Chapter 4: Upgrading Firmware
26
Revision 4.11 Copyright ©2014, Impinj, Inc.
Chapter 4: Upgrading the Speedway Revolution
Firmware
Firmware
Speedway Revolution contains firmware known as Octane. The current version of Octane is
4.10. This chapter details manually upgrading a single Reader.
In addition to supporting upgrade procedures, Speedway Revolution also provides methods
for reverting firmware to a previous valid image and restoring firmware to factory default
settings. The procedure for reverting to the
4.10. This chapter details manually upgrading a single Reader.
In addition to supporting upgrade procedures, Speedway Revolution also provides methods
for reverting firmware to a previous valid image and restoring firmware to factory default
settings. The procedure for reverting to the
is explained in Chapter 5 on page 31.
A Brief Overview of the Speedway Revolution Firmware
To minimize downtime and maximize the robust handling of possible upgrade failures,
Speedway Revolution contains dual images of its firmware. When requesting a firmware
image upgrade, the Reader continues to operate using the primary image. In the
background, Speedway Revolution upgrades the secondary image. When the upgrade
completes, the Reader reboots to the newly upgraded image. Speedway Revolution retains
the previous firmware version in case there are problems with the upgrade.
There are three individual partitions within each firmware image that logically organize the
system software. Although you do not need a full understanding of this architecture to
perform a simple manual upgrade, it is a good idea to be familiar with its structure at a high
level. For a more in-depth discussion of the firmware and how firmware is organized, see
the Embedded Developer’s Guide.
The three partitions in firmware are:
Speedway Revolution contains dual images of its firmware. When requesting a firmware
image upgrade, the Reader continues to operate using the primary image. In the
background, Speedway Revolution upgrades the secondary image. When the upgrade
completes, the Reader reboots to the newly upgraded image. Speedway Revolution retains
the previous firmware version in case there are problems with the upgrade.
There are three individual partitions within each firmware image that logically organize the
system software. Although you do not need a full understanding of this architecture to
perform a simple manual upgrade, it is a good idea to be familiar with its structure at a high
level. For a more in-depth discussion of the firmware and how firmware is organized, see
the Embedded Developer’s Guide.
The three partitions in firmware are:
1. System Operating Partition (SOP)—The SOP is the primary system partition of
the Speedway Revolution Reader. It contains the Linux kernel, FPGA firmware, RFID
management software, Reader management software (RShell), logging management
software, firmware upgrade control, system watchdog software, and the factory
default data.
management software, Reader management software (RShell), logging management
software, firmware upgrade control, system watchdog software, and the factory
default data.
2. System Persistent Partition (SPP)—Files in this partition are automatically
generated and maintained by the software running on the Reader. It contains the
Reader configuration (network settings, LLRP configuration, log settings, and so on),
Reader logs, and debug information used by Impinj engineers.
Reader configuration (network settings, LLRP configuration, log settings, and so on),
Reader logs, and debug information used by Impinj engineers.
3. Custom Application Partition (CAP)—CAP partition contains custom application
software, other items required by the custom application (extra libraries or tools, and
configuration files), plus custom application logs.
configuration files), plus custom application logs.
Upgrading the Firmware
Speedway Revolution provides three methods for upgrading:
1. Using RShell, command line interface.
2. Copying the firmware to a USB memory drive and plugging into the Reader‘s host
2. Copying the firmware to a USB memory drive and plugging into the Reader‘s host
port.
3. Via the web interface.