The present invention relates to multilevel digital signaling, and in particular to mechanisms to test for errors that may occur in a multilevel, multi-line signaling system.
The use of multiple signal levels instead of binary signal levels is a known technique for increasing the data rate of a digital signaling system, without necessarily increasing the signal frequency of the system. Such multilevel signaling is sometimes known as multiple pulse amplitude modulation or multi-PAM, and has been implemented with radio or other long-distance wireless signaling systems.
Other long-distance uses for multi-PAM signaling include computer or telecommunication systems that employ Gigabit Ethernet over optical fiber (IEEE 802.3z) and over copper wires (IEEE 802.3ab), which use three and five signal levels, respectively, spaced symmetrically about and including ground.
Multi-PAM has not traditionally been used for communication between devices in close proximity or belonging to the same system, such as those connected to the same integrated circuit (IC) or printed circuit board (PCB). One reason for this may be that within such a system the characteristics of transmission lines, such as buses or signal lines, over which signals travel are tightly controlled, so that increases in data rate may be achieved by simply increasing data frequency. At higher frequencies, however, receiving devices may have a reduced ability to distinguish binary signals, so that dividing signals into smaller levels for multi-PAM is problematic. Multi-PAM may also be more difficult to implement in multi-drop bus systems (i.e., buses shared by multiple processing mechanisms), since the lower signal-to-noise ratio for such systems sometimes results in bit errors even for binary signals.
Testing of a multi-PAM device is also problematic, since test apparatuses are typically designed for testing binary signals. Thus, in addition to the complexities of designing a multi-PAM device, conventional ways of testing a multi-PAM device to ensure that the device operates free of errors may be lacking.
Error detection mechanisms for signal interfaces are disclosed, including built-in self-test (BIST) mechanisms for testing multilevel signal interfaces. The error detection mechanisms may be provided in an integrated circuit (IC) chip that contains at least one of the signal interfaces, or may be coupled to the interfaces on a printed circuit board (PCB). BIST mechanisms may include, for example, test signal generators and mechanisms for determining whether the test signals generated are accurately transmitted and received by the interface. The BIST mechanisms may check a single input/output interface, a group of interfaces or may operate with a master device that tests a plurality of slave device interfaces. The error detection mechanisms may be particularly advantageous for testing memory circuits designed to communicate according to multi-PAM signals over printed circuit boards.
A first bit of each logical state is termed the most significant bit (MSB) and a second bit of each logical state is termed the least significant bit (LSB). Each logical state may be termed a symbol, since it provides information regarding more than one bit. Data may be transmitted and read at both rising and falling edges of a clock cycle, so that each bit signal and each dual-bit signal has a duration of one-half the clock cycle. The logical states are arranged in a Gray coded order, so that an erroneous reading of an adjacent logic state produces an error in only one of the bits. Another characteristic of this logical 4-PAM arrangement is that setting the LSB equal to zero for all states results in a 2-PAM scheme. Alternatively, the logical states can be arranged in numerical (00, 01, 10, 11) or other order.
In one embodiment the communication system is employed for a memory bus that may for instance include random access memory (RAM), like that disclosed in U.S. Pat. No. 5,243,703 to Farmwald et al., which is incorporated herein by reference. The multi-PAM communication and testing techniques disclosed herein may also be used for other contained systems, such as for communication between processors of a multiprocessor apparatus, or between a processor and a peripheral device, such as a disk drive controller or network interface card over an input/output bus.
Output driver 20 includes first 21, second 22 and third 23 transistor current sources, which together produce a current I when all are active, pulling the voltage at pad 25 down from VTERM by I·Z0, signaling logical state 10 under the Gray code system. Control signal input through lines C1, C2 and C3 switch respective current sources 21, 22 and 23 on and off. To produce voltage VOUT0=VTERM, signaling logical state 00, current sources 21, 22 and 23 are all turned off. To produce voltage VOUT1=VTERM−(⅓)I·Z0, signaling logical state 01, one of the current sources is turned on, and to produce voltage VOUT2=VTERM−(⅔)I·Z0, two of the current sources are turned on. The logical level 00 is chosen to have zero current flow to reduce power consumption for the situation in which much of the data transmitted has a MSB and LSB of zero. The reference levels are set halfway between the signal levels, so that VREFH=VTERM−(⅙)I·Z0, VREFM=VTERM−(½)I·Z0 and VREFL=VTERM(⅚)I·Z0.
Another example of a multilevel signaling apparatus and method is disclosed in U.S. Pat. No. 6,005,895 to Perino et al., which is also incorporated herein by reference. This and other types of multilevel signal interfaces may also be tested in accordance with the present invention. Also incorporated by reference herein is U.S. patent application Ser. No. 09/953,486 entitled “Multilevel Signal Interface Testing with Binary Test Apparatus by Emulation of Multilevel Signals,” filed on the same date as the present application by inventors Werner, Zerbe, Stonecypher, Liaw and Chang, which discloses other means for testing multilevel signal interfaces.
Encoder 100 is shown in more detail in
Table 1 illustrates the correspondence between MSB and LSB signals and the control signals on lines C1, C2 and C3 that translate binary signals into 4-PAM signals.
For example, when MSB=0 and LSB=0, all the control signals are off. When MSB=0 and LSB=1, the OR gate 104 outputs on, so that the control signal on line C1 is on, but control signals on lines C2 and C3 are still off. When both MSB=1 and LSB=1, control signals on lines C1 and C2 are on, but due to inverted LSB signals input to AND gates such as AND gate 110, the control signal on line C3 is off. When MSB=1 and LSB=0, control signals on all the lines C1, C2 and C3 are turned on. In this fashion the MSB and LSB may be combined as Gray code and translated to thermometer code control signals on lines C1, C2 and C3 that control the current sources to drive 4-PAM signals.
An MSBE receiver 202 of the 4-PAM receiver 200 in this example receives and decodes a 4-PAM input signal VIN by determining whether the signal VIN is greater or less than VREFM. In the MSBE receiver 202, a latching comparator 204 compares the value of the voltage of the received input signal VIN to the reference voltage VREFM and latches the value of the result of the comparison B in response to a receive clock signal RCLOCK. Although this embodiment discloses data sampling at both rising and falling clock edges, data may alternatively be sampled at only the rising clock edges or only the falling clock edges.
In an LSBE receiver 208, two latching comparators 210 and 214 compare the value of the voltage of the received input signal VIN to the reference voltages VREFH and VREFL, and latch the value of the result of the comparisons A and C, respectively, in response to the receive clock signal. To decode the LSBE, the signals from the comparator outputs B, A, and C are then passed through combinational logic 220. The latching comparators 204, 210 and 214 may be implemented as integrating receivers to reduce the sensitivity of the output signals to noise. This can be accomplished by integrating the difference between the received signal, Vin, and the three respective reference voltages over most or all of the bit cycle, and then latching the integrated results as the outputs A, B and C. Related disclosure of a multi-PAM signaling system can be found in U.S. patent application Ser. No. 09/478,916, entitled “Low Latency Multi-Level Communication Interface,” filed on Jan. 6, 2000, which is incorporated by reference herein.
Encoder 305 and transmitter 310, which together function as a transmit mechanism, may be similar to encoder 100 and output driver 20 described previously, and input/output pin 313 may be similar to pads 18 or 25 described above, for example. Also coupled to input/output pin 313 is receiver 315, which is adapted to detect multilevel signals from pin 313. The output of receiver 315 is sampled with receive clock signals 317 and decoded into binary signals at decoder 320 to be communicated as data 322 for storage in memory 350. Receiver 315 and decoder 320 may be similar to receive mechanism 200 described previously.
To use device 300 for data storage, multilevel signals may be received at I/O pin 313 from a device external to this figure, such as a transmitter or processor connected to pin 313 by a signal pathway such as a conductive line. Those multilevel signals may be detected by receiver 315, translated to binary signals by decoder 320, and sent as data 322 for storage in memory 350. To read information from memory 350, data 301 is sent to encoder 305, which causes transmitter 310 to send multilevel signals to I/O pin 313 for transmission to the external device.
In addition to the data storage mechanisms described above, device 300 includes a signal generator 355 that creates test signals 358 for testing signal interface 330. Signal generator 355 may, for example, include a linear feedback shift register (LFSR) that generates a predictable series of test signals 358, or may include another known pseudo-random bit sequence (PRBS) generator. As an alternative example, signal generator 355 may be programmed to output a known sequence of signals designed to test worst case transitions of the interface 330 or memory 350.
In a test mode, test signals 358 from signal generator 355 may be fed to encoder 305, which causes multilevel signals to be sent by transmitter 310. In contrast with conventional operation, receiver 315 is enabled to detect the multilevel signals and provide them to decoder 320. Decoder 320 translates the multilevel signals to binary test signals 364 that are output to an error detector 360, which determines whether test signals 358 have been accurately transmitted by signal interface 330. Error detector 360 may include a comparison mechanism such as one or more comparitors or other logic elements.
To make this determination, device 300 may include a second signal generator 362 that creates a series of reference signals 366 for comparison with test signals 364. Signal generator 362 may be substantially identical to signal generator 355, e.g., both may be a LFSR having an identical number of bits. To synchronize signal generator 362 with signal generator 355 in this case, an initial set of test signals 364 may be loaded into the shift register of signal generator 362. Alternatively, signal generator 355 may be connected to a variable delay element 370 that delays test signals 358 by an amount substantially equal to the delay of signal interface 330, to provide reference signals 377 to error detector 360, for comparison with test signals 364. Variable delay element 370 may include a plurality of essentially static delay elements, such as flip-flops, as well as a tunable delay element, to form a kind of phase-locked loop (PLL) or delay-locked loop (DLL).
Delay element 370 may also be offset from its ideal timing so that the timing margin may be determined for either transmitting or receiving data. Likewise, each of the reference voltages in
A first signal interface unit 410 includes a first transmit mechanism 414, a first receive mechanism 416 and a first I/O pin 418. A second signal interface unit 420, which includes a second transmit mechanism 424, a second receive mechanism 426 and a second I/O pin 428, is coupled to first signal interface unit 410 via an optional first multiplexer-demultiplexer 412. First multiplexer-demultiplexer 412 can select to bypass second signal interface unit 420 by connecting instead to an optional second multiplexer-demultiplexer 422. Second multiplexer-demultiplexer 412 selects whether second signal interface unit 420 communicates with or bypasses a third signal interface unit, not shown.
In this manner N signal interface units may be daisy-chained for testing, with an Nth signal interface unit 430 including an Nth transmit mechanism 434, an Nth receive mechanism 436 and an Nth I/O pin 438, the Nth signal interface unit 430 coupled to the other signal interface units with another multiplexer-demultiplexer, not shown. Each transmit mechanism and each receive mechanism times the signals with clock signals, which may be sent from a master clock generator, not shown in this figure. A first signal generator 440 is coupled to the first signal interface unit 410 via an optional demultiplexer 408, which can be switched to instead bypass first signal interface unit 410. An error detector 444 is coupled to the Nth interface unit 430 and a second signal generator 448 is coupled to the error detector 444.
To test the signal interface 404, signal generator 440 sends a test signal or series of test signals to first transmit mechanism 414, which in turn sends test signals to first receive mechanism 416, in a fashion similar to that described above with regard to
Error detector 444 also receives signals from a second signal generator 448, which are compared with the signals from Nth receiver 436 that are detected by error detector 444. The signals from second signal generator 448 are designed to be substantially identical to the test signals output by first signal generator 440 but delayed by a time period substantially equal to the delay encountered in passing through the series of interface units of the signal interface 404. If the signal or series of signals received by error detector 444 from Nth receiver 436 do not match the signal or series of signals received by error detector 444 from second signal generator 448, then error detector 444 outputs an error signal.
A system such as that shown in
If an error is found in the signal interface 400, the multiplexers and demultiplexers, or similar logic circuits that select between two inputs and two outputs, can be set to test the individual interface units until the defective unit or units are identified. Alternatively, the individual interface units may be tested initially for errors, or a subset of the interface units may be tested, by appropriate settings of the multiplexers and demultiplexers. In this manner the multiplexers and demultiplexers allow any subset of the N signal interface units to be tested.
Each interface unit of A-BYTE 505 includes an I/O pin in a group of I/O pins labeled 520. Each interface unit of B-BYTE 511 and each interface unit in R-BYTE 515 also includes an I/O pin, disposed in a group of I/O pins labeled 522 and 525, respectively. Each interface unit in A-BYTE 505 is also coupled by a signal pathway to a corresponding interface unit in B-BYTE 511, allowing the A-BYTE 505 to test the B-BYTE 511 and vice-versa.
A first PRBS generator or plurality of PRBS generators 530 may be coupled to the various interface units of A-BYTE 505, and a second PRBS generator or plurality of PRBS generators 533 may be coupled to the various interface units of B-BYTE 511. For the case in which first PRBS generator(s) 530 includes a plurality of different PRBS generators, each of those PRBS generators may be connectable to one or more of the interface units of A-BYTE 505. Similarly, for the case in which second PRBS generator 533 includes a plurality of different PRBS generators, each of those PRBS generators may be connectable to one or more of the interface units of B-BYTE 511. An error detector 535 is coupled to first and second PRBS generators 530 and 533.
To test the interface units in A-BYTE 505 and B-BYTE 511, first PRBS generator(s) 530 may output binary test signals to one or more of the interface units of A-BYTE 505, as shown by arrow 540. Each of the interface units of A-BYTE 505 that receives test signals from first PRBS generator(s) 530 sends multilevel signals to its corresponding interface unit in B-BYTE 511. The multilevel signals are detected by the corresponding interface unit in B-BYTE 511 and decoded to binary signals that are provided to error detector 535, as shown by arrow 544. Reference signals are sent from second PRBS generator(s) 533 to error detector 535, as shown by arrow 548, the reference signals synchronized with the decoded signals. The decoded signals from B-BYTE 511 are compared at error detector 535 with the synchronized reference signals from second PRBS generator(s) 533. Error detector 535 outputs an error signal if the decoded and reference signals being compared do not match, indicating that the transmit mechanism of A-BYTE 505 and/or the receive mechanism of B-BYTE 511 did not function properly.
Similarly, second PRBS generator(s) 533 may output binary test signals to one or more of the interface units of B-BYTE 511, as shown by arrow 550. Each of the interface units of B-BYTE 511 that receives test signals from second PRBS generator(s) 533 sends multilevel signals to its corresponding interface unit in A-BYTE 505. The multilevel signals are detected by the corresponding interface unit in A-BYTE 505 and decoded to binary signals that are provided to error detector 535, as shown by arrow 552. Reference signals are sent from first PRBS generator(s) 530 to error detector 535, as shown by arrow 555, the reference signals synchronized with the decoded signals. The decoded signals from A-BYTE 505 are compared at error detector 535 with the synchronized reference signals from first PRBS generator(s) 530. Error detector 535 outputs an error signal if the decoded and reference signals being compared do not match, indicating that the transmit mechanism of B-BYTE 511 and/or the receive mechanism of A-BYTE 505 did not function properly.
If system 500 has less PRBS generators than interface units, the testing process may be repeated until all of the interface units have been tested. First PRBS generator(s) 530, or other PRBS generator(s), may be connected to R-Byte 515, and each of the interface units of R-Byte 515 may be coupled to another of the interface units of R-Byte 515, allowing those interface units to test each other by comparing signals transmitted and received at the error detector 535. Thus, testing of the multilevel signal interface can be accomplished by the means described above, without the need for additional test mechanisms to generate or detect multilevel signals.
Multilevel signal interfaces 616, 622, 632 and 642 are coupled to a first signal pathway such as bus 650, which may be a byte wide. Likewise, multilevel signal interfaces 617, 623, 633 and 643 are coupled to a second signal pathway such as bus 655, which may also be a byte wide. Similarly, binary signal interfaces 618, 624, 634 and 644 are coupled to a third signal pathway such as bus 660, which may also be a byte wide. Buses 650, 655 and 660 are terminated at VTERM with a matched impedance to reduce reflections.
Each of the devices 606 and 611-613 may have a test signal generator such as a PRBS generator and an error detector. In this case, receive mechanisms of devices 611-613 can be tested by sending signals from control device CTRL 606, and transmit mechanisms of devices 611-613 can be tested by sending signals sent to control device CTRL 606. Alternatively, only control device CTRL 606 may have a PRBS generator and error detector, with devices 611-613 being tested by sending signals to receive mechanisms of devices 611-613, with corresponding transmit mechanisms of those devices 611-613 sending signals back to control device CTRL 606 for error detection. Optionally, each of the signal interfaces 616-618, 622-624, 632-634 and 642-644 may be coupled to at least one test signal generator and error detector, and each interface unit of each of the signal interfaces 616-618, 622-624, 632-634 and 642-644 may be connected to a test signal generator. The choice of how many test mechanisms to employ along with each device may involve tradeoffs between the cost of the test mechanisms, such as space required by the test mechanisms, and the ease and exactness of the testing.
As an example, to test the receive mechanisms of multilevel signal interface 622, multilevel signal interface 616 may be caused by a PRBS generator to send a series of test signals along bus 650 to interface 622, as shown by arrow 666. Assuming that interface 622 has at least one PRBS detector, which may include a combination of PRBS generator and error detector, the PRBS detector can check whether bus 650 and receive mechanism of signal interface 622 correctly received the signals. For the case in which a PRBS generator is provided for each interface unit of signal interface 616, and a PRBS detector is provided for each interface unit of signal interface 622, the receive mechanisms of signal interface 622 and bus 650 can also be tested for errors caused by cross-talk, for example along bus 650.
To test the transmit mechanisms of multilevel signal interface 642, that interface may be caused by a PRBS generator to send a series of test signals along bus 650 to multilevel signal interface 616, as shown by arrow 670. A PRBS detector connected to interface 616 can check whether the bus 650 and transmit mechanism of signal interface 642 correctly sent the signals. For the case in which a PRBS generator is provided for each interface unit of signal interface 642, and a PRBS detector is provided for each interface unit of signal interface 616, the transmit mechanisms of signal interface 642 and the bus 650 can be tested for cross-talk conditions as well.
To test multilevel signal interface 633, a series of test signals are sent by multilevel signal interface 617 along bus 655 to a receive mechanism of interface 634, as shown by arrow 672. Assuming that the receive mechanism of interface 633 is not coupled to a PRBS detector but instead to a memory and transmit mechanism of that interface 633, the transmit mechanism can later send back a series of signals along bus 655 to a receive mechanism of interface 617, as shown by arrow 677. A PRBS detector connected to interface 617 can check whether the bus 655 and receive and transmit mechanisms of signal interface 634 correctly relayed the signals over bus 655. For the case in which a PRBS generator is provided for each interface unit of signal interface 617, the receive and transmit mechanisms of signal interface 633 and the bus 655 can be tested for cross-talk conditions as well.
For example, control device CTRL 606 can transmit PRBS sequences through interface 616 to interface 632, filling some or all of the addresses of a memory on B-CELL 612. B-CELL 612 is then instructed to transmit all of the PRBS data from its memory, the PRBS data being received by interface 616. Control device CTRL 606 can then check the data with a PRBS error detector.
Buses 650, 655 and 660 may be memory buses or other buses internal to an apparatus such as a computer and may, for example, be affixed to a base such as a PCB or may be part of an IC that is affixed to a base such as a wafer substrate. Alternatively, buses 650, 655 and 660 may connect peripheral devices with a computer, so that control device CTRL 606 may be representative of the computer and A-CELL 611, B-CELL 612 and C-CELL 613 may be representative of peripheral devices such as disk drives. As another example, buses 650, 655 and 660 may represent networks connecting control device CTRL 606, A-CELL 611, B-CELL 612 and C-CELL 613. Further, although it may function as a master device, control device CTRL 606 may be substantially identical to A-CELL 611, B-CELL 612 and/or C-CELL 613. Control device CTRL 606 may also transmit master clock signals along buses 650, 655 and 660 to synchronize various elements of A-CELL 611, B-CELL 612 and C-CELL 613.
In the embodiment of
The signaling paths 650, 655 and 660 may include multiplexed sets of signal lines to transfer both data and control information between the memory controller 606 and memory devices 611, 612 and 613. Alternatively, as described regarding
While a memory system that includes connectors for removable insertion of memory modules is depicted in
Alternatively, the memory devices, the memory controller and the signaling path may all be included within a single integrated circuit along with other circuitry (e.g., graphics control circuitry, digital signal processing circuitry, general purpose processing circuitry, etc.). Such a system or that shown in
Although we have focused on teaching the preferred embodiments of testing, with built-in test mechanisms, devices including multilevel signal interfaces, other embodiments and modifications of this invention will be apparent to persons of ordinary skill in the art in view of these teachings. Therefore, this invention is limited only by the following claims, which include all such embodiments, modifications and equivalents when viewed in conjunction with the above specification and accompanying drawings.
This application claims the benefit under 35 U.S.C. §120 of U.S. Utility patent application Ser. No. 09/953,514, entitled “Built-In Self-Testing of Multilevel Signal Interfaces” by Carl W. Werner, Jared L. Zerbe and William F. Stonecypher, filed Jan. 20, 2005, filed Sep. 14, 2001, which is incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
Parent | 09953514 | Sep 2001 | US |
Child | 11433409 | May 2006 | US |