# Patent

## Title
Memory device with retransmission upon error

## Abstract

A controller includes a link interface that is to couple to a first link to communicate bidirectional data and a second link to transmit unidirectional error-detection information. An encoder is to dynamically add first error-detection information to at least a portion of write data. A transmitter, coupled to the link interface, is to transmit the write data. A delay element is coupled to an output from the encoder. A receiver, coupled to the link interface, is to receive second error-detection information corresponding to at least the portion of the write data. Error-detection logic is coupled to an output from the delay element and an output from the receiver. The error-detection logic is to determine errors in at least the portion of the write data by comparing the first error-detection information and the second error-detection information, and, if an error is detected, is to assert an error condition.

## Background
RELATED APPLICATIONS
This application is a continuation of U.S. application Ser. No. 14/806,011, filed Jul. 22, 2015, which is a continuation of U.S. application Ser. No. 14/175,955, filed Feb. 7, 2014, now U.S. Pat. No. 9,092,352, which is a continuation of U.S. application Ser. No. 13/752,324, filed Jan. 28, 2013, now U.S. Pat. No. 8,656,254, which is continuation of U.S. application Ser. No. 13/398,768, filed Feb. 16, 2012, now U.S. Pat. No. 8,365,042, which is a continuation of U.S. patent application Ser. No. 13/013,779, filed Jan. 25, 2011, now U.S. Pat. No. 8,132,077, which is continuation of U.S. patent application Ser. No. 12/479,684, filed Jun. 5, 2009, now U.S. Pat. No. 7,882,423, which is a divisional of U.S. patent application Ser. No. 11/330,524, filed Jan. 11, 2006, now U.S. Pat. No. 7,562,285, entitled “Unidirectional Error Code Transfer for a Bidirectional Data Link,” which are incorporated herein by reference in their entireties.
This application is also related to U.S. patent application Ser. No. 12/479,688, filed Jun. 5, 2009, entitled “Unidirectional Error Code Transfer Method for Bidirectional Data Link,” now U.S. Pat. No. 7,831,888, which is incorporated herein by reference in its entirety.


FIELD
The subject matter disclosed herein relates generally to integrated circuits, methods and systems having error detection, error correction and/or retry modes of operation using a bidirectional data link.
BACKGROUND
Low bit-error-rate (BER) communication of data over a communications channel is often considered an important requirement in many systems. In the case of memory devices and systems, fulfilling this requirement is increasingly difficult due to signaling and circuit limitations. In future memory devices and systems, scaling of interface circuitry to accommodate higher data rates may be restricted by transistor sensitivity and threshold limits. In addition, even though interconnect lengths and a loss tangent may be constant, the higher data rates may increase noise due to an increased bandwidth. Given constraints on interface overhead and latency, developing faster interfaces with a low BER may become more challenging and expensive. This poses a problem, since conventional interfaces in memory devices and systems typically have an extremely low BER. For example, the BER in the interface in a dynamic random access memory (DRAM) is typically less than a soft error rate in the DRAM core, i.e., less than 10−30. If the BER in the interface increases in future high-speed designs, ensuring reliability with different processes, systems and environments for conventional memory devices and systems may be difficult.



BRIEF DESCRIPTION OF THE DRAWINGS
For a better understanding, reference should be made to the following detailed description taken in conjunction with the accompanying drawings, in which:
FIG. 1 is a block diagram illustrating an embodiment of a system.
FIG. 2A is a block diagram illustrating an embodiment of a controller.
FIG. 2B is a block diagram illustrating an embodiment of a device.
FIG. 3 is a diagram illustrating a data stream and an error code stream in an embodiment of a system.
FIG. 4A is a block diagram illustrating an embodiment of a controller.
FIG. 4B is a block diagram illustrating an embodiment of a device.
FIG. 5 is a diagram illustrating a data stream and a command stream in an embodiment of a system.
FIG. 6 is a block diagram illustrating an embodiment of generating error code bits.
FIG. 7A is a block diagram illustrating an embodiment of a controller.
FIG. 7B is a block diagram illustrating an embodiment of a device.
FIG. 8 is a flow diagram illustrating a method of operation of an embodiment of a system.
FIG. 9 is a flow diagram illustrating a method of operation of an embodiment of a system.
FIG. 10 is a flow diagram illustrating a method of operation of an embodiment of a system.
FIG. 11 is a block diagram illustrating an embodiment of a system.



