Reference Manual

05-4446A01, Rev. E Mercury Reference Manual 131
5. Download the firmware file from the TFTP server into the trans-
ceiver.
(Main Menu>>Maintenance Menu>>Reprogramming Menu>>Retrieve File)
Status messages on the transfer are posted on the Management Sys-
tem screen.
NOTE: The new firmware image file that replaces the “Inactive
Image” file is automatically verified.
6. Reboot the transceiver.
Main Menu>>Maintenance Menu>>Reprogramming Menu>>Reboot Device
7. Test the transceiver for normal operation.
End of Procedure
Error Messages During File Transfers
It is possible to encounter errors during a file transfer. In most cases,
these can be corrected by performing the actions described in
Table 3-9.
Configuration Scripts Menu
A configuration script file contains all of a radio’s setable parameters
that are accessible through the menu interface, with a few exceptions. A
configuration script file is in plain text format and can be easily edited
in any text program.
Configuration scripts can be helpful in several ways. Three common
uses for them are:
Table 3-9. Common Errors During TFTP Transfer
Error Message Likely Cause/Corrective Action
Invalid File Type Indicates that the file is not a valid firmware
file. Locate proper file and re-load.
File not found Invalid or non-existent filename on TFTP
server.
Invalid file path Invalid or non-existent file path to TFTP
server.
Timeout TFTP transfer time expired. Increase the
timeout value.
Flash Error Flash memory error. Contact factory for
assistance.
Bad CRC Cyclic Redundancy Check reporting a
corrupted file. Attempt to re-load, or use a
different file.
Version String Mismatch Invalid file detected. Attempt to re-load, or use
a different file.