Download Files
File Format: This file contains a compressed (or zipped) set of files. Download the file to a folder on your hard drive, then double-click it to unzip the set of files. Follow the instructions to complete the installation.
File Name: SAS-HBA_Firmware_NMR60_P13_24.16.0-0082_A00.exe
File size: 5.02 MB
To ensure the integrity of your download, please verify the checksum value.
MD5: 69e6234727c7d1dd23787fcd18bd5607
SHA1: 2f393f728942728c0ddad3288868f866beb87fed
SHA-256: 0eae5fade222e67b10d0d0fd987db00c73fd8b0e546629760b611ef26c5c0226
File Format: This file format contains plain text which can be viewed with a standard text editor.
File Name: EndUser LicenseAgreementType S_Rev.040512.txt
File size: 11.4 KB
To ensure the integrity of your download, please verify the checksum value.
MD5: c2ffe409366d225552ac6ed58f206b58
SHA1: 88522584d2ed8711c12c71ae9e569116a26e7b0a
SHA-256: b85aae437264a3f053c9efec6b47fa1ba6610de28b749a06c2fec3dfc87bf333
Fixes & Enhancements
Fixes -
Not Applicable
Enhancements -
Not Applicable
Supported Operating Systems
Novell SuSE Linux ES 11
Windows Server 2008 x64
SuSE Linux ES 9
Suse Linux ES 9
Suse Linux ES 10
Not Applicable
Novell SuSE Linux ES 10
Windows 2000
Windows Server 2008 R2
Windows 10, 64-bit
Windows Server 2003 x64
Installation instructions
Use the Firmware Update -f command to download a new firmware image. This process includes the following
operations:
1. Open the specified file.
2. Verify that the file is a valid firmware image, and run through all supported controllers.
The firmware image validation involves the following steps:
a. Check for a valid firmware header signature, as defined by the Fusion-MPT 2.0 MPI Specification.
b. Check for zero checksum on the firmware image.
3. Boot services
4. Clean flash erase everything except manufacturing area
5. Erase complete flash
6. MegaRAID firmware
Parameter Region to Erase
c.Determine whether the firmware image is valid for the controller being flashed.
To validate, the SAS3Flash Utility compares the PCI device and revision ID information from the controller's
PCI configuration space and from the list of devices in the supported devices firmware extended image data.
d.Check for a valid NVDATA extended image in the firmware image.
e.Check for NVDATA compatibility.
Check the signature of the CFGI directory header and CFGI product ID for validity on the firmware image from the file and on the firmware image from the controller if the controller already has firmware on it. If the checks pass and the controller already has firmware on it, compare the NVDATA product ID and NVDATA vendor ID from the NVDATA from the file with the corresponding IDs from the NVDATA from the controller.
f.Verify that the firmware image has a valid INIT image.
g.Verify that the firmware image has a valid BOOTLOADER image.
h.Determine if NVSRAM is present before allowing integrated RAID firmware flashing.
If NVSRAM is not present, do not allow IR firmware flashing.
i.Determine whether the initiator target firmware is present before allowing IR firmware flashing and vice versa.
If the initiator target firmware is present, do not allow the firmware update.
7. Perform a series of safety checks on each controller.
8. Display any firmware validation check failures for a given controller on the screen and log them to the log file.
9. Update the controller if it passes all safety checks.
sas3flash -o -f SAS9300-4i4e.fw (Firmware folder)
sas3flash -b mptsas3.rom (Utility\sasbios_rel)
sas3flash -b mpt3x64.rom (Utility\uefi_bsd_rel)