Method and apparatus for testing an interactive network board in a local area network (LAN).

What is claimed is:

1. A method for testing an interactive network board having a LAN interface, an SCSI interface, and a test interface, comprising the steps of:

loading a test program, which is designed to exercise the LAN interface and the SCSI interface and to monitor the LAN interface and the SCSI interface for abnormalities, into a RAM on the interactive network board;

activating the test program loaded in the RAM;

executing the test program on the interactive network board;

providing a test result after completing the test program;

providing a test computer, coupled to the interactive network board via the test interface, to detect the test result;

scripting an additional test program in accordance with the test result and loading the additional test program into the RAM; and

executing the additional test program on the interactive network board, and providing an additional test result after completing execution of the additional test program.

2. A method according to claim 1, further comprising the steps of:

downloading an operational program into the RAM on the interactive network board after completing the additional test program; and

loading the operational program from the RAM into a PROM disposed on the interactive network board.

3. A method according to claim 1, further comprising the step of performing a power-on self-test program within the interactive network board before said loading step.

4. A method according to claim 3, wherein the step of performing includes a step of monitoring, on the interactive network board, the test interface for an instruction set during a predetermined time interval after the completion of the power-on self-test.

5. A method according to claim 1, wherein the loading step includes a step of downloading a test program stored in the test computer through the test interface to the interactive network board.

6. A method according to claim 1, wherein the step of providing a test result includes the step of sending a test result to the test computer for verification therein, and further including the step of outputting an error signal from the test computer when the test result is not output from the board within a predetermined time period.

7. A method according to claim 1, wherein the step of executing the test program includes the step of receiving data across the SCSI interface and sending confirmation of a receipt of the data to the test computer.

8. A method according to claim 1, wherein the step of executing the test program includes the step of receiving data across the LAN interface and sending a confirmation of a receipt of the data to the test computer.

9. A method according to claim 1, wherein the step of executing the test program includes the steps of:

sending a signal from the interactive network board across the LAN interface to a peripheral to cause the peripheral to be configured as a LAN peripheral;

receiving a response from the configured peripheral; and

sending a confirmation of a receipt of the response from the board to the test computer.

10. A method according to claim 1, wherein the step of executing the test program includes the steps of:

sending a signal from the interactive network board across the SCSI interface to a peripheral to cause the peripheral to be configured as a LAN peripheral;

receiving a response from the configured peripheral; and

sending a confirmation of a receipt of the response from the board to the test computer.

11. A method according to claim 1, wherein the interactive network board includes a ROM which stores a standard program of normal network operability, and further comprising the step of monitoring whether the test program has been received through the test interface, wherein in the case the test program is not received through the test interface within a predetermined time after power-up, the standard program is loaded from ROM into RAM and the interactive network board carries out normal network operations.

12. A method according to claim 1, wherein the interactive network board includes a ROM which stores a standard program of normal network operability, and further comprising the step of concluding testing and the step of issuing a re-boot command via the test interface for the interactive network board to commence normal network operations, wherein in response to the re-boot command, the standard program is loaded from ROM into RAM and the interactive network board carries out normal network operations.

13. A method for testing an interactive network board having a LAN interface, an SCSI interface, and a test interface, comprising the steps of:

loading a test program, which is designed to exercise the LAN interface and the SCSI interface and to monitor the LAN interface and the SCSI interface for abnormalities, into a RAM on the interactive network board;

executing the test program loaded in the RAM;

providing a test result after completing the test program;

providing a test computer, coupled to the board via the test interface, to detect the test result;

downloading ROM firmware into the RAM after completing the test program; and

loading the ROM firmware from the RAM into a PROM on the interactive network board.

14. A method according to claim 13, wherein the step of downloading includes the step of downloading ROM firmware which comprises a plurality of independently executable modules.

15. A method according to claim 13, wherein the step of loading the ROM firmware includes the steps of erasing memory locations in the ROM and storing the ROM firmware into the erased memory locations.

16. A method according to claim 13, wherein the step of downloading includes the step of downloading a MAC address with said ROM firmware.

17. A method according to claim 13, wherein the interactive network board includes a ROM which stores a standard program of normal network operability, and further comprising the step of monitoring whether the test program has been received through the test interface, wherein in the case the test program is not received in the RAM within a predetermined time after power-up, the standard program is loaded from ROM into RAM and the interactive network board carries out normal network operations.

18. An apparatus for testing an interactive network board having a LAN interface, an SCSI interface, and a test interface, comprising:

