Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017

Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017

Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017 Download Summary

  • File size: 32.30 MB
  • Platform: OS Independent
  • Price: FREE DOWNLOAD
  • Downloads: 40
  • Released: January 12, 2024
  • Manufacturer URL: Intel

Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017

Requirements:

Minimal version of current BIOS and Firmware are required to perform a new BIOS and firmware update. If you try upgrading directly from an older BIOS version to a new version but do not meet firmware requirements, the upgrade may fail. Before you perform a new BIOS and firmware update, please verify current BIOS and firmware versions on your server systems. 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 - R02.01.0016
ME Firmware - 04.01.04.804
BMC Firmware - 2.88.71773d70
FRUSDR - 2.04

If the system doesn't currently meet the BIOS and firmware requirements, you must download a previously-posted System Update Package (SUP) from Other Versions list of this web page and update the system to the preceding described firmware revisions before updating the system to the firmware stack included your downloaded Firmware Update Package. Failure to get to the required firmware stack, may cause unexpected results.

Versions:

- System BIOS - 02.01.0017
- ME Firmware - 04.01.05.002
- BMC Firmware - 2.88.e172ff67
- FRUSDR - 2.04
- Intel Optane DC Persistent Memory Firmware (DCPMM) - 01.02.00.5446

BIOS Changes:

- Rename BIOS ID from 0X.02.0609 to 02.01.0017
- [HSD-ES]: [22016215079] PurleySktPkg/Library/ProcMemInit: Merge patch for PSU hot plug hang issue with SKX 512GB LRDIMM
- [HSD-ES]: [15013087092] Remove ITK or replace it with BIOS for ccs message since ITK has EOL
- [HSD-ES]: [22015684413][IPU2023.1] [CVE-2022-26343] Force LT Lock MSR regardless of CSM, Secure Boot or TXT
- [HSD-ES]: [14017005750][IPU2023.1] Inject uce into the micro failing DIMM bad row, the failure row can not be detected by type 18 and EWL type4 is not printed
- [HSD-ES]: [16016328984][IPU2023.1] [CVE-2022-32231] ESPI SMI LOCK enable ESPI SMI LOCK is not set. The purpose of this changes is to enable ESPI SMI Lock.
- [HSD-ES]: [14017767843][IPU2023.2] Hit IERR error during power off the host when channel was disabled - DIMMMTR and AMAP register did not have the map-out information
- [HSD-ES]: [16018928401][IPU2023.2] [CVE-2022-38087] Need RSB mitigation in SMM (SmmCpuFeaturesLib and PiSmmCpuDxeSmm).BIOS mitigation for FirmwareBleed/SpectreRSB/retpoline
- [HSD-ES]: [22016016266][IPU2023.2] P-CATERR observed while creating the goal with non-interleaved AD mode
- [HSD-ES]: [16019037085][IPU2023.2] [CVE-2018-25032] [CVE-2022-37434] Purely: CRC32 library in BIOS builds is not part of the approved bill of materials.
- [HSD-ES]: [16019440912][IPU2023.3] [CVE-2022-43505] [PurleyR]Harden SMM rendezvous before write to flash.
- [HSD-ES]: [15011874031][IPU2023.3] Purley:Set PRR3 PRR4 Lock-Down registers values to 1 to avoid Self Test erors.
- [HSD-ES]: [14018436300][IPU2023.3] PurleySktPkg/Library/ProcMemInit: Update AMT MiscVendor to 3.7 version
- [HSD-ES]: [14017550021][IPU2023.3] PurleySktPkg/MemRas: CMCI will not be informed to OS when eMCADis&VLS created
- [HSD-ES]: [14017397075][IPU2023.3] PurleySktPkg/WheaSiliconHooksLib: When UC happen in VLS region on IMC1, BIOS not enter "Bank is in VLS" flow, 2 PPR entry generated
- [HSD-ES]: [14018107051][IPU2023.3] CpRcPkg/BaseMemoryCoreLib: Adding Manufacturer ID Code CXMT
- [HSD-ES]: [16016328984][IPU2023.3] [CVE-2022-32231]ServerSiliconPkg/Pch/SouthClusterLbg/PchInit/Smm: ESPI SMI LOCK enable
- [HSD-ES]: [15011664636][IPU2023.3] PurleyPlatPkgLibraryOemProcMemInitLib: Fix the platform will hang if there is no KM/BPM when TXT is enabled.
- [HSD-ES]: [14016313622][IPU2023.3] [Purley-R][CPX][TARGET_22.3] Re-add Micron AMT Type18 Update
- [HSD-ES]: [PurleyPC][IPU2023.3] PurleyPcPkg/StitchingPkg:Update ME SPS,E5_04_01_05_002_0
- [HSD-ES]: [PurleyPC][IPU2023.3] PurleyPcPkg/StitchingPkg:Update ucode to SKX H0 mb750654_02007006/ CLX B0 mbf50656_04003604/ CLX B1 mbf50657_05003604
- [HSD-ES]: Add third-party-programs_PurleyR.txt file for license compliance
- RP release Reference code version:CP_PURLEY_0628_P50