Like reference numerals refer to corresponding parts throughout the drawings.
DETAILED DESCRIPTION OF EMBODIMENTS
A controller is described. In some embodiments, the controller may be a memory controller. The controller includes a first link interface that is to couple to a first link to communicate bi-directional data and a second link to transmit unidirectional error-detection information. A first encoder is to dynamically add first error-detection information to at least a portion of write data. A first transmitter, coupled to the first link interface, is to transmit the write data. A first delay element is coupled to an output from the first encoder. A first receiver, coupled to the first link interface, is to receive read data. A second encoder, coupled to an output from the first receiver, is to dynamically add second error-detection information to at least a portion of the read data. A second receiver, coupled to the first link interface, is to receive third error-detection information corresponding to at least the portion of the read data and fourth error-detection information corresponding to at least the portion of the write data. First error-detection logic is coupled to an output from the first delay element, an output from the second encoder and an output from the second receiver. The first error-detection logic is to determine errors in at least the portion of the write data by comparing the first error-detection information and the fourth error-detection information, and is to determine errors in at least the portion of the read data by comparing the second error-detection information and the third error-detection information. If an error is detected, the first error-detection logic is to assert an error condition.
The controller may include retry logic and/or instructions to perform a retry remedial action if the error condition is asserted. The retry remedial action may include re-transmitting the write data using the first transmitter and the first link interface. The retry remedial action may include re-receiving the read data using the first receiver and the first link interface after the read data is re-transmitted by a device.
The controller may include a third encoder to dynamically add fifth error-detection information to at least a portion of write mask information, and a second transmitter coupled to an output from the third encoder and to the first link interface. The first link interface is to couple to a third link to transmit unidirectional command information including the fifth error-detection information, and the first link interface is to couple to the first link to communicate the write mask information.
In another embodiment, a device is described. In some embodiments, the device may be a memory device, including a memory core that utilizes solid-state memory, semiconductor memory, organic memory and/or another memory material. The device includes a second link interface that is to couple to the first link to communicate bi-directional data and the second link to transmit unidirectional error-detection information. A fourth encoder is to dynamically add the third error-detection information to at least the portion of the read data. A second transmitter, coupled to the second link interface, is to transmit the read data. A third receiver, coupled to the second link interface, is to receive the write data. A fifth encoder, coupled to an output from the third receiver, is to dynamically add the fourth error-detection information to at least the portion of the write data. A third transmitter is coupled to the second link interface, and is selectively coupled to one of an output from the fourth encoder and an output from the fifth encoder.
The read data may be re-transmitted using the second transmitter and the second link interface if the device receives remedial action instructions from the controller. The write data may be re-received using the third receiver and the second link interface if the device receives remedial action instructions from the controller.
The device may include a sixth encoder, coupled to an output from the third receiver, to dynamically add sixth error-detection information to at least the portion of the write mask information. The second link interface is to couple to the third link to receive the unidirectional command information. A fourth receiver, coupled to the second link interface, is to receive the fifth error-detection information. Second error-detection logic, coupled to an output from the fourth receiver and an output from the sixth encoder, is to determine errors in at least the portion of the write mask information by comparing the fifth error-detection information and the sixth error-detection information. If an error is detected, the second error-detection logic is to disable a write operation to the memory core.
In another embodiment, a system is described. In some embodiments, the system may be a memory system. The system includes the controller and at least the device. The first link interface in the controller is coupled to the first link and the second link. The second link interface in the device is coupled to the first link and the second link. In some embodiments, the first link interface in the controller and the second link interface in the device may each be coupled to the third link.
In another embodiment, a process for operating a controller is described. The first error-detection information is dynamically added to at least the portion of the write data. The write data is transmitted. The fourth error-detection information corresponding to at least the portion of the write data is received. The fourth error-detection information is compared to a delayed version of the first error-detection information to determine errors in at least the portion of the write data. If an error is detected, an error condition is asserted.
In another embodiment, a process for operating a controller is described. The read data is received. The second error-detection information is dynamically added to at least the portion of the read data. The third error-detection information corresponding to at least the portion of the read data is received. The second error-detection information is compared to the third error-detection information to determine errors in at least the portion of the read data. If an error is detected, an error condition is asserted.
In another embodiment, a process for operating a device is described. The write mask information is received. The sixth error-detection information is dynamically added to at least the portion of the write mask information. The fifth error-detection information corresponding to at least the portion of the write mask information is received. The fifth error-detection information and the sixth error-detection information are compared to determine errors in at least the portion of the write mask information. If an error is detected, a write operation to the memory core is disabled.
In some embodiments, dynamically adding error-detection information may include generating and/or incorporating pre-existing error-detection code information and/or error correction code information (such as a Bose-Chaudhuri-Hochquenghem code) into at least a portion of the transmit data (such as in one or more write data packets and/or one or more read data packets) and/or at least a portion of the write mask information. In some embodiments, the generated error-detection code information is only used locally, i.e., it is not transmitted with the write data and/or the write mask information. In some embodiments, the dynamic adding of respective error-detection code information may include generating and/or incorporating pre-existing error-detection code information or error correction code information into at least a portion of command information, such as commands or address information. In some embodiments, the error-detection code information (such as one or more parity bits or parity codes) and/or error correction code information may be generated in real time in accordance with at least a portion of the transmit data, the write mask information and/or the command information. Such dynamically generated error-detection code information and/or error correction code information may then be used locally and/or incorporated into the transmit data, the write mask information and/or the command information.
In some embodiments, the controller and/or the device may include instructions for and/or may perform one or more additional actions during a respective retry remedial action. The one or more additional actions may be mediated by retry information transmitted from the controller to the device and/or from the device to the controller. The instructions for and/or the performance of the one or more additional actions may include re-transmitting write data, read data, command information and/or write mask information with at least a portion of the re-transmitted write data, read data, command information and/or write mask information having error protection provided by an error correction code that is dynamically generated. The instructions for and/or the performance of the one or more additional actions may include re-transmitting write data, read data, command information and/or write mask information with improved bit error rate (BER). For example, re-transmission may use a circuit having a power greater than that used in a previous transmission for improved transmit characteristics; re-transmission may clock the respective data or information with one symbol per clock cycle (as opposed to transmitting on both rising and falling clock edges or transmitting multiple symbols per clock cycle); re-transmission may use a data or information rate that is less than that used in the previous transmission by adjusting, for example, a clock generator; re-transmission may use a data or information stream having blanks inserted before and/or after the respective data or information in order to have an intersymbol interference that is less than that in the previous transmission; re-transmission may use a different modulation code than that used in the previous transmission by adjusting, for example, a modulator; re-transmission may use a voltage swing that is greater than that used in the previous transmission by adjusting, for example, a voltage generator; re-transmission may use a number of pins that are coupled to one or more of the links (such as the first link, the second link and/or the third link) that is less than the number of pins coupled to one or more of the links in the previous transmission; re-transmission may occur after a predetermined idle time (such as 1, 2 or several clock cycles, or 1, 2 or 3 symbol periods, where a symbol period is an amount of time associated with communication of a symbol of write data or read data); and/or re-transmission may use another transmitter and/or receiver in the controller and/or in the device.
While some embodiments include separate first and second links (i.e., side band communication) to communicate the bi-directional data and the unidirectional error-detection information between the controller and the device, in other embodiments the bi-directional data and the unidirectional error-detection information may be communicated using a common link (i.e., in-band signaling). Such in-band signaling may utilize a technique including time division multiplexing, frequency division multiplexing and/or spread-spectrum signaling.
In some embodiments, the first link, the second link and/or the third link may include one or more pins, one or more lines or wires, one or more pairs of wires, one or more reference or back planes, one or more interconnects, one or more interfaces and/or one or more communications channels. The links may be used for inter-chip communication, such as between one or more semiconductor chips or dies, or for communication within a semiconductor chip, also known as intra-chip communication, such as between modules in an integrated circuit.
In some embodiments, the controller and/or the device may include control logic. The control logic may delay subsequent write operations to the device until the retry remedial action is completed, may delay command operations to a location in the device corresponding to the write or read data until the retry remedial action is completed, or may reorder receive data after the retry remedial action is completed in order to restore the read data received from the device during remedial action to a position corresponding to an original sequence of command operations.
The controller may also include a buffer. The buffer may be used to avoid data hazards. The write data to be transmitted to the device may be temporarily stored in the buffer and, if a read to a location in the device corresponding to the write data occurs during the retry remedial action, the write data may be obtained from the buffer.
By incorporating the error detection, error correction and/or retry modes of operation in the controller, the device or systems including at least one controller and at least one device, the embodiments allow occasional interconnect- or communications-channel-induced bit errors and thereby may allow a reduction in the BER requirements of the interconnect. Such an additional degree of freedom may enable interconnects having increased bandwidth at lower cost and with less complexity.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the subject matter presented herein. However, it will be apparent to one of ordinary skill in the art that the subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
Attention is now directed towards embodiments that address the difficulties associated with the existing memory systems described above. These embodiments may be utilized in one or more controllers, one or more devices and/or one or more systems. In some embodiments, the one or more controllers may be memory controllers, the one or more devices may be memory devices and/or the one or more systems may be memory systems.
FIG. 1 is a block diagram illustrating an embodiment of a system 200. The system 200 includes at least one controller 210 and one or more devices 218. While FIG. 1 illustrates the system 200 having one controller 210 and three devices 218, other embodiments may have additional controllers and fewer or more devices 218. The controller 210 has control logic 212 and each device 218 has control logic 220. In other embodiments, some of the devices 218 may not have the control logic 220. In embodiments where the devices 218 are memory devices, two or more of the devices, such as devices 218-1 and 218-2, may be configured as a memory bank 216.
The controller 210 and the devices 218 are connected by one or more links 214. While the system 200 illustrates three links 214, other embodiments may have fewer or more links 214. The links 214 may be used for bi-directional and/or uni-directional communications between the controller 210 and one or more of the devices 218. Bi-directional communication may be simultaneous. In some embodiments, one or more of the links 214 and the corresponding transmitters, such as transmitters 312 (FIG. 2A), and/or receivers, such as receivers 322 (FIG. 2A), may be dynamically configured, for example, by control logic 212, for bi-directional and/or unidirectional communication.
Data may be communicated on one or more of the links 214 using one or more sub-channels, such as a baseband sub-channel corresponding to a first frequency band and/or a passband sub-channel corresponding to a second frequency band. In some embodiments, such as those where at least one of the links 214 is ac-coupled, the baseband sub-channel may not contain DC (i.e., does not include 0 Hz). In some embodiments, the first frequency band and the second frequency band may be orthogonal. In other embodiments there may be substantial overlap of one or more neighboring pairs of frequency bands. A respective sub-channel may also correspond to a group of frequency bands.
The control logic 212 in the system 200 may be configured to dynamically allocate and/or adjust one or more frequency bands, such as the first frequency band and/or the second frequency band, based on a predetermined data rate, for example, multiple gigabits per second (“Gbits/s” or “Gbps”), between the controller 210 and at least one of the devices 218 and/or the predetermined data rate between at least one of the devices 218 and the controller 210. The control logic 212 may dynamically allocate and/or adjust one or more frequency bands in at least one link 214 by adjusting at least one corresponding transmitter, such as one of the transmitters 312 (FIG. 2A), and at least one corresponding receiver, such as one of the receivers 322 (FIG. 2B). In this example, adjustments to at least one of the transmitters 312 (FIG. 2A) and/or at least one of the receivers 322 (FIG. 2B) may be communicated from the controller 210 to at least one of the devices 218 using at least one of the links 214.
While the embodiment 200 couples the controller 210 to multiple devices 218, in other embodiments two or more controllers may be coupled to one another. The coupled controllers may utilize the unidirectional transfer of error code information described below.
The challenges associated with the existing systems may be at least partially addressed by encoding error detection codes or information on both sides of a link, for example, in a controller and in one or more devices. Two versions of the error-detection information, one generated in the controller and another generated in one or more devices, may be compared in the controller. If errors are detected, an error condition may be asserted and corresponding remedial action, such as re-transmitted write and/or read data, may be taken. The error-detection information may be communicated between the device and the controller using in-band signaling or sideband communication. As described further below with reference to FIG. 4, this approach may reduce an overall latency.
FIG. 2A is a block diagram illustrating an embodiment 300 of a controller 308 incorporating unidirectional error code information transfer. Write data 112 may be synchronized using a flip-flop 310-1 (which is gated by a clock signal that is not shown) and transmitted using transmitter 312-1 on bi-directional data link 326. The write data 112 may also be encoded using encoder 314-1 to generate first write-data error-detection information. An embodiment of an encoder, such as the encoder 314-1 is described further below with reference to FIG. 6. The first write-data error-detection information may be delayed by delay element 316-1 and coupled to error-detection logic 318-1. The delay element 316-1 may compensate for a round-trip delay discussed further below.
Referring to FIG. 2B, which illustrates an embodiment 350 of a device 352, the write data 112 may be received by a receiver 322-3 and synchronized using a flip-flop 310-5 (which is gated by a clock signal that is not shown). The received write data 112 may be coupled to an encoder 314-3 to generate second write-data error-detection information. The second write-data error-detection information may be synchronized using a flip-flop 310-6 and selectively coupled to subsequent components using multiplexer 354. An output from the multiplexer 354 may be synchronized using a flip-flop 310-7 and transmitted on unidirectional error code link 324 using transmitter 312-2.
Referring back to FIG. 2A, the second write-data error-detection information may be received by the controller 308 using receiver 322-1. The second write-data error-detection information may be synchronized using a flip-flop 310-2 and coupled to the error-detection logic 318-1. The error-detection logic 318-1 may compare the first write-data error-detection information and the second write-data error-detection information to determine if the write data 112 was received by the device 352 without error. For example, the error detection logic 318-1 may detect an error using a multi-bit XOR operation in conjunction with one or more parity bits associated with the write data 112. If an error is detected, the error-detection logic 318-1 may assert an error condition 320-1. Retry logic 328 may perform remedial action if the error condition 320-1 is asserted. The remedial action may include re-transmitting the write data 112 to the device 352.
Referring back to FIG. 2B, a similar procedure may be utilized for read data 122. The read data 122 may be synchronized using a flip-flop 310-9 and transmitted using transmitter 312-3 on the bi-directional data link 326. The read data 122 may also be encoded using encoder 314-4 to generate first read-data error-detection information. The first read-data error-detection information may be synchronized using a flip-flop 310-8 and selectively coupled to subsequent components using the multiplexer 354. An output from the multiplexer 354 may be synchronized using the flip-flop 310-7 and transmitted on the unidirectional error code link 324 using the transmitter 312-2.
Referring to FIG. 2A, the read data 122 may be received by a receiver 322-2 and synchronized using the flip-flop 310-3. The received read data 122 may be coupled to an encoder 314-2 to generate second read-data error-detection information. The second read-data error-detection information may be synchronized by a flip-flop 310-4 and coupled to error-detection logic 318-2. The controller 308 may also receive the first read-data error-detection information using the receiver 322-1. The first read-data error-detection information may be synchronized using the flip-flop 310-2 and coupled to the error-detection logic 318-2. The error-detection logic 318-2 may compare the first read-data error-detection information and the second read-data error-detection information to determine if the read data 122 was received by the controller 308 without error. If an error is detected, the error-detection logic 318-2 may assert an error condition 320-2. The retry logic 328 may perform remedial action if the error condition 320-2 is asserted. The remedial action may include transmitting retry information to the device 352 (using a command link that is not shown) such that the read data 122 may be re-transmitted to the controller 308.
In some embodiments, at least one of the transmitters 312 may perform parallel-to-serial conversion. In some embodiments, at least one of the receivers 322 may perform serial-to-parallel conversion. While the retry logic 328 is incorporated in the controller 308 in the embodiment 300, in other embodiments the retry logic 328 may be a separate component. The retry logic 328 may include hardware, such as logic gates to detect and/or interpret the respective error condition, and/or software, including instructions corresponding to the retry remedial action. Providing retry logic that can initiate retry remedial actions enables a system to use transmit and receive data rates greater than a first threshold while maintaining an error rate lower than a second threshold. In some embodiments the first threshold may be on the order of approximately 1 Gbps, 2 Gbps, 5 Gbps or 10 Gbps. In an exemplary embodiment, the second threshold is 10−20 with error condition detection and retry. If error detection and retry are not used, the second threshold may be 10−10.
In an exemplary embodiment, the flip-flops 310 have a one clock cycle delay. The delay element 316-1 has a delay of five clock cycles. A bandwidth used in the error code link 324 may be much less than a bandwidth used in the data link 326.
While not shown, the controller 308 may include one or more modulators, one or more de-modulators, one or more voltage generators and at least one clock generator. The one or more voltage generators may generate one or more voltage signals that set signal levels of one or more of the transmitters 312 and/or the receivers 322. The clock generator may generate one or more clock signals that control timing of transmitting and receiving of data by one or more of the transmitters 312 and/or the receivers 322 using one or more of the flip-flops 310. The one or more modulators and/or the one or more de-modulators may implement bit-to-symbol coding and symbol-to-bit coding, respectively. Suitable symbol coding may include two or more level pulse amplitude modulation (PAM), such as two-level pulse amplitude modulation (2PAM), four-level pulse amplitude modulation (4PAM), eight-level pulse amplitude modulation (SPAM), sixteen-level pulse amplitude modulation (16PAM) or a higher level pulse amplitude modulation. In embodiments with one or more passband sub-channels, multi-level PAM is also referred to as multi-level on-off keying (OOK), such as two-level on-off keying (2OOK), four-level on-off keying (4OOK), eight-level on-off keying (8OOK) or a higher level on-off keying. Suitable coding in one or more passband sub-channels may also include two or more level quadrature amplitude modulation (QAM).
The controller 308 (FIG. 2A) and the device 352 (FIG. 2B) may have fewer or more components. Functions of two or more components (as described above) may be implemented in a single component. Alternatively, functions of some components may be implemented in additional instances of the components. While the embodiments 300 (FIG. 2A) and 350 (FIG. 2B) illustrate one transmitter 312 and two receivers 322, and two transmitters 312 and one receiver 322, respectively, there may be fewer or more of these components. While the data link 326 has been illustrated as bi-directional, as noted previously this may include simultaneous bi-directional communication, reconfiguration for unidirectional communication, as well as dynamic configuration of the data link 326.
FIG. 3 is a diagram illustrating a data stream on the data link 326 and an error code stream on the error code link 324 in an embodiment of a system 400 corresponding to the embodiments 300 (FIG. 2A) and 350 (FIG. 2B). The system 400 illustrates a read-write (RW) bubble 412 and a write-read (WR) bubble 418. While the system 400 illustrates single rate clocking, in other embodiments dual data rate clocking (i.e., clocking on rising and falling edges of clock 410) or other data rates with multiple symbols per clock cycle may be used. While there is a larger write data to error code delay 414 in the approach utilized in embodiments 300 (FIG. 2A) and 350 (FIG. 2B), the overall latency is reduced. By delaying the read error code information relative to the read data, as illustrated by read data to error code delay 416, a single encode delay may be utilized, thereby allowing read data to be returned more quickly.
As mentioned previously, while embodiments 300 (FIG. 2A) and 350 (FIG. 2B) illustrate an approach using sideband communication, via the error code link 324, in other embodiments in-band signaling may be utilized. This is illustrated in FIGS. 4A and 4B.
FIG. 4A is a block diagram illustrating an embodiment 500 of a controller 510 incorporating unidirectional error code information transfer. The write data 112 may be synchronized using a flip-flop 512-1 (which is gated by a clock signal that is not shown) and transmitted using transmitter 514-1 on bi-directional data and unidirectional error-code link 528. The write data 112 may also be encoded using encoder 516-1 and flip-flop 512-2 to generate first write-read error-detection information. The feedback loop may allow encoding of a group of write data 112 symbols or data packets. The first write-read error-detection information may be delayed by delay element 518-1 (to compensate for a delay in receiving a burst of read data 122 discussed further below) and coupled to a multiplexer 520-1. The multiplexer may selectively couple the first write-read error-detection information or a feedback loop to an encoder 516-2 (the feedback loop may allow encoding of a group of write data 112 symbols or data packets along with a group of read data 122 symbols or data packets). The encoder 516-2 may also have read data 122 as an input. The encoder 516-2 may generate second write-read error-detection information. An output from the encoder 516-2 may be synchronized using flip-flop 512-3 and may be coupled to error-detection logic 522.
Referring to FIG. 4B, which illustrates an embodiment 550 of a device 552, the write data 112 may be received by a receiver 526-2 and synchronized using a flip-flop 512-6 (which is gated by a clock signal that is not shown). The received write data 112 may be encoded using encoder 516-3 and flip-flop 512-7 to generate third write-read error-detection information. The feedback loop may allow encoding of a group of received write data 112 symbols or data packets. The third write-read error-detection information may be delayed by delay element 518-2 (to compensate for a delay in receiving a burst of read data 122) and coupled to a multiplexer 520-2. The multiplexer may selectively couple the third write-read error-detection information or a feedback loop to an encoder 516-4 (the feedback loop may allow encoding of a group of received write data 112 symbols or data packets along with a group of read data 122 symbols or data packets). The encoder 516-4 may also have read data 122 as an input. The encoder 516-4 may generate fourth write-read error-detection information. An output from the encoder 516-4 may be synchronized using flip-flop 512-8 and coupled to multiplexer 520-3. The multiplexer 520-3 may selectively couple the fourth write-read error-detection information or the read data 122 to a flip-flop 512-9 (for synchronization) and to a transmitter 514-2. The transmitter 514-2 may transmit the read data 122 and/or the fourth write-read error-detection information on the data and error-code link 528.
Referring back to FIG. 4A, the read data 122 and/or the fourth write-read error-detection information may be received by the controller 510 using receiver 526-1. The fourth write-read error-detection information and/or the read data 122 may be synchronized using a flip-flop 512-5. As mentioned previously, the read data 122 may be coupled to the encoder 516-2. The fourth write-read error-detection information may be coupled to the error-detection logic 522. The error-detection logic 522 may compare the second write-read error-detection information and the fourth write-read error-detection information to determine if the write data 112 was received by the device 552 without error and if the read data 122 was received by the controller 510 without error. For example, the error detection logic 522 may detect an error using a multi-bit XOR operation in conjunction with one or more parity bits associated with the write data 112 and the read data 122. If an error is detected, the error-detection logic 522 may assert an error condition 524. Retry logic 530 may perform remedial action if the error condition 524 is asserted. The remedial action may include re-transmitting the write data 112 to the device 552 and re-transmitting the read data to the controller 510. The remedial action may include transmitting retry information to the device 552 (using a command link that is not shown) such that the read data 122 may be re-transmitted to the controller 510.
In some embodiments, at least one of the transmitters 514 may perform parallel-to-serial conversion. In some embodiments, at least one of the receivers 526 may perform serial-to-parallel conversion. While the retry logic 530 is incorporated in the controller 510 in the embodiment 500, in other embodiments the retry logic 530 may be a separate component. The retry logic 530 may include hardware, such as logic gates to detect and/or interpret the respective error condition, and/or software, including instructions corresponding to the retry remedial action. The retry remedial action may enables transmit and receive data rates greater than the first threshold with an error rate lower than the second threshold. In some embodiments the first threshold may be on the order of approximately 1 Gbps, 2 Gbps, 5 Gbps or 10 Gbps. In an exemplary embodiment, the second threshold is 10−20 with error condition detection and retry. If error detection and retry are not used, the second threshold may be 10−10.
In an exemplary embodiment, the flip-flops 512 have a one clock cycle delay. The delay elements 518 may delay the most recent encoded write data 112 until the next burst of read data 122 is received. If a read burst is not received within a pre-determined time interval, the controller 510 may instruct the device 552 to provide the fourth write-read error detection information directly without waiting for the read burst using a command transmitted on the command link (not shown). Time division multiplexing may be utilized on the data and error-code link 528 to interleave the write data 112, the read data 122 and the fourth write-read error-detection information. The encoders 516 may generate error-detection information for four data packets of write data 112 and four data packets of read data 122 which are coded as a group. Each data packet may include thirty-two bits of data. The data and error-code link 528 may include sixteen parallel signal lines. The encoders 516 may, at least in part, implement a vertical/horizontal parity code in conjunction with a cyclic redundancy code (CRC). In other embodiments, the encoders 516 may implement a CRC code, a parity code, a Hamming code, a Reed-Solomon code, and/or another error checking and correction code.
While not shown, the controller 510 may include one or more modulators, one or more de-modulators, one or more voltage generators and at least one clock generator. The one or more voltage generators may generates one or more voltage signals that set signal levels of one or more of the transmitters 514 and/or the receivers 526. The clock generator may generate one or more clock signals that control timing of transmitting and receiving of data by one or more of the transmitters 514 and/or the receivers 526 using one or more of the flip-flops 512. The one or more modulators and/or the one or more de-modulators may implement bit-to-symbol coding and symbol-to-bit coding, respectively. Suitable symbol coding may include two or more level pulse amplitude modulation (PAM), such as two-level pulse amplitude modulation (2PAM), four-level pulse amplitude modulation (4PAM), eight-level pulse amplitude modulation (SPAM), sixteen-level pulse amplitude modulation (16PAM) or a higher level pulse amplitude modulation. In embodiments with one or more passband sub-channels, multi-level PAM is also referred to as multi-level on-off keying (OOK), such as two-level on-off keying (2OOK), four-level on-off keying (4OOK), eight-level on-off keying (8OOK) or a higher level on-off keying. Suitable coding in one or more passband sub-channels may also include two or more level quadrature amplitude modulation (QAM).
The controller 510 and the device 552 (FIG. 4B) may have fewer or more components. Functions of two or more components (as described above) may be implemented in a single component. Alternatively, functions of some components may be implemented in additional instances of the components. While the embodiments 500 and 550 (FIG. 4B) illustrate one transmitter 514 and one receiver 526 there may be fewer or more of these components. While the data and error-code link 528 has been illustrated as bi-directional for data and unidirectional for error-code information, as noted previously this may include simultaneous bi-directional communication, reconfiguration for unidirectional communication, as well as dynamic configuration of the data and error-code link 528.
FIG. 5 is a diagram illustrating a data stream 612 and a command stream 610 in an embodiment of a system 600 corresponding to the embodiments 500 (FIG. 4A) and 550 (FIG. 4B). While the system 600 illustrates single rate clocking, in other embodiments dual data rate clocking (i.e., clocking on rising and falling edges of the clock 410) or other data rates with multiple symbols per clock cycle may be used. In the system 600, read and write data are separated by read-write (RW) bubble 412 and write-read bubble (WR) 614. In the encoders 516, NW cycles 616 of write data 112 and NR cycles 618 of read data 122 are concatenated and encoded. The resulting write-read error-detection information (SD) is transmitted during cycle 620. Cycle 620 may coincide with a synchronization command (S) sent by the controller 510 (FIG. 4A) at the end of a read command sequence. As described previously, in an exemplary embodiment, the NW cycles 616 and the NR cycles 618 may number four.
FIG. 6 is a block diagram illustrating an embodiment 700 of generating error code bits, such as the write or read error-detection information in embodiments 300 (FIG. 2A) and 350 (FIG. 2B). Sixteen bit slices 708, each containing sixteen bits, are bit-wise summed to generate horizontal parity 710 and vertical parity 712, respectively. The input data may include two-hundred fifty-six bits of write data 112 or two-hundred fifty-six bits of read data 122. The input bits in embodiment 700 are intended as an illustration. Other embodiments may use a different number of bits and/or a different number of bit slices.
The horizontal parity is encoded using a CRC coder 714-1 and the vertical parity is encoded using a CRC coder 714-2. In an exemplary embodiment, each of the CRC coders 714 may implement six-bit encoding using six XOR gates each having sixteen inputs. The CRC coders 714 may output write or read error-detection information or error check (ECHK) bits 716, which are also referred to as check codes. In an exemplary embodiment, each CRC coder 714 may output six bits for a given set of input data, such as horizontal or vertical input bits. An additional four blank bits may also be included. Note that in general a CRC encoder with a k-bit check code can cover up to 2k−1−k−1 input data bits. The check code (k bits) and the data bits (up to 2k−1−k−1 bits) together are called a code word. Any one-bit, two-bit or three-bit errors and any burst errors with length at most k in a code word can be detected by the CRC code. The CRC coder 714 may use the polynomial