a ROM disposed on the interactive network board for storing process steps;

a processor disposed on the interactive network board for processing the stored process steps;

a RAM disposed on the interactive network board for receiving and for storing operational instructions;

a first test station for sending test programs, which are designed to exercise the LAN interface, and the SCSI interface and to monitor the LAN interface and the SCSI interface for abnormalities, to the interactive network board and for receiving test results from the interactive network board through the test interface; and

a second test station for receiving requests for test data from the interactive network board, and for sending test data to said interactive network board through either said LAN interface or said SCSI interface;

wherein said processor processes said process steps stored in the ROM upon receiving power from a power supply, and wherein said first test station receives a process test result of said stored process steps via the test interface, and wherein said first test station sends a test program to said RAM, detects a test result of said test program, and provides an indication of a test failure in accordance with the detected test result, and

further wherein said processor requests test data from said second test station, said second test station sends the test data to said processor, and a confirmation of receipt of the test data is sent to said first test station via the test interface.

19. An apparatus according to claim 18, wherein the interactive network board is coupled to a peripheral device.

20. An apparatus according to claim 18, wherein the RAM comprises a dynamic RAM.

21. An apparatus according to claim 18, wherein the ROM comprises a flash EPROM.

22. An apparatus according to claim 18, wherein the first and second test stations each comprise a personal computer.

23. An apparatus according to claim 18, wherein the second test station emulates a LAN peripheral device.

24. A method for testing an interactive network board having a LAN interface, an SCSI interface, and a test interface, comprising the steps of:

loading a test program, which is designed to exercise the LAN interface and the SCSI interface and to monitor the LAN interface and the SCSI interface for abnormalities, into a RAM via the test interface on the interactive network board;

executing the test program from RAM so as to exercise the LAN interface and the SCSI interface and so as to detect abnormalities in the LAN interface and SCSI interface;

providing a test result which indicates whether abnormalities were detected;

scripting an additional test program in accordance with the test result received;

loading the additional scripted test program into the RAM on the interactive network board; and

executing the additional test program.

25. The method according to claim 24, further comprising the step of executing a standard program of normal network operability stored in a PROM on the interactive network board in the case the test program is not received through the test interface after a predetermined time has elapsed, wherein, after executing the stored program, the interactive network board carries out normal network operability on the LAN interface and the SCSI interface.

26. A method according to claim 24, further comprising the step of sending a signal to reinitialize the interactive network board upon completing the test program.

27. A method according to claim 24, further comprising the steps of downloading operational ROM firmware into a PROM on the interactive network board after the test program has been completed and sending a signal to the interactive network board to reinitialize using the downloaded operational ROM firmware.

28. An interactive network board having a test interface, a LAN interface, and an SCSI interface, said interface network board comprising:

a PROM for storing a standard program of normal network operability and a power-up self-test program;

a RAM for receiving and for storing operational programs; and

a processor for executing the operational programs stored in said RAM and for executing, upon power-up, the power-up self-test program stored in said PROM, wherein after executing the power-up self-test program, the processor monitors the test interface for a predetermined period and wherein, if a test program is received through the test interface within the predetermined period, the processor enters a test mode in which test programs are downloaded to said RAM and executed by said processor so as to carry out tests of network operability on said LAN interface and said SCSI interface, and wherein, if the test program is not received through the test interface within the predetermined period, the stored program stored in said ROM is downloaded to said RAM and executed by said processor so as to carry out normal network operability on said LAN interface and said SCSI interface.

Description Submit all comments and votes

BACKGROUND OF THE INVENTION

1. Field Of The Invention

The present invention relates generally to a circuit board which is coupled to a local area network peripheral (e.g. a printer) and which allows the peripheral to be an intelligent, interactive network member eliminating the necessity of dedicating a personal computer to manage the peripheral. More particularly, the present invention relates to a method and apparatus for testing an interactive network board which has both a local area network interface and a small computer system interface.

2. Related Art

Local Area Networks ("LANs") are known for coupling together a plurality of personal computers with peripheral devices such as printers, copiers, etc., to provide for enhanced communication and shared resources. Heretofore, peripherals such as printers coupled to a LAN were rather unintelligent, merely accepting information from the LAN and printing such information on a hard copy. Moreover, such printers usually required a host personal computer ("PC") to effectively manage the flow of data to the printer, i.e., to act as a "server" for the printer. This almost always required that the host PC be dedicated solely to the printer server task.

