ThunderLAN(tm) - Diagnostics Usage Instructions CONTENTS ======== Before Running TLANDIAG ....... Things that should be done before runnning the diagnostic software. Running TLANDIAG .............. Instructions on how to run TLANDIAG. TLANDIAG Options .............. Describes the command line options avaliable to the user. Tests Descriptions ............ Brief Description of each test performed by TLANDIAG. Release Notes ................. Provides information on diagnostics revision history and any problems. BEFORE RUNNING TLANDIAG ======================= Before running TLANDIAG, make sure to check the following items: 1. Make sure that TLANDIAG is not being run in a DOS window in Windows(tm). If it is run in Windows(tm), it will abort telling the user to please run TLANDIAG in DOS. 2. Make sure that ThunderLAN(tm) drivers are not loaded when running TLANDIAG. If TLANDIAG detects drivers upon start-up, it will abort telling the user to please unload drivers before running TLANDIAG. 3. Currently, TLANDIAG only runs diagnostics on the first instance of the ThunderLAN(tm) card found on the PCI Bus (unless run with the -dc option, See RUNNING TLANDIAG below). So, if multiple cards are installed, only the first card will be tested on each execution of TLANDIAG. 4. If the user wants Wire Tests to be performed by TLANDIAG, have the card plug into an active network. 5. TLANDIAG does not support ThunderLAN(tm) Revisions that are below 2.0. TLANDIAG will tell the user upon start-up if it has encounterd a board with a revision lower then 2.0 and will exit, reporting the revision of board it found. RUNNING TLANDIAG ================ Type 'TLANDIAG' from the DOS command line for the basic execution of the diagnostics program. A report file that contains a hardcopy of the screen output is found in TLANDIAG.REP in the same directory in which TLANDIAG is run. It will test the internal adapter registers and then find and test the internal PHY and any external PHYs. To get command line help, just type 'TLANDIAG -H'. To obtain more information on a error reported by TLANDIAG, run TLANDIAG in verbose mode, 'TLANDIAG -V', and additional information will be reported to \ the report file, TLANDIAG.REP. The information reported by verbose mode is intended for use by TLAN support staff. TLANDIAG Options ================ The following command line options are available: TLANDIAG [-D(ACEHMP)] [-H] [-L] [-P] [-Tpasses] [-V(num)] -D Display mode, will display the contents of the specified Register: -DA will display the Adapter Internal Registers -DC Displays info on all TLAN boards present. -DE will display the EEPROM -DH will display the Host Interface Registers -DM will display the MII Registers -DP will display the PCI Configuration Registers -H Help, shows command line help. -L LED Test, tests the two LED's on back of the ThunderLAN(tm) board. -P Waits for input between each screen of output. -T Number of Passes, controls how many times the diagnostics program loops. -V(num) Verbose mode, provides additional information in the TLANDIAG.REP file. num Optional level control for Verbose Mode 1-20 -X Exclude Test -XI excludes Internal PHY test TESTS DESCRIPTIONS ================== NOTE: PHY and WIRE Tests: PHY auto-detection is implemented to detect what type of external and internal PHY is present and if a link is present on these PHYs. TLANDIAG will then test PHYs that it finds and run wire tests if TLANDIAG finds a link on that particular PHY. Configuration Register Test --------------------------- Checks the PCI Configuration Register to ensure that the configuration space contains the correct preset values, and that the correct areas can be written to. Adapter IO Register Test ------------------------ Checks the ThunderLAN(tm) Adapter Host Interface Registers to ensure that it contains the correct preset values, and that the correct areas can be written to. Adapter DIO Register Test ------------------------- Checks the ThunderLAN(tm) Adapter Internal Registers to ensure that it contains the correct preset values, and that the correct areas can be written to. ThunderLAN(tm) RAM Tests ------------------------ Checks the ThunderLAN(tm) On-board RAM to see if addressing, data reads and writes, and data independence of the RAM are working correctly. Host Interrupt Test ------------------- Sets the Request Host Interrupt bit in the HOST_CMD Register field and checks to see if an interrupt occurred and if it was the correct one. Internal Wrap ------------- Puts ThunderLAN(tm) in internal wrap mode and sends and receives one 64 byte frame. Tests are then performed to see if the network statistics registers are updated, the adapters interrupts occurred correctly, and that the full packet was received. EEPROM Read Test ---------------- Tests to see if acks are returned from reads to all the address of the EEPROM and if the 5 occurrences of the Burned in Address are all equivalent. MII Interrupt Test ------------------ Sets the TINT bit in the PHY Control Register in the MII and checks to see if an interrupt occurred and if it was the correct one. Loopback Tests -------------- This set of test are similar to the Internal Wrap test but transmit the frame through the MII Registers and the PHY depending on the Loopback test. Different Sets of Loopback Tests can performed on different phys: Internal 10BaseT: MII Loopback - Causes the PHY to wrap the Tx data to the Rx data at the MII interface. Full Loopback - Causes the PMI to wrap the Tx data to the Rx data at the furthest point possible. External 100VG: MII Loopback - Causes the PHY to wrap the Tx data to the Rx data at the MII interface. PMI Loopback - Causes the PMI to wrap the Tx data to the Rx data at the far side of the PMI. Full Loopback - Causes the PMI to wrap the Tx data to the Rx data in the analog device (PMD) attached to the PMI. External 100TX: MII Loopback - Causes the PHY to wrap the Tx data to the Rx data at the MII interface. Internal 10BaseT Wire Test -------------------------- Sends a 64 byte frame from the network interface card onto the wire addressed to itself. It then checks to see if it receives this packet back from the hub/concentrator. External 100VG Training Test ---------------------------- Will attempt to train with the attached 100VG hub and check to see if it trains successfully. External 100TX 100Mbs Wire Test ------------------------------- Will send a 64 byte frame from the network interface card onto the wire and check to see if a good transmit occured. External 100TX 10Mbs Wire Test ------------------------------ Sends a 64 byte frame from the network interface card onto the wire addressed to itself. It then checks to see if it receives this packet back from the hub/concentrator. LED Test -------- To perform the LED test the '-L' flag must be specified when running TLANDIAG. The LED test will test the two lights located on the back part (the part viewable when your computer is closed) of the ThunderLAN(tm) board. The test will run through a self automated process of flashing the two LEDs. The pattern that should be observed on the LEDs is indicated to the user on the screen. The pattern is as follows (while looking at the card upright and from the back): LEFT OFF RIGHT OFF LEFT ON RIGHT OFF LEFT OFF RIGHT ON LEFT ON RIGHT ON If the pattern on the board is not identical to the one indicated, an error has occurred. DISPLAY MODE: ------------- Using the '-d' command line switches, TLANDIAG will display the contents of specified register on the screen and to the TLANDIAG.REP file. For example, to display the contents of the PCI Configuration Registers and the contents of the EEPROM, the command line argument would be: "TLANDIAG -DE -DP". -DP displays the PCI Registers -DE displays the EEPROM -DM displays the internal MII Registers unless the '-f' 100vg flag is set then it displays the 100vg MII Registers -DH displays the Host Interface Registers -DA displays the Adapter Internal Registers -DC displays the configuration information for ALL ThunderLAN(tm) boards present NETWORK INTERFACE CARD INFO --------------------------- Appears at the end of every report. Provides the user with a listing of the I/O Base address and Interrupt Request Level obtained from the card's PCI Configuration Register. The burned in Ethernet Address is also given. The Generic ID and link status of the internal and external PHY are reported. The PCI Slot number occupied by the card is additionally displayed. RELEASE NOTES ============= This section describes the revision history and known problems/issues with the driver. Revision history --------------------------------------------------------------------- Rev 1.08R7 - 08Apr97 a) PHY reset routine changed to accommodate new ICS1890 PHY release (PR1) Rev 1.08R2 thru 1.08R6 - internal releases a) support for Broadcom 100T4 phy b) support for ICS PHY's (ICS1889 fiber, ICS1890 copper) c) support for new TI ThunderLAN silicon release (Rev 3) d) incorporated relevant changes made in TI's Rev 1.09 thru 1.13 Rev 1.08R2 - 21Feb96 a) Added underrun check to prevent false error indications on a transmit underrun. Frames are retransmitted up to 6 times to allow for APO. (APO = "Adaptive Performance Optimization"-- The TLAN chip begins with an optimistic transmit commit level setting for best performance, and automatically adjusts the transmit commit level when an underrun occurs, to accommodate PCs which need a slower setting. Such an underrun should not be deemed an error.) Rev 1.08R1 - 08Feb96 a) Added fix for error reading the EEPROM that occurs on the first pass. Rev 1.08 - 04Dec95 a) Added options for overwriting Device ID and Vendor ID Rev 1.07 - 17Nov95 a) Added test for active internal PHY. Rev 1.06 - 08Nov95 a) PHY power-up not correct for Loopback tests. NOTE: This fix for Internal PHY, other PHYS to be tested Rev 1.05 - 08Nov95 a) EEPROM now checks 0x70-0x7F area for correctness! Rev 1.04 - 01Nov95 a) Auto Neg on Internal PHY disabled Rev 1.03 - 30Oct95 a) Interrupt handling code excluded IRQ 15 b) Added different levels of 'verboseness' via -Vn command Rev 1.02 - 10 Oct 95 a) New Power-up sequence for PHYs Rev 1.01 - 03Oct95 a) Fixed problem with not recognising latest 100VG PHY b) Added option -XI, to exclude internal PHY tests Rev 1.00 - 31Aug95 [Production release] Rev Pre Release 5 - 27Aug95 a) Memory tests now test all of SRAM. b) Variable 'Address' not initialised in MEMORY.C Rev Pre Release 4 - 25Aug95 *Changed Name to TLANDIAG* a) Added the -dc option to detect mutiple board instances b) Added the PCI Slot number to NIC Info Table at end of Report c) Internal Restructuring Rev 0.07 - 22Aug95 a) Added abort after the detection of drivers or windows b) Added support to find Revisions of boards older then 2.0 before aborting diagnostics. c) Added support for National 100TX External PHY Rev 0.06 - 15Aug95 a) Added Display mode as a command line option b) Added Auto-Detect and PHY Find to automate testing process, elimnating the need for the user to define these at the command line. c) Added Detection for windows d) Added MII Read/Write Register Test e) Added EEPROM Read Test Rev 0.05 - 03Aug95 a) Added Loopback and Wire Test for 100vg and Internal 10BT b) Added MII Interrupt Test for 100vg and Internal 10BT c) Added command line options to specify tests on 100vg and the Wire Rev 0.04 - 17Jul95 a) Fixed problem in LED Test in 0.03, where it would hang on some machines b) Added Internal Wrap Test Rev 0.03 - 06Jul95 a) Added Host Interrupt Test b) Added Network Interface Card Info Table at end of Report Rev 0.02 - 30Jun95 [Initial beta release] (Called EVMDIAGS) --- END OF README.TXT ---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.