Readme.txt Driver File Contents (BMC_0.32.zip)

=============================================================================
Intel(R) Server Platforms SE7520JR2 BMC RELEASE NOTES
=============================================================================
INTEL Enterprise Platform & Services Marketing
Intel Corporation
2111 N.E. 25th Avenue, Hillsboro, OR 97124 USA
=============================================================================
DATE:		November 11, 2004
TO:		Intel(R) server platform SE7520JR2 customers
SUBJECT:	BMC(R) 0.32 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
=============================================================================
REVISION INFORMATION RETURNED BY GET DEVICE ID COMMAND:

Operational mode:	v00.32
Flash update mode:	v00.11
PIA data:		v01.54
Manufacturer ID:	0x000157 (Intel)
Product ID:		0x0022 (SE7520JR2)

Checksum Information:
Operational Code
  Region:		0x00030000 -> 0x000d8ad2
  Checksum:		0x63c3

Boot Block
  Region:		0x00000000 -> 0x00003052
  Checksum:		0x553a

=============================================================================
			SYSTEM HARDWARE REQUIREMENTS/REVISIONS
=============================================================================
Intel(R) Management Module(IMM):
  - Advanced Edition PBA C44973-302 or higher with BMC 0.23 or higher
    installed.

  - Professional Edition PBA C46194-301 or higher with BMC 0.23 or higher
    installed.

Advanced Edition NIC board (GCM):
  PBA C44941-201 (or later)

Server Board SE7520JR2 with the following PBA revisions (or higher):
  C53659-301 
  C53660-404
  C53661-601
  C53662-503

=============================================================================
		       SYSTEM SOFTWARE REQUIREMENTS/REVISIONS
=============================================================================
- SE7520JR BIOS revision:
  SE7520JR22.86B.RC01.05.00.0065 (or later) 
  SE7520JR23.86B.RC01.05.00.0065 (or later)
  Any BIOS version prior to these will cause the BMC serial channel to not
  function properly.

- SE7520JR2 FRU/SDR pacakge:
  JR-6.5.2 or later

- PC87431M mini-Baseboard Managment Controler (mBMC) from National Semiconductor:
  Revision 2.40
 
- Firmware revisions on the Advanced Edition IMM card:
  FPGA : rev 44
  EDID: rev 04
  Any version prior to these will cause the Keyboard and mouse to become
  non-functional.

=============================================================================
                         IMPORTANT INSTALLATION NOTES
=============================================================================
- The following files are necessary to update the firmware:
  Run.bat	- Batch file used to update the firmware
  7520JR32.hex	- BMC 0.32 firmware hex file for the SE7520JR2 platform
  FWPIAUpd.exe	- DOS utility to program firmware hex file into the flash device
		  Prior versions of this utility will not work with this FW

Executing the fwpiaupd utility with your own command switches is unsupported 
and may leave your baseboard in a non-operational state! Please use the
provided batch file to update the firmware.

Executing the batch file can be done from any media (Hard disk, USB disk-on-key,
shared network drive or floppy).

BMC 0.23 or later must be preinstalled.
If this is not the case, please update the IMM firmware to BMC 0.23 before
updating to this release.

The boot block has been changed with the BMC 0.31 release but it is not
required for this release. The batch file provided with this BMC package
does not update the boot block.

=============================================================================
                         INSTALLATION PROCEDURE
=============================================================================
- If this update is not being applied to BMC 0.23 or later, please update to 
  0.23 before running this 0.31 update.
- Copy the update files from this release package to the 
  media(Hard Drive, USB Disk-on-Key, Floppy...) that you wish to perform
  the update from. Files include:  Autoexec.bat, 7520JRxx.Hex, FWPIAUpd.exe,
- Execute the run.bat file to begin the firmware update process (if running
  from the Software Update package, select update IMM Firmware option)
- Install the webserver EFS image revision 1.7 by either running upd_efs.bat
  (if running from the Software Update package, select update EFS 
  Webserver option) or by uploading the efs_17.efs file using the web server
  at URL http://xxx.xxx.xxx.xxx/!@efsUpdate. Replace the xxx.xxx.xxx.xxx
  with the IP address used to configure the HTTP web server feature.
