What is the special firmware upgrade process for version 4.0.0.0 on external Evolution products?

This upgrade process will only be necessary the first time you upgrade your EDS from version 2.x or 3.x to 4.x. This upgrade will maintain all configuration on the EDS including IPaddress and now combines the Web Manager files with the firmware. Any subsequent firmware upgrades of 4.x or later will be done normally.

If you are upgrading from v2.x or v3.x to any version higher than v4.0.0.0 you must first load v4.0.0.0. Attempting to upgrade directly from an earlier version to v4.1.0.2 or higher will cause the EDSxPR to stop functioning. If this happens, the only resolution is to replace the EDSxPR. If the EDSxPR is out of warranty you will need to purchase a new unit.

V4.0.0.0 contains an upgraded Boot Loader, which must be loaded onto the device after the new firmware has been upgraded. After the new firmware is flashed and the device reboots, further firmware upgrades will be forbidden until the bootloader is upgraded as described in the process below. Click here to download v4.0.0.0.

If the links above do not work with your browser, copy and paste this URL into the address field: V4.0.0.0 Firmware for the XPort-AR, EDS4100, EDS8, EDS16PR and EDS32PR

Note: Any subsequent firmware, version 4.x and later, upgrades for the EDS will have a file name ending with .romz - The .rom.gz file is for the first upgrade to 4.x only.

Note: Customer files will be lost during this conversion process. Only Evolution configuration files will be restored. Back up any customer created files in the EDS's file system by using ftp or tftp to copy them to another host before proceding with this procedure.

To upgrade an EDS, follow these steps:

1. Issue a filesystem compact command from telnet to the CLI.

From a DOS prompt type:

C:\telnet xxx.xxx.xxx.xxx (x = ipaddress of the EDS)

At the > prompt type:

>enable
>(enable)# filesystem
>(filesystem)# compact
Data could be lost if power is cycled during this process
Do you want to compact (yes/no)? yes
compacting filesystem...
(wait for the prompt to return)
>(filesystem)# exit
>(enable)# exit

This will help ensure the integrity of the hidden configuration files.

2. Upload the firmware image filename_of_eds.rom.gz (e.g. eds16pr.rom.gz) and wait for the device to reboot automatically.

From the folder where the firmware files reside at a DOS prompt type the following commands to log into the EDS's ftp server. set it to Binary mode and transfer the *.rom.gz file:

C:\EDS> ftp xxx.xxx.xxx.xxx (x = ipaddress of the EDS)

Connected to xxx.xxx.xxx.xxx
220 FTP server ready
User <xxx.xxx.xxx.xxx:<none>>: admin
331 Password required.
Password: PASS
230 User logged in.
ftp> bin
200 command okay
ftp> put filename_of_eds.rom.gz

The EDS will reboot automatically. When finished you can FTP to the EDS again and follow the next step.

3. Upload filename_of_eds_boot.romz bootloader file (e.g. eds16prboot.romz).

From the folder where the firmware files reside at a DOS prompt type:

C:\EDS> ftp xxx.xxx.xxx.xxx (x = ipaddress of the EDS)

Connected to xxx.xxx.xxx.xxx
220 FTP server ready
User <xxx.xxx.xxx.xxx:<none>>: admin
331 Password required.
Password: PASS
230 User logged in.
ftp> bin
200 command okay
ftp> put filename_of_eds_boot.romz

The EDS will reboot automatically. When finished you can FTP to the EDS again and follow the next step.

4. Then upload the firmware image filename_of_eds.romz (e.g. eds16pr.romz) and wait for the device to reboot automatically.

From the folder where the firmware files reside at a DOS prompt type:

C:\EDS> ftp xxx.xxx.xxx.xxx (x = ipaddress of the EDS)

Connected to xxx.xxx.xxx.xxx
220 FTP server ready
User <xxx.xxx.xxx.xxx:<none>>: admin
331 Password required.
Password: PASS
230 User logged in.
ftp> bin
200 command okay
ftp> put filename_of_eds.romz

The EDS will reboot automatically.

When this firmware is flashed to the device, upon the first boot, the following automatic upgrade procedure is performed:

1. Detection of possible filesystem changes
2. Backup of all hidden configuration files (all other files on filesystem are lost, including web file directory)
3. Format of filesystem to new format and/or location
4. Restore of all hidden configuration files to newly formatted filesystem

[Originally Published On: 10/16/2007 06:02 AM]