chkfirm.exe release note
========================
version 1.29
1. Problem: (CQ34246)
Chkfirm returns incorrect code when the specified device number is out range
Cause:
Count the wrong the number of detected devices.
Fix:
Correct the number of detected devices.
2. Problem: (CQ34250)
Chkfirm returns error code 9 when running -cname for 5752.
Cause:
The hex of 5752 part ID is not equal to its DID.
Fix:
Create a table recording parts of part ID and device id.
version 1.28
1. Enhancement:
Support 5784, 5764, 5723 and 5761
version 1.27
1. Problem: CQ# 29041
CHKFIRM freezes when run with a -cname parameter of ~28+ characters
Cause:
The default size of the buffer to store the parameter of -cname is only 10 bytes.
The parameter that over the size limit may overwrite other data and cause system to freeze.
Fix:
Increased the default size to 128 bytes.
Impact:
None.
version 1.26
1. Enhancement:
Added ISCSI firmware support.
version 1.25
1. Problem: CQ# 27311
-cname switch does not work with 5906.
Cause:
There is a bug which cause the software failed to read the ASIC version of the device when selfboot or hw selfboot
firmware has been used.
Fix:
Modified code to read the ASIC version of the device when selfboot or hw selfboot firmware has been used.
Impact:
All devices which make use of selfboot and hw selfboot firmware will be impacted. The issue has been introduced since
version 1.21.
version 1.24
1. Enhancement:
Enabled 5722, 5756M and 5906 support by default according to MRD for Release 10.0 Alpha V1.0B.
version 1.23
1. Enhancement:
Removed 5906/5906M support for release 9.7
version 1.22
1. Problem: CQ# 26308
When running CHKFIRM on the 5906m snow card, the SVID and SSID do not match w/ B57Diag -dids.
Cause:
Incorrect offset of NVRAM has been used when read SVID and SSID.
Fix:
Using corrected offset of NVRAM when read SVID and SSID resolved the issue.
version 1.21
1. Enhancement:
Adding 5906/5906M support.
2. Enhancement:
Adding the display of MBA configuration for Selfboot and Hardware Selfboot firmware.
version 1.20
1. Enhancement:
Adding 5786 support.
version 1.19
1. Problem: CQ# 22230
chkfirm corrupted ST flash nvram data.
Fix:
Added ST flash support to chkfirm.
2. Problem: CQ# 22221
chkfirm displayed incorrect nvram data in 5780.
Fix:
This is a bug in finding flash type. This has been fixed.
version 1.18
1. Enhancement:
Adding 5755, 5787 and 5754 support.
2. Enhancement:
Adding Selfboot firmware support. New return code (13) has been added for Selfboot firmware.
version 1.17
1. Enhancement:
Adding 5714 A2 support.
version 1.16
1. Enhancement:
Modified code to ignore case when compare input parameters of
-bootver and -asfver to the version string of the firmwares.
version 1.15
1. Enhancement:
Added support for Baxter with different flash type.
2. Enhancement:
Added -bootver option switch to check boot code version.
If there is a mismatch of bootcode version, software will issue a return code of 11.
Example:
a:\chkfirm -c 0 -bootver 3.04a
3. Enhancement:
Added -asfver option switch to check boot code version.
If there is a mismatch of ASF firmware version, software will issue a return code of 12.
Example:
a:\chkfirm -c 0 -asfver 5.05
version 1.14
1. Problem: (CQ# 12085)
Run chkfirm on both 5704c ports gets the same MAC address,
same MAC from the primary ports showed for both dev 0 and dev 1.
Cause:
Chkfirm only read the primary mac address.
As a result, the primary mac address has been used for the secondary devices.
Fix:
If device is a secondary device, chkfirm will read secondary mac address from NVRAM.
version 1.13
1. Enhancement:
Add support for Baxter.
version 1.12
1. Enhancement:
Add support for following flash devices.
- SaiFun SA25F0xx where xx=05/10/20 (512Kbit-2Mbit)
- ST M45PEx0 where x=1/2/4/8 (1Mbit-8Mbit)
Fix:
Support for flash devices specified above added.
version 1.11
1. Enhancement :
Added Shasta 12X12 package support.
2. Problem:
chkfirm failed -cname device matching even if matching devices.
Cause:
Incorrect address mask has been use when detecting rev of device.
Fix:
Update code with the correct address mask to resolve the issue.
version 1.10
1. Enhancement (CQ# 10891):
Request to implement 5751 A1 / A4 detection in CHKFIRM
Cause:
Enhancement request to added the same mechinism to the chkfirm utility
that has been added to the diagnostic to determine if the the rev of silicon.
Fix:
-cname <device+refsil+refbond> specify device ID, silent rev and bond rev to match with detected devices.
If there is no match to the detected devices, an error level 9 will be issue.
Matching will only takes place if only one device is detected or only one device is sepecified by -c option.
Example:
-c 2 -cname 1698A1/A1 (selected device #2 and the matching device id is 1698, the silent rev is A1, the bond rev is A1)
-c 2-4 -cname 1698A1/A1 (no match will take place since 3 devices are selected)
2. Enhancement (CQ# 10953):
Checkfirm displays the TPM Module as "unknown"
Fix:
Added TPM detection support to Chkfirm utility.
3. Enhancement
Added new return codes and new definition to chkfirm.
0: Bootcode and ASF are found but TMP block is NOT presence.
1: No Broadcom NetXtreme Ethernet Adapter has been detected in the system.
2: EEPROM or NVRAM read error.
3: BootCode is not found or BootCode version is not 2.6 or later
4: BootCode firmware is found, TMP bloack is NOT presence and ASF firmware is either not found or not completely installed.
5: Invalid input for command line option switchs
6: No device has been selected for test.
7: BootCode firmware is found, TMP bloack is present and ASF firmware is either not found or not completely installed.
8: Bootcode, ASF and TPM are presence.
9: Detected device does not match with device sepecified by -cname.
10: More then one devices are detected or more then one devices are specified by -c option.
version 1.09
1. Enhancement (CQ# 10331):
This is a request for the checkfirm to be able handle
a command line parameter so that the a particular Broadcom
device can be specfied. The reason is so that chkfirm
can be run with multiple Broadcom devices in the system.
Fix:
"-c" option switch has been added to chkfirm such that user
can select devices to test in a system with mutiple broadcom
devices
version 1.08
1. Fixed the incomplete string display issue.
version 1.07
1. Added Shasta support.
version 1.06
1. Removed duplicated info such as firmware info, mac address, SSID and SVID from chkfirm display.
2. Added Vender ID and Device ID for display.
version 1.05
1. Support multiple devices. Chkfirm will show nvram directory informaton of all the detected cards
2. Return code of chkfirm is only valid for the 1st detected card even with more than one card are detected.
version 1.04
1. Correct version string and date code.
version 1.03
1. Added PXE version support.
version 1.02
1. Added support to 5705;
version 1.01
1. Switch nvclock from 0x5200 to 0x14a00;
Version 1.00
Initial release.
Download Driver Pack
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.