Intel S2600BPS Server Board BIOS/Firmware 00.01.0010 Download

Posted at November 21, 2024 by PCI-DB Team

Intel S2600BPS Server Board BIOS/Firmware 00.01.0010 Description

Versions:

- System BIOS - 00.01.0010
- ME Firmware - 04.00.04.294
- BMC Firmware - 1.43.33e8d6b4
- FRUSDR - 1.30

BMC Firmware Changes:

- [S2600WF] NM configuration Couldn't dispaly the memory power policy in the EWS
- No fwpiaupd.efi version from EFI SUP package
- Use BMC_1.43.1ec4fc15, while entering the BIOS UI, the EWS SEL Log change the Date and Time to 1970.
- [VMViewer]Fail to run the script of fulltest.sh on S2600ST Base SKU.
- iKVM wasn't able to launch after configuring the router for IP map
- [S2600BP] L9 systems BMC log time set to 01/01/2015 or 01/01/2016
- Q4'17 [Xeon Scalable Family BMC] Change behavior for unconditional power off to work around ME bug
- [S2600BT] SUT shut down during first reboot after IFWI update. CRITICAL events on SPS and ME
- BMC Video signal lost(Black Screen) after a randomly time of normal use
- iKVM Video signal lost(Black Screen) after a random time
- [S2600BT] Lots unexpected events logged during execute 3 remote scripts and 1 local script.
- [S2600WF] Lots unexpected events logged during execute 3 remote scripts and 1 local script.
- [S2600BT] Deleting Alert Destination would show wrong message
- [S2600WF] Deleting Alert Destination would show wrong message
- [S2600WF] SOL Log can't download by EWS after record a lot of logs.
- [S2600WF] LNET Router BMC Reporting PS1 Status, P1 and P2 Status, and Fan Non-redundant:Insufficient Resources events on OS and DC Cycling
- [S2600BP] OpenIPMI driver fails to detect BMC on startup.
- [S2600BT] The time stamp in sellog is incorrect after offline flash BIOS , BMC , set clear CMOS jumper and remove battery.
- It generates some incorrect event logs in the AC cycle stress test
- Sometimes system will generate an abnormal event log about “Sensor failure—HSBP temp -- Asserted” and status LED show green blinking
- [S2600WF] NM configuration Couldn't dispaly the memory power policy in the EWS

System BIOS Changes:

- Rename BIOS ID from X0108 to R0010.
- Higher security ID from 04 to 05 because Microcode 3c include security patch
- Integration BIOS ACM to 1.3.4
- When hotplug NVMe HDDs the RSTe GUI location couldn't match actual HDDs location.
- [S2600BP]Some variables cannot load default when it was deleted after SUT reset
- CCB 2076] Allow user to change serial communications setting values independent of Console Redirection and Serial Over LAN state
- [s2600BT] System boot no hotkey string displayed on POST diagnostic screen with change System Boot Timeout value to 30 and unplug the proper markerfile (payloadsig.txt) USB Key devices.
- [S2600WF] Smbios Type 8 doesn't list table of CPU1 PCIe_SSD port connector on WFQ
- [Retimer]The system HDD5~7 carrier LED no display on first power on.
- Request to modify PCH SATA Tx De-emph and Rx CTLE setting
- Integrate latest v2.021R8153 EFI driver
- ITK modified Bifurcation settings for Riser slots will revert back to factory default value after pressing f9
- [CCB 2005]S2600WF: support WRG Retimer on S2600WF system
- [CCB 2005]S2600BP: support WRG Retimer on S2600BP system
- [S2600BP] Boot manager still show pcie device if disable it on PCIe Port Oprom Control.
- BIOS F2 menu doesn't show drive's OPROM under re-timer AIC in slot 4 when populating slot 2 with RSP3WD080
- C1E help text character display abnormal under console redirection
- Unable to locate/fault/rebuild instructions to NVME drive from EFI tool and OS for drives under retimer AIC
- RAID module RMS3HC080 and Software RAID RSTe can't work together on a S2600WF system
- #CCB 2049:To add ITK option to change MMIO High base to support various PCIe cards and Some OS compatibility issue
- CCB#1896: iSCSI Boot Options Support for RSD 2.2 Spec.
- RSD [S2600WF]: Provide SMBIOS table type 192 for RSD 2.2 Spec.
- [S2600WF] Lan Device will disappear if only enable one NIC port after two NIC ports both are disabled.
- [S2600WFQ] Boot time becomes very slowly, almost 6 times after flash FTPM Enabled Capsule file
- [HaT] 3rd party code (OPROMs) can fake their TPM measurement
- #CCB 2145: Expose BIOS option [CPU Power and Performance Policy] to ITK and Syscfg
- [S2600BP] CHIPSEC test find all PRx set to 0 after enable security.
- [S2600BP] the Current Usage of SMBIOS Type 9 - System Slots are all In use even no PCIe Device attached with -F CPU
- [PC Production] Sync Rp code to PC Production
- CCB#1896(S2600WF): Provide SMBIOS table type 197 for RSD 2.2 Spec.
- CCB#1896:(S2600BP): Provide SMBIOS table type 200 for RSD 2.2 Spec.
- [S2600WF] Modify Legacy Boot Order "EFI Shell" item via ITK do not take effect, shell always in the Bottom.
- Iflash32 utility can't get ITK modified custom BIOS revision string correctly.
- S2600ST QAT SKU PCH PCIE Uplink margin failed on Silver Build 3(PCH=QN1L B2)
- RSD [S2600WF]: Provide SMBIOS table type 192 for RSD 2.2 Spec.
- [Retimer]The system HDD5~7 carrier LED no display on first power on.
- Rp RAS code sync CL528211 5386077: Mirrorfailover should happen when mirrorfailover=1 and (mccmdvld=1 or errortype[4]=1)
- [S2600WF] Add one Switch/Retimer card, RAID controller still shows in EFI shell via PCI command after disable VMD
- RSD SMBIOS table was overwritten by OOB RSD SMBIOS table
- RSD: [S2600BP]Current link speed always is 0x40 in RSD SMBIOS type 190.
- CCB#1896: Provide SMBIOS table type 199 for RSD 2.2 Spec.

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.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Intel Drivers