Important Notes on Firmware Upgrade

Only PCIe physical devices may operate the FW upgrade. PCIe virtual devices will be excluded by the upgrade script.

The User must stop all transcoding processes before performing a firmware upgrade, otherwise it may lead to a device malfunction.

Each device will check the file integrity of the Firmware binary before committing to use it.

Before any temp upgrade, the device will check the Firmware binary version. The temp upgrade feature requires both the firmware version on the nor flash as well as the firmware binary the device is updating to, to be v5.1.5 or higher.

For temp upgrade, the device will also check the firmware flavor. Both the proposed new temp upgrade firmware binary and the binary currently loaded on to the nor flash must match. If the firmware flavors do not match the temp update will be rejected.

The User must NOT interrupt the upgrade process once it has started, doing so may lead to a device malfunction. If the cold upgrade fails, a system reboot may resolve the issue, the upgrade process should then be repeated.

Additional logs on the upgrade process can be found in ./upgrade_log.txt which is generated by the upgrade script.

The behavior of the warm upgrade process is identical to that of the cold upgrade except a system reboot is not required. If the warm upgrade fails, a system reboot will resolve the issue, and then the warm upgrade process can be repeated. However, if warm upgrade repeatedly fails then a cold upgrade and reboot should be used.

The temp upgrade is reverted when the device is reset. Temp firmware upgrade is a temporary state only and the firmware in the nor flash will be loaded and executed on reboot. If the temp upgrade fails the drive is unaffected, and will continue to execute the firmware in the nor flash.