                One-Boot Flash Update Utility Release Notes
                 Copyright (c) 2010 Intel Corporation
                            All Rights Reserved
                             July 14, 2010


The One-Boot Flash Update Utility is a program used for updating the system 
BIOS, BMC, Sensor Data Records (SDR) ,FRU, ME, HSC and LCP of systems.

RELEASE NOTES FOR THE ONE-BOOT FLASH UPDATE UTILITY VERSION 9.70 Build 16

A. Features or changes added in this release 
   1. Fixes for the POST SRA issues for S3420 platform series.

B. DEPENDENCIES


   1. When running the One-Boot Flash Update utility, the current working directory must 
      be the location where the flashupdt executable and the \enus folder reside.  
      Running the utility from a different directory is not supported.

   2. All package files mentioned in the flashupdt.cfg file should be present in the same  
      folder.

   3. Recommended BIOS upgrade/downgrade with one version separation.

   4. For Platforms supporting OEM BIOS updates , the system BIOS capsule file should be  
      updated before OEM Capsule.
  
   5. The name of files used for updating the system should be exactly same(including the  
       case) as what is mentioned in the configuration file.
   
   6. The chaff2l.bat or chaff2l.sh scripts can be customized to handle
      more http and ftp options. Please refer to cURL help for more informations.
   
   7. OFU is not supported on VT enabled kernel.

   8. OFU doesn't support 'FWNAME' cfg file command on S3200, S3210, X38MLST, S3420, 
       S5500 and S5520 platforms. 
       The user has to use FWDNAME command to update the BMC firmware. 
	   For S5000, S5400, SC5400 and S7000FC4UR platforms use 'FWNAME' command.

   9. For the use of 'BOOTUPDATE' config file command or 'boot' area type in 'FWDNAME'
       command , ensure BMC Boot block is write enabled.

   
C. COMMAND LINE INTERFACE

   Syntax:  flashupdt [-h] [-c] [-i] [-q] [-u {URL or path of update package}]

   where

      -h : (or -?) Displays the command line help.
      -i : Displays the current BIOS, BMC, and SDR versions of the system.
           This option can also be used in conjunction with -u to display
           the version information contained in the update package files.
      -u : Updates the BIOS, BMC and SDR as specified in the CFG file.
           The URL or path, if any, of the update package must immediately
           follow this option.  The package files can reside on a local
           drive. The current directory is used if no location is specified.
      -q : Suppresses output and progress messages from being displayed. 
	   Note : Executing OFU with this option suppresses all output messages 
		  including questions to user. The user has to use this switch 
		  only when he is sure that no interaction will be required
		  at the time of execution. This option is targeted to specific 
		  programs / advanced users and will not be documented elsewhere.

   There is a new switch added in order to support BIOS related operations only on a BMC present system. 
   When any of the above mentioned commands are appended with the switch "-b" at the end, the utility 
   will perform only BIOS operations on the system.

   Eg:
	flashupdt -i -b
	The above command displays only BIOS inventory from the system.
	
   Note: The switch "-b" needs to be given only at the end of the command, other wise the utility will
	 error out.


