American access system ADV-1000 Guía de usuario Pagina 26

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 65
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 25
Speedway Reader IPJ-R1000 for Gen 2 UHF RFID
26
section 7.5.2.1.
6.9.2. Upgrade decision
Not all upgrade attempts will result in an actual upgrade, even if the upgrade file is valid. The reader’s upgrade decision is
based on the following factors:
The image versions of the SOP and CAP partition of the primary image.
The image version(s) of the partition(s) in the upgrade metafile and the upgrade image files downloaded, as well as
the number of partitions present.
The image type of the primary image, as well as the type indicated by the image metafile and upgrade file.
The upgrade mode, forced or auto, as indicated in the upgrade metafile.
In auto upgrade mode, the upgrade will happen only when either one of the following is true:
The upgrade image has the same type as the primary image and at least one partition in the upgrade image has a
version higher than the corresponding version in primary image. In this case the partition in the upgrade file that has
lower version number than the one in primary image will not be used, instead the current primary partition will be
kept.
The upgrade image has different image type from the primary and SOP is present in the upgrade file.
In forced upgrade mode, an upgrade will happen as long as at least one partition in upgrade file has a different version from the
primary image. If the upgrade is started with config image upgrade command, the upgrade is always performed regardless of
version numbers.
6.9.3. Partition copy-over
The upgrade image file does not necessarily contain all the partitions. The missing partition(s) will be copied over to the
secondary image from the primary image upon reboot after upgrade whenever applicable. The behavior is as follows:
If the upgrade file has image type same as the primary image, then
If the upgrade file contains SOP only, primary SCP and CAP (if present) are copied over.
If the upgrade file contains SOP and CAP, primary SCP is copied over.
If the upgrade file contains CAP, the primary SOP and SCP are copied over.
If the upgrade file contains SOP and SCP, primary CAP, if present, is copied over.
Else if the upgrade file has a different image type from the primary image, no partition is copied over. The new
image will use the factory default configuration if there is no SCP in the upgrade file.
Such copy-over behavior allows the current configuration and custom application to be carried over to the new image after an
upgrade.
6.9.4. Image partitions already programmed
There are cases when the partitions in the upgrade file are already on the secondary image. For example, when a reboot is
scheduled in 10 hours following a successful upgrade and the reader is pulling the metafile every 10 minutes, it will find that
the same partitions in the metafile already programmed on the secondary image. To avoid unnecessary programming of flash,
the reader checks if any or all of the intended partitions are already programmed and the behavior in these cases is as follows:
If the upgrade file contains SOP only and it is already on the secondary image, there is no reprogramming of flash
except for marking the primary SCP, and CAP if present, to be copied over upon reboot after upgrade. (See section
6.9.3)
If the upgrade file contains SOP and CAP and both are already on the secondary image, there is no reprogramming of
flash except for marking the primary SCP to be copied over upon reboot after upgrade.
If the upgrade file contains CAP only and it is already on the secondary image, the primary SOP is copied to
secondary image and the primary SCP is marked as to be copied over upon reboot after upgrade.
Note that these behaviors only apply to automatic upgrades performed via the periodic pull method with auto or forced upgrade
mode. When the upgrade is manually pushed with the config image upgrade command, the flash is always programmed with
the upgrade image regardless of the versions on the primary and secondary images.
Vista de pagina 25
1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 64 65

Comentarios a estos manuales

Sin comentarios