Intel HNS2600BPB24 Compute Module OFU Firmware 00.01.0014

Versions:

- BIOS: 00.01.0014
- ME: 04.00.04.340
- BMC: 1.60.56383bef
- FRUSDR: 1.37

Changes in BIOS R00.01.0014:

- Rename BIOS ID from X0149 to R0014
- Update Microcode 0x4d for Xeon Scalable H0 and 0x144 for Xeon Scalable B1
- Update OPA UEFI driver to v1.6.0.0.0
- Update ME SPS version to 340
- Update RSTE Drivers to v5.4.0.1039
- TPM Update fail on STP and WFP
- [Purley PSIRT Factory BMC & BIOS] enabling one-time software update to any version
- [BNP] Windows2016 cannot be installed with SATA port5+port7 RSTe RAID0
- Other PCI device's SsidSvid is 0xFFFFFFFF and is different from NIC Controller on SFP+ BNP board
- Higher security ID from 1.05 to 1.06 because HECI PRT and Backup BIOS PRT patch
- BIOS Change for #CCB 2083[Syscfg tool]Add option to configure fan pwm offset in syscfg on Purley
- System will not boot to IPV4 PXE if UEFI Network Stack disabled for IPV6 PXE in BIOS
- [Purley BMC+BIOS]Need mechanism for BMC to return MAC addresses for add-in card on demand
- [Purley BIOS] Allow all SMBIOS extensions as defined by RSD extensions to be supported by default
- Toshiba THNSN5128GPU7 M.2 PCIe SSD can't detect successful under Win2016 OS.
- [Purley BIOS] Add Infineon FW update capability support in BIOS and UEFI application
- BSOD after warm reboot if HT is enabled with Windows Server 2016 version 17663 and 17666 SKLX
- [WFP]SMBIOS Type 8 NIC number is not match motherboard number
- [WFP&BNP]Fix system will hang with POST code 0x94 when one riser slot of HOST connects two WRG JBOD nodes with 32 RSSDs
- BIOS does not return Type 199 records
- [STP] BIOS copyright information 2006-2017 should be changed to 2006-2018
- [ Purley BIOS-Post Launch]Support Relax Ordering and No Snoop in BIOS setup and ITK
- [WFP]bios_wp protection has not been enabled
- Add SMBIOS OEM String modification capability in ITK
- After clear CMOS, EWS doesn’t display about CMOS log when boot to BIOS setup
- MMIO size set to Auto/1G can't boot to BIOS with NIC Card-XL710 in Legacy modeQ2'18
- BIOS Change for #CCB 2083 [Syscfg tool]Add option to configure fan pwm offset in syscfg on Purley
- Inject Memory Address Parity error and no error event occurred in SEL accordingly
- Change "CPU Power and Performance Policy" from "Balanced Performance" to "Performance" on the custom BIOS capsule by ITK tool, related items "C1E" can’t be changed automatically.
- [PC Production] Sync Skylake Production code to PC Production --CL 541242 5386244: BaseTraceHubInitLibNull references non-existing SkylakeSiPkg
- [PC Production] Sync Skylake Production code to PC Production --CL547293 5386319: CLONE SKX Sighting: [CLX Enabling] 2933 mc transient error
- [PC Production] Sync Skylake Production code to PC Production --CL556508 5386005: [SKX] Purley BIOS NTB PPD Option Setup is Reversed
- [PC Production] Sync Skylake Production code to PC Production -- CL558559 5386307:Some validated DIMMs have not been included in the DimmWT4 table
- [PC Production] Sync Skylake Production code to PC Production -- CL558628 5385969: Advanced Memory Test failed at MT_CPGC_READ_WRITE
- [PC Production] Sync Skylake Production code to PC Production --CL570837 5386628: HECI_MBAR can be reallocated by ring-0 anywhere in the address map (BIOS vulnerability)
- [PC Production] Sync Skylake Production code to PC Production -- CL569535 5386412: 2SKT DEBUG build ASSERTs with a Security Violation
- [Purley]Clone from HSD - Security VT - PCH UEFI FW shall delay PCI Bus Master Enable(PCICMD.BME) until end of POST to prevent DMA attacks on UEFI FW in RAM
- [PC Production] Sync Skylake Production code to PC Production -- CL566239 5386475: System hangs after error injection during DIMM Address Translation
- [PC Production] Sync Skylake Production code to PC Production -- CL571328 5386488: 2006702382: NVDIMM not in memory map when NUMA is disabled
- [PC Production] Sync Skylake Production code to PC Production -- CL576560 5386813: Enable MSR_VIRTUAL_MSR_LLC_PREFETCH reconfiguration on Skylake B-step
- [PC Production] Sync Skylake Production code to PC Production -- CL579507 5386817: Add device IDs for QS/PRQ S LBG SKU
- BIOS POST messaging shows no errors when in fact a DIMM is mapped out
- [PC Production] Sync Skylake Production code to PC Production -- CL575833 5386751: Function RemovePsfAccess () is not called with SPS FW binary
- [PC Production] Sync Skylake Production code to PC Production -- CL582692 5386573: IioEarlyInit.c:IioPciePortEWL() swaps link_width and link_speed in EWL
- [PC Production] Sync Skylake Production code to PC Production -- CL558927 5386052: [220586227] Early SEC RC is not properly programming the HPET due to coding bug, causing rogue write to memory [IPS 220586227]
- [PC Production] Sync Skylake Production code to PC Production --CL 553223 + CL556549 5386074: ACPI table will miss some core with some specific bit mask processor
- Clone from 5386949 FW-UEFI-Vuln-2018-008 - "PSIRT-BIOS-2018-008 Additional protection for DCI enable"
- When hotplug NVMe HDDs the RSTe GUI location couldn't match actual HDDs location
- Sprint: XL710 show the same boot order name in Boot management
- CCB 2161 [Purley BIOS]Support more memory vendor DIMMs on Purley -- Apacer,ATP,Hyundai,Innodisk,intelimem,V Color
- [Purley BIOS] BIOS support for WFC, WFD, WFS cluster systems
- [BNP] Boot manager still show pcie device if disable it on PCIe Port Oprom Control. -->Fix CL552580 side effect
- NIC Port Mapping between Chassis and Windows Server OS are inverted on S2600BP SFP+, RJ45 and S2600WFT
- EWS and SEL viewer shown incorrect ME version when online update ME version
- [Purley BMC+BIOS]Need mechanism for BMC to return MAC addresses for add-in card on demand
- Purley: add two APIs in fast video ppi and protocol
- [WFP] After downgrade FD and ME, SUT will halt with beep code 1-5-1-2 when reboot

