L440GX+ (Lancewood) Server Baseboard Management Controller (BMC) Firmware Version 1.24 (Boot block Version 0.33) Release Notes - 30 August 2001 Introduction. This document applies to the firmware used in the Intel L440GX+ Baseboard Management Controller (BMC). File LWFB0124.HEX is used by the FWUPDATE utility version 2.x to update the BMC code on a running server. ----------------------- Flash Update Advisory. ----------------------- When updating the BMC firmware, a boot block update is NOT required unless specified to do so in these BMC firmware release notes under the "Changes Incorporated" section, or by an authorized Intel Customer Service representative. If a boot block update is deemed necessary, L440GX+ users should ALWAYS update both the boot block and operational code at the same time, and not just update the boot block code. The L440GX+ BMC flash part erases the contents of the flash if a write to the boot block is attempted. However, if the boot block is protected (default) by the Boot Block Protect jumper at J4J2 on the baseboard, only the operational code will be erased. This leaves the system with incomplete firmware. The platform will now be in an unstable state until a complete firmware update is performed, i.e.; updating the boot block and operational code. ------------------------------------------------------------------ Firmware Update Utility (FWUPDATE) Version 2.0 Or Later Required. ------------------------------------------------------------------ Beginning with L440GX+ BMC 1.08, the firmware .HEX file is delivered in a new format. This format adds a "header" to the beginning of the file. This header controls the order in which various portions of the flash memory chip are programmed. Only FWUPDATE version 2.0 and later will work with this new file format, older versions of the utility will issue an "Invalid Hex File" error. Please note that the FWUPDATE utility, version 2.0 and later, is not backwards compatible with previously released L440GX+ BMC firmware .HEX files. The utility will issue an "Invalid Hex File" error message if an attempt is made to flash in firmware prior to ver 1.08. A compatible version 2.2 of FWUPDATE (the latest available at the time of this writing)is included in this firmware package for the users convenience. ------------------------------------------------------------------------------- Changes incorporated to BMC version 1.22 (Boot block version 0.33),28 March, 2001 BMC version 1.24 (Boot block version 0.33), 30 August 2001 - BMC 1.24 DTR output is directly connected to the COM2 serial driver chip, as is the system's COM2 serial port DTR output. When the BMC switched the mux to the system serial port, it was discovered that the BMC's DTR output remained low. The baseboard serial port had to overcome this low to drive a high DTR signal; in some cases the output drive wasn't enough to overcome the BMC. BMC 1.24 corrects this by setting it's DTR signal high whenever it gives the port to the system and driving it low again when it takes it back. ROM Checksum (reported as "Flash operational code checksum" by the firmware update program FWUPDATE.EXE): 4045 ---------- - BMC 1.21 would reset the system after performing a BMC firmware update. BMC 1.22 corrects this when updating from some previous releases of BMC firmware. A reset will not occur if updating to 1.22 from 1.13, 1.14, 1.18, or 1.22. A reset may occur after performing an update from 1.17. This will be addressed in the next release of BMC firmware. Note: customers that update the system software using an automated process, may need to modify their process depending on whether they experience a system reset or not when performing a BMC update to 1.22. ROM Checksum (reported as "Flash operational code checksum" by the firmware update program FWUPDATE.EXE): B289 --------------------------- Specification conformance. --------------------------- L440GX+ Baseboard Management Controller Interface EPS Revision 1.2. PEF/PEP EPS, Draft Revision 1.01. Emergency Management Port v1.1 Interface EPS, Revision 0.86 -------------------------------------- L440GX+ BMC firmware release history. -------------------------------------- (Release Candidate) BMC 1.21 changes: ROM Checksum=B8D6; Bootblock version 0.33 - The fix in BMC 1.20 neglected to include the VID sensors, BMC 1.21 corrects this. ---------------------------------------------------------------------------- (Release Candidate) BMC 1.20 changes: ROM Checksum= D4D8 (Bootblock version 0.33) - Some sensors does not respond on Lancewood BMC 1.19. Bug was found by exiting firmware transfer mode. The real issue was when the BMC executed a cold reset in response to exiting firmware transfer mode. Six sensors would return completion code 0xCE in response to a get sensor reading. The fan speeds were corrected by moving a variable to reset survivable RAM. The temperatures were fixed by re-initializing the MAX1617 devices. ------------------------------------------------------------------------------ (Release Candidate) BMC 1.19 changes: ROM Checksum = D25E; Boot block version 0.33 - In Intel manufacturing test fixtures, BMC 1.17 and BMC 1.18 would erroneously declare FRB-3 errors for processor 2. This was caused by several factors - the fixture supplies DC power to the board without waiting for the BMC to turn power on, which confuses several "power valid" checks, the fixture initiated a system reset while the BMC was attempting to power up the system, and a routine which was supposed to halt the FRB task until the BMC had powered up the system did not function correctly. This issue is not seen outside of Intel's factory and does not affect customer testing or usage. - BMC 1.18 didn't always clear the CMOS when the front panel CMOS clear function was used. This has been corrected in BMC1.19. Beginning with BMC 1.19, the HEX file used with the firmware update program is much smaller - 135 Kbytes rather than 309 Kbytes. This is due to use of an updated mapping utility that avoids filling unused areas of the file. --------------------------------------------------------------------------------- BMC 1.18 changes: (Bootblock version 0.33) NOTE: BMC 1.18 was never publically released due to the anticipated production release date of BMC 1.19 - Some operating systems and/or application programs can erroneously write to the CMOS memory when AC power is unexpectedly lost. Intel is not aware of any specific OS, application or combination of OS and application that will cause this. As the system undergoes a power loss, it becomes inherently unstable and any software currently executing can become corrupt, causing unpredictable errors. BMC 1.18 acts to prevent this by asserting reset signals to the processors and the chip set as soon as power fails. --------------------------------------------------------------------------------- BMC 1.17 changes: (Bootblock version 0.33 October 25, 2000) - The BMC was erroneously logging an FRB3 failure at every boot, BMC 1.17 corrects this. - The BMC commands the HSC to shut down the Hot Swap Backplane fans when the system entered S1 Sleep. However, it was discovered that some RAID cards do not spin down the drives during Sleep mode, thus posing a risk that the drives could overheat. Beginning with BMC 1.17, the BMC no longer turns off the HSC fans when in Sleep mode. - The EMP Skip Reinit bit wasn't being cleared after certain resets when in modem connect mode. BMC 1.17 corrects this. - When an FRB-2 timeout occurred, the BMC would erroneously indicate that an FRB-3 error had also occurred. BMC 1.17 corrects this. - BMC 1.15 wasn't recording any processor IERR's that occurred, BMC 1.17 does. - BMC 1.15 caused the system to not boot when the baseboard CLEAR CMOS jumper was installed. BMC 1.17 corrects this. --------------------------------------------------------------------------------- --------------------------------------------------------------------------------- (Release Candidate) BMC 1.16 changes: (Bootblock version 0.33) September 29, 2000 *Note BMC 1.16 was never production approved --- BMC 1.15 incorrectly monitored processor fans for processor slots that had terminator cards installed. BMC 1.16 corrects this by not monitoring the nonexistent fans. ---------------------------------------------------------------------------------- ---------------------------------------------------------------------------------- (Release Candidate) BMC 1.15 changes: (Bootblock version 0.33), September 27, 2000 *Note BMC 1.15 was never production approved --- Modem Ring Indicate would not cause EMP to reactivate under some condition. BMC 1.15 now activates correctly when Ring Indicate is asserted. --- The Set System Phone Number command 7Eh allowed reserved bits in the command to be set. --- The EMP command Set Password (73h) was erroneously requiring that all password characters after the first 0 character must also be 0, this is no longer true. --- After switching EMP from Pre Boot Only to Always Active mode, EMP would not connect when the modem Ring Indicate signal became active. This has now been fixed. --- The EMP Skip Reinit bit wasn't being cleared after certain resets. --- Forcing a mux switch from the system to the system or from the BMC to the BMC would deactivate the current session. This has been corrected. --- The Set Cooling Fault Light command used by the HSC to turn on the front panel cooling fault LED was originally designed to work with a single HSC. With 2 HSCs in a system, clearing a cooling fault on one HSC would turn off the LED even if the other HSC continued to have a fault. This has been corrected. The command now determines the source of the command and keeps the LED turned on as needed. Receiving the command from any source other than an HSC will override the HSCs and turn-on/turn-off the LED. --- When the system resets, any front panel fault LEDs that were turned on due to an HSC problem would be turned off even if the fault condition still persisted. This has been corrected. --- A non-Intel power supply was found that had a similar sensor to the Intel SC5000 power supply sensor at the same I2C bus address. Systems with this power supply would erroneously indicate faults since the sensor was not configured the same as the Intel SC5000 sensor. BMC 1.15 now requires that the SC5000 SDRs be loaded before generating any SC5000 power supply events or fault LEDs. --- The FRB3 algorithm used in the L440GX+ would often reset the processors twice, causing long boot times and a possible lockup with 350 MHz processors. The FRB3 algorithm has been re-written to prevent this. A 1-5-1-1 beep code is now sounded after all processors have failed to boot. --- The BMC task scheduler idle loop has been re-written to avoid excessive access to the flash part. This change is an enhancement to the scheduler & idle loop execution methodology. --- The BMC now sounds a 1-5-2-1 beep code when an empty processor socket is detected. ---------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------- BMC 1.14 Changes - EMP was not handling incorrect passwords correctly. The Submit Password command 72h now operates as follows: * While the lockout timer is inactive, a SEL entry is logged for each bad password. * If the user enters 3 bad passwords in a row, the lockout timer (30 sec) is started. * During the lockout time, good passwords will be ignored. Completion code 0x02 is returned for the Submit Password (72h) command. * During the lockout time, bad passwords will NOT generate a SEL event. Completion code 0x02 is returned for the Submit Password (72h) command. * During the lockout time, all passwords, good and bad, will restart the lockout timer. * Once the lockout time expires, the bad password count is reset to 0 and counting of bad passwords begins anew. If 3 bad passwords in a row are received, the lockout process begins again. - The Write SMS Message Buffer command 79h was erroneously discarding the first byte of data when the command was issued via EMP. - EMP connection could not be established in Always Active mode. The BMC was erroneously re-initializing the modem every time it detected a ring signal, thus causing the modem to not answer the incoming call. - Modem ring would not cause EMP re-activations. - The Set System Phone Number command 7Eh was erroneously being allowed via EMP Restricted mode. - The Set BIOS Flags command 7Ch was erroneously being allowed via EMP Restricted mode. - Approximately 1 in 20 times that the system was powered down via EMP, the EMP connection would be lost, requiring a manual power up. This was traced to new code introduced in BMC 1.09 that effectively turned off the BMC's serial transmit pin. - When using the Set System Phone Number command 7Eh to set a phone number in NVS block 1, the phone number storage area in the FRU would get corrupted. -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- BMC vresion 1.13 (Bootblock version 0.33). - Previous versions of the firmware did not report the status of the SUSSTAT1 signal in the response to the Get ACPI Configuration command. BMC 1.13 now reports a "1" for SUSSTAT1 when the signal is active, indicating that the server is in S1 sleep. - When Windows 2000 (or any ACPI OS) put the server into Standby mode (ACPI S1 sleep), the BMC did not automatically disable the watchdog timer. If server management software was using the timer when the system went into standby, the BMC would then reset or power cycle the server when the timer expired. To avoid this, the BMC now turns off the timer when the server enters S1 sleep. - When the server is placed into Standby mode (ACPI S1 sleep), the BMC turns off the baseboard fans and instructs the SCSI Hot Swap backplane Controllers (HSC) to turn off any fans they control. However, both the BMC and HSC continue to monitor the fans and log fan failures almost immediately. BMC 1.13 partially resolves this as noted below, a complete resolution requires updating firmware for the HSCs. BMC 1.13 now monitors the baseboard fans only when they are enabled by the BMC, this eliminates baseboard fan events when in S1 sleep. BMC 1.13 also issues a new "sleep mode on/off" command to the HSC when the server enters and exits sleep state. Existing HSC firmware (Astor II firmware 0.13 and below, Hudson HSC firmware 0.02 and below) will ignore this command. Thus, any fans run by the HSC will continue to spin, thus avoiding fan failure events being logged. Complete resolution to this will require Astor II HSC firmware 0.14 or later, or Hudson HSC firmware 0.03 or later. This firmware will obey the new "sleep mode" command which will both turn off the fans and stop monitoring them. - The BMC would log events when Single Ended SCSI drives were connected. This was caused by an incorrect comparison, this has now been corrected. ----------------------------------------------------------------------------------- ----------------------------------------------------------------------------------- BMC version 1.11 (Bootblock version 0.33) Bootblock change - BMC firware 1.11 contains new bootblock code, see below for details of the changes. Updating the bootblock in this firmware release is optional. The changes that were made do not affect the operation of the server. Bootblock changes: (Updating the bootblock in BMC 1.11 is optional. See "Flash Update Warning" above if you plan to update the boot block) - Modified the firmware transfer code to erase all of the opcode region before programming any area of the opcode region. Operational Code Changes: - Modified Get Device ID command, when in firmware transfer mode, to return an additional 6th byte for capabilities. The sixth byte indicates that no IPMI capabilities for accessing the SEL, SDR, FRU, or ICMB exist during firmware update. - When a Chassis Control power down or power cycle command was sent to the BMC, the system would power down but would not power up again until AC power was removed and re-applied. This has been fixed in BMC 1.11. - In an Astor II chassis, the server would always log a power supply redundancy lost event during each boot. This was an erroneous entry since the Astor II doesn't support redundant supplies. This has been fixed in BMC 1.11. - The server would not recover from a short term AC power loss in which 5 volt standby power to the BMC was not lost. BMC 1.11 correctly detects this and power cycles the server. - The server would not power up when certain non-ATX compliant power supplies were installed. Support for such supplies has been improved in BMC 1.11, however operation with non-ATX compliant power supplies is not guaranteed. - The BMC would not log an AC lost event in the System Event Log when installed in an SC-5000 chassis. This has been corrected in BMC 1.11. Users should note that the event is actually logged several seconds after AC power is restored, it is not logged upon power loss. - The server was taking 4 seconds to turn off power. This was due to notifying the Inter Chassis Management Bridge (ICMB) of the pending shutdown after I2C communications had been halted. The I2C timeout caused the 4 second delay. - Added support for the Hudson chassis 1+1 redundant power subsystem. - Added low-level drivers to access the AD1024 device on the Hudson Power Distribution Board. - Added the following new sensors; sensor 0x29 Power Unit : power cycle, AC lost sensor 0x2A Redundancy Lost : regained, lost sensor 0x2B Power Supply #1 : presense & failure detected sensor 0x2C Power Supply #2 : presense & failure detected sensor 0x2D PDB Temperature : threshold If a power supply failure is detected the power fault LED signal is asserted. Similarly, if a power supply fan fails the cooling fault LED signal is asserted. - Updated the I2C communications library to the latest version. This reduces the chances of communication failure under high I2C traffic loads. - Added a synchronization between power state changes and the I2C sensor tasks, and I2c traffic. This should also improve I2C communications reliability. -------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------- BMC version 1.08 (Bootblock version 0.30) Intel has determined that the method used to update the flash part is causing a degradation of the information retention properties of the flash part. This is causing corruption to the BMC firmware resulting in eventual loss of BMC functionality. The specific time at which the firmware becomes corrupted cannot be determined. A BMC failure may occur immediately after updating the firmware, or it may occur sometime after the update. To fully address this issue, Intel has determined an enhanced method for flashing the BMC firmware to the flash device. FWUPDATE utility rev. 2.x (where x is any number) is now released and must be used to update the BMC firmware. FWUPDATE utility ver 2.x will only be compatible with BMC firmware revisions 1.08 and later. -------------------------------------------------------------------------------------- -------------------------------------------------------------------------------------- BMC Version 1.07 (Bootblock version 0.30), November 24, 1999: - When event logging was disabled and a "clear event log" command was received, the BMC would not actually clear the log. It would appear to do so, but the next time the BMC was reset, the old contents of the log would appear. Beginning with BMC 1.07, the event log is actually cleared when the clear command is received while logging is disabled. - The Get Raw VID Values sensor command (30h) now returns all 5 bits of each processor VID, not just the lower 4 bits. - If AC power was lost for less than about 0.5 seconds, the BMC would not properly restart the system when AC was restored. -------------------------------------------------------------------------------------- BMC Version 1.06 (Bootblock version 0.30), October 15, 1999: The BMC allows up to 5 seconds between attempting to turn on the power supply via the PS_ON signal and receiving the PWR_GD signal back from the supply. However, the Intel Monet server uses a power supply that can require up to 10 seconds to come up. BMC 1.06 now waits for 10 seconds to detect the PWR_GD signal. -------------------------------------------------------------------------------------- BMC Version 1.05 (Bootblock version 0.30), June 9, 1999: - Changing processor lower critical or non-critical temperatures in the SDR from 0 & -5 degrees C to +5 & +8 degrees would cause lower critical & non-critical events to be logged at power-up. - Lower critical baseboard temps not being logged. Processor & baseboard temperatures no longer start at 0 degrees and slowly ramp up to operating temperature, they now reflect the operating temperature immediately after startup. - If you write the FRU and then cold reset the BMC, the power LED now winks at you quickly rather than turning off. -------------------------------------------------------------------------------------- BMC Version 1.04 (Bootblock version 0.30), June 4, 1999: - Enlight* power supplies did not turn on the system, now they do. -------------------------------------------------------------------------------------- BMC Version 1.03 (Bootblock version 0.30), May 28, 1999: - L440GX+d was determined to be at risk from a problem seen on N440BX with temperature sensors locking up the private I2C bus, causing FRU/SDR and SEL reads and writes to fail until the system was power cycled. This firmware resolves that problem. -------------------------------------------------------------------------------------- BMC Version 1.02 (Bootblock version 0.30), March 5, 1999: (Also known as ECO Release Candidate 2) - Voltage events incorrectly logged on sensors #7 and #8 (LVDS sensors). Fixed bug with regard to negative going thermal sensors. -------------------------------------------------------------------------------------- BMC Version 1.01 (Bootblock version 0.30), February 12, 1999: (Also known as ECO Release Candidate 1) - Upper and lower non-recoverable sensor events were ignored. - Secure mode floppy protect still on after secure mode disabled. - Get device ID command returns wrong BMC version. - Submit password (0x72) command not accepted from ISA. - Get sensor event message enable fails with certain data. - False lower critical events through ISC. - Sensor event commands 24h/2dh fail if sensor scanning disabled. - Power LED doesn't blink upon power supply failure. - ACPI: Fan fault LED illuminated in sleep mode.