Firmware TCP/IP Upgrade using
covers the TCP/IP procedures required for upgrading the
firmware version of all Microplex products (with flash
PROMs), using the TFTP protocol.
demonstration purposes only, the following
assumptions and values will be used for the
TCP/IP upgrade steps given below;
this document the Microplex product being
upgraded is represented by <prod>,
some examples are;
<prod> is being upgraded
to the latest firmware level.
<prod> uses the IP address
TFTP server (i.e. host running the TFTP
daemon and containing the upgrade files)
is a Unix host and uses IP address
TFTP server uses the directory
"/tftpboot" as the common
directory for TFTP files based on the
"tftp" line in
the required upgrade files for the
Microplex product you are upgrading (see
Upgrade Files" section),
and place them on to your TFTP host
server. You will need;
binary file (e.g. <prod>_dl.hex.zip)
binary file (e.g. <prod>.hex.zip)
these binary files which were downloaded
in ZIP format (e.g. <prod>.hex).
these uncompressed binary files into the
"/tftpboot" directory with
global read permissions.
- If using
a Unix host as the TFTP server in
this process, you will need to
look at the "tftp" line
in the file
find out the best place for these
- If you
see a "-s" option
followed by a directory at the
end of this line, you will need
to place the upgrade files into
this directory specified.
- If you do
not see a "-s" option
at the end of this line, then you
can safely assume that the files
need to sit at root or in a
with open permissions.
- If using
a PC as the TFTP server in this
process, look to your product
documentation for your TCP stack
or TFTP service to find out where
to place these files.
to the <prod> you are
upgrading and log in as "root".
this telnet session, put the <prod>
into upgrade mode by typing
- The <prod>
will automatically reset
itself meaning you will lose your
30 seconds, log back into the <prod>
you are upgrading again (as in step
4). A message should appear telling you
the unit is now in upgrade mode, for
character is '^]'.
Version 1.0 (18.104.22.168)
Unit is in firmware upgrade mode.
the downloader program by typing the
following command at the command prompt:
following is presented as an
this command, you will see output similar
- Download <prod>_dl.hex
from 22.214.171.124 ? (y/n) y
resolving ethernet address for
reading file <prod>_dl.hex
/ got 133646 bytes
firmware upgrade ? (y/n)
shows that the downloader program now
wants to get the firmware file. Enter
"y" to continue with the
telnet session will be closed by
the <prod> being
upgraded after pressing
- You will
not see any further diagnostic
the <prod> undisturbed for
at least 5 minutes. During this time,
the <prod> will reprogram
it's flash memory as follows;
- The new
firmware file is read twice.
the first pass, it validates the
- If the
first pass succeeds, it then
reads the file and writes the
contents to flash memory.
not disturb this upgrade process
or else the flash memory may get
corrupted. However, if
you find the upgrade process takes
longer than 30 minutes,
you're only choice may be to
reset the product. Usually an
upgrade taking this long means
the unit could not find the
firmware file so the flash memory
activity may not have taken
place. This means the flash may
not get corrupted with a reset but
be sure to wait the 30 minutes
before doing this!
the <prod>, you should see
the LED labelled "STAT"
flashing quite regularly, and the LED
labelled "NET" should be on
most of the time indicating network
the <prod> flash memory
has been upgraded, it will automatically
restart and you should notice that the
LED labelled "STAT" will only
flash once per second again (after
waiting one minute).
you'd like to test whether the upgrade procedure
has completed or not, you can try telnetting to
the <prod> after a few minutes.
it refuses the connection, it's still
working on the upgrade.
it allows you in, log in as root and
execute "list sysinfo" to check
for the new firmware level.
find the same version exists after telnetting
back in and checking the firmware level, try
resetting the <prod> by unplugging
and plugging it back in and then check again.
run into upgrade problems, please contact
Microplex Technical Support for additional help.
Microplex products can be upgraded across
routers, meaning if the unit sits on one subnet,
the TFTP server does not have to be
sitting on the same subnet.