============================================================================= Intel(R) Server Platform SE7520JR2 SR1400 1U SCSI HSBP FIRMWARE RELEASE NOTES ============================================================================= INTEL Enterprise Platform & Services Marketing Intel Corporation 2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA ============================================================================= DATE: September 11, 2006 TO: Intel(R) server platform SE7520JR2 SR1400 1U customers SUBJECT: SR1400 1U SCSI Hot Swap Backplane Firmware 1.10 Release Notes ============================================================================= LEGAL INFORMATION ============================================================================= Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any time, without notice. Intel is a registered trademark of Intel Corporation. *Other names and brands are the property of their respective owners. Copyright (c) 2004 Intel Corporation. ============================================================================= ABOUT THIS RELEASE ============================================================================= ****** IMPORTANT NOTE ****** * This release is made for back planes that have AMD algorithm compatible Flash Device. * Manufacturing - If upate happens in the factory (i.e. with out using "FAPIAUPD.EXE" software utility), then FW update SHOULD BE DONE ONLY ON AMD algorithm compatible flash devices. * Software - If update happens using attached batch file in this release package(Autoexec.bat), then it can be updated on any flash device because the S/W utility "FWPIAUPD.EXE" updates only OPCODE and Op Code is same for both Intel and AMD algorithm compatible flash devices. No boot code update is supported using FWPIAUPD.EXE uility. REVISION INFORMATION RETURNED BY GET DEVICE ID COMMAND: Operational code : v01.10 Boot code : v01.14 Manufacturer ID : 0x000157 (Intel) Product ID : 0x0905 (BP1USCSI) Config Version : v01.04 Checksum Information: --------------------- The following checksum were calculated using the Firmware Range Checksum command. Boot code checksums (match data from Range Checksum command): Boot code (0x7C000 - 0x7FFFF): 0xe495 Operational code checksums (match data from Range Checksum command): Section 1 (0x61000 - 0x6FFFF): 0xeef6 Section 2 (0x70000 - 0x7A36F): 0x2faa Overall (0x61000 - 0x7A36F): 0x11ea0 QLogic Core: V1.14A1 ============================================================================= SYSTEM HARDWARE REQUIREMENTS/REVISIONS ============================================================================= 1U SCSI Hot Swap Back Plane: - Fab -4xx or higher. Prior versions can be used if the following rework is performed: Fix for firmware op-code update issue: * Change R3A10 to 4.7k * Change R3A11 to 0-ohm * Change C3A2 to 0.01uF * Change R3A3 to 2k Fix for HD Fault LED issue: * Change R3A6 to 0-ohms * Change Q3B1 to Motorola MGSF1N02LT1 (or can use MMBF170 or 2N7002) * Change R3B4 to 470-ohms Fix for SCSI Termination Issue: * On D2A1, connect the center stub to the pad just below it. Intel(R) Management Module(IMM): - Advanced Edition Fab -2xx or later. Fab -1xx Advanced Edition modules are not supported. - Professional Edition Fab -1xx or later. Server Board SE7520JR2: Fab -1xx or later ============================================================================= SYSTEM SOFTWARE REQUIREMENTS/REVISIONS ============================================================================= - PC87431M mini-Baseboard Managment Controler (mBMC) from National Semiconductor: Revision 2.31 or later. - SE7520JR2 FRU/SDR pacakge: JR-6.2.1 (or later) ============================================================================= IMPORTANT INSTALLATION NOTES ============================================================================= - The following files are necessary to update 1U SCSI back plane firmware: Autoexec.bat - Batch file used to update the firmware. 1USCSI10.hex - SCSI HSBP 1.10 firmware hex file for the SE7520JR2 1U platform. IS_IMM.exe - DOS utility to identify whether an IMM card is installed or not. FWPIAUpd.exe - DOS utility to program firmware hex file into the flash device. Executing the fwpiaupd utility with your own command switches is unsupported and may leave your back plane in a non-operational state! Please use the provided batch file to update the firmware. Executing the Autoexec.bat file can be done from any media (Hard disk, USB disk-on-key, shared network drive or floppy). ============================================================================= INSTALLATION PROCEDURE ============================================================================= - Apply AC and power on the server. - Copy the following files from this release package to the media(Hard Drive, USB Disk-on-Key, Floppy...) that you wish to perform the update from. - Autoexec.bat - 1USCSI10.hex - IS_IMM.exe - FWPIAUpd.exe - Execute the Autoexec.bat file to begin the firmware update process. - Power down server and remove all AC power going to power supplies. - Apply AC and power on the server. ============================================================================= KNOWN ISSUES/WORKAROUNDS ============================================================================= - Boot Code Update is not supported. If you try to update the boot code, the FW update utilitiy will display an error message showing that the boot code is not verified successfully. The only way to update the Boot code is: 1> De-solder the flash part from the back plane. 2> Using the flash programmer, burn the firmware "1USCSIxx.hex" to the flash part. 3> Solder back the flash part on the back plane. The above process also updates Operational code along with Boot code. ============================================================================= FEATURES ADDED ============================================================================ Version 1.10: ============= -None Version 1.09: ============= - None. Version 1.08: ============= ****** IMPORTANT NOTE ****** * This release is made for back planes that have AMD algorithm compatible Flash Device. * Manufacturing - If upate happens in the factory (i.e. with out using "FAPIAUPD.EXE" software utility), then FW update SHOULD BE DONE ONLY ON AMD algorithm compatible flash devices. * Software - If update happens using attached batch file in this release package(Autoexec.bat), then it can be updated on any flash device because the S/W utility "FWPIAUPD.EXE" updates only OPCODE and Op Code is same for both Intel and AMD algorithm compatible flash devices. No boot code update is supported using FWPIAUPD.EXE uility. - Changed the Flash update algorithm in the Boot code from an Intel compatible Flash Device to an AMD compatible Flash Device. Both algorithms cannot reside in the Boot code because of code space therefore separate Flash devices must be used for Intel and Amd type flash devices. Version 1.07: ============= - Added event generation for "Drive Slot Status" sensors. - Changed Event generation logic to allow events to be generated for Type 0x0D with Event Reading Type 0x6F. Added a mask definition using the last 8 bits of the 13 Event bits defined to initialize the Event generation logic to prevent Events from being generated at POR. The Mask is defined in the Gem359 Firmware Functional Spec under Section Header Runtime IPMI Sensor Support Drive Slot Status. - Removed the 5 second timeout at POR which waited for a SetPowerSupply cmd before using the default values. Now uses default values immediately and continues on with POR. The SetPowerSupply cmd can be sent anytime and as often as desired. Version 1.06: ============= - None Version 1.05: ============= - None Version 1.04: ============= - None Version 1.03: ============= - None Version 1.02: ============= - None ============================================================================= ISSUES FIXED ============================================================================= Version 1.10: ============= - Added an additional read and compare of the byte written to flash when an write error occurred during the firmware update routine. This problem showed up with 3.3V Macronix flash parts. Version 1.09: ============= - Fixed a problem with the Flash update routine (AMD algorithm) which caused the STMicro 3.3V flash parts to fail in the write mode. Was looking at the erase timeout Bit instead of the error bit. This problem did not show up on other Vendor flash parts. Version 1.08: ============= - None Version 1.07: ============= - Added event generation for "Drive Slot Status" sensors. - Fixed a problem [X]HSBP FW version wrongly shown - Fixed a problem Set Power Supply State is not working as expected - Fixed a problem backplane not responding after sending Master write read command - Fixed a problem drive slot events on every boot - Driskill/Dowling SCSI BP - Fixed a problem BMC does not detect/report hard drive going offline in the SEL. - Fixed a problem where slot power enable control flag was not being set after reset in runtime. This caused slot power state to remain in the hardcoded (not configuration) state. - Fixed SetPowerSupplyState command to allow power supply state to be updated more than just at Init time, if power supplies do not have input status pins assigned. - Changed runtime Inquiry response to return firmware version from Qlogic runtime header firmware version parameters instead of the Intel runtime header firmware version parameter. - Fixed a problem with an I2C Read only(not a MasterWrite/Read) which caused the firmware to allocate all buffers and not release them. This particular condition was prevelant when the command was a 1 byte Read. The driver would allocate a buffer and wait for more info which it didn't receive. The next read would allocate the alternate buffer or return a busy if alternate buffer was unavailable. Without the buffer aging feature (not enough memory to implement) the buffers would remain allocated and the Gem would appear to be locked up I2C wise. The Gem firmware does not support I2C Read only commands. NOTE: This fix changes both Boot and Runtime code, but under normal conditions the I2C read only command(which the Gem firmware does not support) should not be executed while in booter so it should not affect backward compatibility. Version 1.06: ============= - Changed default Event Receiver IPBM address to 0xFF. This is done to disable event generation in case of mBMC. In case of BMC systems, the BMC InitAgent handles setting of Event Receiver Address to 0x20 automatically provided there is a "Management Controller Device Locator" SDR record (_SDR_TYPE 12) for the HSC(s). Version 1.05: ============= - Disabled I2C bus-check for both Port0 and Port1. I2C bus-check is disabled because the keep alive transactions (to 0xFE slave address) are causing firmware update fail of other devices like mBMC and LCD front panel. Version 1.04: ============= - FIxed a problem where Get Slot Status returned wrong data in byte 4 of the response when an inserted drive was removed. - Fixed a problem in the event generation logic where an event was being transmitted multiple times in certain cases. - FIxed a problem where event generation logic missed sending a deassertion of a non-critical event when the deassertion of a critical and non critical event occurred at the same sampling time. Version 1.03: ============= - Changed IPMI completion code responses to synchronize with responses from the Gem424. - Fixed a problem where the I2C clock speed was not correctly selected from the config file entry. - Fixed a problem where the GEM359 stopped reading the LM75 temperature sensor after responding to an IPMI Read FRU Inventory Data command with a FRU Inventory Offset LSB other than zero. Version 1.02: ============= - Changed POR/RESET logic to Initialize the Power Supply State to a Default condition after waiting 5 seconds if a Set Power Supply State command is not received. Previously waited for the Set Power Supply command before the normal SCSI commands were processed. - Changed the response to "0xCE" for I2C Enclosure Status and Enclosure Configuration commands received before the Set Power Supply State command was received or the Default timeout occurred. - Changed the event generation initial state to use values from the NOMINAL byte in Full SDRR and OEM byte in compact SDRR to prevent generating an event message and/or event status on the first reading of the sensor unless the sensor was out of range. - Changed a count used for detection of a byte wrap in the firmware update function. This would cause a problem with odd numbered byte packets being downloaded over a flash erase boundry. This problem was only produced with with our test tools, it did not occur with the FWPIAUPD Utility using the various packet sizes allowed. ============================================================================= REFERENCE MATERIAL ============================================================================= [END OF RELEASE NOTES]