Introduction
Provides Intel® Server Board M50CYP Family BIOS and Firmware Update Package for UEFI (R01.01.0010)
Available Downloads
- Size: 30 MB
- SHA256: B1277F6EB3BDCE7E7008934BE83D9017E081D8F96E689D528CA0CC59C7A66436
Detailed Description
uEFI System Update Package (SUP) Installation and Operation Instructions
Intel highly recommends reading this document in its entirety before performing the system update.Verifying that your system meets the documented requirements will ensure a successful update and provide the most reliable system functionality after the update has completed.
Released - April 24, 2025
This update package includes the following production level system software updates and update utilities:
- System BIOS - R01.01.0010
- ME Firmware - 04.04.04.603
- BMC Firmware - 2.93.a858f4d1
- FRUSDR - 0.47
- Pmem - 2.2.0.1553
- CPLD - v5P1
sysfwupdt.efi - Version 16.0.12
Supported Products
Intel® Server Board M50CYP Family
Contact Intel for pre-production hardware support requirements
Important NOTES:
If you are on BIOS R01.01.0007 or earlier, update to CPLD v4p7 included with the BIOS R01.01.0008 package first. Reboot, then apply the rest of the BIOS R01.01.0008. Then you can update to R01.01.0009 or R01.01.0010.
- BIOS R01.01.0010 requires new secure boot keys for Microsoft Windows 2025:
- KEK – Microsoft Corporation KEK 2K Certificate Authority (CA) 2023*.
- DB – Windows UEFI CA 2023*, Microsoft UEFI CA 2023* and Microsoft Option ROM UEFI CA 2023*.
- To update the new KEK and DB keys, the previous secure boot keys stored in BIOS must be removed via the "UpdateNvram" parameter, via SUP (UEFI) or SFUP (Windows/Linux) update packages. The 'UpdateNvram' parameter can not be used, if updating the BIOS via the BMC Embedded Web Server (EWS).
- If using SUP/UEFI, modify the UpdBIOS_CYP.nsh script from
- sysfwupdt.efi -u R01010010_CoyotePass_LBG_ICX_UpdateCapsule_prd.bin ImmReset
- to
- sysfwupdt.efi -u R01010010_CoyotePass_LBG_ICX_UpdateCapsule_prd.bin ImmReset+UpdateNvram
- If using SFUP/WINLNX, modify the bios_update.sh from
- BIOS="R01010010_CoyotePass_LBG_ICX_UpdateCapsule_prd.bin -recovery"
- to
- BIOS="R01010010_CoyotePass_LBG_ICX_UpdateCapsule_prd.bin -recovery UpdateNvram"
- These will also restore all BIOS settings to default values.
- The above parameter are only necessary if you are using Microsoft Windows 2025. Other operating systems will not require these steps.
- To downgrade the BIOS to R01.01.0007 or older, set the PCH SVN Bypass jumper, and use a flash utility sysfwupdt version older than v16.0.9. (e.g. sysfwupdt.efi -u xxx.bin -recovery)
- To downgrade the BIOS to R01.01.0007 or older through EWS, first flash a BMC version earlier than 2.91.3b34a3ee
- If you are on BIOS R01.01.0006 and have the Admin password set, add the password parameter to the update
For example, Online update BIOS at EFI shell/OS: sysfwupdt -u xxx.bin Password=xxxx+ImmReset
To update the BIOS online through EWS, you need to enable the BIOS setup option: Server Management->Enforce Password Support. Otherwise, EWS will pop up a message and can't update the BIOS. xxxx is the BIOS Admin password that is set at BIOS setup.
- If you are BMC 2.91 or earlier, update to the BIOS R01.01.0009 package, including BMC 2.92 first. The BIOS R01.01.0009 package has additional BMC update parameters.
- To downgrade the BMC to 2.90 or older, set the BMC SVN Bypass jumper and add "-recovery" parameter
- The startup script checks the current versions of firmware. If the installed version of a component is the same as the target version, the script will skip that component and move to next one. To skip the current version check, edit "startup.nsh" and add a "#" before "FwVerCheck.nsh".
- If the system has never been updated, Intel recommends updating the recovery regions. The BIOS recovery region is already set to be updated in this version of the script. Use the two script files "UpdBMCRecovery_CYP.nsh" and "updCPLDRecovery_CYP.nsh" to update the recovery regions of the BMC and CPLD firmware.
- To update individual components, use: UpdBIOS_CYP.nsh, UpdM50FruSdr_CYP.nsh, UpdCPLD_CYP.nsh, UpdBMC_CYP.nsh, UpdCPLDRecovery_CYP.nsh, UpdBMCRecovery_CYP.nsh and UpdatePmemFW.nsh
System Software Requirements
To update the system software stack to the versions included in this update package, the system software stack currently installed on the target server system MUST meet the following, or else the update may fail:
- System BIOS - R01.01.0009
- ME Firmware - 04.04.04.500
- BMC Firmware - 2.92.19c01286
- FRUSDR - 0.46
- Pmem - 2.2.0.1553
- CPLD - v4P9
Important Information for the Update Procedure
- To complete update process of CPLD/Pmem/BMC/FRUSDR/BIOS, must execute the startup.nsh, it will update CPLD/Pmem/BMC/FRUSDR/BIOS and then the system will reboot automatically. After reset, the screen will be off and blue ID LED will be solid on for some minutes. Once update process is completed, the ID LED will be off and system will boot up again.
- Due to the new structure of FW using PFR, the first time the server is rebooted once FW has been updated, will take around 12 minutes on the first reboot to conclude the update process, on that time the screen will be off and the System LED will be blinking green/amber, after the first 3 minutes the blue ID LED will be solid on, once the process is completed the ID LED will be off and system will turn on again, after post screen the server could be rebooted a second time. The time to conclude the FW update process is an expected behavior and only presented on the first reboot part of the FW update process.
- If you want to flash a custom BIOS file "R01010008_CAPSULE_ITK.cap", first flash all FW ingredients including regular R01.01.0008 BIOS calling the "startup.nsh" and once all the FW has been updated and the server has completed the reboot process, flash the customized BIOS file "R01010008_CAPSULE_ITK.cap" calling the "UpdBIOS_CYP_CAP.nsh" script.
General Update 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 boot into uEFI shell.
4. Firmware update process will be started with Startup.nsh running automatically.
5. Once BIOS update process has successfully completed, system will reboot automatically and will take around 12 minutes with the screen off, after that time the server will turn on again.
6. After first reboot and post screen, the server could be rebooted a second time.
Verifying Updates:
1. After the final update has been completed successfully, reboot the system.
2. During POST, hit <F2> Key when prompted to access BIOS Setup Utility.
3. From BIOS Setup Utility main menu, verify the BIOS revision is the same as updated.
4. Move cursor to SERVER MANAGEMENT menu and hit <Enter>.
6. Move cursor to SYSTEM INFORMATION option and hit <Enter>.
7. Verify BMC Firmware revision is correct.
8. Verify SDR revision is correct.
9. Verify ME Firmware revision is correct.
10. or boot SUT into EFI shell, run "sysfwupdt.efi -i" to check SUT active firmware version.
CPLD Firmware version can be verified on BIOS main menu, Main->PFR
The System Software Update is Complete.
WARNING
- Do NOT interrupt or reboot or remove power from your system during the update process. Doing so may render your system inoperable.
- Do NOT attempt to downgrade the system software once loaded on to the system. Doing so may render your system inoperable.
Please refer to the respective "Release Notes" files for complete list of known issues, workarounds and detailed requirements:
- BIOS: Release Notes BIOS ####.txt
- BMC: Release Notes BMC ####.txt
- FRUSDR: Release Notes FRUSDR ####.txt
- CPLD: Release Notes CPLD ####.tx
This download is valid for the product(s) listed below.
Disclaimers1
Product and Performance Information
Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.