X6+X5+X3+X2+X+1

as a generation polynomial. The horizontal and vertical parity bits may be multiplied with a generation matrix corresponding to the generation polynomial to generate the check codes.

A further approach addresses the issue of write masking when a bidirectional data link, such as the data link 326 (FIG. 2A), couples a memory controller and a memory device. Write mask information permits individual bytes of write data 112 to be written or not-written into a respective column address location. Such write mask information may be transferred between a controller, such as the controller 308 (FIG. 2A), and a device, such as the device 352 (FIG. 2B), using sideband communication or in-band signaling. In embodiments with a sideband link, there may be 1⁄8 fewer signal lines than in the data link. In in-band signaling, the write mask information may be communicated on the data link. A write key technique may be used or bandwidth in the data link may be allocated explicitly for the write mask information. In these embodiments, the data rate of the write mask information may be the same as that used for the write data.
Whether write mask information is communicated using sideband communication or in-band signaling, it may be susceptible to errors during communication on a link. The remedial action and retry instructions described previously may not, however, adequately address errors in the write mask information. This is because an error in the write mask information may result in erroneous overwriting of a byte location that is not supposed to be overwritten. In the case of an error in the received write data 112, the bad data in the device, such as the device 352 (FIG. 2B), is only a copy. The original write data 112 is in the controller, such as the controller 308 (FIG. 2A), and may be re-transmitted. In the case of some errors in the write mask information, however, the only copy of data at a byte location that is not to be written resides at that byte location in the device. There is no copy in the controller. As a consequence, an error in the write mask information could destroy the only copy of the data at that byte location.
FIGS. 7A and 7B illustrate embodiments of a solution to this challenge. FIG. 7A is a block diagram illustrating an embodiment 800 of a controller 810. The controller 810 may be a memory controller. A data stream containing write data 812 and write mask information is coupled to an encoder 314-5. The encoder receives the write mask information and generates first write-mask error-detection information. The first write-mask error-detection information is synchronized using a flip-flop 310-10 and is coupled to a transmitter 312-4. Address and command information 814 is synchronized using a flip-flop 310-12 and is also coupled to the transmitter 312-4. The transmitter 312-4 transmits the address and command information 814 and the first write-mask error-detection information on a request link 818. The request link 818 may operate at a lower data rate that the data link 326. Such as lower data rate may reduce a probability of an error during the communication of the first write-mask error-detection information. The write mask information 816 may also be synchronized using flip-flop 310-1 and coupled to the transmitter 312-1. The transmitter transmits the write data 812 and the write mask information 816 on the data link 326.
FIG. 7B illustrates an embodiment 850 of a device 852, which may be a memory device. The write mask information 816 may be received by receiver 322-3. The write mask information 816 may synchronized using a flip flop 310-5. The write mask information 816 may be encoded using encoder 314-6 to generate second write-mask error-detection information. The second write-mask error-detection information may be coupled to error detection logic 318-3.
The first write-mask error-detection information may be received via the request link 818 using receiver 322-4. The first write-mask error-detection information may be synchronized using flip-flop 310-11 and coupled to the error-detection logic 318-3. The error-detection logic 318-3 may compare the first write-mask error-detection information and the second write-mask error-detection information to determine if the write mask information 816 has been received without an error. If no error has occurred, the write operation is allowed to proceed. If an error has occurred, the error-detection logic 318-3 may output signals that disables a write operation 856 to a memory core, thereby prevent an accidental erasure of the data at the corresponding column address location. The device 852 may transmit retry instructions to the controller 810 (FIG. 7A), for example, using a retry link (not shown). The retry instructions may request that the write mask information 816 and/or the corresponding write data 812 be re-transmitted. The retry instructions may be processed by retry logic 820 (FIG. 7A).
The approach described in embodiments 800 (FIG. 7A) and 850 may be utilized if there is sufficient space and/or bandwidth on the request link 818. This is often the case since a row address in the address and command information 814 is typically larger in size than a corresponding column address. If there are multiple devices 852, such as multiple DRAM chips, however, there may not be sufficient communications capacity on the request link 818. In such a circumstance, a separate link may be included for the write-mask error-detection information. Alternatively, different error-detection codes may be utilized for different groups of one or more devices 852 coupled to a common request link 818.
Attention is now directed towards processes for operating controllers, devices and/or systems. FIG. 8 is a flow diagram illustrating a method of operation of an embodiment 900 of a system. First write-data error-detection information is dynamically added to at least a portion of write data (910). Dynamically adding error-detection information may include generating (for example, in real time) and appending error-detection information. The write data is transmitted (912). Second write-data error-detection information corresponding to at least the portion of the write data is received (914). The second write-data error-detection information and a delayed version of the first write-data error-detection information are compared to determine errors in at least the portion of the write data (916). An error condition is asserted if an error is detected (918). In some embodiments, there may be fewer or additional operations, an order of the operations may be rearranged and/or two or more operations may be combined.
FIG. 9 is a flow diagram illustrating a method of operation of an embodiment 1000 of a system. Read data is received (1010). First read-data error-detection information is dynamically added to at least a portion of the read data (1012). Second read-data error-detection information corresponding to at least the portion of the read data is received (1014). The first read-data error-detection information and the second read-data error-detection information are compared to determine errors in at least the portion of the read data (1016). An error condition is asserted if an error is detected (1018). In some embodiments, there may be fewer or additional operations, an order of the operations may be rearranged and/or two or more operations may be combined.
FIG. 10 is a flow diagram illustrating a method of operation of an embodiment 1100 of a system. Write mask information is received (1110). First write-mask error-detection information is dynamically added to at least a portion of the write mask information (1112). Second write-mask error-detection information corresponding to at least the portion of the write mask information is received (1114). The first write-mask error-detection information and the second write-mask error-detection information are compared to determine errors in at least the portion of the write mask information (1116). A write operation to a memory core is disabled if an error is detected (1118). In some embodiments, there may be fewer or additional operations, an order of the operations may be rearranged and/or two or more operations may be combined.
The unidirectional transfer of error-detection information and related methods of operation are well-suited for use in improving communication in systems and devices. They are also well-suited for use in improving communication between a memory controller chip and a DRAM chip. The DRAM chip may be either on the same printed circuit board as the controller or embedded in a memory module. The apparatus and methods described herein may also be applied to other memory technologies, such as static random access memory (SRAM) and electrically erasable programmable read-only memory (EEPROM).
Devices and circuits described herein can be implemented using computer aided design tools available in the art, and embodied by computer readable files containing software descriptions of such circuits, at behavioral, register transfer, logic component, transistor and layout geometry level descriptions stored on storage media or communicated by carrier waves. Data formats in which such descriptions can be implemented include, but are not limited to, formats supporting behavioral languages like C, formats supporting register transfer level RTL languages like Verilog and VHDL, and formats supporting geometry description languages like GDSII, GDSIII, GDSIV, CIF, MEBES and other suitable formats and languages. Data transfers of such files on machine readable media including carrier waves can be done electronically over the diverse media on the Internet or through email, for example. Physical files can be implemented on machine readable media such as 4 mm magnetic tape, 8 mm magnetic tape, 31⁄2 inch floppy media, CDs, DVDs and so on.
FIG. 11 is a block diagram an embodiment of a system 1200 for storing computer readable files containing software descriptions of the circuits. The system 1200 may include at least one data processor or central processing unit (CPU) 1210, a memory 1214 and one or more signal lines 1212 for coupling these components to one another. The one or more signal lines 1212 may constitute one or more communications busses.
The memory 1214 may include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices. The memory 1214 may store a circuit compiler 1216 and circuit descriptions 1218. The circuit descriptions 1218 may include circuit descriptions for transmit and receive circuits 1220, one or more synchronization circuits 1222 (such as flip-flops), one or more multiplexers 1224, one or more encoders 1226, one or more delay circuits 1228, one or more error-detection logic circuits 1230, one or more memory cores 1232, one or more controller circuits 1234 and/or one or more retry logic circuits 1236.
Attention is now directed towards additional embodiments of unidirectional error-code transfer. In some embodiments, a controller includes a link interface, a first encoder, a first transmitter, a first delay element coupled to an output from the first encoder, a first receiver coupled to the link interface, a second encoder coupled to an output from the first receiver, a second receiver coupled to the link interface, and error-detection logic coupled to an output from the first delay element, an output from the second encoder and an output from the second receiver. The link interface is to couple to a first link to communicate bi-directional data and a second link to transmit unidirectional error-detection information. The first encoder is to dynamically add first error-detection information to at least a portion of write data. The first transmitter is to transmit the write data. The first receiver is to receive read data. The second encoder is to dynamically add second error-detection information to at least a portion of the read data. The second receiver is to receive third error-detection information corresponding to at least the portion of the read data and fourth error-detection information corresponding to at least the portion of the write data. The error-detection logic is to determine errors in at least the portion of the write data by comparing the first error-detection information and the fourth error-detection information, and is to determine errors in at least the portion of the read data by comparing the second error-detection information and the third error-detection information, and, if an error is detected, is to assert an error condition.
The controller may include retry logic to perform a retry remedial action if the error condition is asserted. In some embodiments, the retry remedial action includes re-transmitting the write data using the first transmitter and the link interface. In some embodiments, the retry remedial action includes re-receiving the read data using the first receiver and the link interface after the read data is re-transmitted by a device.
The controller may include a third encoder to dynamically add fifth error-detection information to at least a portion of write mask information and a second transmitter coupled to an output from the third encoder and to the link interface. The link interface may couple to a third link to transmit unidirectional command information including the fifth error-detection information. The link interface may couple to the first link to communicate the write mask information.
In another embodiment, a device includes a link interface, a first encoder, a first transmitter is coupled to the link interface, a first receiver coupled to the link interface, a second encoder coupled to an output from the first receiver, and a second transmitter coupled to the link interface, and selectively coupled to one of an output from the first encoder and an output from the second encoder. The link interface is to couple to a first link to communicate bi-directional data and a second link to receive unidirectional error-detection information. The first encoder is to dynamically add first error-detection information to at least a portion of read data. A first transmitter is to transmit the read data. The first receiver is to receive write data. The second encoder is to dynamically add second error-detection information to at least a portion of the write data.
The read data may be re-transmitted using the first transmitter and the link interface if the device receives remedial action instructions from a controller.
The write data may be re-received using the first receiver and the link interface if the device receives remedial action instructions from a controller.
The device may include a third encoder coupled to an output from the first receiver, a second receiver coupled to the link interface, and error-detection logic coupled to an output from the second receiver and an output from the third encoder. The third encoder is to dynamically add third error-detection information to at least a portion of write mask information. The link interface is to couple to a third link to receive unidirectional command information including fourth error-detection information. The error-detection logic is to determine errors in at least the portion of the write mask information by comparing the third error-detection information and the fifth error-detection information, and, if an error is detected, is to disable a write operation to a memory core.
In other embodiments, a system includes a first link to communicate bi-directional data, a second link to communicate unidirectional error-detection information, a controller, and a device. The controller includes a first link interface coupled to the first link and the second link, a first encoder to dynamically add first error-detection information to at least a portion of write data, a first transmitter coupled to the first link interface, a first delay element coupled to an output from the first encoder, a first receiver coupled to the first link interface, a second encoder coupled to an output from the first receiver, a second receiver coupled to the first link interface, and first error-detection logic coupled to an output from the first delay element, an output from the second encoder and an output from the second receiver. The first transmitter is to transmit the write data. The first receiver is to receive read data. The second encoder is to dynamically add second error-detection information to at least a portion of the read data. The second receiver is to receive third error-detection information corresponding to at least the portion of the read data and fourth error-detection information corresponding to at least the portion of the write data. The first error-detection logic is to determine errors in at least the portion of the write data by comparing the first error-detection information and the fourth error-detection information, and is to determine errors in at least the portion of the read data by comparing the second error-detection information and the third error-detection information, and, if an error is detected, is to assert an error condition. The device includes a second link interface coupled to the first link and the second link, a third encoder to dynamically add the third error-detection information to at least a portion of the read data, a second transmitter coupled to the second link interface, a third receiver coupled to the second link interface, a fourth encoder coupled to an output from the third receiver, and a third transmitter coupled to the second link interface, and selectively coupled to one of an output from the third encoder and an output from the fourth encoder. The second transmitter is to transmit the read data. The third receiver is to receive the write data. The fourth encoder is to dynamically add the fourth error-detection information to at least a portion of the write data.
A retry remedial action may be performed if the error condition is asserted. In some embodiments, the retry remedial action includes instructions for re-transmitting the write data using the first transmitter and the link interface in the controller. In some embodiments, the retry remedial action includes instructions re-receiving the read data using the first receiver and the link interface in the controller after the read data is re-transmitted using the second transmitter and the second link interface in the device.
The system may include a third link to communicate unidirectional command information. The controller may include a fifth encoder to dynamically add fifth error-detection information to at least a portion of write mask information and a fourth transmitter coupled to an output from the third encoder and to the link interface. The first link interface is coupled to a third link to transmit unidirectional seventh error-detection information. The first link interface is coupled to the first link to communicate the write mask information. The device may include a sixth encoder coupled to an output from the third receiver, a fourth receiver coupled to the second link interface, and a second error-detection logic coupled to an output from the fourth receiver and an output from the fourth encoder. The sixth encoder is to dynamically add sixth error-detection information to at least a portion of the write mask information. The second link interface is coupled to the third link and the fourth receiver is to receive the fifth error-detection information. The second error-detection logic is to determine errors in at least the portion of the write mask information by comparing the fifth error-detection information and the sixth error-detection information, and, if an error is detected, is to disable a write operation to a memory core.
In another embodiment, a controller includes a link interface, an encoder to dynamically add first error-detection information to at least a portion of write data, a transmitter coupled to the link interface, a delay element coupled to an output from the encoder, a receiver coupled to the link interface, and error-detection logic coupled to an output from the delay element and an output from the receiver. The link interface is to couple to a first link to communicate bi-directional data and a second link to transmit unidirectional error-detection information. The transmitter is to transmit the write data. The receiver is to receive second error-detection information corresponding to at least the portion of the write data. The error-detection logic is to determine errors in at least the portion of the write data by comparing the first error-detection information and the second error-detection information, and, if an error is detected, is to assert an error condition.
In another embodiment, a controller includes a link interface, a first receiver coupled to the link interface, an encoder coupled to an output from the first receiver, a second receiver coupled to the link interface, and error-detection logic coupled to an output from the encoder and an output from the second receiver. The link interface is to couple to a first link to communicate bi-directional data and a second link to transmit unidirectional error-detection information. The first receiver is to receive read data. The encoder is to dynamically add first error-detection information to at least a portion of the read data. The second receiver is to receive second error-detection information corresponding to at least the portion of the read data. The error-detection logic is to determine errors in at least the portion of the read data by comparing the first error-detection information and the second error-detection information, and, if an error is detected, is to assert an error condition.
In another embodiments, a system includes a link to communicate bi-directional data and unidirectional error-detection information, a controller, and a device. The controller includes a first link interface, a first encoder to dynamically add first error-detection information to at least a portion of write data, a first transmitter coupled to the first link interface, a first delay element coupled to an output from the first encoder, a first receiver coupled to the link interface, a second encoder coupled to an output from the first receiver and selectively coupled to an output from the first delay element, and error-detection logic coupled to an output from the second encoder and an output from the first receiver. The first link interface is to couple to the link. The first transmitter is to transmit the write data. The first receiver is to receive read data and second error-detection information corresponding to at least a portion of the read data and at least the portion of the write data. The second encoder is to dynamically add third error-detection information to at least the portion of the read data and at least the portion of the write data. The error-detection logic is to determine errors in at least the portion of the write data and at least the portion of the read data by comparing the second error-detection information and the third error-detection information, and, if an error is detected, is to assert an error condition. The device includes a second link interface, a second receiver coupled to the second link interface, a third encoder to dynamically add fourth error-detection information to at least a portion of write data, a second delay element coupled to an output from the third encoder, a fourth encoder coupled to read data and selectively coupled to an output from the second delay element, and a second transmitter coupled to the second link interface, selectively coupled to the read data and selectively coupled to an output from the fourth encoder. The second link interface is to couple to the link. The receiver is to receive write data. The fourth encoder is to dynamically add the second error-detection information to at least the portion of the write data and at least a portion of the read data. The second transmitter is to transmit the read data and the second error-detection information.
In another embodiment, a device includes a link interface, a receiver coupled to the link interface, a first encoder to dynamically add first error-detection information to at least a portion of write data, a delay element coupled to an output from the first encoder, a second encoder coupled to read data and selectively coupled to an output from the delay element, and a first transmitter coupled to the link interface, selectively coupled to the read data and selectively coupled to an output from the second encoder. The link interface is to couple to a link to communicate bi-directional data and unidirectional error-detection information. The receiver is to receive write data. The second encoder is to dynamically add second error-detection information to at least the portion of the write data and at least a portion of the read data. The first transmitter is to transmit the read data and the second error-detection information.
In another embodiment, a controller includes a link interface, a first encoder to dynamically add first error-detection information to at least a portion of write data, a transmitter coupled to the link interface, a delay element coupled to an output from the first encoder, a receiver coupled to the link interface, a second encoder coupled to an output from the receiver and selectively coupled to an output from the delay element, and error-detection logic coupled to an output from the second encoder and an output from the receiver. The link interface is to couple to a link to communicate bi-directional data and unidirectional error-detection information. The transmitter is to transmit the write data. The first receiver is to receive read data and second error-detection information corresponding to at least a portion of the read data and at least the portion of the write data. The second encoder is to dynamically add third error-detection information to at least the portion of the read data and at least the portion of the write data. The error-detection logic is to determine errors in at least the portion of the write data and at least the portion of the read data by comparing the second error-detection information and the third error-detection information, and, if an error is detected, is to assert an error condition.
In another embodiment, a device includes a link interface, a first receiver coupled to the link interface, an encoder to dynamically add first error-detection information to at least a portion of the write mask information, a second receiver coupled to the link interface, and error-detection logic coupled to an output from the second receiver and an output from the encoder. The link interface is to couple to a first link to communicate write mask information and a second link to receive unidirectional error-detection information. The first receiver is to receive the write mask information. The second receiver is to receive second error-detection information. The error-detection logic is to determine errors in at least the portion of the write mask information by comparing the first error-detection information and the second error-detection information received by the second receiver, and, if an error is detected, is to disable a write operation to a memory core.
The foregoing descriptions of specific embodiments of the present invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Rather, it should be appreciated that many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.