D. LINUX INSTALLATION

  1. The OFU binaries for SuSe will be distributed as compressed archives as following:
       ofu-sles.zip : Binaries for SLES Linux flavors

  2. Unzip the above binaries using the 'unzip' command in Linux Shell prompt. The installation program
       setup_linux can be found in the releases/OFU directory.

  3. The setup_linux is used as follows:
        ./setup_linux	 [-ni] 	[-p=Target Installation Directory]
	
     Specific changes for CCB# 625 support.
	./setup_linux [-b] 
	The above command will install only the drivers required for the BIOS update operation. The IPMI drivers are not installed.
	

  4. The installation of the One-Boot Flash Update utility requires the following
     separate RPM files to be installed.

   a. On Red Hat El5.3 Linux
         a. flashupdt-1.9.70-15.i386.rpm
   b. On SuSE Linux Enterprise Server 11 

         a. flashupdt-1.9.70-15.i586.rpm

      The first file contains the One-Boot Flash Update Utility.

      There is an installation script called, "setup_linux", which will
      ensure all components of the One-Boot Flash Update utility are installed.  To
      install the One-Boot Flash Update utility using the setup_linux script, perform
      the steps below.

   5. Prior to installing this version of the One-Boot Flash Update utility, 
      the setup_linux removes the rpm's in the order mentioned below and does the
      install of the rpm's as mentioned in point 1. The order in which the rpm's get
      uninstalled is as :

    	 rpm -e flashupdt
 	  Note:- Drivers and other OFU components should not be uninstalled manually.
	  If done unintentionally please re-install again.
	  
   6. Please ensure that the /sbin directory is part of the system path. The current
      system path on the server can be displayed by executing the following command:
      
         echo $PATH

   7. After installation, a reboot is NOT required prior to running the utility. 

   8. To run the One-Boot Flash Update utility, change the working directory to
      the /usr/local/flashupdt directory.

   9. You may now run the utility as described in section B above.

      NOTE: In linux when executing a file, you must precede the name of the 
            executable with its path, (e.g. "./flashupdt -?").

   Removal of One-Boot Flash Update Utility
   
   To uninstall the One-Boot Flash Update utility,change to /usr/local/flashupdt
   directory and execute the command "./setup_linux /u" . When the /b switch is also given, the drivers related to BIOS operations only will get uninstalled.

E. WINDOWS INSTALLATION AND REMOVAL
   
   Installation of One-Boot Flash Update utility via the Setup_win program
 
   Note:- Please ensure you have uninstalled older version of OFU before
          installing OFU 9.70 Build 15. For more details please refer
		  "Removal of One-Boot Flash Update utility" section.
		  
   1. Open a command prompt and go to the folder where OFU installable(Setup_win.exe)
      is present(eg:cd c:\Utilities\OFU).*
   2. In order to enable every update operation, execute the command --"Setup_Win.exe" .This will copy all the files
      needed for OFU to the directory %Programfiles%\Intel\Flashupdt
      and will also install the required drivers based on the target platform.

      To perform only BIOS update operation, use the same command with "-b" option. ("Setup_win -b")

   3. Restart the System .
   4. To run the One-Boot Flash Update utility, open a command prompt, and 
      change directory to the folder in which the flashupdt.exe file resides 
      (e.g. cd %ProgramFiles%\Intel\Flashupdt).
   5. You may now run the utility as described in section C above.

   * - The user should not change the location or delete any files in the 
      OFU installation folder

		 
   Removal of One-Boot Flash Update utility

   1. Open a command prompt and Change to the directory where the utility
      is installed (e.g. cd %ProgramFiles%\Intel\Flashupdt)
   2. Execute "Setup_Win.exe /u" . This will uninstall the One Boot flash update
      utility
	  Note:- Drivers and other OFU components should not be uninstalled manually.
	  If done unintentionally please re-install again.
      When the /b switch is given, the drivers related to BIOS operations only will get uninstalled.
	  
   3. Reboot the system for the changes to take effect. 

   NB: For SHW40, S5000 platforms after doing step 2 verify that flashud.sys & 
       ibsmutil.sys is removed from "%windir%\system32\drivers" directory. If this file is 
       present manually remove the file.


F. SAMPLE UPDATE PACKAGE CONTENT

   The following is a list of files that make up a complete update package:

   1. Configuration File (CFG)

      flashupdt.cfg

   2. BMC firmware file

      BMC0022.ima

   3. SDR file

      UR_BMC.sdr

   4. FRU file

      UR_FRU.fru

   7. BIOS file
    
      R0020.CAP

   8. HSC file
      
      RG6BP209.hex
	
   9. LCP file 
    
      LCP74.hex

   10. OEM BIOS file
     
       Oem.Cap

   11. ME file
       
       SPSOperational.bin

 
G. Supported Platforms

      S5000  family of Servers
      SC5400 family of servers
      S7000FC4UR 
      S5400 family of Servers
      S3200/S3210 family of Servers
      X38MLST
      S5500 family of Servers
      S5520 family of Servers 
      T5500 family of Servers
      S3420 and S3450 family of Servers
      S3420GPV family of servers
      	
