6. Firmware Upgrade and Configuration Management
ROS® v3.11User Guide
108
RMC30
tftp <TFTP server> get <remote filename> main.bin
where:
• TFTP server is the IP address of the TFTP server
• remote filename is the name of the binary image file of the main ROS® application firmware
residing in the TFTP server outgoing directory
Verify, as above, the successful transfer via the ROS® CLI “version” command. A sample
transcript from the ROS® CLI:
>tftp 10.0.0.1 get ROS®-CF52_Main_v3.7.0.bin main.bin
TFTP CMD: main.bin transfer ok. Please wait, closing file ...
TFTP CMD: main.bin loading succesful.
>version
Current ROS®-CF52 Boot Software v2.14.0 (Sep 29 2008 13:25)
Current ROS®-CF52 Main Software v3.6.0 (Oct 03 2008 09:33)
Next ROS®-CF52 Main Software v3.7.0 (Jun 02 2009 08:36)
6.4.6. Upgrading Firmware Using SFTP
This method requires that the binary image file of the main ROS® application firmware, along
with SFTP client software, be available on a computer with a network connection to the ROS®
device to be upgraded. SFTP is the Secure File Transfer Protocol (also known as the SSH
File Transfer Protocol), a file transfer mechanism that uses SSH to encrypt every aspect of
file transfer between a networked client and server.
Establish an SFTP connection with administrative privileges to the ROS® device to be
upgraded. Begin a transfer to the device, specifying a destination filename of “main.bin”. An
SFTP client utility will provide an indication that the file was transferred properly, but, again, it is
recommended to also query the device directly in order to verify successful transfer. A sample
SFTP session to upgrade the ROS® main firmware image from a Linux workstation follows:
user@host$ sftp admin@ros_ip
Connecting to ros_ip...
admin@ros_ip's password:
sftp> put ROS®-CF52_Main_v3-7-0.bin main.bin
Uploading ROS®-CF52_Main_v3-7-0.bin to /main.bin
ROS®-CF52_Main_v3-7-0.bin 100% 2139KB 48.6KB/s 00:44
sftp>
6.5. Updating Configuration
ROS® maintains its complete configuration in an ASCII text file, in CSV (Comma-Separated
Value) format. All configuration changes, whether they are performed using the web interface,
console interface, CLI, SNMP, or SQL, are stored in this one file. The file, named config.csv,
may be read from and written to the ROS® device in all the same ways that firmware image
files can, as described in the preceding sections. The configuration file may be copied from
the unit and used as a backup, to be restored at a later date. Configuration files from different
units may be compared using standard text processing tools.
The transfer mechanisms supported for the update of config.csv are the same as for ROS®
firmware image files: