Diagnostics and Firmware Update Utillity for Backplane Controllers MG9073S, MG9077 and MG9082
from American Megatrends, Inc. verison I3.13 1/8/09
CONTENTS
________
1.0 Overview
2.0 Installation and setup instructions
3.0 Web information and support phone Number
4.0 Notices and trademarks
5.0 Disclaimer
1.0 Overview
________________________
1.1 This utillity can perform a diagnostic scan and query of the Backplane Controllers MG9073S and MG9077. The controllers are typically located
on backplanes and connected to the system through an I2C/SMBus.
There may be one or more devices present in one system. This utillity can
be configured to scan for all occurances of the device in the system,
even if the devices reside behind a multiplexer.
Command-line parameters are used to configure the access mechanism and
scanning methode of the tool.
1.2 Limitations
Although the utillity can upgrade multiple instances of backplane controllers
in the same system, they must all be of the same type, since only one
binary file can be specified.
1.3 Log-file (log.txt)
The utillity generates a logfile that contains all technical details of the
from start to finish during the execution of the program. This log-file is
over-written every time the program runs and is placed in the same directory
as the executable. If a log.txt file already exists, it will be renamed to
logprev.txt, so that two levels of log files are preserved.
The log-file is not intended to end-user interpretation, but is useful in
by the tool vendor in the analysis of a problem or failure. For any support
issues, please collect and provide the log.txt file generated.
1.4 Dependencies and Prerequisites for the update:
For all Linux versions the tool requires OpenIPMI drivers to be present
installed, and running.
For all Windows versions the tool requires the Microsoft or OSA IPMI
drivers to be installed and running.
For DOS direct-IO is used, and no drivers are required.
2.0 Installation and setup instructions
______________________________________
This utility will update the firmware of one or more backplane controllers.
A scan is performed first to locate all instances of the controller.
When the tool is run without specifying a firmware binary, a list of the
devices found is displayed, and the firmware is not upgraded on any of the devices.
2.1 Performing firmware update
_______________________________________
- Run the tool by specifying the executable followed by command line options
- The command line interpretation is identical under DOS, Windows and Linux
2.2 Full List of Command Line Options
_______________________________________________
Usage: mg90tool [options]
-f file Firmware file
-u Unconditional Upgrade, does not ask to confirm
-c Continous Mode, upgrades same firmware continously
-c[NUM] Continous Mode, upgrades [NUM] times
-a Append log-file (only in Continous Mode)
-i Scan Addresses 0xc0 thru 0xc6
-q Suppress all screen output (quiet mode)
-b[NUM][NUM] BusID scan range [NUM] must be between 1-9
(defaults to -b35)
-ma[NUM] Enables Mux support and specifies Mux Address [NUM]
(for example: -mae6 specifies mux at slave addr 0xE6)
-mc[NUM][NUM] Mux Channel scan range [NUM] must be between 1-9
(defaults to -mc24, requires -ma)
-ms Manually Send Mux switch commands
(defaults to expect BMC to switch mux, requires -ma)
-d Diagnostic Mode, blinks LEDs and reads mated status
-vl Verbose log file
-vpd Get VPD Data
-i2c[ADR][LEN] The address for the VPD, if omitted defaults to address 0xa0 and lenght 16
-sc[FIRST][LAST] Scan Channel. Used as the upper nibble of the BusID
-?, -h, --help Displays this screen
2.3 Command Line Examples
_______________________________________________
Scan BMC busIDs 0x01 though 0x0f: (all possible busIDs)
> mg90tool.exe -b1f
NOTE: The default is to scan only 3 though 5
Scanning Behind a mux:
> mg90tool.exe -b35 -mae6 -mc24
NOTE: This will scan for the presence of a mux ad address 0xe6 and then
scan mux-channels 2 through 4. The mux channel is the upper nibble of the
BusID field. This option requires that the BMC sends the correct mux switching
commands according to the upper nibble.
Scanning behind a mux and sending mux switching commands:
> mg90tool.exe -b35 -mae6 -mc24 -ms
NOTE: The =ms switch will cause the application to send the mux switching commands
explicitly before each access to the device
Scanning Channels:
> mg90tool.exe -b88 -sc02
NOTE: This will scan only BusID 8, but will scan channels 0,1 and 2.
The resulting BusIDs for this command line will then be: 0x08, 0x18, 0x28
This is typically used if the device(s) are behind a mux, and the BMC is sending
mux-switching commands based on the channel.
2.4 Diagnostics Mode
_______________________________________________
Running Diagnostics:
> mg90tool.exe -b35 -mae6 -mc24 -d
NOTE: This command line will invoke a diagnostics mode after the scan.
This is the output of a typical diagnostics mode session:
************************************
ENTERING DIAGNOSTICS MODE
************************************
Activity LED Test:
Are all activity (green) LEDs active?
Press Y or N (Yes or No):
[Y] Key pressed. Test passed.
Status LED Test:
Are all status (amber) LEDs active?
Press Y or N (Yes or No):
[Y] Key pressed. Test passed.
Individual Backplane Drive Mated Test:
Is the active backplane a 2 slot with 1 drive(s) inserted?
Press Y, N, or L (Yes, No, or Loop):
[Y] Key pressed. Backplane passed.
************************************
DIAGNOSTICS SUMMARY:
************************************
Devices Tested: Addr: 0xc0, BusID: 0x14:
Activity LED Test...........................Pass
Status LED Test.............................Pass
Slots Mated Test............................Pass
2.5 Firmware Upgrade Mode
_______________________________________________
Upgrading firmware for MG9077 behind a mux:
> mg90tool.exe 9077_10.bin -mae6 -mc24 -b44
NOTE: Scans bus 4 only and upgrades all devices found to the binary specified
The MUX is at address 0xe6 and uses channels 2 through 4.
2.6 "quiet" upgrade mode
_______________________________________________
Specifying -q as a command line switch causes the utillity to run completely
without any display output to the console. The log-file is still generated normally.
The "quiet mode" is intended for upgrade distributions where a highe level
upgrade utillity invokes this utillity and handles all interaction with the user.
2.7 Directory Structure
_______________________________________________
The executable has the same name for all versions.
The supported Operating Systems are distinguished by folders.
bin\dos DOS
bin\lnx Linux (RHEL4, RHEL5, etc.)
bin\win32 Windows 32-bit
bin\win64 Windows native 64-bit executable
2.8 32-bit vs 64-bit Operating Systems
_______________________________________________
Under Linux versions, the 32-bit executables will also run under 64-bit OS versions
Under Windows versions, the 32-bit will run even in 64-bit Windows environments,
except under Windows PE, which require the native 64-bit executable.
3.0 Web information and support phone number
_________________________________________
3.1 IBM Support Web Site:
http://www.ibm.com/support/.
For a list of supported operating systems on legacy (non-shipping)
controllers, see
http://www.ibm.com/servers/eserver/serverproven/compat/us/.
You can receive hardware service through IBM Services or through your IBM
reseller, if your reseller is authorized by IBM to provide warranty
service. See
http://www.ibm.com/planetwide/ for support telephone numbers, or in
the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378).
In the U.S. and Canada, hardware service and support is available 24 hours
a day, 7 days a week. In the U.K., these services are available Monday
through Friday, from 9 a.m. to 6 p.m.
3.2 IBM eServer xSeries Web Site:
http://www.ibm.com/eserver/xseries
3.3 If you have any questions about this update, or problems applying the
update, go to the following Help Center World Telephone Numbers and URL:
http://www.pc.ibm.com/qtechinfo/YAST-3P2QYL.html.
4.0. Notices and trademarks
______________________________
4.1 The following terms are trademarks of the IBM
Corporation in the United States, or other countries
or both:
* IBM
* Advanced System Management
Other company, product, and service names may be
trademarks or service marks of others.
5.0. Disclaimer
__________________
5.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF
ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS
OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN
THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM
GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.
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.