CUMULATIVE RELEASE NOTES FOR LSI MFLASH UTILITY
-----------------------------------------------
( for SCSI And Intelligent IDE MegaRAID Cards)
FEATURES OF Mflash Utility PROGRAM:
----------------------------------
a)mflash utility is a Command Line Interface program
b) It supports 8-ld and 40-ld MegaRAID Cards
40LD: 471/475/493/489/488
/511/ Discovery system/494/503
/518/520/533/520-0.
8LD: 466/467/428/438/434/762.
c)Supports silent flashing without user input.
d)Multiple adapters can be flashed one after another
using the same utility in same session.
e) Flash utility will find all the images files from the current directory
for flashing only for the controllers available in the system
f)Utility will compare the current version and the version in the file and
then flash if /v option is used
g)Can be used to force flash some adapters with files given with /f option
h)Flashes the controller with corrupt or no firmware automatically
detecting the current firmware state.
i)Flashes with corrupt firmware and an running boot
block through boot block with /b option.
(Applicable only for certain 40-ld controllers)
And flash utility will ignore any file in the current directory
from being flashed with /i option
j) Will output information date like if flashed successfully or not -
needs reboot or not in the xml format when /xml used.
k) Supports flashing any image without checking the
signature with /p after getting the filename from
the user.
l) Flash progress will be shown as percentage + progress bar with current
component being flashed like BIOS, Firmware etc(applicable only for
certain 40-ld controllers)
FACTS/LIMITATIONS:
-----------------
a)Will not find files in subdirectories or in other directories.
b)If reboot in the middle of flashing, configuration as well firmware may get corrupted.
c)All I/O's will be stopped during flashing process by the firmware.
d)No other controllers other then above listed will be flashed.
e)For flashing with corrupted firmware Himem.sys should be loaded.
Utility may take longer time to flash with corrupted or no firmware.
f)No support added for 531-series card's 3 mode 0 support.
************************
This Release
************************
[10/17/2003: LSI Ver3p20: Anuj Jain]
{
1. CR LSID100004716: Add path support to the flash utility for /f command line
argument.
}
********************
PREVIOUS RELEASES
*******************
[09/29/2003: LSI Ver3p20: Bibhu Das]
{
1. For SATA 6 controller the firmware version was corrupted is fixed.
}
[08/08/2003: LSI Ver3p19: Bibhu Das]
{
1. For 1035 controller the firmware and bios versions were not showing properly is fixed.
}
[05/19/2003: LSI Ver3p18: Alpha Test release: Bibhu Das]
{
1. 1035 support added
Note:
------
1. Developer level test is done with single 1035 controller ( 03-01010-03 ) with 1035gen.rom image (size: ~ 852 KB)
2. There are some debug messages kept intentionally for this test release -- only in the 1035 card path.
3. It is observed that the 1035 card used for testing sometime failed to response to the command issued to it.
4. This test version could not able to find F/W and BIOS version from the image though those were available from the existing F/W inside the card.
}
[3/7/2003 : LSI Ver 3.17 : By Rajesh Prabhakaran]
{
1. Supports any new controllers by firing Get Check-word (0xA4-0x37) command to get the check-word and proceeds flashing.
Please Note: Any new controller with new check-word will not work(all functionalities), only a new controller added that has its check-word already hard-coded in the program will have its all functionalities work.
2. Updated mode 0 flashing to flash additional chip & controllers (This new addition is not tested)
}
**************************************************************************
PREVIOUS RELEASES
**************************************************************************
[12/17/02 : LSI Ver 3.16 : By Timir Pandit]
{
- multiple adapter type showing from firmware enquiry was showing
data for last 40-ld adapter for others. Fixed in this release
-Version string tells date of generation also since this version
Developer Level Testing:
-Checked appearance of distinct adapter-type strings in mixed environment
of 471+493 cards in the system.
Flashed a 466 card and a 493, 471 card all same session.
No other testing is done at developer's end.
File Details:
MFLASH.EXE 131,408 12-17-02 5:58p OS=DOS
}
[11/25/02 : LSI Ver 3.15 : By Bibhu Das]
{
- multiple adapter type showing from firmware enquiry added
}
[10/14/02 : LSI Ver 3.14 ]
{
1. Bug Fix for 503 : Problem in detecting the controller is fixed.
}
[5/9/02 : LSI Ver 3.13 ]
{
1) Added support Verde,LSI ZCR. - not tested
2) Checking for back ground activites before flashing.
3) Read/write of NVRAM configuration before flashing.
}
[3/27/02 : LSI test release]
{
1)Added support for 518 & 520 controller. Supports mode 0 flashing for 518.
}
[ July-09-2001: AMI : Ver 3.13 ] --- this should be HP -- rajesh. clarify ??????
{
Mflash.exe ver 3.13 : 7-09-01 ]
Please ensure himem.sys is loaded before running mflash in Mode 0.
Also, the Everest controller should not be in slot 8 in "T11 system" for flashing in Mode 0.
Support added for HP Everest card in Mode 0.
Done only for a special manufacturing case for flashing some 100-150 cards.
This version of mflash will automatically detect an HP Everest in Mode-0.
without any command line options. The vendor/device/sub-system id it will look
for is 8086h or 101E/5309h/60E3h.
This version is not meant for GENERAL RELEASE.
}
[ July-05-2001: AMI : Ver 3.12 ]
{
Mflash.exe ver 3.12 : 7-05-01 ]
Please ensure himem.sys is loaded before running mflash in Mode 0.
Support added for HP Everest card in Mode 0.
Done only for a special manufacturing case for flashing some 100-150 cards.
This version of mflash will automatically detect an HP Everest in Mode-0.
without any command line options. The vendor/device/sub-system id it will look
for is 8086h or 101E/1964h/60E3h.
This version is not meant for GENERAL RELEASE.
}
[ May-11-2001: AMI : Ver 3.11 ]
{
Mflash.exe ver 3.11 : 5-11-01 ]
Support added for 511 card (IDE) in Mode 0.
Done only for a special manufacturing case.
This version of mflash will automatically detect a 511 in Mode-0 without any command line options.
This version is not meant for GENERAL RELEASE.
}
[ May-1-2001: AMI : Ver 3.10 ]
{
Mflash.exe ver 3.10 : 5-1-01 ]
Support added for 511 card (IDE).
}
[ March-5-2001: AMI : Ver 3.09 ]
{
[Mflash.exe ver 3.09 : 2-26-01 ]
- Support added for 503, 477 and 494 cards. Mflash will detect these cards and display them as "503", "477" and "494" respectively.
- Removed /b option for AMI, ie., the utility will automatically detect adapter(s) with corrupt firmware and prompt the user to
flash them. If more than one flashable image is found, the user is prompted to select the appropriate file.
Restrictions:
- On the 477 card, the max. image filelength has been restricted to 1Mb due to lack of current firmware support for flashing files of
more than 1Mb.
}
[ February-22-2001: AMI : Ver 3.08 ]
{
Mflash.exe ver 3.08 : 2-22-01 ]
- Version no. change
}
[ January-18-2000: AMI : Ver 3.08(Test) ]
{
Mflash.exe ver 3.08(Test) : 1-18-00 ]
- This version supports 477 cards. It looks for P477 in the image files to determine if the image
file is a 477-flashable file.
- It checks for the sub-system id and if it is 477 then displays the card as a 477 card.
- This is only a test release for flashing 477 cards.
Testing done: None
}
[ November-16-2000: AMI : Ver 3.07 ]
{
Mflash.exe ver 3.06 : 11-16-00 ]
- A bug which was causing the system to crash during flashing has been removed.
- Version no. change
}
[ November-10-2000: AMI : Ver 3.06 ]
{
Mflash.exe ver 3.06 : 11-10-00 ]
- Display CTRM and WBIO version no.
- Testing with image files with WBIO and CTRM has not been done.
- Search for flash header at three locations in the image.
}
[ October-16-2000: AMI : Ver 3.05 ]
{
Mflash.exe ver 3.05 : 10-16-00 ]
- Added Support for 490 Card.
}
[ August-28-2000: AMI : Ver 3.04 ]
{
Mflash.exe ver 3.04 : 8-28-00
- There was a bug in detection of corrupted F/W with new vendor
ID i.e. 0x101E with Dev ID 0x1964. Now resolved in this version.
}
[ July-06-2000: AMI : Ver 3.03 ]
{
Mflash.exe ver 3.03 : 7-06-00
- In older BOOT block if sub-opcode BIOSFW_DOWNLOAD_OPCODE (0x03)
is ORed with 0x80 then the flash doesn't work, since older BOOT
block doesn't support it. In the newer BOOT block this was
rectified. So for older adapters now always firing
BIOSFW_DOWNLOAD_OPCODE without ORing with 0x80 when flashing
through BOOT block i.e. using /b option.
}
[ June-30-2000: AMI : Ver 3.02 ]
{
Mflash.exe ver 3.02 : 6-30-00
-When Flashing through boot block now waits in an infinite loop rather
than timing out for flash command to complete.
}
[ June-19-2000: AMI : Ver 3.01 ]
{
Mflash.exe ver 3.01 : 6-19-00
-Supports searching for alternate 471 cards with Vid=101Eh Did=1960h
along with old-style 8086h/1960h in case /b option is specified i.e.
flash thru the boot block.
}
[ June-12-2000: AMI : Ver 3.00 ]
{
Mflash.exe ver 3.00 : 6-12-00
-Supports searching for alternate 471 cards with Vid=101Eh Did=1960h
along with old-style 8086h/1960h.
-Supports searching for alternate 48x cards with Vid=8086h Did=B555h
along with old-style 1011h/0046h.
Earlier this 48x-detection had some bug - it would not detect
all 48x-cards in a mixed environment.
Corrected in this.
NOTE:
Version number is now started from 3.00 as 2.xx series is still
being used even though there were major changes for 40-ld and
others.
}
[May 15, 2000 AMI] v 2f01
Changes in this version:
1. Code added to detect another bridge 21555 for 48x controllers.
2. Now displays "493 " for 493 controllers instead of 471.
[May 03, 2000 AMI] v 2e01
Changes in this version:
1. Resovled the issue where mflash was detecting Adaptec OBSIDIAN as
48x.
p.s. Just a test version.
[Feb 08, 2000 AMI] v 2d01
Changes in this version:
1. Mflash was not showing proper status and was timing out after
flashing just one component, though other components were being
flashed in the background. This bug is solved in this release.
p.s. Just a test version.
[Jan 21, 2000 AMI] v 2c01
Changes in this version:
1. Proper percentage progress shown in case of 471/491/48x.
2. Proper display of what actually the F/W is flashing i.e. either
BIOS or FIRWARE or BOOT BLOCK for 471/493/48x.
3. Support added for 471/493/48x to flash different components
i.e.BIOS or FIRWARE or BOOT BLOCK at the same time. The F/W
as opposed to previous cards now flashes individual components
seperately one by one. Mflash now recognizes what is being
flashed and displays proper progress bars and percentages.
4. Now in the case of 471/493/48x version is shown only for those
components which are present in the flash.
5. Flashing through BOOT BLOCK is supported in the case when the F/W
is corrupt and BOOT BLOCK can flash the F/W. No progress bars
etc are shown during this since information for this is not
available at the time of this repairing.
p.s. Just a test version.
[Jan 06, 2000 AMI] v 2b01
1. Problem with 48x not flashing solved.
2. Now also displays the F/W and BIOS version in the image to be
flashed. For this the FLASH image should have the version set
at proper location, specified in the header of the flash.
p.s. there seems to be a problem when flashing 48x as percentage
progress is not shown properly, since info returned from F/W
doesn't look correct.
[Dec 28, 1999 AMI] v 2a01
1. Support for 471/493/472/491 and 48x type controllers added.
p.s. The version for BIOS and F/W to be flashed currently is not
being shown correctly. Also the card type will be shown as 471
for 471/493/472/492 and 48x for 488/489 type controllers.
This is just a test release.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.