Intel M50CYP2SBSTD Server Board OFU Firmware 01.01.0003

Versions:

- System BIOS - R01.01.0003
- ME Firmware - 04.04.03.53
- BMC Firmware - 2.81.99b20e11
- FRUSDR - 0.35
- Pmem - 2.2.0.1553
- CPLD - v3P3

Changes in BIOS:

- Change BIOS ID to SE5C620.86B.01.01.0003
- Merge code change to fix 2103639051: SUT will not auto power on at second T-1 state after flash BIOS recovery region via Sysfwupdt_V14_2_Build9.
- XCC microcode update to 0x0d000280
- HSD-ES:2103639075, Current Active Processor Cores is not changed after change Active Processor Cores via syscfg
- HSD-ES:2103639471, BIOS version in recovery region is incorrect with R01.01.0001 on active region and 0020.P20 on recovery region.
- HSD-ES:1508970720, Correct the help text of PCIE Correctable Error Threshold.
- HSD-ES:1508946483, Use efivarstore UBA_SETUP to judge if hide USB Rear Ports Enable setup item.
- HSD-ES:2103639392, Correct SMBIOS type 8 data on D50TNP.
- HSD-ES:1508930909, Missing device definitions for NorthPeak devices in PlatformPciTree10nm asi files.
- HSD-ES:2103639070, Adjust the code poistion of enabling CSMI for IMC bank.
- HSD-ES:1508846031, Please replace BIOS RAID Option "Intel RSTe" to "Intel VROC".
- HSD-ES:1508903189, Notify BMC when SMI update BIOS.
- HSD-ES:18015073494, Set the value of PcieMaxReadRequestSize to 4096B by default.
- HSD-ES:1508907381, it will not show any error message when user 2 name the same with user 6 name.

Changes in BMC:

- Update kernel to 4.9.268
- [Utilities] [SDPTool-2.1-0][Redfish] CPLD version showing incorrect
- Fixed the problem that the server was not started for the second time during the BIOS in-band recovery update (need the new version of CPLD) Fixed the beep code and abnormal SEL problems that occurred on the server during the BIOS in-band update warm reset
- EWS does not decode CPU ID correctly, there are additional “f” characters contained in process signature.
- Move "LicenseStatus" & "LastUpdateTime" to pre-defined schema
- Update HSBP CPLD to v1.90
- 3.5 in SIlver SKU HSPB IPMI returns incorrect LED status
- Update retimer to 1.2.0
- Upgrade glib to 2.68.1
- Update curl to 7.76.1
- Fix Can't upload SSL cert through EWS, warning message will pop up.
- Update kernel to 4.9.265
- Upgrade jQuery-ui to v1.12.1
- Update glib to 2.68.0
- Update openssl to 1.1.1k
- Update mbedtls and monit
- Update openldap to 2.4.58
- Update libcurl to 7.76
- Add busybox patch.
- Help info of ASMK is not completed on EWS.
- Fix WebSocket session timeout problem
- After OOB flash corrupted BIOS and reboot SEL log behavior is changed on BMC 2.78.
- Fix the caution message incorrect when upload invalid and expired SSL certificates in EWS.
- Temperature,RSSD Thrm Mrgn 2 (#0x62)" SEL event reported during DC cycle on TNP Storage Module [Storage][Pre-ST]BMC report "RSSD Thrm Mrgn 1,Temperature, Lower Critical - going low - Asserted/NVMEof-FIO about 1 day"
- Fix incorrect values in System NIC info and cannot access Drive.
- Correct the help info of Date & Time to align with User guide.
- [InBand-update]SUT will have beep code after flash BIOS and reset.
- [InBand-update]"VR Watchdog" and "Power Unit Failure detected" error event show in SEL after flash BIOS via Sysfwupdt_V14_2_Build9.
- SDR Report present empty (invalid) contain in System Debug log. (regression issue)
- Fix Advanced System Management Key” function link is disappear randomly after login/logout EWS multiple times.
- Fix cannot upload 4096 bits SSL cert via Redfish.
- Correct the EWS certificate time.
- Mount folder remotely via Virtual Media over HTML5 of EWS is not work.
- [klocwork] Fix klocwork issue: 56489
- Fix mount folder can not work of VM HTML5 at EWS issue.
- Restrict the private key length to RSA 2048-bit and verify the cert prior to replacing it.
- Fix SSL Certification file can not upload at EWS issue.
- Correct the interpreting when SMBIOS type 190 offset 0x17 value is FFh
- Fix Advanced Boot Options of BIOS Configurations can not loading via firefox/IE.
- Fix OEM SEL record type range 0xE0-0xFF overwriting non-timestamped data.
- Update HSBP version number in release note
- Correct the warning message when adding a user.
- Help info of ASMK is not completed on EWS as user guide.
- Check whether username contains the password prior to adding a username.

Changes in CPLD:

- Fix BMC will not reset when execute BIOS recovery online update. Files changed: t0_update.h、transition.h

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 Key when prompted to access the BIOS Setup Utility
03. From the BIOS Setup Utility main menu, hit the key to load BIOS defaults
04. Hit the 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.