Intel S2600WFT Server Board OFU Firmware 02.01.0016

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 - 02.01.0015
- ME Firmware - 04.01.04.601
- BMC Firmware - 2.88.6999d21a
- FRUSDR - 2.03
- PMEM - 01.02.00.5446

This update package includes the following production-level system firmware updates:

- System BIOS - 02.01.0016
- ME Firmware - 04.01.04.804
- BMC Firmware - 2.88.71773d70
- FRUSDR - 2.04
- Intel Optane DC Persistent Memory Firmware - 01.02.00.5446

Important notes:

- OFU utility with flashupdt tool does not support PMEM FW update, please refer to "PMEM_Update_Intructions.txt" part of this package for instructions to update PMEM.
- This SFUP package includes the FW 01.02.00.5446 for Intel Optane DC Persistent Memory (PMEM), if you received your PMEM DIMMs with a different FW, please install this one.
- This Update package must be installed using Intel One-boot Flash Update (OFU) V14.1 Build 28
- Starting from BMC v2.86, BMC does not allow upload .key files and only accepts .pem file for SSL certificate.
- If uploaded SSL Certificate or Key files fail to format checking, BMC will remove the invalid format file before starting BMC EWS and re-generate a self-signed certificate to ensure the BMC EWS can boot up successfully. Please consult TA-1176 for more details
- Starting from BMC v2.88, Purley platfomrs only support SSL certificate which is equal to or longer than 2048 bit.
- A security issue was fixed in Purley platforms. BMC credential is required to access files in internal virtual media from BMC v2.88.
- Issue:[Internal Virtual Media] Files in internal virtual media are accessible without BMC credential
- Starting from BMC v2.88, EWS Active Directory should allow domain name and user name longer than 16 characters.
- The AD Setting will be cleared after downgrade to v2.86 or lower BMC versions if the Domain Name is equal to or longer than 32 characters.
- Starting from BMC 2.22.59c3b83a, when KCS Policy Control Mode is configured as "Deny ALL" on BMC EWS, BMC and FRUSDR cannot be upgraded/downgraded as expected behavior.
- Updates can still be performed via Redfish or BMC EWS

Changes in BIOS:

- [HSD-ES] :[15012936020]CryptoPkg/Library/OpensslLib: Update Open SSL from version 1.1.1j to 1.1.1t to fix new reported BDBA CVEs.
- [HSD-ES] :[2103656951] [S2600ST] System will halt at post code 0X9A after insert raid key.
- [HSD-ES] :[2103656856] PurleyPcPkg: Fix EWS capsule update failed with BIOS password.
- [HSD-ES] : PurleyPcPkg: Update the copyright year to 2023 for BIOS release
- [HSD-ES] :[15011189651][CCB3616]PurleyPcPkg/Restricted: Add new knob "Posted Interrupt Throttle".
- Advance->Integrated IO Configuration->Intel(R) VT for Directed I/0->Eanbled
- Advance->Integrated IO Configuration->Intel(R) VT for Directed I/0->Posted Interrupt Throttle->Enabled
- [HSD-ES] :[15011189655][CCB3617]PurleyPcPkg/Restricted: Reduce susceptibility to DDR4 Rowhammer attacks.
- [HSD-ES] :[2103652209][CCB3627]PurleyPcPkg/Platform: [CCB3627]Update IFXTPMUpdate.efi to add support for Infineon SLB9672 TPM firmware update.
- [HSD-ES] :[15011189655] PurleyPcPkg/Include: Amend CCB3617 to follow GenerationVariable define rule.
- [HSD-ES] :[15012214482] PurleyPcPkg/StitchingPkg: Update VROC EFI driver to version 7.8.0.1012
- [HSD-ES] :[14016466448] Revert CpRcPkg/Library/BaseMemoryCoreLib: Improve PPR logging and prevent launch PPR on the same location if not spare rows available
- [HSD-ES] :[14016620884] CpRcPkg/Library/BaseMemoryCoreLib: [IPU2022.3 BIOS Candidate][Purley-R][622.D12][Regression] Cannot find PostPackageRepair info in serial log when inject UCE
- [HSD-ES] :[14016466448] CpRcPkg/Library/BaseMemoryCoreLib: Improve PPR logging and prevent launch PPR on the same location if not spare rows available
- [HSD-ES] :[15011111294] When enable Secure Boot LT_LOCK bit are 0 if go to the EFI boot path
- [HSD-ES] :[15010308440] PurleyPcPkg: [Purley-R][LEGACY] PCH LBG GPP_G17 did not keep its ADR_COMPLETE native function setting across the warm reboot which caused unexpected save/restore flows during the periodical warm reset test with NVDIMM
- [HSD-ES] :[22015113608] PurleySktPkg/Library/ProcMemInit: [22.3 Candidate][Purley]Hynix failing DIMM cannot be detected by type 16 and can be detected by AMT 13,14,15 of EWL type 4
- [HSD-ES] :[14016284151] PurleySktPkg/Library/ProcMemInit/Chip/Mem/: DDR4 Advanced Memtest Code update for SK hynix to V2.8.7
- [HSD-ES] :[14014555453] CpRcPkg/Library/AdvMemTestLib: Unexpected reset when meeting "N1: UpdateRowFailures" and hang at "Invalid Socket Id 0"
- [HSD-ES] :[14014548874] CpRcPkg/Library/BaseMemoryCoreLib: EWL logging is missing for UCE PPR using failing DIMM
- [HSD-ES] :[14014144524] ServerPlatformPkg/Platform: HSTI update for the TCG event log format
- [HSD-ES] :[15010089605] PurleyPlatPkg: Use PchResetPpi for BiosGuard reset
- [HSD-ES] :[22013634156] PurleySktPkg/Library/ProcMemInit/Chip/: [2nd Generation Intel(R) Xeon(R) Scalable] [2020.2 IPU] System got ce/ue errors when toggling "Volatile Memory Mode" between 1LM and 2LM when Intel(R) Optane(TM) PMem dimm was already provisioned to MM
- [HSD-ES] :[22014673557] PurleySktPkg/Library/ProcMemInit/Chip/Mem: Memory - 3 Rank Memory 2 way Interleaving through Purley BIOS
- [HSD-ES] :[14016298358] PurleySktPkg/Library/ProcMemInit: MEMORY MATRIX SYSTEM (128GB LRDIMM)IS UNABLE TO BOOT with 2400MT/s speed
- [HSD-ES] :[14015902887] [PurleyWS22] Lock TXT configuration before running untrusted code
- [HSD-ES] :[18021347489] ServerSiliconPkg/CrystalRidge: Subtract 1 from end address in ARS DSM's, so all functions work in the same way.
- [HSD-ES] :[15011725908] PurleyPlatPkg/Override: [Purley][BIOS]BIOS should check the password once administrator password is set when performing BIOS online update
- [HSD-ES] :[15011564237] PurleyPcPkg/Restricted: Fix Help string of Intel ERST2 of SATA controller shows incorrect.
- [HSD-ES] :[15011215801] CpPcRestrictedPkg/PasswordUtilityLib: [DSG][pen-test] No Password Salt or System Wide Salt Used
- [HSD-ES] :[15011197631] PurleyPcPkg/Library: Fix PTK0002709: Intel Server BIOS Buffer overflow vulnerability
- [HSD-ES] :[16015709660] PurleyPlatPkg: [INTEL-UA-00365] Update memory/io allocation
- [HSD-ES] :[14016023993] CpRcPkg/Library/BaseMemoryCoreLib: PPR entries are getting removed in case of full memory training with IPU2021.2 change
- [HSD-ES] :[14016039756] CpRcPkg/BaseMemoryCoreLib: Change to support Renesas Databuffer with Intel(R) Optane(TM) PMem
- [HSD-ES] :[15011076108] PurleyPcPkg/RasPkg: Fix [1st Generation Intel(R) Xeon(R) Scalable/2nd Generation Intel(R) Xeon(R) Scalable] LEGACY TARGET_22.1 BIOS log, PPR record, and OS log are not correctly logging primary and buddy banks while inject UC into a VLS region
- [HSD-ES] :[14015489456] CpRcPkg/Library/AdvMemTestLib: Revert Micron DRT 3.0 AMT algorithm changes
- [HSD-ES] :[22014008124] PurleyPlatPKg: DMI MMIOL_RULE11 value is not correct and overrided by LT baseaddress.
- [HSD-ES] :[14015276559] PurleySktPkg/Library/WheaSiliconHooksLib: [IPU2021.1] [VLS] [1st Generation Intel(R) Xeon(R) Scalable/2nd Generation Intel(R) Xeon(R) Scalable][LEGACY][TARGET_22.1] BIOS log, PPR record, and OS log are not correctly logging primary and buddy banks while inject UC into a VLS region
- [HSD-ES] :[15010096546] CpPlatPkg/Whea/WheaElog: [TARGET_22.1][CVE-2021-0189] WheaElogSw SW SMI does not check pointers (PTX0001624)
- [HSD-ES] :[14014234667] CpRcPkg/Library/AdvMemTestLib, PurleySktPkg/Library/ProcMemInit : Micron requested updated to Advanced Memtest Pattern for Purley
- [HSD-ES] :[22012934800] ServerSiliconPkg/MemCpgc: Fix Invert or DC control programming for Purley
- [HSD-ES] :[14014868418] CpRcPkg/Library/BaseMemoryCoreLib, PurleySktPkg/Library/ProcMemInit: Program Margin Read to reduced or increased values in case TSE EEPROM CRC failures
- [HSD-ES] :[14015056238] CpRcPkg/Library/BaseMemoryCoreLib: RemoveInvalidPprEntry input parameter is Ch in Socket (0 to 7) and PprAddrSetup uses mc Channel (0 to 1)
- [HSD-ES] :[22012815450] PurleyPlatPKg: Fix the issue if MeSegSize =0 or DPR size =0 for PostedInterrupt workaround
- [HSD-ES] :[2103651081] PurleyPcPkg/GenerationSetup: [DSG] Question value mismatch Option value message will show after modify BIOS options setting and get back to security or Server Manager page
- [HSD-ES] :[1509670376] CpPcRestrictedPkg/UefiOpromSetup: BCM NIC card Oprom is disappeared in UEFI Option ROM control after BIOS load default
- [HSD-ES] :[PurleyPC][IPU2022.3] PurleyPcPkg/StitchingPkg:[S2600WF/S2600BP]Sync the NvmDimmDriver and NvmDimmHii driver to v01.00.00.3536
- [HSD-ES] :[PurleyPC][IPU2022.2] PurleyPcPkg/StitchingPkg:Integrate SPS FW to E5_04_01_04_804_0 to Trunk
- [HSD-ES] :[PurleyPC][IPU2022.2] PurleyPcPkg/StitchingPkg:[S2600WF/S2600BP]Sync the NvmDimmDriver and NvmDimmHii driver to v01.00.00.3534
- [HSD-ES] :[PurleyPC][IPU2022.2] PurleyPCPkg/StitchingPkg: Intergated Microcode 02006e05 for 1st Generation Intel(R) Xeon(R) Scalable H0 + change size
- [HSD-ES] :[PurleyPC][IPU2022.1] PurleyPcPkg/StitchingPkg:Integrate SPS FW to E5_04_01_04_700_0 to Trunk+spsfiles
- [HSD-ES] :[PurleyPC][IPU2022.1] PurleyPcPkg/StitchingPkg:Sync the SINIT version to Production v1_7_55_LBG
- [HSD-ES] :[PurleyPC][IPU2022.1] PurleyPcPkg/StitchingPkg:Integrate Microcode 05003302 for clx B1 / 04003302 for clx B0 and 02006d05 for 1st Generation Intel(R) Xeon(R) Scalable H0 (update).
- [HSD-ES] :[PurleyPC][IPU2022.1] PurleyPcPkg/StitchingPkg:Sync the BIOSACM version to Production v1_7_54_LBG.
- [HSD-ES] :PurleyPlatPkg: [IPU2021.2]Add Uba support for CVE-2020-8673 Opt out and PurleyR CVE-2020-8673 changes
- [HSD-ES] :PurleyPcPkg/Platform/Dxe/WheaElog: [Purley]IPU 2022.1 porting for [TARGET_22.1][CVE-2021-0189] WheaElogSw SW SMI does not check pointers (PTX0001624)
- [HSD-ES] :Revert "CpPcRestrictedPkg/PasswordUtilityLib: [DSG][pen-test] No Password Salt or System Wide Salt Used"
- [HSD-ES] :PurleyPcPkg/Restricted/Platform/Dxe/GenerationSetup: Add VTD check for Posted Interrupt Throttle knob

Changes in BMC:

- Upgrade kernel to 4.9.326
- 15012183195 - [Purley][22'Q4][Internal test] BMC cannot be updated from 2.88.22563765 to 2.88.22563765 under UEFI Shell
- 15011050603 - [Purley] The problems about EWS help text in English and Chinese version.
- 15012249643 - [Purley][22'Q4][Internal test]When create IVM of 150M and then upload a 30M file via redfish, it returns 500 error
- 15011596494 - [BMC][S2600BP] random fan boost in L9 S2600BP system
- 2103641613 - [S2600ST]Install windows/linux OS failure via HTML5
- 15011969420 - [Purley] FRU and sensor info lost after several DC cycling
- 22014254977 - Stack buffer overflow SendRawPECI IPMI command
- 22014086811 - System memory info leak in MDR commands
- 22014076835 - Integer overflow in AgentSMBIOS_SendDataBlock causes memory corruption
- 14015534437 - Double free on AgentSMBIOS_DataStart MDR command

Changes in FRU/SDR:

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

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.