BMC Changes:

 - Upgrade kernel SMBIOS_DataStart MDR command
- Upgrade kernel to 4.9.337
- Update openssl to 1.1.1w

FRUSDR Changes:

- 14017396176 Change the Riser 2 Sensor (2Ch) as clamp sensor instead of HSBP 4 Sensor (E0).
- 15012037399 change the BIOS Sensor from "ADDDC Error" to "ADDDC VLS Event".

GENERAL INSTALLATION PROCEDURE:

1. Unzip the contents of the update package and copy all files to the root directory  of a removable media (USB flash drive)
2. Insert the USB flash drive to any available USB port on the system to be updated
3. Power on the server and load the uEFI shell
4. Access to the USB flash drive insterted and begin the update process running the Startup.nsh
5. Systen will reboot automatically after the update process has successfully completed
6. If PMEM installed, run Startup.nsh a second time after the first reboot to upgrade PMEM Firmware and power cycle the system to allow PMEM load the new FW.

Verifying Updates:

01. After the final update has completed successfully, reboot the system
02. During POST, hit the Key when prompted to access the BIOS Setup Utility
03. From the BIOS Setup Utility main menu, hit the key to load BIOS defaults
04. Hit the key to Save Changes and Exit the BIOS defaults
04. At the main menu verify the BIOS revision is correct
05. Move cursor to the SERVER MANAGEMENT menu and hit Enter
06. Move cursor to the SYSTEM INFORMATION Option and hit Enter
07. Verify the BMC Firmware revision is correct
08. Verify the SDR revision is correct
09. Verify the ME Firmware revision is correct
10. Configure desired BIOS Option settings
11. Hit the F10 Key to Save Changes and Exit

UEFI iFlash32:

1. Copy the entire contents of the zip file to the root of a USB flash drive
2. Boot to UEFI Shell, then change the Shell to the mapped device (USB flash drive) Example: Shell> fs0: (or fs1:)
3. Run updBIOS.nsh, updME.nsh, updFD.nsh and reset the system after each region upgrade
4. Reboot the system after the last upgrade is completed
5. Do NOT interrupt the BIOS POST during the first and second boot

BMC

 Web GUI update:
1. Unzip the package onto your system
2. Log into the BMC web GUI
3. Navigate to Configuration, then Firmware Update
4. Click browse, and direct the browser to the location of Purley_2.88.71773d70.bin
5. Click upload. Progress and status will be shown as the update progresses

BMC UEFI update:

1. Unzip package and load onto a flash drive
2. Boot to UEFI shell, and navigate to the folder where this package lives
3. Run fwUpdateBMC.nsh and follow the prompts

FRUSDR INSTALLATION:

1. Ensure BMC FW release 2.42 or later is pre-installed before attempting this FRU/SDR update.
2. Copy all of the files and directories of this zip file to a USB key, hard disk drive or floppy drive.
3. Execute the following script to bring up the main FRU/SDR load menu: updS2600WF.nsh
4. Select Option 1 to do the SDR update.
5. Answer the prompts, and the SDRs will be loaded

About Firmware Updates:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device's functionality in the event of a software update either turning up faulty or causing the unit's overall performance to drop. However, bear in mind that applying an older firmware isn't recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it's best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device's firmware. Also make sure you constantly check with our website to ensure that you don't miss a single new release.

Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017 Bookmark

Hyperlink code:
Hyperlink for Forum code:

Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017 Drivers Download Notice

Top 4 Download periodically updates information of Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017 full driver from the manufacturer, but some information may be slightly out-of-date.

Using warez version of Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017 driver is hazardous. Our driver download links are directly from our mirrors or publisher's website, Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017 torrent files or shared files from free file sharing and free upload services, including Rapidshare, HellShare, HotFile, FileServe, MegaUpload, YouSendIt, MailBigFile, DropSend, MediaMax, zUpload, MyOtherDrive, SendSpace, DepositFiles, Letitbit, LeapFile, DivShare or MediaFire, are not allowed!

It is not recommended to download drivers from illegal sites which distribute a keygens, key generators, pirate keys, serial numbers, warez full versions or cracks for Intel R2208WF0ZSR Server System UEFI BIOS/Firmware 02.01.0017. These drivers might corrupt your computer installation or breach your privacy. A driver might contain a trojan horse opening a backdoor on your computer. Hackers can use this backdoor to take control of your computer, copy data from your computer or to use your computer to distribute viruses and spam to other people.