Intel R2224WFQZS Server System OFU Firmware 02.01.0009

Versions:

- BIOS: 02.01.0009
- ME: 04.01.04.323
- BMC: 2.22.59c3b83a
- FRUSDR: 1.96
- DCPMM: 1.2.0.5395

BIOS R02.00.0009

- HSD-ES: 2103626250, SUT will hang on black screen when use NVMe SSD then install windows chipset driver
- HSD-ES: 5388345, 6 sec time window from MB3 (EKV entering normal mode) to iMC entering normal mode - SCS
- HSD-ES: CCB2763, [BIOS/BMC Q3'19] Single reboot to update BIOS, FD, ME & BMC: Current design requries 3 reboots to update FD, BIOS and ME.
- HSD-ES: 5388220, CCB 136637 OS Mgmt: Intel Optane DC Persistent Memory fallback to SMBus when DDRT training fails to allow log collection & firmware upgrade
- HSD-ES: 5388361, CCB 136533 Intel Optane DC Persistent Memory SW RAS: BIOS Driven "BACKGROUND" ARS thread - critical for proper Windows/Azure error handling behavior (phase 2)
- HSD-ES: 5388220, CCB 136637 OS Mgmt: Intel Optane DC Persistent Memory fallback to SMBus when DDRT training fails to allow log collection & firmware upgrade
- HSD-ES: 5388223, CCB 136654 Clear PCD0 corruption without overwrite DIMM
- HSD-ES: 5388342, MCA Recovery Test Issue with 6133 CPU
- HSD-ES: 5387495, CCB 136533 Intel Optane DC Persistent Memory SW RAS: BIOS Driven "BACKGROUND" ARS thread - critical for proper Windows/Azure error handling behavior
- HSD-ES: 5388325, Short ARS - Allows errors to be returned even user requested no notification.
- HSD-ES: 5388097, Save S3 boot script for IOAPIC There was an issue with missing some PCIE graphic cards after S3 resume.
- HSD-ES: 2103626817, The KTI Prefetch item help text is different BIOS spec. The prefetch letter p in KTI prefetch should be capitalized.
- HSD-ES: 5388323, User CAPS State for WS in support of CCB 136665
- HSD-ES: 5388342, IRPPERRSV CSR maps protocol parity errors to correctable
- HSD-ES: 5388338, CLX64L - Enabling CLTT w/PECI results in both CLTT mode and CLTT w/PECI
- HSD-ES: 5388350, [IPS 1409117089][AMI] x2APIc broken
- HSD-ES: 5388309, PlatformDxeSmmBiosGuard: Vuln-2019-012 -- Unregister IO trap once triggered
- HSD-ES: 5388326, Incorrect DIMM location reported when disabling CMCI-SMI Morphing in 2LM
- HSD-ES: 5388356, PCU machine check (MSCOD = 0x68) observed when memory channel fails to train
- HSD-ES: 5388337, Against the DIMM rule with 2DPC RDIMM (SR is in DIMM0, DR is in DIMM 1), this channel will be disabled as design, but the system will hang when booting Windows server 2012 R2
- HSD-ES: 5388340, Need final resolution for FW-UEFI-Vuln-2019-012 BIOSGuard issue
- HSD-ES: 5388389, [2nd Generation Intel Xeon Processor Scalable family] SST-BF Frequency Table in BIOS needs minor adjustment
- HSD-ES: 5388264, Add software timeout and issue cold reset
- HSD-ES: 5388324, Intel Optane DC Persistent Memory BIOS - ARS Error Inject updates
- HSD-ES: 1507355635, CpPcRestrictedPkg/Ipmi: User configuration page is hidden after setting BMC KCS to Restricted Mode
- HSD-ES: 5388313, Intel Optane DC Persistent Memory DIMM's showing ECR_WDATA_PE (data path poisoned) without error media log created (or WDB UE)
- HSD-ES: 5388339, Firmware Test Suite failures with NVDIMM _NBS & _NCH methods
- HSD-ES: 1507354875, OOB update caused system be in reboot loop under restricted/Deny all mode
- HSD-ES: 1607594883, FRB-2 triggered on option ROMS under Deny All mode.
- HSD-ES: 1507337951, Released BIOS bug with Intel Optane DC Persistent Memory in description instead of Optane DCPMM.
- HSD-ES: 1407979768, BMC KCS Policy Control Modes Implementation.
- HSD-ES: 1806951266, XmlCliDxe Assert on reboot after creating max number of namespaces in UEFI CLI.
- HSD-ES: FIV10506, PC Stitching Update RSTeSataLeagcy version to 6.1.0.1017 for RP
- HSD-ES: OSS_0011668, OSS_0011668_Integrate SPS E5_04_01_04_323_0 to Trunk
- HSD-ES: 2103627012, "Password is set successfully" message show up when press "F10" to save the config after create BMC user account.
- HSD-ES: 2103625822, Revert"Intel Optane DC Persistent Memory 55785.1 - Invalid Configuration - Mixed NVDIMMs and DCPMMs, Step2 - Intermittent POST 0x32 hang and IERR logging."
- HSD-ES: 1607211313, Race conditions in VariableInterface() allow arbitrary writes inside of SMRAM
- HSD-ES: 2103626532, Complex Password setting will change to default setting (disable) after reset SUT
- HSD-ES: 1507212924, Onboard VGA Always On knob is grey out and display output from add-in video card
- HSD-ES: 1507223712, "DCPMM Invalid Configuration found" after running UEFI NVRAM variables without any DCPMM installed.
- HSD-ES: 1507140808, Vulnberabilities CVE-2019-6260 as BMC didn't disable superIO
- HSD-ES: 2103626444, SUT will reset after udpate BIOS/FD/ME via OFU in Linux
- HSD-ES: 2103626509, System cannot boot to recovery mode with some memory population
- HSD-ES: 2103626021, SUT will halt at 0x99 probably when Intel Optane DC Persistent Memory set to 2LM MM mode
- HSD-ES: 1507136963, S2600WFR FRUSDR/SYSCFG utility stall for quite a long time when dumping FRU content or bios/bmc setting under uefishell with USB31000SA installed.
- HSD-ES: 1607277367, Operands in a bitwise operation have different size KW issue
- HSD-ES: 2103626208, It can enroll CA cert via Setup UI after login as user.
- HSD-ES: 1507072526, ServerAmiRestrictedPkg: FW-UEFI-Vuln-2019-009 UsbRt SMM callout code execution Server Board S2600ST
- HSD-ES: 2103625317, [S2600STR] RAID option ROM have no display background color and only display character in SOL session.
- HSD-ES: 2103626238, Stop bits should be "0" according to new ACPI SPCR spec.
- HSD-ES: 1507136963, [S2600WF0R] FRUSDR/SYSCFG utility stall for quite a long time when dumping FRU content or bios/bmc setting under uefishell with USB31000SA installed.
- HSD-ES: 2103625234, There are some issue when SUT boot with invalid DCPMM config
- HSD-ES: 1507036525, There are 7 PSIRT BIOS security issues reported on R15 code base.
- HSD-ES: 1507173389, SMBIOS type 16/ type 19 show incorrent info.
- HSD-ES: 1507175341, RSD Type 194 info is incorrect.
- HSD-ES: 2007797829, BMC Web Console doesn't show CPU and DIMM information.
- HSD-ES: 1507175309, RSD Type 193 info is incorrect
- HSD-ES: 2103625822, [Intel Optane DC Persistent Memory] 55785.1 - Invalid Configuration - Mixed NVDIMMs and DCPMMs, Step2 - Intermittent POST 0x32 hang and IERR logging.
- HSD-ES: 2103624920, BIOS / ME / FD image still can be updated via OOB feature when the mismatch type is selected
- HSD-ES: 2103626488, S2600BPR Configure out Intel Optane DC Persistent Memory for CFG1 2-1-1(Intel Optane DC Persistent Memory 256G x 4, and 128GB DIMM x12), appeared 0XFA fatal error after power on Fatal error is thrown when high memory is used with the SKU which does not supports.
- HSD-ES: 11581, Integrate Microcode 03000012 for 2nd Generation Intel Xeon Processor Scalable family A0 from PC-1st Generation Intel Xeon Processor Scalable family
- HSD-ES: 1507170024, [S2600WF] ipmi set bootdev bios/disk sometimes doesn't work
- HSD-ES: 11544, PC Stitching Sync Intel Optane DC Persistent Memory UEFI driver v01.00.00.3458 from RP
- HSD-ES: 1607116940, Add BIOS options to change different PCIe Uncorrectable Error Severity mapping
- HSD-ES: 1507072526, FW-UEFI-Vuln-2019-009 UsbRt SMM callout code execution Server Board S2600ST
- HSD-ES: 1507146548, CCB#2591-Q2'19 To add [Onboard VGA Always On] to support GPGPU usage
- HSD-ES: 1607184056, Resolve BMC network problem from LAN disabling under BIOS and MAC address problem
- HSD-ES: 2103624263, S2600ST Q3'18 SFUP test failed with SUSE12.3 OS that show critical issue for ME in BMC web
- HSD-ES: 1607202054, [2nd Generation Intel Xeon Processor Scalable family] SST-BF identification of High Priority cores broken in VMWare ESXi
- HSD-ES: 2103626179, The SUT will halt at early video with some memory config.
- HSD-ES: 2207272621, S2600WF: PCI device slot id is not unique
- HSD-ES: no_sighting, Integrate microcode 2nd Generation Intel Xeon Processor Scalable family A0 mb750655_03000012 to Trunk
- HSD-ES: 5388296, Incorrect DIMM location reported when PS finds UCE
- HSD-ES: 5388329, [2nd Generation Intel Xeon Processor Scalable family] SST-BF identification of High Priority cores broken in VMWare ESXi
- HSD-ES: 5388209, DXE_ASSERT - Protocol 'gEfiVariableWriteArchProtocolGuid' is not available
- HSD-ES: 5347308, Post code hang d5 after enable BIOS Gard option in BIOS setup
- HSD-ES: 5388298, [2nd Generation Intel Xeon Processor Scalable family] Dimm re-training and ADR enable results in loosing DIMM data
- HSD-ES: 1607113667, CCB-2570-Complex BMC Password
- HSD-ES: 1506985873, S2600BP BdsUpdateHook driver is loaded on S9200WK.
- HSD-ES: 1607042642, IIO config help string override by SDP.
- HSD-ES: 5388322, BIOS hangs at "Pipe Exit starting..." message during S3 flow in 2DPC system configuration
- HSD-ES: FIV11501, Integrate true version of NMPTU binary for SPS E5_04.01.04.296.0 to Trunk
- HSD-ES: 1607085596, Restrict Update Nvram support for DC requirement
- HSD-ES: 1607201873, Sync the Setup options value with respect to refresh and non-refresh project trunks
- HSD-ES: 1507108474, BIOS post fail with S2600BPS SKU in Riser solt2 M.2 NVME
- HSD-ES: 1607172379, CCB-2659: [Q2'19 BIOS]Support for Priority Based Frequency
- HSD-ES: 11482&11483, Integrate Microcode 04000024 for 2nd Generation Intel Xeon Processor Scalable family B0 and 05000024 for 2nd Generation Intel Xeon Processor Scalable family B1
- HSD-ES: 1507095678, On 1 CPU system SMBIOS type 9 Current Usage value for CPU 2 - PCIE slot don't follow SMBIOS SPEC.
- HSD-ES: 2103625234, There are some issue when SUT boot with invalid DCPMM config
- HSD-ES: 5388283, Dynamic loops accessing one element beyond boundary (MAX_TT_ROW) due to <= operator in DimmTT
- HSD-ES: 5388046, [2nd Generation Intel Xeon Processor Scalable family] System getting stuck at postcode FF during AC cycling"
- HSD-ES: 5388139, BMC version is changing to NA in bios setup menu after flashing IFWI/ loading any config file
- HSD-ES: 5388153, When running MRC cycling with Intel Optane DC Persistent Memory, each boot results in surprise clock stop.
- HSD-ES: 5388031, BIOS hang at "Config TDP Level 2..." after enable "Opportunistic SR" with full memory configuration
- HSD-ES: 5388222, [2nd Generation Intel Xeon Processor Scalable family] Speed Select Base Config P1 frequency is lost and not available to discover when CPU is in a different ISS config than base
- HSD-ES: 5388195, MRC: Limit EKVCMD Vref high side boundary to 63
- HSD-ES: 5388301, ASSERT_EFI_ERROR 451 while running MLC at high temp
- HSD-ES: 5388286, [2nd Generation Intel Xeon Processor Scalable family B0] Add datecode check for CTLE for Samsung C-die and D-die
- HSD-ES: 5388285, [2nd Generation Intel Xeon Processor Scalable family B0] Fatal error during DRAM Rx Eq training on Samsung 8Gb based DIMMs
- HSD-ES: 5388261, SMBIOS Type 19 for UMA should expose LMMIO gap.
- HSD-ES: 5388266, Intel BIOS Guard implementation IO TRAP SMI call-out
- HSD-ES: 5388288, Surprise clock stop after S3 reset
- HSD-ES: 5388239, DXE_ASSERT when flushing ADWB memory
- HSD-ES: 5388281, Incorrect DIMM location reported in ADWB or 2LM when injecting CE or UCE
- HSD-ES: 5388290, Fixed counter RDPMC failures
- HSD-ES: 5388101, Add PPR
- HSD-ES: 5388231, CPU string is not matched between BIOS and DCL SPEC
- HSD-ES: 5388284, The current BIOS implemenation is not following the POR validation matrix
- HSD-ES: 5388260, Intel MRC change broken customrefreshrate setting to 2x refresh.
- HSD-ES: 5388217, Fix size check for ADDDC Ranks
- HSD-ES: 5387999, Unnecessary HECI resets causing SPS failures
- HSD-ES: 1606927743, to reduce the build time for PurleyPcPkg
- HSD-ES: 5388108, [2nd Generation Intel Xeon Processor Scalable family AP] Observing Package cstate & Core cstate value of PKG-C1 to be greater than 90% instead of PKG-C6 values.
- HSD-ES: 5388209, DXE_ASSERT - Protocol 'gEfiVariableWriteArchProtocolGuid' is not available
- HSD-ES: 5388237, Intel Optane DC Persistent Memory FIS version as part of input structure fed to 'Identify DIMM' Intel Optane DC Persistent Memory command is wrong.
- HSD-ES: 5388229, The starting/initial values for CLK signals seems exist problem on BIOS
- HSD-ES: 5388274, Mixed Mode Intel Optane DC Persistent Memory is not throwing out an unsupported warning message
- HSD-ES: 5388271, PCD Error Handling - BIOS runs into infinite loop on invalid signature
- HSD-ES: 5388254, LSS - All Intel Optane DC Persistent Memorys Reports Dirty Shutdown After Same-Level BIOS Flash Following a Cold Reset
- HSD-ES: 5388251, Implement workaround for CoreBo credit leak issue dropped from Intel Xeon Processor Scalable family code
- HSD-ES: 5388178, BIOS don't follow FIS 1.14 to parsing BSR in serial debug msg
- HSD-ES: 5388261, Fix for SMBIOS Type 19 missing if NUMA disabled
- HSD-ES: 1507042968, Remove the lock feature of Power LED
- HSD-ES: 5388198, L3 Cache Size is incorrect in SMBIOS table type 7
- HSD-ES: 5388190, [2nd Generation Intel Xeon Processor Scalable family - AP] Platform is not booting after changing the boot mode to power optimized in Bios setup menu.
- HSD-ES: 5388252, DCPMM Protocol - do not switch to SMM for TSOD polling state retrieval
- HSD-ES: 5388198, L3 Cache Size is incorrect in SMBIOS table type 7
- HSD-ES: 1507094928, Support RSD SMBIOS table 190 NIC
- HSD-ES: 5388202, Update NvmCtlrGetPlatformInterpretedLss & NvmCtlrGetPlatformInterpretedUnlatchedDsc to return new dirty shutdown reasons from BSR
- HSD-ES: 5388241, CCB 136659 Disable DDRT on 1st Generation Intel Xeon Processor Scalable family CPUs before Intel Optane DC Persistent Memory goes to production
- HSD-ES: 5388246, [2nd Generation Intel Xeon Processor Scalable family] CPC Error on windows after enabling Prioritized base frequency support
- HSD-ES: 210362551, There is no "Direct To Core (D2C)" and "Direct To UPI (D2K)" option on BIOS Setup.
- HSD-ES: 5387873, SMBIOS Type 19/20 is not showing effective memory Size.
- HSD-ES: 2007793994, BIOS displays 2934 MHz for Current memory Speed instead of 2933MHz.
- HSD-ES: 1507073575, Patch 2 Die as One to get logic socket ID for 2nd Generation Intel Xeon Processor Scalable family AP
- HSD-ES: 5388203, Intel Optane DC Persistent Memory surprise warmreset detection does not work
- HSD-ES: 5387983,[2nd Generation Intel Xeon Processor Scalable family AP] UEFI PXE Boot is not present in the DragonRock BIOS
- HSD-ES: 5387156, Add support to report FRU information in Error Logs based on 2nd Generation Intel Xeon Processor Scalable family AP 2 dice in 1 Skt
- HSD-ES: 5388125, BIOS BDAT crc incorrect
- HSD-ES: 5388163, BIOS hangs during platform boot when get PCD for partition 0 (or 1) fails as a consequence of UCC (or poison)
- HSD-ES: 5388216, RAS Clear Poison while ARS running
- HSD-ES: 5388215, [2nd Generation Intel Xeon Processor Scalable family AP] Remove 2die as 1S Setup Option
- HSD-ES: 1507099817, [S2600WF] BIOS does not have a memory setting for 2666 or 2933 memory
- RP relese Reference code version: CP_PURLEY_0581_D01.
- This release is mapping to RP daily build:CP_PURLEY_0581_D05.

BMC v2.22.59c3b83a

- 1507299182 - The crash dump json file in the BMC debug log miss some part
- 1607818386 - BMC login problem by ipmiutil and EWS if the password length is longer than 16 bytes
- 1507285420 - Upgrade Curl from 7.64.0 to 7.65.1
- 2103628329 - EWS: It can not send the SNMP alert packages to destination IP
- 1507357494 - [Redfish]Unable to change property "BootSourceOverrideEnabled" from "Continuous" to "Disabled"
- 1607346326 - [Redfish] Username or password length is abnormal when create or modify
- 2208243530 - BMC Session ID hijacking flaw
- 1507373053 - The latest BMC has no event log on EWS
- 1607346326 - [Redfish] Username or password length is abnormal when create or modify
- 1507343404 - [S2600WF][KCS]Cannot change BMC KCS mode in BMC force-update mode.
- CCB2546: [Redfish] Add additional eventing to Redfish support
- CCB2645: Support virtual media
- CCB2570: Complex BMC Password

FRUSDR 1.96

- Add new sensor "KCS Policy" for feature "KCS policy control mode"
- Changed the fans PWM for fan profile #3,4,5 and 6 and the Riser 1 shift profile number for 1U configurations.

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. Begin the update process running the Startup.nsh
5. Reboot the system after the update process has successfully completed

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 the .bin file
5. Click upload. Progress and status will be shown as the update progresses

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

Verifying Updates:

01. After the final update has completed successfully, reboot the system
02. During POST, hit the <F2> Key when prompted to access the BIOS Setup Utility
03. From the BIOS Setup Utility main menu, hit the <F9> key to load BIOS defaults
04. Hit the <F10> 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  

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.