H.  Supported Operating Systems
    
      RHEL4 Update 4 and updates. Both x86  and x86_64.
      RHEL5 and updates. Both x86  and x86_64.
      SLES9. Both x86  and x86_64.
      SLES10 and updates. Both x86  and x86_64.
      RHEL5.3 and updates. Both x86  and x86_64.
      RHEL 5.4 and updates. Both x86 and x86_64.
      SLES11 and updates. Both x86  and x86_64.
      Microsoft Windows Server 2003 R2 (32bit and x64 versions)
      Microsoft Windows Server 2008 (32bit and x64 versions)
      Microsoft Windows XP (On Workstation SKUs)
      
       	
I. Known Issues

1. This version of OFU is not supported in the following platforms,
      SE7221BK1-E
      SE7320SP2
      SE7320VP2
      SE7520AF2
      SE7520BD2
      SE7520JR2
      SE7525GP2
      SR6850HW4, SR6850HW4M, SR4850HW4 and SR4850HW4M
	  
2. OFU doesn't support updating secondary HSC controller firmware.

3. Updating the boot block of LCP firmware is not supported.

4. It is mandatory to do a reboot of the server after every BIOS update. 
   Retry of BIOS update without reboot may result in error or incorrect behavior.

5. In  linux if any failures occur's in firmware (BMC, HSC, LCP, ME) or FRUSDR upgrade, 
   stop the ipmi service and retry. Enable it back once you are completed with the 
   upgrade process.

6. Presence of any mounted virtual CD ROM device could lead BMC update failure. 
   The behevior is unpredictable in such scenario.  

7. The BMC FW update could take maximum of 18 minutes on Windows OS if used default IPMI driver.

8. The HSC FW update is not supported on LINUX OS with the OPEN IPMI driver in the GUI mode, due to certain driver limitations.

J. Other notes:

	1. OFU will use USB interface for firmware update operation
   	   on S5500 & S5520 platforms. This may cause BMC emulated Virtual floppy
   	   and CD Drives to be detected when the update in progress.
           
	2. By default, if present,the utility will use Microsoft IPMI and/or 
	   Open IPMI driver on Windows and Linux OSs respectively.  
	   Utility installation procedure checks for presence of any of the above
	   mentioned drivers and accordingly install Intel drivers.

	3. In order to use the Intel IMB driver on Windows, the user needs to disable the MS IPMI driver, 
	   install Intel IMB driver, followed by a reboot. For installtion of the driver, one needs 
	   to issue the following command from the directory where 
	   the utility is installed.
		 devicesetup install imbdrv.inf *IMBDRV

	4. OpenIPMI KCS interface is disabled when the Fast FW update is in progress in Linux and enabled again .
	 


K. Legal Information

========================================================

                               LEGAL INFORMATION

========================================================

Information in this document is provided in connection with Intel Products

and for the purpose of supporting Intel developed server boards and systems.

No license, express or implied, by estoppel or otherwise, to any intellectual 

property rights is granted by this document. Except as provided in Intel's 

Terms and Conditions of Sale for such products, Intel assumes no liability 

whatsoever, and Intel disclaims any express or implied warranty, relating to 

sale and/or use of Intel products including liability or warranties relating 

to fitness for a particular purpose, merchantability, or infringement of any 

patent, copyright or other intellectual property right. Intel Corporation may 

have patents or pending patent applications, trademarks, copyrights, or other 

intellectual property rights that relate to the presented subject matter.  

The furnishing of documents and other materials and information does not 

provide any license, express or implied, by estoppel or otherwise, to any 

such patents, trademarks, copyrights, or other intellectual property rights.  

Intel products are not intended for use in medical, life saving, or life 

sustaining applications. Intel may make changes to specifications and product 

descriptions at any time, without notice.

 

Intel is a registered trademark of Intel Corporation. 

 

*Other names and brands are the property of their respective owners.

 

Copyright (c) 2010 Intel Corporation.

 (end)

