Embodiments of this invention relate to, among other things, implementation of data bus inversion in a memory system using Through-Wafer Interconnects (TWIs).
An example illustrating data transmission between high-speed components within a single semiconductor device, or between two devices in a communication system, is represented by the system 1 shown in
As discussed in U.S. patent application Ser. No. 11/873,779, filed Oct. 17, 2007, a data bus is susceptible to cross talk, simultaneous switching noise, intersymbol interference, and draws power based on the state of the data and/or frequency of data transition. One way to reduce these adverse effects and to prevent unnecessary power consumption is to encode the data. One specific form of data encoding that can be used is Data Bus Inversion (DBI).
Implementation of DBI includes encoding circuitry at the transmitter which assesses the relationship between data bits to be transmitted across a data bus and then decides (based on a particular DBI algorithm) if it would be advantageous to invert some or all of the data bits prior to transmission. If the data bits are inverted, an additional signal, referred to as a DBI bit, is also set at the encoding circuitry to indicate which data bits are inverted. Typically, as shown in
One specific DBI algorithm, illustrated in
The minimum transitions technique can be implemented using the encoding circuitry of
Different DBI algorithms are beneficial in different circumstances, and not all DBI algorithms are directed to minimizing the number of data transition across transmission channels. For example, other well-known DBI algorithms include the “minimum zeros” algorithm and the “minimum ones” algorithm. The purpose of these algorithms is, respectively, to minimize the number of binary zeros or binary ones transmitted across a channel. Such minimum zeros or ones algorithms conserve power when the driver or receiver circuits coupled to the transmission channels are referenced to VDDQ and VSSQ, respectively, through a resistive termination, and therefore will draw more power when transmitting or receiving a particular data state. For example, if a pull-tip resistor connected to the voltage supply is used in a particular driver circuit, driving a logic ‘0’ will require more power than would driving a logic ‘1’. As a result, use of a minimum zeros DBI algorithm would be warranted. Likewise, if a pull-down resistor is used, a minimum ones algorithm would be warranted. The minimum transitions and either of the minimum zeros or ones algorithms can also be combined in a DBI algorithm, as is disclosed in U.S. patent application Ser. No. 12/015,311, filed Jan. 16, 2008. In another DBI algorithm, discussed in the above-mentioned Ser. No. 11/873,779, only a portion of the data hits on a bus are inverted to balance the logic states in an encoded byte across the bus, which can he referred to as a Balanced DBI algorithm. Regardless of the DBI algorithm used, all of these DBI algorithms have the common feature of sequentially receiving groups of N original data signals and selectively encoding each group to form a corresponding group of N encoded data signals while issuing at least one encoding (DBI) indicator associated with each group of the N encoded data signals.
A system 100, potentially benefiting from the implementation of DBI is shown in
Intervening between the microprocessor 10 and the memory set 25 is a memory controller 12. Memory controllers 12 are well known in the art and work to create a standard interface 20 with which the microprocessor 10 can predictably communicate. The memory controller 12 couples to the microprocessor's data (DQ), address (A), and control (end) busses 11, and converts them to new busses 13 DQ′, A′, and cntl′ suitable for interfacing with a logic integrated circuit (IC) 14, discussed further below. Memory controller 12 typically comprises an integrated circuit separate and independent from other components in the system 100, but this is not strictly necessary, and the controller 12 could be integrated with other components if desired, A high speed differential interface between the controller 12 and the logic chip 14 may exist to improve the overall bandwidth of the system.
In the disclosed embodiment, a logic IC 14 intervenes between the memory controller 12 and the RAM ICs 16x. The logic IC 14 contains much if not all of the logic circuitry 49 typically present on a standard RAM IC. For example, the logic IC 14 can contain command decode and queuing circuitry 50. Such circuitry 50 interprets the various command signals on the end′ data bus (such as signals write enable (WE), row address strobe (RAS), column address strobe (CAS), and chip select (CS), assuming the RAM arrays 16x comprise DRAM memory), and issues and organizes the commands as appropriate for distribution to the RAM ICs 16x along a control bus end″. The logic IC 14 may also contain redundancy circuitry 52 for determining faulty memory addresses in the modified RAM ICs 16x and for rerouting around such defective addresses to functioning memory cells using programmable fuses or antifuses, as is well known. Logic IC 14 may additionally contain error correction circuitry 54, which can comprise well known circuitry for assessing and correcting faulty data in accordance with any number of error correction algorithms. Further, logic IC 14 may contain test mode circuitry 56, which is typically used during manufacturing and/or under the application of special test commands to test the operation of the various RAM ICs 16x. Typically, such circuits 50-56 are formed as part of the peripheral logic of a standard memory integrated circuit (not shown), but in the illustrated system such circuitry has been removed from the RAM ICs 16x.
System 100 can be manufactured as shown in
Logic IC 14 may also contain additional integration circuitry relevant to the modular integration of the RAM ICs 16x. For example, TWI rerouting circuitry 58 (
As recognized in the above-mentioned '868 application, DBI can be used with the TWI-based bus 15. However, although the use of DBI can reduce power draw in a system such as system 100, it is generally not desirable to have to provide additional signaling on the bus to provide the DBI channels, such as channel from
Nevertheless, the inventor believes that advances in system integration as exemplified by system 100 are making the implementation of DBI, and other data encoding algorithms, more attractive. At the same time, the use of such algorithms is becoming more important as systems shrink and as it becomes increasingly important that such systems reduce their power consumption and operate at high speeds. The inventor believes that it would be desirable to include DBI in a system such as system 100, without adding additional TWI-based channels to carry the DBI signals.
Implementations of encoding techniques are disclosed. The encoding technique, such as a Data bus inversion (DBI) technique, is implementable in a vertically stacked memory module, but is not limited thereto. The module can be a plurality of memory integrated circuits which are vertically stacked, and which communicate via a bus formed in one embodiment of channels comprising Through-Wafer Interconnects (TWIs), but again is not limited thereto. One such module includes spare channels that are normally used to reroute a data signal on the bus away from faulty data channels. In one disclosed technique, the status of a spare channel or channels is queried, and if one or more are unused, they can be used to carry a DBI bit, thus allowing at least a portion of the bus to be assessed in accordance with a DBI algorithm. Depending on the location and number of spare channels needed for rerouting, DBI can be apportioned across the bus in various manners. Implementations can also be used with other encoding techniques not comprising DBI.
The data channels DATAi transfer original data signals Di between the logic IC 14 and the RAM ICs 16x. Generally speaking, and ignoring the distinction between original data signals Di and encoded data signals Xi for the moment, each data signal Di is designated for connection to a particular data channel DATAi, although this correspondence can vary if rerouting is necessary as explained further below. Absent such rerouting, and assuming a write to the RAM ICs 16x is occurring, output data path circuitry in the logic IC 14 produces original data signals D0-D3 in parallel, which are then ultimately transferred to data channels DATA0-DATA3 respectively, and ultimately to the D0-D3 input data path circuitry in the RAM ICs 16x. A reading operation occurs similarly, but in the opposite direction.
Also illustrated in
Returning to
The control channels CNTR0-CNTRY may be time multiplexed such that they carry different control signals at different points in time. For example, the control channels may can signals relevant to rerouting only upon initialization of the module 40′, or when it is otherwise warranted to make a continuity check of the TWI-based bus of data channels, which is discussed further below. The control channels CNTR0-CNTRY may then carry memory-specific control signals (e.g., from system control circuit blocks 106 or 110) during periods of normal operation, for example.
As just noted, the control channels CNTR0-CNTRY may carry control signals relevant to rerouting around faulty data channels. Such control signals are generated at rerouting circuity 58 in the logic IC 14, which generally functions during periods of initialization or testing to check for faulty data signals and to perform rerouting to an appropriate spare channel such as SPARE0. (The above-referenced patent applications discuss such operations further). In the example shown, rerouting circuitry 58 generates four switch control signals SW<3:0>, which are sent to the switching network 122 in the logic IC 14. As will be shown in further detail later, the switching network 122 then reroutes the data signal originally assigned to the faulty data channel onto the spare channel. Indication of these switch control signals SW<3:0> are also sent via the control channels CNTR0-CNTRY to the rerouting/DBI slave circuitry 108 in the RAM ICs 16x, where they are stored and used to generate matching control signals SW<3:0> to control matching switching networks 122 in the RAM ICs 16x. The switch control signals can be transported across the control channels CNTR0-CNTRY along one channel, many channels, in serial or parallel, in an encoded fashion, or in any appropriate fashion.
In the event that the spare channel, SPARE0, is not used for rerouting, it may be used for DBI in accordance with embodiments of the disclosed technique, as shown in
Regardless of the DBI algorithm employed in DBI codec 120, the algorithm assesses the original data signals D0-D3 and decides whether to invert all or part of those signals. If the DBI algorithm's assessment reveals a benefit to inverting all or a portion of the original data signals D0-D3, then all or a portion of those data signals are inverted to produce encoded data signals X0-X3, and a DBI bit, DBI0, is issued. If the algorithm decides that there is no benefit to inversion, then the original data signals D0-D3 are simply passed as signals X0-X3 without inversion, and the DBI bit is not asserted for that data set.
Whether DBI can be enabled is determined by DBI control circuitry 104. DBI control circuitry 104 essentially determines whether the spare channel, SPARE0, is being used because it is needed for rerouting. If SPARE0 is not being used, DBI control circuitry 104 will enable the DBI codec 120 to apply the DBI algorithm to the original data signals D0-D3 to produce encoded data signals X0-X3 which are forwarded to data channels DATA0-DATA3, and to provide the DBI bit to SPARE0. If SPARE0 is being used because it is necessary to reroute one of the data signals away from a faulty data channel, DBI control circuitry 104 disables the DBI codec 120 such that the original data signals D0-D3 merely flow through the DBI codec without analysis and without generation of the DBI bit. The switching network 122 then reroutes the data signal affected by the reroute to SPARE0, and the other data signals pass to their respective data channels DATA0-DATA3 as discussed previously.
To do this, the DBI control circuitry 104 receives an indication of the spare channel status from the rerouting circuitry 58 in the logic IC 14. Specifically, the rerouting circuitry 58 contains spare channel status circuitry 102, which comprises a means for storing an indication of the status of the spare channel. In one simple embodiment, spare channel status circuitry 102 can comprise a four-bit storage register for the switch control signals SW<3:0>, which values are then sent to the DBI control circuitry 104. The DBI control circuitry 104 then analyzes the switch control signals SW<3:0> to determine whether the spare channel is being used for rerouting or not, and whether the DBI codec 120 can be enabled.
One simple implementation of the DBI control circuitry 104 is shown in
Should none of the switch control signals be asserted (i.e., SW<3:0>=0), meaning that rerouting of data is not necessary, then the NOR gate of DBI control circuitry 104 outputs a 1 as the DBI enable signal, DBI_en. This enables the DBI codec 120 to apply its algorithm to the original data signals D0-D3, to produce encoded data signals X0-X3, and to generate a corresponding DBI bit, DBI0. Additionally, enabling the DBI enable signal enables pass gate 124, which allows the DBI bit, DBI0, to pass to the otherwise unused spare channel, SPARE0. At the same time, the failure to assert any of the switch control signals SW<3:0> causes the switching network 122 to pass the encoded data bits X0-X3 to their respective data channels DATA0-DATA3. Such routing is shown in dotted lines in
In the technique as described thus far, the logic IC 14, via operation of rerouting circuitry 58 and DBI control 104, comprises the master controllers for rerouting and DBI enablement. The RAM ICs 16x, by contrast, contain mere corresponding slave controllers, i.e., rerouting/DBI slave circuitry 108. As mentioned earlier, the rerouting/DBI slave circuitry 108 can receive and store rerouting signals from the rerouting circuitry 58 in the logic IC 14 via control channel(s) CNTR0-CNTRY. The DBI enable signal, DBI_en, can also be transmitted to the RAM ICs 16x by the control channel(s) CNTR0-CNTRY, but it may be more convenient instead to merely generate the DBI enable signal at the RAM ICs 16x from the switch control signals stored at the slave circuitry 108. To summarize, rerouting DBI slave circuitry 108 essentially mimics the operation of the rerouting circuitry 58 and DBI control circuitry 104 operable in the logic IC 14 so that the DBI codecs 120 and the switching networks 122 in both the logic IC 14 and the RAM ICs 16x can be controlled similarly.
A larger bus with a plurality of spare channels increases the sophistication with which DBI algorithms can operate, assuming that at least one spare channel is not being used for rerouting. For example, and as shown in
Apportioning the bus 15 in this manner for DBI purposes adds complexity, but can improve the benefits of DBI. This is because dividing the bus into groups of data signals, and applying DBI to each group independently and generating a DBI bit for each portion independently, reduces power consumption when compared to applying DBI to a larger, undivided bus (which undivided bus would only require one DBI bit). Applying DBI to an apportioned bus is addressed in the following references, which are submitted with the Information Disclosure Statement filed with this disclosure: U. Narayanan, “Enhanced Bus Invert Encodings for Low-Power,” IEEE, Circuits and Systems, vol. 5, pgs 25-28 (2002); Y. Shin, “Reduction of bus transitions with partial bus-invert coding,” Electronic Letters, vol. 34, no. 7 (Apr. 2, 1998); and M. Stan & W. Burleson, “Bus-Invert Coding for Low Power I/O,” pgs. 1-20 (1999).
DBI can also operate to assess portions of the bus 15 larger than a byte. For example, the DBI codec 120 can be enabled to apply DBI to a group comprising a word's worth of data, i.e., 16 bits. This can occur by providing two different DBI enable signals to the DBI codec 120: DBI_en<T>, which enables the DBI codec 120 to apply its algorithm to the top word of data, i.e., to the data signals presented to data channels DATA0-15; and DBI_en<B>, which similarly enables the DBI codec 120 to apply DBI to the bottom word of data to be presented to DATA16-31. Apportioning the bus in this manner requires two DBI bits, DBI_T and DEI_B, to be carried on the spare channels.
Finally, DBI can also operate on the entire double word of data, i.e., a single group of all 32 data signals. The DBI codec 120 can be enabled to do so via signal DBI_en<W>, which assesses DBI based on the whole of the data channels. If DBI is applied to the entire bus, only one DBI bit, DBI_W, would be required, which could be carried on any free spare channel.
The ability to apply DBI at these various levels of bus apportionment improves the flexibility with which DBI can be applied to the data bus 15. However, since the DBI bit or bits are sent over the spare channels, the options for applying DBI will be constrained depending on which spare channels are needed for rerouting. The DBI control circuitry 104 therefore, after consideration of the status of the switch control signals to understand where rerouting is occurring along the bus 15, should issue appropriate DBI enable signals to apportion the bus for DBI purposes without inhibiting rerouting. Various conditions illustrating such options are shown in
In the option of column B, DBI can be apportioned to the top and bottom words of data, This requires the use of enable signals DBI_en<T> and DBI_en<B>, and the generation of two DBI bits: DBI_T associated with the top word of encoded data signals X0-X15 and DBI_B associated with X16-31. Here, DBI_T can be sent on spare channel SPARE1 (or SPARE0) and DBI_B can be sent on spare channel SPARE3 (or SPARE2), with the other spare channels remaining unused.
In the option of column C, the bus is not apportioned, and DBI is applied to all 32 data signals, requiring the use of enable signal DBI_en<AV> and the generation of only a single DBI bit, DBI_W, which can be sent on any of the spare channels, but which is shown in
All other options B, C, and D of
In option C, DBI is performed on a word basis. This requires issuing enable signals DBI_en<T> and DBI_en<B>, which enables the codec 120 to produced encoded data signals X0-X15 and X16-X31, and their associated DBI bits, DBI T and DBI_B, respectively. As with option B, the faulty encoded data signal continues to be carried by SPARE0, with the other spare in the word, SPARE1, carrying DBI_T. On the bottom word, the DBI bit, DBI_B, is sent to one of the bottom word spare channels (e.g, SPARE3) and the other spare channel (SPARE2) is unused. Option C thus differs from option B in that the DBI apportionment is applied to equally-sized portions of the data bus, i.e., two words, instead of one word and two bytes.
In option D, DBI is applied to all 32 bits, similar to what occurred in option C of
Scenario III′, in which both errors occur in the same word, is essentially the same as Scenario III just discussed. However, in option B, where DBI assessment occurs on a word basis, there is no spare channel in the top byte to carry the DBI bit for the top byte (i.e., DBI_T′). Therefore, in this scenario, DBI_T bit is routed to the available spare channel in the bottom word (i.e., SPARE2). Although this generally violates the preference to keep a particular DBI bit in proximity to its associated data, it requires no particular technical challenge to so reroute the DBI bit.
Circuitry for implementing the various conditions illustrated in
The switching network 122 will likewise be implementation specific and will depend on the DBI options chosen. When applied to a more complex bus such as that shown in
Although conceived of in the context of a vertically stacked memory module, it should be noted that the inventive concepts disclosed herein are not necessarily limited to that environment.
Any of these DBI algorithms mentioned above, or other data encoding algorithms more generally, can be used in the context of the disclosed embodiments of the invention. Additionally, other embodiments of the invention would not necessarily require operation of a data bus inversion algorithm. Instead, the codecs 120 could comprise other types of encoders and decoders (e.g., error detection, or error correction), and the DBI bit could more generally comprise an encoding indicator bit or hits (e.g., an error detection bit, or an error correction bit) consistent with the particular decoder. Thus, previously-existing or future-developed encoding decoding schemes will also benefits from the disclosed techniques.
While some implementations have been disclosed, it should be understood that the disclosed circuitry can be achieved in many different ways to the same useful ends as described herein. In short, it should be understood that the inventive concepts disclosed herein are capable of many modifications. To the extent such modifications fall within the scope of the appended claims and their equivalents, they are intended to be covered by this patent.
Number | Name | Date | Kind |
---|---|---|---|
5517436 | Andreas et al. | May 1996 | A |
5930527 | Shin | Jul 1999 | A |
6111833 | Nakagawa | Aug 2000 | A |
6385739 | Barton et al. | May 2002 | B1 |
6490703 | De la Iglesia et al. | Dec 2002 | B1 |
7082489 | Yeh et al. | Jul 2006 | B2 |
7154300 | Anders et al. | Dec 2006 | B2 |
7221292 | Hein | May 2007 | B2 |
7300857 | Akram et al. | Nov 2007 | B2 |
7400541 | Jang et al. | Jul 2008 | B2 |
7549011 | Moschopoulos | Jun 2009 | B2 |
7739545 | Check et al. | Jun 2010 | B2 |
7795134 | Sulfridge | Sep 2010 | B2 |
9087025 | Hollis et al. | Jul 2015 | B2 |
9946612 | Hollis | Apr 2018 | B2 |
10698776 | Hollis | Jun 2020 | B2 |
20040136319 | Becker et al. | Jul 2004 | A1 |
20080017306 | Liu et al. | Jan 2008 | A1 |
20080140987 | Rixner et al. | Jun 2008 | A1 |
20080288844 | Nieuwland | Nov 2008 | A1 |
20090019344 | Yoon et al. | Jan 2009 | A1 |
20090057745 | Yin et al. | Mar 2009 | A1 |
20090083453 | Hsueh et al. | Mar 2009 | A1 |
20090193159 | Li et al. | Jul 2009 | A1 |
20090193319 | Shen et al. | Jul 2009 | A1 |
20090294954 | Bakir et al. | Dec 2009 | A1 |
20090313521 | Hollis | Dec 2009 | A1 |
20100088460 | Jeddeloh | Apr 2010 | A1 |
20100118618 | Kwak | May 2010 | A1 |
20100199017 | Hollis | Aug 2010 | A1 |
20150324261 | Hollis | Nov 2015 | A1 |
20180232289 | Hollis | Aug 2018 | A1 |
20200364121 | Hollis | Nov 2020 | A1 |
Entry |
---|
“Bus-Invert Coding for Low Power I/O”, (1999), 1-20. |
Ghoneima, et al., “Reducing the Data Switching Activity on Serial Link Buses”, IEEE Computer Society, Proceedings of the 7t. International Symposium on Quality Electronic Design, (Jul. 2006), 6 pgs. |
Jang, et al., “Spare Line Borrowing Technique for Distributed Memory Cores in SoC”, Instrumentation and Measurement Technology Conference, (May 17, 2005), 6 pgs. |
Stan, M R, et al., “Coding a Terminated Bus for Low Power”, Great Lakes Symp. on VLSI, (Mar. 1995), 70-73. |
Stan, Mircea R, et al., “Bus-Invert Coding for Low Power I/O”, IEEE Transactions on VLSI Systems, vol. 3, No. 1, (Mar. 1995), 9 pgs. |
Unni, Narayanan, et al., “Enhanced Bus Invert Encodings for Low-Power”, IEEE, Circuits and Systems, vol. 5, (2002), 25-28. |
Youngsoo, Shin, et al., “Reduction of bus transitions with partial bus-invert coding”, Electronic Letters, vol. 34, No. 7, (Apr. 2, 1998), 2 pgs. |
Number | Date | Country | |
---|---|---|---|
20230126998 A1 | Apr 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16915413 | Jun 2020 | US |
Child | 17982047 | US | |
Parent | 15954149 | Apr 2018 | US |
Child | 16915413 | US | |
Parent | 14804027 | Jul 2015 | US |
Child | 15954149 | US | |
Parent | 12366379 | Feb 2009 | US |
Child | 14804027 | US |