Release Notes: ESP Flash Components for Windows
Installation Instructions
This release package provides the download flash components for the Equinox standard, 10/100 and Multi-Interface ESPs. It should be noted that the flash components are the same for all server OS types. However, this package is provided for easy installation on Windows based systems.
Expected Usage
It is expected that this package will be used to augment an existing ESP driver package (for Windows NT, Windows 2000). This package is used to upgrade the ESP flash components without altering the existing driver package.
Components
- espapp.img, version 3.05d (ESP embedded application image)
- espboot.img, version 3.50 (standard ESP bios/bootstrap image)
- espbootb.img, version 3.61 (Multi-Interface ESP bios/bootstrap image)
- espbootc.img, version 3.80 (10/100 ESP bios/bootstrap image)
- INSTALL.exe
Installation of Package
The following are the steps to install this package:
1. Download espappwin_3.05d.exe (to any temporary directory).
2. Run espappwin_3.05d.exe and click on unzip.
3. Files will be unzipped to c:\temp unless you specify another folder.
4. Install.exe will be executed automatically to copy files to the appropriate WINDIR\system32\drivers directory. Or uncheck option to run install.exe, so you can run it later.
5. Install.exe will display new versions of the files installed.
After installation, the temporary directory and its contents may be removed.
Flash Updating the ESP
Instructions for performing the flash update using EquiView Plus are available in the documentation. It is important to update the BIOS/Bootstrap BEFORE the Application.
The correct steps are:
- Upgrade to EquiView Plus 4.5 or later
- Using EquiView Plus, update the ESP BIOS/Bootstrap to version 3.80 (10/100) or update the ESP BIOS/Bootstrap to version 3.61 (Multi-Interface ESPs) or update the ESP BIOS/Bootstrap to version 3.50 (standard ESP)
- Reboot the ESP
- Using EquiView Plus, update the ESP Application to version 3.05d
- Reboot the ESP
BIOS/Bootstrap files ESPBOOT version 3.50, ESPBOOTB version 3.61, ESPBOOTC version 3.80, and ESP Application version 3.05d are installed on the NT server with this ESP release, but each ESP's FLASH must also be updated as described above. You may also use the new 'Update Flash' feature in the Network Control panel if you are not using EquiView Plus. Refer to the online help for the 'Update Flash' wizard of the Device Manager.
NOTE: If you are upgrading an ESP that is installed on a remote LAN segment with any 1.xx version of the ESP application firmware, it will be necessary to upgrade that ESP's FLASH from an NT system that is on that remote LAN segment. Prior to release 2.0x, the ESP did not support FLASH update from a LAN segment located on a remote network.
Release Notes
-
ESPAPP.IMG Version 3.05d
- The ESP has been corrected to operate serial ports correctly at 2400 baud. When running the datascope in EquiView Plus, the ESP will now forward data within 10 seconds of the first write to the file after it is created. It does not affect operation of the maximum size or the inter-character forward timeout. However, it corrects a problem where the maximum size is large and characters are arriving regularly enough so that the inter-character timer never
expires. Previously, no data would be forwarded in this case until the maximum file size was reached. Now, the data will be forwarded at least every 10 seconds.
-
- Upon loss of Ethernet LINK, a UDP timeout will be declared on all active TCP connections for which the UDP timeout is declared to be 4 seconds. The customer MUST set the HeartBeatTimeout to 4 to activate this feature.
- The time to notice a UDP timeout has been reduced. In previous versions, it may have taken as long as 5 seconds, regardless of the frequency and timeout settings provided by the TCP host that connected.
- When a UDP Heartbeat timeout occurs, the ESP will now drop the DTR and RTS control signals on every open serial port.
-
BIOS/Bootstrap Version 3.80
- Update the CPSBOOT.IMG and ESPBOOTC.IMG to correct an error in the BOOTP REPLY processing. During BOOTP Reply processing, the CPS bootstrap required the BOOTFILE option to contain two filenames separated by a comma. This was required for ESP/CPS manufacturing, but is not needed when the unit is deployed at a customer. The edits on the BOOTP REPLY response were being applied in both the customer and manufacturing modes. This means that the user could not
correctly assign an IP address to a CPS with BOOTP unless the BOOTFILE option was correctly provided. The data provided was not used, but had to be present.
-
BIOS/Bootstrap Version 3.61
- Corrected a problem with switches that use the spanning tree algorithm. Customers report that these switches block transmission of Ethernet packets from devices that establish LINK with the switch. From the time that LINK is established, the switch will block transmission of Ethernet packets for up to 30 seconds. As such, BOOTP request for IP address and TFTP requests for flash update will fail. This is because these are tried for less than 30 seconds.
Because Ethernet packets transmitted to the switch are discarded, the BOOTP and TFTP requests never reach the intended server. The correction is to BOOTP for up to 45 seconds and to TFTP up to 45 seconds before declaring a failure. This will elongate ESP and CPS initialization time, but is the only way to solve this problem.
-
BIOS/Bootstrap Version 3.50
- The bootstrap images for ESP 10/100 and ESP Multi-Interface have been enhanced to support compressed application image files.
- The bootstrap images have been enhanced to support more comprehensive DRAM testing.
|