Updating to firmware 9.2c or higher may fail on SNAP-PAC-R units

Applies To:

PAC Manager when updating firmware for:

SNAP-PAC-R1
SNAP-PAC-R1-B
SNAP-PAC-R2

Versions Affected:

PAC Manager versions R9.2c and lower when updating any firmware version to R9.2c or higher

Resolved In Version:

R10.6a (see Resolution below)

Symptoms:

NOTE: If your controller is secured with a private key through PAC Terminal Secure Strategy Distribution (SSD), see NOTES for SSD (below).

Attempts to download firmware version 9.2c or higher to a SNAP-PAC-R1, -R1-B, or -R2 controller may fail, with or without displaying a message. Messages that may be reported include:

"'Response' file is empty. Probable cause - not enough file space"
"File load failure: Memory allocate/flash"
"Invalid CRC in file"
The firmware update may fail and not show any errors.

NOTES for SSD

When a controller is programmed with a private key through PAC Terminal SSD*, you may see similar symptoms if you did not first digitally sign the firmware. For instructions to digitally sign the firmware, see the Using Secure Strategy Distribution Technical Note (form 1762), which was provided when you purchased PAC Terminal SSD.

If the firmware is already digitally signed and you are still experiencing this issue, follow the steps in the Workaround section below.

* To determine if your controller is configured for SSD:

In PAC Manager, click Tools > Inspect.
Select Other, and then set:
- The Address field to F4080004.
- The Type to 32-Bit Integer.
- The Length to 1.
Click Refresh.
If the resulting value is 2, the controller is configured for SSD.

Workaround:

Use the current version of PAC Manager, which can be installed independently from any other PAC Project application or versions.

Resolution:

The current version of PAC Manager has been updated to address this issue, including the use of a special intermediate "bridge" firmware file when necessary.

Questions?

Contact: Opto 22 Product Support.
Phone: 800-835-6786 or 951-695-3080
Email: support@opto22.com

DISCLAIMER

This Opto 22 Knowledge Base ('OptoKB') article is intended to provide general technical information on a particular subject or subjects and is not an exhaustive treatment of such subjects. Accordingly, the information in this OptoKB article is not intended to constitute application, design, software, or other professional engineering advice or services. Opto 22 may modify the OptoKB articles at any time. Before making any decision or taking any action which might affect your equipment, you should consult a qualified professional.

OPTO 22 DOES NOT WARRANT THE COMPLETENESS, TIMELINESS, OR ACCURACY OF THE DATA CONTAINED IN THIS OPTOKB ARTICLE AND MAY MAKE CHANGES THERETO AT ANY TIME AT ITS SOLE DISCRETION WITHOUT NOTICE. FURTHER, ALL INFORMATION CONVEYED HEREBY IS PROVIDED TO USERS 'AS IS.' IN NO EVENT SHALL OPTO 22 BE LIABLE FOR ANY DAMAGES OF ANY KIND INCLUDING DIRECT, INDIRECT INCIDENTAL, CONSEQUENTIAL, LOSS PROFIT, OR DAMAGE, EVEN IF OPTO 22 HAS BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGES.

OPTO 22 DISCLAIMS ALL WARRANTIES WHETHER EXPRESSED OR IMPLIED WITH RESPECT TO THE INFORMATION (INCLUDING HARDWARE, SOFTWARE, AND/OR FIRMWARE) PROVIDED HEREBY, INCLUDING THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTIBILITY, AND NON-INFRINGEMENT. Note that certain jurisdictions do not sanction the exclusion of implied warranties: thus, this disclaimer may not apply to you.