A number of products have recently appeared which ostensibly eliminate the need for such a dedicated PC by incorporating hardware and software into a circuit board which may be coupled into the peripheral in order to perform limited server functions. For example, ASP Computer Products, Inc. provides a device known as "JetLAN/P" which acts as a stand-alone print server for Novell networks. The JetLAN/P.RTM. device couples to a LAN using a 10Base-2 thin coaxial cable or a 10Base-T twisted-pair cable. However, the JetLAN/P.RTM. couples to the printer only through the printer's parallel port. Thus, while print information can be sent to the printer, the amount of printer status information which can be returned from the printer is severely restricted. For example, such a device may obtain "off-line" and "out of paper" status from the printer, but little else. Such a device does very little toward making the printer a truly intelligent, responsive member of the network.

Other known devices for coupling a printer to a LAN include the Hewlett-Packard Jet Direct.RTM. C2071A/B and C2059A, the Extended Systems EtherFlex.RTM., the Intel NetPort.RTM. and NetPort II.RTM., the Castelle LANPress.RTM. and JetPress.RTM., and the MILAN FastPort.RTM.. However, all of these devices suffer from the same disadvantages as the ASP JetLAN in that they do not allow the printer to transmit sufficient amounts of data to the LAN to enable the printer to be an effective and intelligent member of the network.

Conventionally, prior to shipping an interactive peripheral device to a customer, the manufacturer will perform several operational tests. At the completion of each test, the interactive peripheral device will output a checkpoint to the test station. In accordance with the checkpoint, it is determined at the test station whether the interactive peripheral device functions appropriately. If in the case the returned checkpoint does not coincide with an expected result, the interactive peripheral device is removed from the test interface to be either further debugged or ultimately disposed.

Heretofore, it has not been possible to test an interactive peripheral device, determine if an interactive device is properly operational, load either (or both) an updated executable file or a new executable file, and, in the case the interactive peripheral device is determined to operate improperly, to perform further tests in accordance with a returned checkpoint result. Consequently, since an interactive peripheral device which has failed testing must be manually tested and manually debugged, labor time and expenses are increased.

SUMMARY OF THE INVENTION

The present invention overcomes the drawbacks noted above by providing structure and function on a circuit board coupled to a peripheral which will permit the peripheral to be a responsive, intelligent member of a network.

In one aspect of the present invention, a method is provided for testing an interactive network board having a local area network interface, an SCSI interface, and a test interface whereby test programs are loaded from a test station through the test interface, stored in RAM on the board, and executed from the RAM. After successful completion of the test programs, an operational program may be downloaded into the board and stored into a PROM disposed on the board. According to this aspect of the invention, a method for testing an interactive network board having a LAN interface, an SCSI interface, and a test interface, comprises the steps of supplying power to the interactive network board, and performing a power-on self-test program within the interactive board. At the completion of the power-on self-test, a test program is loaded into a RAM on the interactive network board through the test interface, and the test program resident in the RAM is activated. The test program is executed and checkpoint test results are outputted after completion of the test program. A test computer is provided to receive the checkpoint test result and to script additional tests in accordance with checkpoint test results. At the completion of the test program, an operational program is downloaded into the RAM on the interactive board and the operational program is loaded into an EPROM on the interactive network board.

In a related aspect of the invention, there is an apparatus for testing an interactive network board having a local area network interface, a small computer system interface, and a test interface which comprises power supply means for supplying power to the interactive network board, a ROM for storing process steps, processing means for processing the stored process steps, and a RAM for receiving and for storing operational instructions. A first test station sends test programs and receives test results from the interactive network board. A second test station receives requests for test data and sends test data to the interactive network board through the LAN and/or SCSI interfaces.

The processor processes the process steps stored in the ROM upon receiving power from the power supply. The first test station receives results of the process steps, sends test programs to the RAM, receives results of the test programs, and reports failures in accordance with the test results. The processor requests test data from the second test station, the second test station sends the test data to the processor, and a signal acknowledging receipt of the test data is sent to the first test station.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-noted advantages and features of the present invention will become more readily apparent from the following detailed description of the preferred embodiments when taken in conjunction with the Drawings in which:

FIG. 1 is a bock diagram of a Local Area Network according to the present invention;

FIG. 2 is a block diagram of a plurality of Local Area Networks coupled together;

FIG. 3 is a block diagram showing the Network Expansion Board according to the present invention coupled between the Local Area Network and the printer;

FIG. 4 is a block diagram of the Network Expansion Board according to the present invention;

