Release.txt Driver File Contents (broadcomGbe.zip)

                          Broadcom Corporation
                          16215 Alton Parkway,
                          Irvine, CA 92619-7013
			  
                              Release Notes
                              
                        Broadcom ASF Firmware
            
                            February 26, 2002

Table of Contents
=================

  Introduction
  Revision History
  
			       
Introduction
============
Broadcom ASF firmware is the core logic that performs all ASF operations.
The ASF firmware communicate to the ASFNetMon that is running on the Remote Console via RMCP protocol
The ASF firmware monitors various sensors over the SMBus and generate PET alert to the Remote Console.
The ASF firmware by itself can be configured to generate HeartBeat PET.
The ASF firmware runs inside BCM5702/03 A1 NIC's core CPU.
The ASF firmware is stored on the SEEPROM/Flash device via B57diag utility.
The ASF firmware, when enabled, is loaded after the system has (1) full power and (2) auxilary power.
The ASF firmware can co-exist with NIC Driver that runs on the Windows based operating system.
The ASF firmware begins to operate after properly configured during a "one good boot".
The ASF firmware configurations can be done using either (1)Dos based B57diag utility or (2) Windows based ASFCFG utility
The ASF firmware configuration parameter allows setting of an IP address, this IP address should be the same when OS is running
The ASF firmware internal IP address can be synchronized with the OS' IP address via ASFIpMon utility
The ASF firmware can co-exist with WoL functions.  "secfg" option 24=1 enables Magic Packet WoL.  NIC Driver WoL enables Interesting Packet WoL


Revision History
================
ASF 1.8 (2/26/02)
- Fixed Gateway hop.  Now ASF can communicate with Remote Console over Gateway correctly.
- Added support for 5702FE.
- Fixed a bug in how ASF gets VMain status.  Now the checking of the system power state is done in real-time.
- Fixed a bug in the way that the Magic Packet detection bit is set.  Now we let the NIC driver set this bit.

ASF 1.7 (2/18/02)
- Modified to ignore following ASF config parameters: MinPollingInterval, NumberOfDevices, Fixed SMBusAddresses, SEEPROMAddress
- Fixed the Heartbeat timer value variable from BYTE to WORD so we can accomodate up to 600 seconds.
- Added ASF Version string.  The version string will show on both ASFCFG and B57Diag ("dir" command).
- Dependencies:
  a. This version of ASF firmware requires the following:
     a.1. B57diag (v2.31)
     b.2. ee5702.bin (v2.19)
     c.3. NIC Driver (v2.56)
  b. This version of ASF firmware requires the GPIO2 to be tied to the system's VDD with a pull up resister,
     so the NIC cannot bring down the system by driving the GPIO2 low.  The GPIO2 input to the NIC should 
     allow NIC to determine if the system is in VMain (1) or VAux (0) mode.


ASF 1.6 (2/12/02)
- Modified EEPROM to use burst read while bootstrap the ASF firmware.  This minimized the EEPROM corruption problem.

ASF 1.5 (02/11/02)
- Completed co-exist with WoL function
- Included VPD support (proven that VPD handling cannot cause SEEPROM/Flash corruption)
- Included sending of ASD_READY when the Ethernet Link goes from down to up state
- Fixed the SMBus FIFO overflow problem that causes intermitten BIOS "push message" failure
- Removed the special "debug" way of generating ASD_READY in ASFCFG option '7'.
- Fixed the lost states problem (chassis intrusion state) due to NIC reset.  Now remembered the states until power completely down.
- Removed ICMP handling (it was a debug feature).  DOS 'Ping' to the ASF NIC will not get a respond.
- Note, in order for WoL to work requires versio of NIC driver that is capable of supporting ASF Wol handling.

ASF 1.4 (01/29/02)
- Fixes SetUpLink conflict with the OS
- Fixes HeartBeat always disabled (no HeartBeat)
- Temporary remove of VPD support (to avoid possible SEEPROM/Flash corruption)

ASF 1.3 (01/25/02)
- Added Dell's customization
- Added VPD support

ASF 1.0 (01/14/02)
- Initial release
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: web1, load: 1.39