- Proceed to install the latest FRU/SDR package.

=============================================================================
                           KNOWN ISSUES/WORKAROUNDS
=============================================================================
- This and all future firmware releases will only support the fab -3xx 
  and later Professional and Advanced IMM.
  Fab -2xx and prior modules are no longer supported!

  See the SYSTEM HARDWARE REQUIREMENTS section above for details.

=============================================================================
                           FEATURES ADDED
=============================================================================
BMC 0.32:
- None

BMC 0.31:
- Support for Telco Alarm Manager hardware



=============================================================================
                           ISSUES FIXED
=============================================================================
BMC 0.32
- DCS: 17950
  [IMM] Boot Initator info Block seemingly not validated 
- DCS: 19398
  PDB failure status not logged by BMC
- DCS: 15895, 16213, 16597, 16840, 17179, 18805, 19246, and 19321
  Miscellaneous HTTP web server fixes




===============================================================================
Pedigree of Changes
===============================================================================

BMC 0.31
- DCS: 16325
  EMP is not available for 10 seconds after DC ON  
- DCS: 18410
  Communication failure in Terminal mode
- DCS: 19027
  Failed to make direct serial connection (LSM)  
- DCS: 19028
  Failed to establish Serial Modem Connection (LSM)  
- DCS: 19031
  [IMM] SecureModeActive bit is not set by the Secure Mode KB signal.  
- DCS: 19306
  CRERR04 - during console redirection and EMP is enabled
- DCS: 19354
  Enable Telco Alarm Manager feature in Jarrell BMC (IMM)
- DCS: 19363
  BMC 30:SMTP -Parameter Revision is not 0x11 
- DCS: 19369
  SMTP config parm#6, DNS override, inverted 
- DCS: 75975
  [J1-IMM] BMC did not lock the Power and Reset push-buttons when Secure Mode
  signal is asserted.
- DCS: None
  Add support to allow the SE7520JR2 BMC firmware to execute on a SHW4 server

BMC 0.30
- DCS: 15819
  IPMI2.0 commands not implemented correctly.
- DCS: 16415
  KVM - Get Video Status requires video data structure
- DCS: 16634
  FW: Setting an SMTP configuration appears to set multiple configurations
- DCS: 16837
  FW: User Feature cmd for HTTP/S enables returns incorrect # of data bytes
- DCS: 17186
  Get Channel Payload Support responses the same output
- DCS: 17459
  KVM - Set KVM Config. to set in progress results in invalid completion code
- DCS: 17460
  KVM - issuing Set KVM Configuration to disable KVM does not work.
- DCS: 17501
  KVM - Activate Payload not returning all required bytes
- DCS: 17502
  KVM - Video Status incorrectly reported when powered off
- DCS: 17503
  Get SNMP Config Params command returns bad completion code
- DCS: 17538
  FW:  Issues with Set SMTP Config Params command
- DCS: 17540
  FW:  Issues with Set/Get LAN Config Params cmd w/ parameter 0xc4
- DCS: 17773
  KVM - No Video Data Received
- DCS: 17779
  KVM - Video packets still sent after Payload Deactivated
- DCS: 17815
  KVM - Invalid Mouse Type reported
- DCS: 17860
  KVM - BMC Becomes unresponsive to LAN connection
- DCS: 17863
  KVM - Capture Reference Frame has too much data in it
- DCS: 17865
  KVM - System will not boot w/KVM session Active
- DCS: 17949
  LAN: chan 3 MAC Addr not auto-populated
- DCS: 18387
  [IMM] Front Panel LCP is not discovered.
- DCS: 18698
  Status LED does not turn amber when there is a fault on the system
- DCS: 19169
  Restart Cause command is not working as expected
- DCS: 19237
  PCI Hot Plug sensors stuck in init update mode after exit FW-Xfer mode
- DCS: 19239
  [IMM] IERR occured at  AC power cycle test.
- DCS: 19267
  BMC29:Power control fault beep codes are emitted when repeated power cycles are
- DCS: 19299
  LAN Alerts with Alert strings are reported as malformed packets
- DCS: 19321
  EFS format/content not finalized yet
- DCS: 19324
  Mouse / Keyboard Not Initialized when OS booted during  a KVM session
