Introduction
Provides BIOS, ME Firmware, BMC Firmware, and FRUSDR updates. (R01.01.0029)
Available Downloads
- OS Independent
- Size: 23.6 MB
- SHA1: F441E570B2E4AF948199D8277287B1A7A7DC40F4
Detailed Description
uEFI System Update Package (SUP) Installation and Operation Instructions
Intel highly recommends reading this document in its entirety before performing the system update. Verifying that your system meets the documented requirements will ensure a successful update and provide the most reliable system
functionality after the update has completed.
Released - Jul. 1 2020
This update package includes the following production level system software updates and update utilities:
System BIOS - 01.01.0029
ME Firmware - 03.01.03.072
BMC Firmware - 01.60.12355
FRUSDR - 1.19
iFlash32.efi - Version 14.1 Build 15
fwpiaupd.efi - Version 14.1 Build 18
frusdr.efi - Version 14.1 Build 18
Supported products
- Intel® Server Board S2600WT Family
Contact Intel for pre-production hardware support requirements.
Important notes:
- All updates provided in this package are installed using the embedded uEFI
operating environment only. - Do not modify any of the script files. The scripts as written will provide the most reliable update experience.
- If for any reason the System BIOS, BMC Firmware, or FRU&SDR data need to be re-installed after the initial update has been performed, the package does include standalone script files that can be run individually. These files include: UpdALL.NSH, UpdBIOS.NSH, UpdME.NSH, UpdFD.NSH UpdBMC.NSH, and UpdS2600WT.NSH.
Do NOT use these files until after the system has been updated initially using the STARTUP.NSH file.
Note:
When updating the BMC Firmware using the BMC.NSH update script file, there is an interaction between the BMC flash and the BIOS USB drivers in this release which may cause random characters (usually the letter 'e') to appear in the
command line after the BMC update has completed. A reboot after the BMC flash will clear this error.
System software requirements
To update the system software stack to the versions included in this update package, the system software stack currently installed on the target server system MUST meet the following or the update will fail:
- System BIOS - Production version 01.01.0028 or later
- ME Firmware - Production version 03.01.03.051 or later
- BMC Firmware - Production version 1.56.11315 or later
For pre-production hardware and software support requirements, contact Intel for details.
Update procedure
- Unzip the contents of the update package and copy all files to the root directory on a USB flash drive
- Insert the USB flash drive to any available USB port on the server system to be updated
- Power on the server
- The system will automatically access the uEFI shell and begin the update process.
Or
- If the files were copied to a folder other than the root, Boot the Server to the uEFI shell. This can be accessed via the BIOS setup utility during POST or via the Boot Menu accessed during POST.
- Run the command "map -r" in the uEFI shell to mount the USB flash drive.
- Run the command "fs0:" to change folders to the USB flash drive. The USB flash drive may also mount to fs1: depending on other installed devices. The number of "fs#" is dependent on the result of command "map -r".
- Change folders to the folder holding the update package files and manually start the "Startup.nsh" script file to start loading all updates.
- Reboot the system after the update process has successfully completed.
Advisory note:
Whenever the system BIOS is updated, two BIOS images are installed, a primary image and a backup image. The backup image is loaded during the 1st system reboot after the primary BIOS image is updated. During the 1st system reboot, the screen will be blank for approximately 2 minutes while the backup BIOS image is being loaded. DO NOT power off or reboot the system during this time. A message will appear on the screen when the backup BIOS image update has completed.
Verifying updates:
- During POST, hit the Key when prompted to access the BIOS Setup Utility.
- From the BIOS Setup Utility main menu, Hit the key to load BIOS Defaults.
- At the MAIN menu verify the BIOS revision is correct.
- Move cursor to the SERVER MANAGEMENT Menu.
- Move cursor down to the SYSTEM INFORMATION Option and hit Enter.
- Verify the BMC Firmware revision is correct.
- Verify the SDR revision is correct.
- Verify the ME Firmware revision is correct.
- Configure desired BIOS Option settings.
- Hit the F10 Key to save changes and Exit.
The System Software Update is Complete.
Warning:
Do NOT interrupt or reboot or remove power from your system during the update process. Doing so may render your system inoperable.
Do NOT attempt to down rev the system software once loaded on to the system. Doing so may render your system inoperable.
This download is valid for the product(s) listed below.
- Intel® Server Board S2600WTTR
- Intel® Server Board S2600WT2R
- Intel® Server System R1304WTTGSR
- Intel® Server System R1304WT2GSR
- Intel® Server System R1208WTTGSR
- Intel® Server System R2208WT2YSR
- Intel® Server System R2208WTTYSR
- Intel® Server System R2208WTTYC1R
- Intel® Server System R2308WTTYSR
- Intel® Server System R2312WTTYSR
- Intel® Server System R2224WTTYSR
- Intel® Server System R1208WT2GSR
- Intel® Server System VRN2208WAF6
- Intel® Server System VRN2208WAF8
- Intel® Server System VRN2208WHY8
- Intel® Server System R2208WTTYC1
- Intel® Server System R2308WTTYS
- Intel® Server System R1304WT2GS
- Intel® Server System R2208WT2YS
- Intel® Server Board S2600WT2
- Intel® Server System R2208WTTYS
- Intel® Server System R2224WTTYS
- Intel® Server System R1208WT2GS
- Intel® Server System R2312WTTYS
- Intel® Server System R1208WTTGS
- Intel® Server System R1304WTTGS
- Intel® Server Board S2600WTT
- Intel® Server System MCB2208WAF4
- Intel® Server System MCB2208WAF5
- Intel® Server System MCB2312WHY2
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.