Problem
"A Firmware Loader error occurred: <Location Code/Message>"
Solution
This is not an exhaustive list of causes, but some common or reoccurring sources of these particular errors.
| Expand |
|---|
| title | A CRC checksum error occurred during data transmission. |
|---|
|
- One or more connected drives has an unknown or corrupt firmware image. Connect each drive individually to narrow down the problem. An RMA can be created to return the drive for evaluation/repair.
- You are attempting to upgrade directly from an early 2.xx version of A3200 to 6.xx. Create a technical support case to determine whether the drive in question is capable of upgrading. Compatible drives must upgrade in steps, first to 2.55, then to 6.xx.
- One or more connected drives are "firmware locked". The firmware is locked from the factory and cannot be modified.
|
| Expand |
|---|
| title | One or more drives reported an incorrect controller family. |
|---|
|
- One or more connected drives does not have A3200 firmware. The following drives are compatible with both A3200 6.04 and Automation1: XC2, XC4, XC4e, XR3, XL4s, GL4
- To convert a drive from Automation1 to A3200, see "Legacy Control Systems" under Automation1 FAQ on the website. This conversion will require an installation of the Automation1 software.
|
Related articles
| Content by Label |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | AKB |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label in ("a3200","firmware","error","loader") and type = "page" and space = "AKB" |
|---|
| labels | a3200 firmware loader error |
|---|
|