EDS Firmware upgrade notes for V4.1.0.2
How do load v4.1.0.2 onto an EDS4100, EDS8PR, EDS16PR, EDS32PR, EDS8PS or EDS16PS?
Due to changes in the memory allocation and operating system of the EDS, the following procedure must start with an EDS running v.4.0.0.0.
If you are running firmware earlier than v4.0.0.0 follow the procedure in this article, then return to this article:
A Special Upgrade Process For External Evolution Products For Version 4.0.0.0
If you are running v4.0.0.0, download V4.1.0.2 from the links provided below.
| Device Name | Firmware | Bootloader | Release Notes |
|---|---|---|---|
| EDS4100 | eds4100.romz | eds4100boot.romz | EDS4100 V4.1.0.2 Release Notes.txt |
| EDS8PR | eds8pr.romz | edsprboot.romz | EDSPR V4.1.0.2 Release Notes.txt |
| EDS16PR | eds16pr.romz | ||
| EDS32PR | eds32pr.romz | ||
| EDSxPS | edsps.romz | edspsboot.romz | EDSPS V4.1.0.2 Release Notes.txt |
PLEASE FOLLOW THIS PROCESS. Should a failure occur the unit will be unreachable on the network and you may not be able to recover.
To upgrade from v4.0.0.0 code v4.1.0.2, follow the procedure below. In the file names below, eds[x] indicates the prefix of the file you downloaded for your model of EDS:
- Open or connect to the Evolution Web manager either via the device installer's web configuration or by opening a browser and typing in the IP address of the EDS.
- Type in the username and password. They are admin and PASS by default.
- From the orange menu options on the left, select System
- Under Upload New Firmware select Browse and navigate to the file eds[x].romz you downloaded in the first part of this article
- Click Upload. The file will automatically load and the EDS will reboot.
- When the EDS has finished rebooting, return to System in the Evolution web manager and navigate to the eds[x]boot.romz file as in step 4.
- Click Upload. The file will automatically load and the EDS will reboot.
- When the EDS finishes rebooting, return to System in the Evolution web manager and Upload the eds[x].romz (again) as in step 4. (This must be done because the bootloader reorganizes the memory partition.)
NOTE: Use the DeviceInstaller serial recovery method to attempt to recover from a failed upgrade. See: DeviceInstaller firmware serial recovery procedure
[Originally Published On: 03/25/2011 02:54 PM]