SC5100 Chassis Hot Swap Backplane Controller (HSC) Firmware Version 0.08 (Bootblock Version 0.47) Release Notes - January 17, 2002 Introduction. This document applies to the firmware used in the Intel Hudson-2 server chassis Hot-Swap SCSI Backplane (HSBP). File H2FHxxxx.HEX is used by the FWPIAUPD utility to update the Hot Swap Controller (HSC) code on a running server. A note about DCS numbers. The DCS numbers used in this document refer to Intel's internal defect tracking database. These numbers are generally not meaningful outside of Intel, they are included in these release notes as part of Intel's tracking and correction process. 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. There are no known compatibility issues or dependencies between system software revisions. 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|s] -nopc H2FHxxxx.HEX The notation -[p|s] means to include either the -p OR the -s, but not both. -p selects the primary HSC for updating, -s selects the secondary HSC for update. In a system with only one HSC installed, that is the primary HSC, so all users will need to use the -p switch. If two HSCs (supporting up to 10 drives) are installed, the FWPIAUPD command will need to be run twice, once with -p and once with -s. The order they are run is not important. (There is no way to tell the utility to do both at once.) The supplied PRIUPDAT.BAT and SECUPDAT.BAT batch files update the primary and secondary HSCs using the command lines described above. Regarding Boot Block Updates. The boot block on the HSC cannot be updated. 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, it will not be modified, that area of the flash chip is write-protected. However, when the utility attempts to verify that the code in the flash matches the code in the H2FHxxxx.HEX file, the verify will fail. Please note that this is a "false" warning - the boot block on the HSC 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 H2FHxxxx.HEX file. It is this data that changes with each new file and causes the verify to fail. SC5100 HSC firmware release history. HSC version 0.08 (Bootblock version 0.47), Jan 17, 2002 The Temperature Out-Of-Range bit and the ETA bit returned by the SAF-TE Read Enclosure Status command would set to 1 when the temperature rose above the threshold specified in the SDR, but would not reset to 0 when the temperature fell back below the threshold. This caused SAF-TE-based management software such as Mylex GAM to indicate an alarm condition after the alarm no longer applied. This has been corrected in HSC 0.08. The HSC would occasionally log a fan event rather than a temperature event when an over temperature condition occurred. This has been fixed in HSC 0.08. The FRUSDR.EXE program would occasionally not detect the presence of the HSC, causing SDRs for the HSC not to be loaded. This was caused by the HSC firmware and has been corrected in HSC 0.08. Occasionally the HSC would log a temperature event twice. This only occurred during periods of high SAF-TE communications and has been corrected in HSC 0.08. The HSC would report via SAF-TE a fan status of "unknown" for all fan sensors that did not have a corresponding SDR. HSC 0.08 correctly reports the status as "not installed". The boot block has been updated to provide additional troubleshooting information. The HSC boot block cannot be updated in the field so this change only affects boards manufactured with this firmware. HSC version 0.07 (Bootblock version 0.46), Aug 7, 2001 HSC version 0.07 (Bootblock version 0.46), Aug 7, 2001 Previous versions of the firmware would not handle a system with 3 power supplies, version 0.07 corrects this. These release notes had several errors regarding boot block versions and update commands, these errors have been fixed in this version of the notes. To update a running HSC to this firmware, use the enclosed batch files PRIUPDAT.BAT to update the Primary or only HSC in a system and SECUPDAT.BAT to update the second HSC in a system. HSC version 0.06 (Bootblock version 0.46), July 5, 2001 No DCS # - The HSC was formatting the Get Power Supply State command as if it were an event message, version 0.06 corrects this. To update a running HSC to this firmware, use the command: FWPIAUPD -nopc -oldhsc h2fh0006.hex HSC version 0.05 (Bootblock version 0.46), June 5, 2001 No DCS # - HSC version 0.04 would power all drives off and then on every time the HSC would reset. Resets occur due to entering and exiting firmware transfer mode, as well as when the Cold Reset command is sent to the HSC. The HSC is supposed to only power the drives off and on during the HSC power-up reset, version 0.05 operates correctly. Note that this change is entirely in the boot block. To update a running HSC from version 0.01, 0.02 or 0.03 to this firmware , use the command: FWPIAUPD -nopc -oldhsc h2fh0005.hex HSC version 0.04 (Bootblock version 0.45), June 4, 2001 Release Candidate 1, feature complete. Both the boot block and operational codehave been updated to use version 6 Device Information Blocks. Because of this, the new utility FWPIAUPD.EXE is required to update a running HSC. A copy of FWPIAUPD.EXE is included with this firmware. NOTE - This version of firmware was never released. HSC version 0.03 (Bootblock version 0.44), May 21, 2001 Beta 2 release, operational code is function complete. This version uses the new Intel-specific OEM command "Get Power Supply Status" to obtain power supply information. It also reports fault information via the updated Intel-specific OEM command "Set Fault Indication" as well as by logging events to the SEL. This version of the firmware requires the FWUPDATE utility to update the firmware on a running server. This version contains an updated boot block, however the new boot block is not essential to HSC operation. This boot block is the foundation for changes that will occur in the next major release of this firmware. HSC version 0.02 (Bootblock version 0.43), April 23, 2001 Beta 1 release. IPMI 1.5 compliant. All functionality should be complete with the following exceptions: The Device Information Blocks in the boot block and opcode block are not version 6 compliant. This is expected in the Beta 2 release. In the meantime, use the enclosed FWUPDATE program to flash in this code: FWUPDATE H2FH0002.HEX -NOPC Firmware is byte-checksummed rather than word-checksummed. Operation of some firmware transfer mode commands may change as the new firmware update program is developed. The firmware does not actually query the BMC for power supply data. Instead, it always reports that there is 1 supply and that its status is good. Checksums as reported by FWUPDATE.EXE: Boot block: FF2D Op code: 7E50 HSC version 0.01 (Bootblock version 0.42), January 10, 2001 This is the initial pre-production release of the HSC firmware. This version is IPMI 1.0 compliant rather than IPMI 1.5. Note that in order to flash this code over the original Baytown code, you must use this command: FWUPDATE H2FH0001.HEX -NOPC ROM Checksum (reported as "Flash operational code checksum" by the firmware update program FWUPDATE.EXE): 514A