Introduction
Provides Intel® Server Board M50FCP Family BIOS and Firmware Update Package for UEFI.
Available Downloads
- Size: 45.1 MB
- SHA256: A9785DD1FCAE82356F8895F07A14B0926B9AFB1C1FBAC6D3534D8EBAB93CA1FD
Detailed Description
Overview
This update package includes the following production level system software updates and update utilities:
- System BIOS: 01.02.0002
- ME Firmware: 06.01.04.047.0
- BMC Firmware: 2.20
- FRU: 0.07
- CPLD: v3p0
- sysfwupdt.efi: Version 16.0.9
Intel highly recommends reading Readme and Update Instructions.txt entirety before performing the system update.
System Software Requirements
- System BIOS: production version R01.02.0001 or later
- BMC Firmware: production version 1.95 or later
- CPLD: production version V3P0 or later
Important notes
- This FW version supports the 5th Generation Intel® Xeon Scalable Processors
- The update script in the Version R01.02.002 package contains the "-UpdateNvram" parameter. This parameter will update the NVRAM region and restore the BIOS Default settings
- FW R01.02.0001 updated the PCH SVN to 03, If a FW downgrade is required, refer to the SVN_Bypass Jumper on the BIOS Release Notes on this package
- 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 down rev the system software once loaded on to the system. Doing so may render your system inoperable.
- Please refer to the readme for detailed information on the package and update instructions.
- Please refer to the respective "Release Notes" files for a complete list of known issues, workarounds, and detailed requirements.
Supported Products
- Intel® Server Board M50FCP Family
Contact Intel for pre-production hardware support requirements
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.