## Claims

1. A solid state memory device comprising:
a link interface configurable to transfer bidirectional signals in a first configuration, and to transfer unidirectional signals in a second configuration, wherein the link interface includes:
receiver circuitry to receive command information that specifies a read operation of a group of read data bits, and first error detection information associated with the command information, from a controller device; and
transmit circuitry to transmit the group of read data bits, the group of read data bits being transmitted time multiplexed with second error-detection information; and,

an encoder to generate the second error-detection information from the group of read data bits, wherein the transmit circuitry is operable to retransmit the group of read data bits and the second error detection information in the event that an error condition associated with the group of read data bits is detected.

2. The solid state memory device of claim 1, wherein the second error-detection information is to include a cyclic redundancy check (CRC) code.

3. The solid state memory device of claim 1, wherein the command information includes address bits that identify a location of the group of read data bits in a memory.

4. The solid state memory device of claim 1, further comprising:
a circuit to receive remedial action instructions from the controller device in the event that the error condition is detected, wherein the remedial action is to include the receiver circuitry re-receiving the command information associated with the group of read data bits in the event that the error condition is detected.

5. The solid state memory device of claim 4, wherein the receiver circuitry is to re-receive the command information along with fourth error detection information in the event that the error condition is detected.

6. The solid state memory device of claim 4, wherein the receiver circuitry is to re-receive the command information using one symbol per clock cycle of a clock signal action in the event that the error condition is detected.

