SCB2 Server Baseboard Management Controller (BMC) Firmware Version 0.63 (Bootblock Version 0.08) Release Notes - August 22, 2002 Introduction. This document applies to the firmware used in the Intel SCB2 server Baseboard Management Controller (BMC). File SCB2_xx.HEX is used by the FWPIAUPD utility to update the BMC code on a running server. Updating the Firmware. The firmware is updated by the FWPIAUPD.EXE utility program that is included with this release package. This program can be run interactively (the program prompts the user for information) or with all information supplied on the command line. Using the command line is less prone to error, the command line to use is: FWPIAUPD -ni -u -o -p SCB2_xx.HEX Regarding Boot Block Updates. The boot block on the BMC is write protected and should never be updated unless these release notes specifically call for a boot block update. Never use the -b or -boot switch on the command line. If the utility is run interactively, always answer NO to the "Update the boot block" question. If you do attempt to update the boot block while the write protection jumper is in place, the boot block will NOT be modified. However, when the utility attempts to verify that the code in the flash matches the code in the SCB2_xx.HEX file, the verify will fail. Please note that this is a "false" warning - the boot block on the BMC is still perfectly fine since it is write protected. The reason the verify fails in this case is that each version of firmware places a time/date stamp of when the firmware was compiled into the boot block area of the SCB2_xx.HEX file. It is this data that changes with each new file and causes the verify to fail. To perform a boot block update, do the following: 1. Power down the server, unplug the AC cord and open the chassis. 2. Move the rear jumper on pins J1F1 (labelled "BT BLK WP") from the write protect position (front 2 pins connected) to the write enable position (rear 2 pins connected). 3. Plug in the AC cord, power up and boot to DOS. 4. Enter the command: FWPIAUPD -ni -u -o -p -b SCB2_xx.HEX 5. After the update completes, power down and unplug AC. 6. Move the rear jumper on pins J1F1 back to the write protect position (front 2 pins connected). 7. Close the chassis, plug in AC and boot normally. System software compatibility note: This version of BMC Firmware is compatible with SCB2 BIOS Rel 2.0 Build 39 and later only. Previous versions of BIOS are not supported. This version of BMC Firmware is compatible with SCB2 FRUSDR 5.0.P and later only. Previous versions of the FRUSDR utility are not supported. This version of BMC Firmware is compatible with ISC 3.5.2 and later only. Previous versions of ISC are not supported. This version of BMC Firmware is compatible with SSU rel 2R1 and later only. Previous versions of SSU are not supported. Known BMC Issues. When updating the BMC from BMC 4x or 5x to BMC 60 or later, console redirection (if enabled) will fail the first time the system is reset after BMC 6x is flashed in. Redirection failures can be avoided by doing an AC power cycle (which is the standard procedure) or by powering off then on again via the front panel power button. This redirection failure only occurs as an artifact of flashing in the new firmware, once redirection is restored it will continue to work normally. Also, flashing from BMC 6x to BMC 6x will not cause redirection failure. SCB2 BMC firmware release history. BMC version 0.63 (Bootblock version 0.08), August 2, 2002 - This version of firmware works with both the A3 and A4 steppings of the Super I/O chip. BMC version 0.62 (Bootblock version 0.08), July 23, 2002 (This version was not released to production) - Corrected the additional FRB3 logging that occurs if the Init Agent hasn't run. Specifically, the system would log the processor as offline but wouldn't actually take the processor offline. BMC 62 corrects this so that the processor is taken offline and the FRB3 is logged. BMC version 0.60 (Bootblock version 0.08), July 9, 2002 (This version was not released to production) - Using the GetSMSignal command to read the chassis intrusion switch state would cause the front panel fault LED to light and a spurious 3.3VSB event to be logged into the SEL. BMC 60 corrects this. This fix is mostly of concern to Intel manufacturing rather than end users. - The system would occasionally hang when exiting firmware transfer mode if the firmware was being updated from a floppy disk. This has been root caused to problems within the Super I/O chip on the baseboard, BMC 60 works around these problems to eliminate the hang. Note that it is always safe to update firmware from a floppy. The hang occurred after the new firmware had been flashed in and verified so no BMC corruption was possible. - BMC 60 adds some debounce to the chassis intrusion input to eliminate spurious "noise" events being logged. - The ADM1026 chip that monitors most voltages in the system would occasionally glitch and produce a spurious reading. For example, the 5V sensor might read 5V, followed by 2V and immediately back to 5V again. The voltage isn't actually making wild swings, the sensor chip glitch causes these readings. The firmware now performs averaging on these sensors to eliminate such glitches. - Multiple enhancements were made to BMC 60 to eliminate bugs that could spuriously cause an FRB3 error and take a processor offline for no good reason. In addition, BMC 60 now logs FRB3 and Processor disable events even if the Init Agent has not yet run. BMC version 0.58 (Bootblock version 0.08), June 26, 2002 - The firmware would occasionally log a spurious "SMI Timeout" event. Logging this was most likely when a USB keyboard and/or mouse was in use. BMC 58 corrects this. BMC version 0.56 (Bootblock version 0.08), January 11, 2002 Production release.