One-Boot Flash Update Utility Release Notes
Copyright (c) 2006-2008 Intel Corporation
All Rights Reserved
August 5, 2008
The One-Boot Flash Update Utility is a program used for updating the system
BIOS, BMC, Sensor Data Records (SDR) ,FRU, HSC and LCP of systems.
RELEASE NOTES FOR THE One-Boot FLASH UPDATE UTILITY VERSION 9.70 Build 3.2
A. Features added in this release
1. Microsoft IPMI driver support is added in One-Boot Flash Update Utility
to update BMC FW, FRU and SDR. The OS supported are:
Windows Server 2003 R2 SP2 (32 bit & EM64T).
2. Flash update driver iS certified.
B. DEPENDENCIES
1. The Microsoft IPMI Device Driver is not installed by default in
Microsoft Windows Server 2003 R2 SP2. It is installed via the
Add/Remove System Components feature of the Control Panel as a
Hardware Management feature under the Management and Monitoring Tools.
For information on Hardware Management enabling in
Microsoft Windows Server 2003 R2, refer the url:
http://www.microsoft.com/technet/scriptcenter/preview/wsm/enable.mspx
2. Servers with IMM modules must be running a version of the BMC that supports the
rolling update feature, prior to running the One-Boot Flash Update utility.
3. For BMC and SDR updates, the IMM modules must contain 4MB flash parts.
4. The One-Boot Flash Update utility for windows requires that the Flash Update (flashud),
Intelligent Platform Management Interface (IPMI) driver and Memory Map (ibsmutil) driver
already been installed, prior to running the utility. The drivers get installed during
installation of the One-Boot Flash Update utility, (see sections D and E below).
5. 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.
6. All package files mentioned in the flashupdt.cfg file should be present in the same folder.
7. System should be rebooted after uninstalling the driver in Windows.
8. Recommended BIOS upgrade/downgrade with one version separation.
9. For Platforms supporting Oem bios updates, the system BIOS capsule file should be updated
before OEM Capsule.
10. In Linux the fru, sdr, pef, tbl and cfg files should be converted to unix format using
"dos2unix" tool.
11. In SE7XXX family of servers , if the utility hangs while updating the BIOS, then boot the
linux OS with kernel parameter nmi_watchdog=2 or nmi_Watchdog=0 whichever is applicable
based on the OS .
12. SLES9-32 bit support is not there for SE7XXX family of servers.
13. For SE7XXX family of servers, OFU will work only for ELSmp kernel in RHEL4.0.
14. For running OFU in Rhel4.0-EM64T Os'es, install libstdc++ version 3.2 (i386)
15. The name of files used for updating the system should be exactly same(including the case)
as what is mentioned in the configuration file.
16. When a user id and password is used with the ftp option, if the package files are located
on a Red Hat Enterprise Linux 3.0 (ES) based ftp server, the full absolute path of the package
location on the ftp server must be specified. The package location on the ftp site cannot be
relative to the home directory of the user id/ password used.
17. One-Boot Flash Update Utility is not supported on VT enabled kernel.
18. One-Boot Flash Update Utility doesn't support 'FWUPDATE' cfg file command on S3200 / S3210/X38MLST
platforms. The user has to use FWDUPDATE command to update the BMC firmware.
19. One-Boot Flash Update Utility doesn't support the '-c' switch on S3200 / S3210/X38MLST platforms.
20. For the use of 'BOOTUPDATE' config file command ensure BMC Boot block is write enabled.
21. One-Boot Flash Update Utility uses Microsoft IPMI driver as a default to communicate to BMC for
updating BMC FW, FRU and SDR. If Microsoft IPMI driver not installed then One-Boot Flash Update Utility
uses Intel IMB driver for updating BMC FW, FRU and SDR.
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.
-c : This option is used to cancel all pending BIOS, BMC and SDR update
operations by resetting the BMC update notification flag. FRU
updates can not be cancelled with this option (FRU updates
take effect immediately). This utility resets the internal BMC
flag to cancel the update operation whether there is one or not.
-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.
D. WINDOWS INSTALLATION AND REMOVAL
Installation of One-Boot Flash Update utility via the Setup_win program
1. Open a command prompt and go to the folder where OFU installable(Setup_win.exe)
is present(eg:cd c:\Utilities\OFU).*
2. 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.
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
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.
E. LINUX INSTALLATION
1. The installation of the One-Boot Flash Update utility requires the following
separate RPM files to be installed.
a. On Red Hat EL 3.0/ Red Hat El4.0 / Red Hat El5.0 Linux
a. flashupdt-1.9.70-3.i386.rpm
b. afu-1.40-1.i386.rpm - only for SE7XXX family
b. On SuSE Linux Enterprise Server 9 (SLES 9)
a. flashupdt-1.9.70-3.i586.rpm
b. afu-1.40-1.i586.rpm - only for SE7XXX family
The first file contains the One-Boot Flash Update Utility.The
second rpm file contains the bios update driver for SE7xxx family of servers.
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.
2. 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
rpm -e afu -- only for SE7XXX family
3. 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
4. After installation, a reboot is NOT required prior to running the utility.
5. To run the One-Boot Flash Update utility, change the working directory to
the /usr/local/flashupdt directory.
6. 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" .
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 Hex file
ALBMC12.hex
3. SDR file
BFAD.sdr
4. FRU file
4hs2.fru
5. PEF file
saf1.pef
6. TBL file
saf2.tbl
7. BIOS file
R0014.CAP
8. HSC file
RG24BP_132.hex
9. LCP file
LCP74.hex
10. OEM BIOS file
Oem.Cap
G. Supported Platforms
S5400 family of Servers
H. Known Issues
1. To execute OFU on Windows Server(R) 2008:
Please follow the below steps every time while booting the server on Windows
Server(R) 2008.
a. Press F8.
b. On boot options menu, select Disable Driver Signature Enforcement from the list
and press ENTER.
2. To install Flashupdate driver on Windows Server(R) 2008:
a. Go to Device manager.
b. Select "Add Legacy hardware" option from "Action" Menu.
C. Click "Next" on "Welcome to the Add Hardware Wizard" screen.
d. Choose "Install the hardware that i manually select from a list" and Click
"Next"
e. Choose "System Devices" from Common hardware types and click "Next".
f. Click on "Have Disk" and point to flashud.inf from the installation package.
g. Select "Intel 28f320c3 Flash Update Driver" from the list and click "Next"
h. Click "Install this driver software anyway" from "Windows Security" dialog.
i. Click finish on completion
3. On S7000FC4UR platforms , LCP boot code version will be displayed as 0.00,
4. This version of OFU is not supported in the following platforms,
SE7221BK1-E
SE7320SP2
SE7320VP2
SE7520AF2
SE7520BD2
SE7520JR2
SE7525GP2
SR6850HW4, SR6850HW4M, SR4850HW4 and SR4850HW4M
5. This version of OFU does not support remote http/ftp update.
6. This version of OFU does not support IMM3 update.
7. This version of OFU does not support HSC & LCP FW updates.
8. Utility will not install Intel IMB driver if Micosoft IPMI driver
is detected. If later Microsoft IPMI driver is removed or
utility not able to communicate with BMC, install the
Intel IMB driver manually or re-install utility.
The command to install the Intel IMB driver manually is:
DeviceSetup.exe -v install %IMB_DRV_INF% *IMBDRV
I. Other notes:
========================================================
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) 2008 Intel Corporation.
(end)
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.