Introduction
As of 17 February 2024, no functional, security, or other updates will be provided for Intel® Server Board S2600ST Family BIOS and Firmware Update Packages. Intel® Server Board S2600ST Family BIOS and Firmware Update Packages will no longer be available after 29 March 2024. All versions are provided as is. Intel recommends that users of Intel® Server Board S2600ST Family BIOS and Firmware discontinue use as soon as possible. Intel® Server Board S2600ST Family BIOS and firmware update for Intel® One Boot Flash Update (Intel® OFU) Utility and WinPE*. (00.01.0014), read firmware dependencies in requirements section
Available Downloads
- OS Independent
- Size: 30.7 MB
- SHA1: 0DAD3790FA198BD58455E4758885CAE4CCCA1A89
Detailed Description
System firmware requirements
To update the system firmware stack to the versions included in this update package, the currently loaded system firmware stack on the system must meet the following:
System BIOS - 00.01.0013 or later
ME Firmware - 04.00.04.294 or later
BMC Firmware - 1.43.91f76955 or later
FRUSDR - 1.28 or later
Failure to get to the required firmware stack, may cause unexpected results.
About this release
BIOS : 00.01.0014
ME : 04.00.04.340
BMC : 1.60.56383bef
FRUSDR : 1.40
Support platforms and dependency
Processors supported:
Intel® Xeon® Scalable processors
Microcode versions:
CPUID Version Status
0x50653 0x01000144 (Xeon Scalable B1)
0x50654 0x0200004D (Xeon Scalable H0)
The following update process must be followed to ensure a trouble free update.
1. BMC firmware
2. BIOS
3. Manageability Engine (ME) firmware
4. FD
5. FRUSDR
Important note
This Update package must be installed using Intel® One-boot Flash Update (Intel® OFU) V14.1 Build 14 or later.
1. Package C-State only works well with Xeon Scalable Family H0 parts, for other Xeon Scalable Family stepping, C6 non-retention is hardcode from BIOS side.
2. BIOS R00.01.0001 does not support online downgrade to any Dxxx or Xxxx BIOS.
3. BIOS R00.01.0001 removed Xeon Scalable Family A1 microcode(m1350651_8000002B) and Xeon Scalable Family B0 microcode(m9750652_80000035).
4. Removed 'UpdateNvram' support for iflash32 tool for security reason of SRA bios.
5. Security revision upgrade to v0002 on BIOS R00.01.0002 will prevent BIOS downgrade via normal mode to R00.01.0001; user can use BIOS recovery mode for BIOS downgrade, although Intel doesn't recommend downgrading firmware
6. One new production key is integrated onto R0004 BIOS, which will correct an OEM string.
7. This release includes security revision upgrade to version 0004. This will prevent BIOS downgrade via normal mode to a previous version with lower security revision, user can use BIOS recovery mode process for BIOS downgrade.
8. System will prevent downgrading ME from 04.00.04.288 to 04.00.04.235 or older version if system BIOS version is R0009. This is an expected behavior.
9. Security revision upgrade to 0005 since BIOS R010, it will prevent BIOS downgrade via normal mode to previous version with lower security revision. User can use BIOS recovery mode for BIOS downgrade.
10. Downgrading below 1.43.660a4315 is not supported due to a security revision change.
System firmware update package usage instructions
This package can be updated using one of the following methods:
- Windows* or Linux* operating system using Intel One-boot Flash Update (Intel OFU) V14.1 Build 14 or later
- Windows* Preboot Execution Environment (WinPE)
To update from Windows* and Linux* or operating systems using the Intel One Boot
Flash Update Utility (OFU)
Intel One Boot Flash Update utility can be downloaded from http://downloadcenter.intel.com/ and it is part of the "BIOS, Firmware Update & Configuration Utilities" for Windows and Linux. Please refer to Intel OFU user guide about the details of installation and usage of OFU.
Use Intel OFU to update system firmware by the following steps:
- Install Intel OFU on Windows or Linux system
- Download the latest firmware update package from http://downloadcenter.intel.com/
- Unzip package to a folder
- Run the following command in Windows* command line/Linux terminal window: :\flashupdt -u \flashupdt.cfg
To update from Windows Preboot Execution Environment (WinPE)
The System Firmware Update Package can be inserted to Windows PE customized image for creating a bootable Windows PE CD. User is able to update system firmware from customized WinPE CD by the following steps:
- Boot server with customized WinPE CD
- Run script "WinPE_x64_Update.bat" (name may vary depending on your own customization)
Note:
1. The Intel OFU utility is case sensitive. Therefore, when you transfer the
Firmware Update Package using USB flash drive from a Microsoft Windows system to a Linux environment, you must first extract under the Linux* environment. Otherwise, you will need to mount the USB flash drive manually with 'vfat' option under Linux to avoid conversion from upper case to lower case and vice versa.
2. To make Intel OFU utility run properly under x64 OS, you have to read Intel OFU release notes on known issues for OFU installation.
3. In this SFUP package, Intel only provides batch file "WinPE_x64_Update.bat"
for WinPE2.1/3.0 64 bit solution as an example. Please refer to white paper
"White Paper-Intel Server Utilities Procedure for WinPE.pdf" for details on
building your own customized WinPE CD.
4. Windows PE 2.0 - built from Windows Vista SP1 EM64T
5. Windows PE 2.1 - built from Windows Vista SP1 or Windows Server 2008, EM64T
6. Windows PE 3.1 - built from Windows Server 2008 R2, EM64T
7. Microsoft IPMI driver is loaded by default from WinPE CD, if you want to use
Intel IPMI driver instead of MS IPMI driver for firmware update, you can un-install
Microsoft IPMI driver by:
Devicesetup.exe ¨Cv remove *IPI0001
Note: IPI0001 is the device ID for Microsoft IPMI driver.
This download is valid for the product(s) listed below.
Disclaimers1
Product and Performance Information
Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.