- DCS: 19326
  FPGA Encryption Problematic - After 100 + packets video data length is invalid

BMC 0.29:
- DCS: 19155
  BMC doesn't correctly transition to S1 sleep state
- DCS: 34955
  To implement Memory board Front and rear temperature sensors
- DCS: None
  Better handling of power loss & DC off events.
- DCS: 19139
  Console Redirection Causes Firmware Progress Errors in LD  
- DCS: 38307
  System failed to log AC power failure during boot
- DCS: 19107
  BMC 0.28 Encountered failure while verifying sensor initialization value.  
- DCS: 18875
  Online Firmware Update causes BMC to hang 
- DCS: 19156
  RQ_SyncSMBus command locking wrong bus  
- DCS: 18963
  PS_PWR_GD ISR is not being enabled occasionally
- DCS: 18215
  Removed init agent changes that were causing other problems.
- DCS: 18936
  [IMM] IERR event is always occur right after AC on
- DCS: 19135
  mBMC update with IMM installed fails on Alief and Brandon
- DCS: 16483
  BMC and SDR updates fail 
- DCS: 75901
  DC cycling failed with IMM cards installed (Procs go offline)
- DCS: 75907
  Processors being Disabled after an OS Restart
- DCS: 75908
  Problems Powering On after an OS Shutdown
- DCS: 75915
  BMC25 is shutting down immediately after loading and disabling the processors
- DCS: 74593
  BIOS B19~P03 versions cause UUT boot failed after several front panel power
  cycling while IMM card installed.
- DCS: 74618
  IMM fails in Brandon -601A SCSI

BMC 0.28:
- DCS: 18866 & 18867
  Thermal Trips were calling power control code to power down system. This
  functionality is handled directly by the hardware.
- DCS: None
  Added new module selection for Memory Board
- DCS: None
  Fans would sometimes indicate failure at DC on.
- DCS: 19066
  PCI Hot Plug Sensors do not show up 
- DCS: None
  Power supplies from shutting down due to current spikes caused by fan speed
  changing to quickly.
- DCS: None
  Processors are getting enabled and disabled twice during FRB3 failures.
- DCS: None
  ID LED on would get locked on when button is pushed during power state
  transitions.
- DCS: 18883
  OOB connection not working out of subnet 
- DCS: 19054
  Repeat issuance of CLI power actions causes IMM to stop responding 
- DCS: 19056
  Thermal Trips being seen during DC power cycle testing 
- DCS: 19072
  1-5-4-4- beep code 
- DCS: 19083
  CLI lockup on power commands with BMC A.27 engineering release  
- DCS: 19084
  BMC a.27 causing therm trip and IERR errors on Brandon and Jarrell 

BMC 0.27:
- Only released as incremental developer drops to verify resolutions that are
  in place with the BMC 0.28 release.

BMC 0.26:
- DCS: 19010
  Self test error with LSM Linux Console 
- DCS: 18875
  Online Firmware Update causes BMC to hang 
- DCS: 19056
  Thermal Trips being seen during DC power cycle testing 
- DCS: 19016
  Temporary failure of boot 
- DCS: 18215
  Init Agent fails to initialize the sensor thresholds
- DCS: None
  Added some kick start ramping, but then went to a fixed 50% kick start.
- DCS: 19066
  PCI Hot Plug Sensors do not show up  
- DCS: 38317
  BMC release process not producing repeatable checksums
- DCS: None
  Changed to notify waiting task if multiple loss of arbitration detected,
  regardless of task state.
- DCS: 18963
  PS_PWR_GD ISR is not being enabled occasionally 
- DCS: 19019
  Rapid, succesive activation of the Power button, hangs BMC  
- DCS: 19054
  Repeat  issuance of CLI power actions causes IMM to stop responding 


BMC 0.25:
- DCS: 18963
  PS_PWR_GD ISR is not being enabled occasionally 
- DCS: 18638
  BMC22: OnlineUpdateOpenArea is returning 0x00 as CC when it should not return so
- DCS: None
  Fix for LAN channels not working after an exit firmware transfer mode
- DCS: 18875
  Online Firmware Update causes BMC to hang 

