Release Note for BCM5700 Engineering Diagnostics. ================================================== Version 1.23: 1. Provided a command line option to overwrite corrupted vendor ID of Broadcom NIC. For examples, bcmediag -i Diag. program will search for network adapter with BCM5700 ASIC and overwrite with BROADCOM vendor ID/device ID. If BIOS has not assigned valid memory base address, user can specify an memory base address for this adapter card (User can verify this by reading config space at 0x10 and 0x14. e.g. read @10 and read @14) For examples, bcmediag -i -a 0xfebf0000 Users have to make sure that this address range is not used in the system. 2. Added changes so that firmware upgrade via upgfrm command will not be allowed if manufacturing information is invalid. Version 1.22: 1. Fixed a problem where packet test executed in nictest fails if driver is not loaded first. 2. Added code to allow user to update PXE (e.g upgfrm -p -f=b57pxe.bin). Version 1.21: 1. Added changes due to changes in boot code firmware 0.6. Before issuing CHIP reset (or GRC reset), it writes a siginature to SRAM so that firmware wouldn't perform code boot initialization such as PHY H/W reset, PXE loading, etc... 2. Added new command to upgrade boot code firmware without corrupting manufacturing information. upgfrm -b -p -f=<filename> -b: upgrade boot code. -p: upgrade PXE. -f: input filename. Version 1.20: 1. Fixed loopback issues when no cable is attached. Version 1.19: 1. Fixed loopback issues in NIC test. 2. Added new command pkttest to allow user to perform both MAC and PHY internal loopback. pkttest -n=<iteration> -p -m -p : PHY internal loopback -m : MAC internal loopback -n : Number of iterations. Version 1.18: 1. Added command sechk to verify and update checksum of manufacturing region. Command secfg now recalculates checksum when updating parameters. Version 1.16: 1. Changed to do chip reset per NIC test iteration. Version 1.15: 1. Changed to support VPD with or without loading driver. Version 1.14: 1. Fixed a problem where txpkt command cannot transmit packets after long period of transmission. This happens very rarely. Version 1.13: 1. Initializating code is changed to support B0 silicon. 2. Command txpkt is enhanced to support : * Transmit packets with fixed/random length. * Transmit packets with fixed/random number of BDs. * Transmit packets with minimum byte per BDs. * Transmit packets with interpacket gap in microseconds. 3. Command memtest is changed to test additional memory scenarios: * Random Address and random data. * Special test where writing one location and checking for 128 bytes of adjacent location. 4. Command sever to dump serial eeprom and firmware version. 5. Added command memsearch to search a given contents in the memory. 6. Command mbuf is modified to dump all MBUF headers and check for MBUF header corruption in MBUF pool. 7. Fixed a problem where txpkt can stop if packets to be transmitted has too many fragments.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.