7. The solid state memory device of claim 1, wherein, in the first configuration, the link interface is configurable as bidirectional for data signals and unidirectional for error detection information and, in the second configuration, is reconfigurable as unidirectional for both data signals and the first error detection information.

8. The solid state memory device of claim 1, wherein the transmitter circuitry transmits the group of read data bits in a single data rate format.

9. The solid state memory device of claim 1, wherein transmitter circuitry transmits the group of read data bits using both rising and falling edges of a clock signal.

10. A method of operation of a solid state memory device, the method comprising:
configuring a link interface to transfer signals in one of a bidirectional format in a first configuration, and a unidirectional format in a second configuration;
in one of the first configuration and the second configuration, receiving, from a controller device, command information and first error detection information associated with the command information and transmitting a group of read data bits in response to the command information, the group of read data bits being transmitted time multiplexed with second error-detection information;
prior to transmitting, generating the second error-detection information from the group of read data bits; and
retransmitting the group of read data bits and the second error detection information in the event that an error condition associated with the group of read data bits is detected.

11. The method of claim 10, wherein the second error-detection information includes a cyclic redundancy check (CRC) code.

12. The method of claim 10, further comprising:
receiving remedial action instructions from the controller device in the event that the error condition is detected.

13. The method of claim 12, wherein the remedial action includes re-receiving the command information associated with the group of read data bits in the event that error condition is detected.