FIGS. 5A, 5B and 5C comprise a top-level flowchart showing the basic functions of the Network Expansion Board according to the present invention;

FIG. 6 is a diagram showing the sequence in which software modules are loaded from the Network Expansion Board ROM to RAM;

FIG. 7 is a block diagram showing hardware and software interfaces between the LAN and the Network Expansion Board;

FIG. 8 is a flowchart showing how the EPROM firmware is configured for placing the Network Expansion Board in an operational mode;

FIG. 9 is a chart showing the physical construction of different frame packets used on Ethernet;

FIG. 10 is a flowchart showing the operation of a PRESCAN software module;

FIG. 11 is a chart showing that the PRESCAN module may be used with other software protocols;

FIG. 12 is a chart for explaining the software structure of the SAPSERVER program;

FIG. 13 is a flowchart showing the operation of SAPSERVER;

FIG. 14 is a flowchart showing the operation of a CPINIT program;

FIG. 15 is a flowchart showing the operation of a CPCONSOL program;

FIGS. 16A and 16B comprise a flowchart showing the operation of a CPSOCKET program;

FIGS. 17A and 17B comprise a flowchart showing the automatic logging of peripheral statistics;

FIG. 18 is a flowchart showing how multi-tasking processing is performed;

FIG. 19 is a flowchart showing how to place the printer in a safe, default configuration;

FIG. 20 is a flowchart showing the downloading of executable files to the Network Expansion Board from the local area network;

FIG. 21 is a flowchart showing the loading of independently-executable modules in the EPROM of the Network Expansion Board;

FIG. 22 is a block diagram showing Network Expansion Board EPROM flash protection circuitry;

FIG. 23 is a flowchart showing the operation of the circuitry of FIG. 22;

FIG. 24 is a flowchart showing the operation of remotely loading firmware in the Network Expansion Board EPROM;

FIG. 25 is a block diagram showing a hardware configuration for testing the Network Expansion Board; and

FIGS. 26A and 26B comprise a flowchart showing a method of testing the Network Expansion Board using the test configuration of FIG. 25.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In its general aspects, the present invention provides hardware and software solutions for making a network peripheral, such as a printer, an interactive network member which not only receives and processes data received from the network, but of also transmits to the network significant amounts of data such as detailed status information, operational parameters, and even data input to the peripheral through other modalities such as scanning, facsimile reception, etc. By integrating such hardware and software with the peripheral, it is possible to eliminate the requirement for dedicating a personal computer to the peripheral to act as a peripheral server.

1. ARCHITECTURE

FIG. 1 is a block diagram showing the present invention incorporated into a Network Expansion Board ("NEB") 2 coupled to a printer 4 which has an open architecture (to be discussed below). The NEB 2 is coupled to the LAN bus 6 through a LAN interface 8, for example, Ethernet interfaces 10Base-2, 10Base-T, or 10Base-5, respectively, with a Coax connector, an RJ45 connector, or a DB15 connector (AUI). Also coupled to the LAN 6 may be such network members as PC 10, PC 12, PC 14 (which in this case acts as the network administrator if the administrator has logged in at that PC; to be discussed below), and a printer 16 (with embedded QSERVER functionality; also to be discussed below). Other LANmembers may include PC 18 (acting as a print server; to be discussed below) with attached printer 20, PC 22 (acting as an RPRINTER; to be discussed below) with attached printer 24, and printer 26 which is coupled to the LAN 6 through a NetPort device 28 (discussed in the Background of the Invention above). A file server 30 is coupled to the LAN 6 and serves as a "library" for files to be transmitted and processed on the LAN. The file server 30 may have attached printers 32 and 34.

In more detail, the network depicted in FIG. 1 may utilize any network software such as Novell or Unix software in order to effect communication among the various network members. The present embodiments will be described with respect to a LAN utilizing Novell NetWare.RTM. software (to be discussed in greater detail in section 3a below) although any network software may be used. A detailed description of this software package may be found in the publications "NetWare.RTM. User's Guide" and the "NetWare.RTM. Supervisor's Guide" by M&T Books, copyrighted 1990, incorporated herein by reference. See also the "NetWare.RTM. Print Server" by Novell, March 1991 edition, Novell Part No. 100-000892-001. Briefly, the file server 30 acts as a file manager, receiving, storing, queuing, caching, and transmitting files of data between LAN members. For example, data files created respectively at the PCs 10 and 12 may be routed to the file server 30 which may order those data files and then transfer the ordered data files to a printer 24 upon command from a print server in PC 18. The file server 30 may include or may be coupled to a large capacity storage member such as a 10 Gigabyte hard disk subsystem. Furthermore, the printers 32 and 34 may be coupled to the file server 30 to provide additional printing stations, if desired.

