flashsvf(1M)flashsvf(1M)Nameflashsvf - EEPROM update utility for SGI FPGA based boards
SYNOPSIS
/usr/sbin/flashsvf [--l2 hostname|IP]
[--sysname name] [--ssn serial_number] [--interface name]
[--serial host:port] [--dev device_name] image_name
rack.slot
/usr/sbin/flashsvf -version|-v image_name
Additional host OS command formats:
/usr/sbin/flashsvf [-f] [--sc] [--scdev device_name] image_name
rack.slot
DESCRIPTION
The flashsvf utility updates the configuration EEPROM on a FPGA based
board. The only currently supported board is the IO9 Base I/O card.
flashsvf supports updates via three methods:
- ethernet connection to an L2 controller
- direct USB connection to a L1 controller
- direct from the host OS on the system to be updated. (Default on IRIX
or Linux)
Valid command line options are:
-version|-v image_image
Return the version number and build time of the specified image.
--l2 hostname|IP
Connect to the L2 controller with the specified hostname or IP
address.
--ssn serial_number
Search for an L2 with the System Serial Number serial_number, and
connect to the first one found.
--sysname name
Search for an L2 with the System Name name, and connect to the first
one found.
Page 1
flashsvf(1M)flashsvf(1M)--interface name
When searching for an L2 Controller to connect to, only search on
the specified network interface (i.e. eth0, eth1, etc.) This option
is ignored when --l2, --serial, or --dev is specified.
--serial host:port
Connect to the controller via a serial (SMP) connection to the Annex
box host on network port port (port number of the connection to the
Annex box plus 7000).
--dev device_name
Connect to the controller via a direct serial (SMP) connection to a
serial port on the system where flashsvf is running.
--sc Connect via the system's own System Controller network. This option
allows the power bay flash memory firmware to be updated from the
host OS. This option selects causes flashsvf to connect to the L1
Controller of the brick with the lowest numbered rack/slot in the
system. The connection is established by opening one of the
/hw/module/*c*/L1/controller (IRIX) or /dev/snsc/*c* (Linux)
devices.
--scdev device_name
Connect via the system's own System Controller network using
device_name. This option is identical to --sc, except that it uses
device_name rather than selecting a default device to use. Valid
devices are any of /hw/module/*c*/L1/controller (IRIX) or
/dev/snsc/*c* (Linux) devices.
image_name
The image name is the file name of the image, which for the IOC4 is
usually ioc4.svf.
rack.slot
rack is the rack number of the controller(s) that will be updated.
slot is the slot number of the controller(s) that will be updated.
Without any options, flashsvf attempts to connect to an L2 controller (a
"real" L2, or a software L2 running on the L3). When communicating with
the system via the USB connection (in a system where there is no actual
L2), the application /stand/sysco/bin/l2 must be running.
Page 2
flashsvf(1M)flashsvf(1M)FILES
/usr/sbin/flashsvf EEPROM firmware update utility
/usr/cpu/firmware/ioc4.svf IOC4 firmware image
/hw/module/*c*/L1/controller (IRIX only) IRIX System Controller devices
/dev/snsc/*c* (Linux only) Linux System Controller
devices
EXAMPLES
Updating an IO9/IOC4 in a Chimera from the host OS on the system to be
updated using the default system controller path. The brick ID is 001c01.
1) cd /usr/cpu/firmware
2) /usr/sbin/flashsvf ioc4.svf 1.1
Updating an IO9/IOC4 in an IX-Brick from an Linux L3 via a hardware L2 at
IP address 137.38.82.154. The brick ID is 101i01.
1) cd /usr/cpu/firmware
2) /usr/sbin/flashsvf --l2 137.38.82.154 ioc4.svf 101.1
Page 3