BMC 0.24:
- DCS: None
  Fixed a defect in the VERIFY macro
- DCS: None
  Added support for using a manufacturing test SDR
- DCS: None
  HW team reporting fan circuit FETs being blown due to LM93 PWM outputs being
  driven while DC is off
- DCS: None
  If the private store gets cleared both processors will come up as disabled
  by FRB3 on the next boot
- DCS: 18208
  [IMM] CF9 hard reset does not work 
- DCS: None
  mBMC Driver potential error fix
- DCS: None
  HW folks have the nominal, boost & sleep values set to FCh in the SDRs
  which is wrong.
- DCS: 18217 & 18551
  Implement a bi-color system fault indicator
  (follow-up: counter-act the mBMC’s clearing of the LEDs on DC power on)
- DCS: None
  Added defines to nullify printf in release mode
- DCS: 18806
  BMC generates Self Test Error/ Parity Error with LanDesk SOL console 
- DCS: None
  Added support for using a shipping, TDE Adv IMM and TDE Pro IMM SDR.
- DCS: 18217
  The comment describing the mBMC color conversion value assumptions was incorrect
- DCS: None
  Found a memory leak in mactconet.c
- DCS: None
  mBMC Driver reduce number of retries
- DCS: 18461
  HDD LED on front panel is red when IMM is installed 
- DCS: None
  Incorporate the latest FSC spreadsheet data into the LM93 register defaults
- DCS: None
  Added support for handling the IPMI requests “Set ACPI Power State” 
  and “Get ACPI Power State” through the SMM channel.
- DCS: None
  mBMC Driver parameter tweaking to increase performance 
- DCS: 18866
  [IMM] Thermal trip event is not logged in SEL
- DCS: 18867
  [IMM] IERR event is not logged in SEL
- DCS: 18745
  Fans do not contribute to the overall health of the system 
- DCS: 18883
  OOB connection not working out of subnet 
- DCS: 18243
  2nd CPU fails with frb3 during post 
- DCS: 18802
  BMC failing self test corrupts BIOS information 
- DCS: 18854
  Alief BMC 23 - Resolve MAC hangs BMC 
  
BMC 0.23:
- DCS: 16967
  PET Traps were not getting detected
- DCS: 18548
  [IMM] BMC failed BIOS self test after update to  BMC version 21
- DCS: 18612
  BMC does not retain OOB connectivity after installation of ISM on server  
- DCS: 18217
  Front Panel Bi-Color LED behaviour 
- DCS: 18551
  [IMM] Status LED is not changed at  the critical event.  
- DCS: 75827
  [J1] Baseboard Management Controller Failed by Self Test command during POST
  with Sahalee FW 0.21.
- DCS: 18549
  LM93 OEM SDR would cause the BMC to hang 
- DCS: 18595
  FRUSDR version 6.2.1 Update failling with BIOS P01 and BMC 21
- DCS: None
  Added encapsulating PACKED_xxx definitions around some packed structures.
- DCS: None
  Refined the fan control for power ON and Hot swap kick Start;
  Added checks to avoid C, NC Assertions during power ON&Reset;
  Added the de-assertion Actions in the PIA for hot swap fans; Fans boost
  in the particular domain on HS fan removal
  Restored the default Nominal to half by handling the power on and HS kick
  start in the fanctrl.c code
- DCS: None
  New OEM command to restore the non-volatile configuration.
  This command needs to be called by the utility when the platform mismatch
  found during the FW update.
- DCS: None
  SensAvgCreate() would allow illegal input data
- DCS: None
  Baseboards with maximum DIMM capacity were causing systems to reset
  during POST due to the FRB3 timer expiring.
- DCS: None
  mBMC Driver message potential error fix
- DCS: None
  Multiple stack overflow issues
- DCS: None
  This check-in partially addresses clearing out bogus fan failures that are
  persistently stored.
  I have seen issues with moving my IMM between different platform types,
  where ATTNID_OK has a different value.



=============================================================================
                             REFERENCE MATERIAL
=============================================================================
Intel(R) Server Platform SE7520JR2 Technical Product Specification (TPS)

[END OF RELEASE NOTES]
Download Driver Pack

How To Update Drivers Manually

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.

server: web5, load: 1.53