14. The method of claim 13, wherein re-receiving the command information comprises re-receiving the command information along with fourth error detection information action in the event that the error condition is detected.

15. The method of claim 13, wherein re-receiving the command information comprises re-receiving the command information using one symbol per clock cycle of a clock signal action in the event that the error condition is detected.

16. The method of claim 10, wherein transmitting the group of read data bits comprises one of transmitting the group of read data bits in a single data rate format, and transmitting the group of read data bits using both rising and falling edges of a clock signal.

17. The method of claim 10, wherein, in the first configuration, the command information is transmitted using a unidirectional format and data is transferred in a bidirectional format, the data including the plurality of read data bits.

18. The method of claim 17, wherein, in the second configuration, the command information is received using the unidirectional format and the transmitting of the group of read data bits comprises transmitting the group of read data bits in the unidirectional format.

19. The method of claim 17, further comprising:
in the first configuration, receiving write data in the bidirectional format, wherein the data includes the write data, and,
receiving, using the unidirectional format, a write command associated with the write data.

20. A solid state memory device comprising:
means for configuring a link interface to transfer signals in one of a bidirectional format in a first configuration, and a unidirectional format in a second configuration;
in one of the first configuration and second configuration, means for receiving, from a controller device, command information and first error detection information associated with the command information, and means for transmitting a group of read data bits in response to the command information, the group of read data bits being transmitted time multiplexed with second error-detection information; and
means for generating the second error-detection information from the group of read data bits; and
wherein the means for transmitting the group of read data bits is to retransmit the group of read data bits and the second error detection information in the event that an error condition associated with the group of read data bits is detected.