Changes in BMC v1.60.56383bef:

- [BMP]SSL/TLS use of weak RC4 cipher
- [BMP]Birthday attacks against TLS ciphers with 64bit block size vulnerability (Sweet32)
- [STP] Chinese characters are not displayed properly in Event Log page while login Web in Chinese
- [Purley BMC]Implement 0xD5 return code when user requests power on and system is already on
- Completion code for OEM get sensor reading(platform power consumption) isn't right when no ADM chipset is available.
- BMC User and Network setting will change to default after online update BMC to 1.59&AC cycle
- [BMP] Media will be unmounted after boot into OS
- [WFP] Media will be unmounted after boot into OS
- [BMP] Event log page can't be read via IE browser
- [WFP] The Event Log shown abnormally on EWS after pressed NMI Button.
- EWS: Use firefox browser to check the system event log, all the information is unreadable code unless clearing the browser cache
- EWS: There is a unreadable character in the system event log
- EWS: When set the language to Chinese, the event log information show unreadable characters
- EWS: It could not establish the session to EWS after setting the https port to customized value
- [BMP] BMC can't stuck in Safe mode after execute 4 times BMC watchdog
- [BMP] HTTPS Port can't login from other values after HTTPS Port modify 8443
- Remote ipmitool chassis power off returns error when chassis is already off.
- [KVM/VM] Virtual Media redirection fails installing OS and console spews SSL errors
- [BNP LCR]Sensors are not correctly display in one cycle when run AC/DC cycle test
- [BMP] Enable Remote Debug function commnad response incorrect via BMC Shared LAN IP
- [Purley BMC]Increase KVM timeout to 1+ minutes
- EWS Uesr Enable is blank
- [BMP] EWS some information will be abnormal via IE browser
- [STP] There is no display information for DIMM and FRU in system information while login Web by using IE
- [WFP] Event log page can't be read via IE browser
- IE: After updating the BMC_1.58, it could not show the system event log in EWS
- BMC EWS GUI SEL Fails to Finish Loading
- BMC Web console fails to show FRU and Memory information after update to SUP x0135
- [BNP LCR]Event log “Sensor failure—HSBP temp -- Asserted” during AC/DC/linpack test
- Sometimes system will generate an abnormal event log about “Sensor failure—HSBP temp -- Asserted” and status LED show green blinking
- [BNP] 17 of 3456 nodes ( 9 of 864 system) failed EST for intermittent BMC FW Health unable to read HSBP Temp sensor
- [BMP]profile can't be shifted by the riser number
- RKVM can't launch if we have setup port forward from external IP address to internal address
- [BMP] Event log page can't be read via IE browser
- [BMP] Network configuration will be abnormal on EWS after stress VLAN ID test
- [WFP] Network configuration page can't worked on EWS after stress VLAN ID test
- Get Security Version Information returns 00 00, hence no way to know the security revision of the firmware.
- ReadSelfTest command response not as expected and the command missing in EPS
- [KVM/VM] Java pegs the CPUs on Linux when kvm/virtual media loses connection to the BMC
- [KVM] - The TLS ciphers used by KVM (port 5902) and USB (port 627) allow weak encryption algorithms and ciphers

Changes in FRUSDR 1.37:

- When retrieve the "P1/P2 Temperature" threshold by command or EWS, it shows "00" or "NA"
- [S2600BP] 1 of 2000 nodes failed for intermittent +1.05V_PCH_Aux SEL event, crossing upper non-critical threshold
- Rename QPI sensor name from QPI to UPI

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 Purley_1.04.f80688d0.bin
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.