1. SCRUtilityA02.zip Driver
2. README File Contents

README Driver File Contents (SCRUtilityA02.zip)

COMMAND LINE:

The following commands are given for the root SDK directory.  Running the program from the
demo\DownloadFirmware directory will not work because of the package designation.  The 
classpath environment variable must be set as specified in the readme in the main directory 
as well in order to compile and run the programs correctly.

   Compiling
      javac demo\DownloadFirmware\DownloadFirmware.java

   Using runsample to run the program
      runsample DownloadFirmware <firmware/NVSRAM filename> <IP Address or Host Name> [<Additional Addresses or Names>]
      runsample DownloadFirmware <-?>

   Running the program without runsample
      java demo.DownloadFirmware.DownloadFirmware  <firmware/NVSRAM filename> <IP Address or Host Name> [<Additional Addresses or Names>]
      java demo.DownloadFirmware.DownloadFirmware <-?>

GENERAL HELP:

 The program is used to demonstrate downloading FIRMWARE and NVSRAM using the SYMbol API 
 commands loadControllerFirmware and loadControllerNVSRAM. This program allows only atomic 
 downloading of Firmware/NVSRAM.  Firmware/NVSRAM image files typically have a *.dlp file extension.


RESTRICTIONS:

Both controllers should have their firmware updated.

Using this program could cause the controllers to be unmanageable by SYMsm due to version conflicts!

If your controller supports staged firmware download, you can either activate the new firmware right 
after the download or activate it at the next sysReboot.  Wait approximately 2 minutes after the program
terminates before running another opperation to the Storage Array if you choose to activate now.



PROGRAMMING NOTES:

Downloading Firmware-
First, a connection is established with the storage array.  Then, the file is examined to make sure

it is a valid firmware file (The first 8 bytes of the file spell out the word "firmware").
Note that this example does not parse much of the information stored in the header of the firmware
file (supported board types, firmware version, etc...).  The program next retrieves the length of
the header to find the start of the data. Finally, the program repeatedly calls the API
command, loadControllerFirmware, sending the firmware data to the controller in chunks as large as the
controller accepts (MAX_FW_CHUNK).

Downloading NVSRAM-
NVSRAM can be downloaded to the controller using a similar process.  These files typically have a 
*.dlp extension.  A NVSRAM file contains the text "NVSRAM" as the first bytes.  NVSRAM files contain
a header similar to the firmware.  

Downloading Firmware and NVSRAM together-
You can pass in two filenames, one for controller firmware and one for NVSRAM. Find the start of the 
data of both files, add the image size of both files to form the total size, and use loadControllerFirmware
to send the images together. Things to remember: 1) You need to specify numberOfFiles of 
FirmwareUpdateDescriptor to 2, 2)You need to reset the offset to 0 when you start to send the NVSRAM image, 
3)You cannot mix firmware and NVSRAM image in one image chunk.
      
The NVSRAM image is downloaded to the controller using the method
SYMbolAPIClientV1.loadControllerNVSRAM(FirmwareUpdateDescriptor).  The entire NVSRAM image must 
be downloaded to the controller at once, since downloading of multiple segments is not supported.