
889-3809-02
Model 2018E Operations Manual Rev Apr 2020 Page
39
of 39
Section 5
Firmware Upgrade
The firmware for the main microprocessor in the Model 2018E can be upgraded via the front panel COMM port.
The most current version of firmware is available on the Reno A & E web site (www.renoae.com) in the support
section. Firmware upgrades to the monitor are accomplished through the use of the RaeComM software, version
3.0.7 or greater.
There are three separate firmware files that can be upgraded for the main microprocessor in the monitor.
Main Code: This is the code (firmware) that runs the monitor under normal conditions. In most cases, this is the
only file that must be upgraded and ends with BOOTCODE.RAE if more that one file is in the downloaded file.
Secondary Boot Loader: This is the code that is responsible for allowing firmware upgrades if the main code
(boot code) is corrupt or becomes corrupt during the programming process and ends with BOOTLD2.RAE.
Primary Boot Loader: This is the code that is responsible for allowing firmware upgrades if the secondary boot
loader is corrupt and ends with BOOTLD1.RAE. This file can only be upgraded by a user with factory level
privileges.
The two boot loaders exist to allow the monitor to recover from problems during the upgrade process (power fail
during programming, computer crash during programming, etc.). They should not need to be upgraded, but
provisions to do so have been made in case they need to be upgraded.
To upgrade the main code:
1)
Ensure that RaeComM version 3.1.0 or greater is installed on the computer to be used during the upgrade
process.
2)
Download the latest main code file for the monitor to be upgraded from the Reno A&E web site
(www.renoae.com).
3)
Connect the monitor to the computer through the
COMM PORT.
4)
Start the RaeComM program.
5)
Ensure that the RaeComM software can communicate with the monitor to be upgraded by clicking on
IDENTIFY
in the menu and observing that the monitor is correctly identified by the program.
6)
On the
CONFIG
menu choose
UPGRADE FIRMWARE
.
7)
On the Code Loader form that appears, click on the file folder icon after the file name.
8)
Select the file that was just downloaded from the Reno A&E web site. If more than one file was in the
downloaded file, select the one ending with BOOTCODE.RAE.
9)
If the file you selected is the correct file for the attached monitor, the Upgrade Firmware form will show
the current version of firmware in the monitor and the version that is about to be transferred.
10)
If this is correct, click on the
UPGRADE FIRMWARE
button and the process will begin. The red LED
on the front panel labeled
DIAG FAIL
will begin to flash at a 5 Hz rate to indicate that the transfer
process is underway.
11)
If an error is encountered once the transfer has begun, RaeComM will automatically retry the transfer
process up to five times. Do not cycle power to the monitor if an error is encountered. Attempt the
transfer again by closing the Upgrade Firmware form and repeating Steps 6 through 10.
12)
Wait a few seconds to ensure that the RaeComM software does not automatically start another upgrade
process (this will happen if the boot loaders need to be upgraded and is automatic). Once the transfer is
complete, the red LED on the front panel labeled
DIAG FAIL
will begin to flash at a 1 Hz rate to indicate
a pending code change (i.e. new code has been downloaded but not implemented).
13)
Cycle power to the monitor to begin running the new code. The pending code change indication will
cease.
IMPORTANT Do not interrupt power to the monitor during the programming process. This will corrupt the
firmware being transferred!
Each firmware file is encrypted and contains information identifying what model monitor it can be used in and
what type of firmware it is. This ensures that the user cannot inadvertently upgrade a monitor with the incorrect
firmware and that the firmware file has not been tampered with.