SCB2 Server
Baseboard Management Controller (BMC)
Firmware Version 0.56 (Production Release)
(Bootblock Version 0.08)
Release Notes - April 1, 2002
---------------------------------------------------------------
Key Notes for BMC version 0.56:
-- A boot block update is not necessary if updating your system from BMC firmware version 0.44 or later. If you are flashing from a BMC firmware previous to version 0.44, see the Boot Block update instructions described towards the end of these release notes.
-- BMC firmware version 0.56 is ONLY compatible for use with SCB2 BIOS Production 2.0 build 39 or later and FRUSDR 5.0.P or later. The SCB2 BMC firmware version 0.56 is not backward compatible with any previous releases of BIOS or FRUSDR.
-- BMC firmware rev 0.56 is not compatible for use with ISC 3.5.1. SCB2 BMC firmware 0.56 and later is only compatible for use with ISC 3.5.2 or later.
----------------------------------------------------------------
Validation note:
-- Intel only validates system software releases that are current. System software is defined as BIOS, BMC firmware, and FRU/SDR. Intel does not perform regression testing of current system software with previous versions of system software. Intel recommends upgrading to the latest revisions of system software as necessary.
--------------------------------------------------------------
List of changes and issues addressed in BMC 0.56 from BMC 0.50
--------------------------------------------------------------
- The BMC was not properly handling a case where the number of bytes specified in the Partial Add SDR command did not match the actual number of bytes. BMC 56 correctly handles this.
- Earlier firmware allowed serial/modem parameter 7 flow control and baud rates to reserved values, BMC 56 does not.
- Earlier firmware did not create SEL entries when a processor was disabled by the Set Processor State command, BMC 56 corrects this.
- The BMC would log a "LAN Leash Lost" event incorrectly, BMC 56 corrects this.
- Sending a Get SM Signal command for chassis intrusion would erroneously cause the power alarm LED to light. This does not occur in BMC 56.
- The ACPI sensor would erroneously read 0 after entering and exiting firmware transfer mode. In BMC 56, the sensor reports the correct state.
- The BMC used to write to the persistent store SEEPROM several times per boot even if the data written was unchanged from the data in the SEEPROM. This was shortening the part's 10,000 write lifetime. In BMC 56, the part is written only if the data has actually changed.
- If both a correctable and uncorrectable front side bus error occurred simultaneously, earlier firmware would only
log the correctable event. BMC 56 will log both events.
- Set SDR repository Time command is not needed.
- Master Write Read I2C will return bad completion code when 0 bytes requested
- Master Write Read returns wrong completion code and handles insufficient bytes
- Firmware command support does not match latest Sahalee EPS.
- SyncSMBus command implementation uncertain.
- BMC: No per-interface max length checks
- BMC times out when trying to send 27 or more bytes on a FRU Write
- get LAN Cfg (param 8 & 9) when accessed should return 80h
- BB temp & FP temp sensor event status not cleared by RunInitAgent cmd.
- Config API tuple Axxx
- Comp code of the Platform Event Message cmd is wrong.
- Chassis name, restore policy, POH counter is cleared...
- Set and Get System Boot Options Parameters command returns incorrect values.
- Not Receiving LanAlerts for Chassis Intrusions
- Mismatch between EAS/EPS on FP NMI Assert.
- LanAlerts have Unknown Generator Sensor Device
- WHQL - LAN Leash Lost logged in SEL files
- Power alarm LED turns on after Get SM Signal switch command
- ACPI sensor reads 0 after exiting FW transfer mode
- BMC: Running ICTS tests converted for IPMI 1.5 causes BMC fail to function error
- Identify switch not ignored when set with Get SM Signal
- ISC fan reporting errors
- Volatile Settings are mainained after power actions
- Get System Restart Cause command not reporting correctly for Ctrl/Alt/Del
- PEF: Able to set parameter 1 to reserved values.
- PEF: Able to set parameter 2 to reserved values.
- PEF: Invalid requests to parameter six return incorrect completion codes
- PEF: Setting a filter to pre-configured trashes filter entry data
- PEF: No checking of set and block selector values
- PEF: Invalid requests to parameter nine return incorrect completion codes
- PEF: Invalid requests to parameter seven return incorrect completion codes
- Passing sensor error on BIOS splash Screen.
- Incorrect beep code for power good de-assertion
- BMC: FRB3 -- First FRB3 Reset occurs without a processor being disabled.
- PEF: Incomplete checks on request length
- PEF module doesn't check "enable PEF startup delay"
- BMC: Config API does not support partial sets
- PEF: Able to set parameter 10 byte 1 to reserved values.
- PEF: Invalid requests to parameter 12 do not receive "out of range" response
- PEF: Able to set parameter 97 to unspecified values.
- PEF: Invalid requests to parameter 96 return incorrect completion codes.
- SCB2 doesn't support SMI Timeout sensor
- PEF: No SEL event deposited for alerts.
- A power supply redundancy lost event is generated unexpectedly.
- BMC 16 - LAN alerts are lost or delayed indefinitely during boot
- BMC doesn't respond to broadcast Get Device ID
- PEF: Able to set last processed event ID byte 1 to reserved values
- PEF: Alert Immediate behavior is inconsistent
- POST can't start when all cpus was thermaltrip/ierr(by FRB config of PIA)
- PEF: Startup delays are nonfunctional
- BMC 18 intermittently does not communicate with HSC
- Heceta SEEPROM is re-written with existing data shortening life
- Fan sensors should be manual re-arm sensors in PIA
- ACPI mode should be set to Legacy Mode on system reset
- BMC stalls when system is reboot or power off (It is occurred on only Hodges)
- LAN - Channel 6 is using the gateway's MAC for traffic on same subnet.
- LAN Leash Lost for 05h Physical Security #0x05- falsely reported in SEL.
- The BMC doesn't send mux switching ping at POST end in Preboot only mode
- [HSC] Temperature Out of Range flag1 and ETA bit should not be hold to 1
- Incorrect HSC Fan failures are logged into BMC SEL
- BMC gets stuck in reset state after update with force jumper closed
- PEF: BMC gets stuck in infinite power cycle when matching generator ID 1
- Clear Message Flags (30h) returns 0x00 for unsupported OEM flag
- BMC: FP PwrBtn isn't passed down to chipset during minimum power-off time.
- Power cycle delay prevents the system from power on by FP power button.
- Comp code 01h for Get Configuration data command via LAN interface.
- FSB error monitoring should be enabled on memory monitoring enable
- NMI source incorrect when uncorrectable FSB error occurs
- Fan sensor callback issues
- PEF Spends too long inside the timer event callback
- PEF: Generator ID 1 and 2 match alogirhtm incorrect for IPMI 1.5
- Incorrect Timestamp in SEL
- Critical Interrupt Management
- Shasta BMC EPS needs clarification in FRU Table 2.12-1
- BMC 06 intermittently does not communicate with HSC 0.7
- BMC: The first keyboard reset following an FRB3 Timeout is ignored.
- Sanyo Denki fans exceed max raw sensor reading capability
- FAN boost problem by Ambient Fan Speed Control OEM SDR when degree below zero
- BMC E.52 update cleared configuration data.
- No SEL entries entered for FP Button or ACPI State Changes
- PEF: NMI source bit is not set when Diagnostic Interrupt is triggered.
- Config API Get Configuration of tuple A-1-1-1, incorrect response
- NMI switch is protected in secure mode
- BMC clears HE-SL AGP Error
- BMC: Invalid offsets in Get SDR Entry requests are not rejected.
- LAN - Power button unresponsive during high vol LAN traffic.
- Config API - Get Config Info (60h) does not return all tuples
- Config API, Get Config Info/Data returns unsupported data from tuple B,1,1,1
- 7200 RPM fans cause fan faults
- [BMC 23] - able to access invalid FRU device 12
- Power Good de-assertion provides no beep code
- Chassis Identify does not work over remote connection
- ICMB no longer working. Cannot connect.
- BMC: Able to enter firmware transfer mode over any interface.
- BIOS/FRB2 with action Hard Reset does not reset the system
--------------------------------------------------------------------------------------------------------------------
Boot Block Updates:
-- The BMC firmware is divided into two seperate components, the Boot Block and the Operational Code. The Boot Block is the area of firmware that contains the software used to update the firmware in a server. The operational code contains the software that controls the BMC controller. In most cases when a new version of BMC firmware is made available, only the Opertional Code will need to updated. Only on rare occassions will a BMC boot block be necessary. Generally, Intel recommends not updating the BMC boot block unless specified in these release notes. In the unlikely event of lost power occuring during a BMC boot Block update, the BMC will be lost and the baseboard would need to be replaced.
Updating the BMC Boot Block:
The following steps need to be followed when updating the BMC Boot block:
1) Power off and unplug your SCB2 based server
2) Remove the chassis cover
3) Move the jumper labled "BMC BT BLK" from pins 2-3 over to pins 1-2. The jumper block is located on the edge of the server board above the legacy IDE connector.
4) Power up your server and boot to a bootable floppy disk
5) Insert the BMC Firmware Update floppy disk
6) type the following at the DOS prompt: FWPIAUPD SCB2_56.Hex
Note: when running the firmware update utility from a floppy disk, loading the firmware .hex file into memory may take upto 2 minutes
7) The utility will ask the following questions:
7a) Upload or Verify? - Select 'U' to Upload
7b) Upload Boot Block? - Select 'Y'
7c) Continue to Upload? - Select 'Y'
8) When the update is complete, update to the latest FRUSDR utility compatible with this version of BMC firmware.
9) When updating the system software is complete, power off the server, unplug it from the wall, and move the jumper back to its original default position.
---------------------------------------------------------------------------------------------------------------------
How to update the operational code only.
The batch file BMCUPDAT.BAT included with this package will update
the BMC firmware to version 0.56. This batch file will not update
the boot block.
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.