While personal computer equipment is illustrated in FIG. 1, other computer equipment may also be included, as appropriate to the network software being executed. For example, Unix workstations may be included in the network when Unix software is used, and those workstations may be used in conjunction with the illustrated PC's under appropriate circumstances.

PCs 10 and 12 may each comprise a standard work station PC capable of generating data files, transmitting them onto the LAN, receiving files from the LAN, and displaying and/or processing such files at the work station. The PCs 10 and 12, however, are not capable of exercising control over LAN peripherals (unless the network administrator is logged into that PC).

A PC capable of exerting limited control over LAN peripherals is PC 22 which includes an embedded RPRINTER program. The RPRINTER program is a MS-DOS Terminate and Stay Resident ("TSR") program which runs on a work station to allow users to share the printer 24 connected to the work station. RPRINTER is a relatively unintelligent program that does not have the ability to search printer queues for work. RPRINTER gets its work from a PSERVER (to be discussed below) that is running elsewhere in the network. Because they communicate with the attached printer over the printer's parallel port, RPRINTERs are able to obtain only limited status and to return that status information to the responsible PSERVER over the LAN 6. From a control standpoint, an RPRINTER allows stopping of a print job and little more. Some printers include RPRINTER features by offering internal or external circuit boards that provide the same limited features of the RPRINTER TSR program running in a personal computer.

Another network entity capable of exercising limited control over LAN peripherals is a printer 16 with attached circuit board 36 having an embeddedQSERVER program. Here, the QSERVER program runs inside an HP LaserJet III.RTM. SI printer, and has the capability of searching the file server 30 print queues for eligible print files. The QSERVER's search queues cannot be dynamically altered nor does the QSERVER respond to any form of status inquiry. The benefit of the QSERVER is its ability to autonomously search for work. The QSERVER does not require a PSERVER running elsewhere in the system to feed it work. Since the QSERVER does not have a corresponding PSERVER and it does not itself have any status and control capabilities, it offers less control than even the RPRINTER. A QSERVER also differs from a PSERVER in that it has extremely limited notification features and cannot print banners at the beginning of each print job.

Another network member having a QSERVER capability is printer 26 which is coupled to the LAN 6 through an external NetPort device 28.

Other peripheral server programs may be executed to service various peripherals, such as scanners, copiers, facsimiles etc., and servers may also be provided based on network software protocol such as a Unix-compatible Line Printer Remote server ("LPR").

A LAN member capable of exercising significant control over LAN peripherals is the PC 18 having a PSERVER program embedded therein. PSERVER has the ability to service multiple user-defined print queues, perform dynamic search queue modification, and provide defined notification procedures for exception (failure) conditions and status and control capabilities. PSERVER is provided in several forms. PSERVER.EXE is a program that runs dedicated on a work station and controls both local and remote printers. The local printers can be connected to either serial or parallel ports, and the remote printers are printers running elsewhere in the system. Two other forms of the PSERVER program are the PSERVER.VAP and the PSERVER.NLM. These are PSERVER versions that run on the file server 30 itself. The .YAP version is for NetWare.RTM. 286, and the .NLM version is for NetWare.RTM. 386. While the PSERVER provides much more capability than the RPRINTER and QSERVER, one of its drawbacks is that the .EXE version requires a dedicated personal computer.

A dedicated personal computer running PSERVER.EXE can control as many as 16 local/remote printers and can request print information from many file server queues. However, there are several drawbacks to relying on PSERVER to control network printing services. The first drawback is that multiple printer streams must all be funnelled through a single network node and personal computer processor. This can become a bottleneck. The second drawback is that for the most efficient operation, the printers should be connected to the computer locally, as with the printer 20. This can be an inconvenience for users since it requires the printers to be clustered around PC 18. The third drawback is that if the controlled printers are remote as in the case of printer 24 which is serviced by RPRINTER, then the print data must make the trip from the file server 30 to the PSERVER PC 18 and then be retransmitted to the printer running RPRINTER. This is inefficient.

The fourth drawback is the limited amount of printer status and control information offered through PSERVER, It has already been stated that RPRINTER does not allow for much more than rudimentary status such as "out of paper" and "off line". PSERVER itself for locally and remotely connected printers does not offer much more than this because it was designed with consideration of the limitat