Intel S2600WFTF Server Board OFU Firmware 02.01.0017

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.0016
- ME Firmware - 04.01.04.804
- BMC Firmware - 2.88.71773d70
- FRUSDR - 2.04
- PMEM - 01.02.00.5446

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

- 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 - 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:

- 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

Changes in BMC:

- Upgrade kernel to 4.9.337
- Update openssl to 1.1.1w

Changes in FRU/SDR:

- Change the Riser 2 Sensor (2Ch) as clamp sensor instead of HSBP 4 Sensor (E0).
- 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.