Information may be stored on individual memory cells of the memory as a physical signal (e.g., a charge on a capacitive element). The memory may be a volatile memory, and the physical signal may decay over time (which may degrade or destroy the information stored in the memory cells). It may be necessary to periodically refresh the information in the memory cells by, for example, rewriting the information to restore the physical signal to an initial value.
As memory components have decreased in size, the density of memory cells has greatly increased. An auto-refresh operation may be carried out where a sequence of memory cells are periodically refreshed. Repeated access to a particular memory cell or group of memory cells (often referred to as a ‘row hammer’) may cause an increased rate of data degradation in nearby memory cells. In addition to the auto-refresh operations, it may be desirable to identify and refresh memory cells affected by the row hammer in a targeted refresh operation.
The following description of certain embodiments is merely exemplary in nature and is in no way intended to limit the scope of the disclosure or its applications or uses. In the following detailed description of embodiments of the present systems and methods, reference is made to the accompanying drawings which form a part hereof, and which are shown by way of illustration specific embodiments in which the described systems and methods may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice presently disclosed systems and methods, and it is to be understood that other embodiments may be utilized and that structural and logical changes may be made without departing from the spirit and scope of the disclosure. Moreover, for the purpose of clarity, detailed descriptions of certain features will not be discussed when they would be apparent to those with skill in the art so as not to obscure the description of embodiments of the disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the disclosure is defined only by the appended claims.
A memory device may include a plurality of memory cells. The memory cells may store information (e.g., as one or more bits), and may be organized at the intersection of word lines (rows) and bit lines (columns). A number of word lines and bit lines may be organized into a memory bank. A memory device may include a number of different memory banks. The memory device may receive one or more command signals which may indicate operations in one or more of the banks of one or more memory packages. The memory device may enter a refresh operation, in which word lines in one or more of the memory banks are refreshed.
Information in the memory cells may decay over time. The memory cells may be refreshed on a row-by-row basis to preserve information in the memory cells. During a refresh operation, the information in one or more rows may be rewritten back to the respective rows to restore an initial value of the information. Repeated access to a given row (e.g., an aggressor row) may cause an increased rate of information decay in one or more neighboring rows (e.g., victim rows). Accesses to different rows of the memory may be tracked in order to determine victims and refresh them as part of a targeted (or ‘row hammer’) refresh operation. However, individually tracking every row access may be difficult due to space and/or power limitations of the device.
To save space and/or power, a memory device may include a data storage component, for example a register or stack of registers, which stores a number of count values, each of which may be associated with a portion of the word lines of the device (e.g., one count value may be associated with multiple word lines). The count value may be adjusted (e.g., incremented) each time any of the word lines in the associated portion are accessed. Between them, the count values may represent accesses to every word line of the device. When a count value crosses (e.g., meets or exceeds) a threshold value, one or more victim rows based on the portion of the word lines associated with the count value may be determined. In some cases, the portion of the word lines may represent one or more sections of word lines, in which all the word lines of the group are physically adjacent to one another, but this is not required. The victim addresses may be associated with each of the word lines in the portion of word lines. In some cases, all of the victim row addresses may be refreshed by one or more targeted refresh operations.
While count values that correspond to multiple word lines may save space and/or power, it may lead to excessive targeted refresh operations in some applications. For example, if a count value corresponds to accesses to sixteen word lines, when the count value exceeds the threshold value, victim row addresses for the sixteen word lines may be calculated. If victim word lines are considered to be the word lines adjacent to the word lines associated with the count value, this results in up to thirty-two victim row addresses that are provided for targeted refresh operations. If more distant word lines are considered to be victim word lines, then even more victim row addresses may be provided for targeted refresh operations (e.g., 64 row addresses, 128 row addresses). In some applications, there may not be enough time to refresh all of the victim row addresses in the time allotted for targeted refresh operations.
In many cases, it is unlikely that all of the word lines in the portion of word lines associated with a count value are being repeatedly accessed (e.g., hammered). Rather, it is likely only one or a few of the word lines are being hammered. Thus, only the victim word lines associated with the word lines actually being repeatedly accessed may benefit from targeted refresh operations. Accordingly, it may be beneficial to determine which sub-portion of the portion of word lines associated with a count value are being hammered and only refresh victim word lines associated with the sub-portion. This may reduce power consumption and/or operation time dedicated to targeted refresh operations.
The present disclosure is drawn to apparatuses, systems, and methods for tracking accesses to rows. In some embodiments, in addition to tracking accesses for a groups of rows, access to sub-portions of a group of the rows may be tracked, and victim addresses may only be generated for the sub-portions when an aggressor row is determined to be in the sub-portion. That is, a first number of word lines may be tracked (e.g., a portion) and a second number of word lines may be tracked (e.g., a sub-portion) where the second number is smaller than the first number. In some embodiments, the sub-portions may be further divided into sub-portions.
In some embodiments of the disclosure a first storage device, such as a stack of registers, stores a first number of count values, each of which may be associated with a portion of the word lines of the memory device. A count value may be adjusted each time any of the word lines in an associated portion are accessed. Between them, the count values may represent accesses to every word line of the memory device. When a count value from the first storage device crosses a first threshold value, the portion of word lines associated with the count value may be assigned to a second storage device. The second storage device may store a second number of count values, each of which may be associated with a sub-portion of the portion of word lines. A count value may be adjusted each time any of the word lines in an associated sub-portion are accessed. Between them, the count values may represent accesses to every word line of the portion of word lines. In some examples, a count value may be associated with each word line of the portion of word lines. When a count value from the second storage device crosses a second threshold value, victim word lines associated with the sub-portion of word lines may be calculated for performing targeted refresh operations.
The semiconductor device 100 includes a memory array 112. In some embodiments, the memory array 112 may include of a plurality of memory banks. Each memory bank includes a plurality of word lines WL, a plurality of bit lines BL and /BL, and a plurality of memory cells MC arranged at intersections of the plurality of word lines WL and the plurality of bit lines BL and /BL. The selection of the word line WL is performed by a row control 108 and the selection of the bit lines BL and /BL is performed by a column control 110. In some embodiments, there may be a row control 108 and column control 110 for each of the memory banks.
The bit lines BL and /BL are coupled to a respective sense amplifier (SAMP) 117. Read data from the bit line BL or /BL is amplified by the sense amplifier SAMP 117, and transferred to read/write amplifiers 120 over complementary local data lines (LIOT/B), transfer gate (TG) 118, and complementary main data lines (MIO). Conversely, write data outputted from the read/write amplifiers 120 is transferred to the sense amplifier 117 over the complementary main data lines MIO, the transfer gate 118, and the complementary local data lines LIOT/B, and written in the memory cell MC coupled to the bit line BL or /BL.
The semiconductor device 100 may employ a plurality of external terminals that include command and address (C/A) terminals coupled to a command and address bus to receive commands and addresses, clock terminals to receive clocks CK and /CK, data terminals DQ to provide data, and power supply terminals to receive power supply potentials VDD, VSS, VDDQ, and VSSQ.
The clock terminals are supplied with external clocks CK and /CK that are provided to a clock input circuit 122. The external clocks may be complementary. The clock input circuit 122 generates an internal clock ICLK based on the CK and /CK clocks. The ICLK clock is provided to the command control 106 and to an internal clock generator 124. The internal clock generator 124 provides various internal clocks LCLK based on the ICLK clock. The LCLK clocks may be used for timing operation of various internal circuits. The internal data clocks LCLK are provided to the input/output circuit 126 to time operation of circuits included in the input/output circuit 126, for example, to data receivers to time the receipt of write data.
The C/A terminals may be supplied with memory addresses. The memory addresses supplied to the C/A terminals are transferred, via a command/address input circuit 102, to an address decoder 104. The address decoder 104 receives the address and supplies a decoded row address XADD to the row control 108 and supplies a decoded column address YADD to the column control 110. The row address XADD may be used to specify one or more word lines WL of the memory array 112 and the column address YADD may specify one or more bit lines BL of the memory array 112. The address decoder 104 may also provide a bank address BADD, which specifies a particular bank of the memory. The bank address BADD may be provided to the row control 108 and/or column control 110 to direct access operations to one or more of the banks.
The row address XADD may include multiple bits. As used herein, the different bits of the row address XADD may be labeled as RA0-RAn, where n is the total number of bits of the row address. Accordingly, RAi may refer to an ith bit of the row address XADD.
Different subsets of the bits of the row address XADD may be associated with different levels of organization of the memory array 112. For example, a subset of the bits of the row address XADD may be a section address which refers to a section of the memory array 112 containing a number of word lines and a different subset of the bits of the row address XADD may be a word line address which refers to a particular word line within that section. Different arrangements of the row address and word lines may be used in other embodiments. Although properties and uses of the row address are generally described herein, it should be understood that the column addresses may be organized and used in a similar way in some embodiments.
The C/A terminals may be supplied with commands. Examples of commands include timing commands for controlling the timing of various operations, access commands for accessing the memory, such as read commands for performing read operations and write commands for performing write operations, as well as other commands and operations. The access commands may be associated with one or more row address XADD, column address YADD, and/or bank address BADD to indicate the memory cell(s) to be accessed.
The commands may be provided as internal command signals to a command control 106 via the command/address input circuit 102. The command control 106 includes circuits to decode the internal command signals to generate various internal signals and commands for performing operations. For example, the command control 106 may provide a row command signal to select a word line and a column command signal to select a bit line.
The device 100 may receive an access command which is a row activation command ACT. When the row activation command ACT is received, a row address XADD is supplied with the row activation command ACT.
The device 100 may receive an access command which is a read command. When a read command is received, a bank address BADD and a column YADD address are timely supplied with the read command, read data is read from memory cells in the memory array 112 corresponding to the row address XADD and column address YADD. The read command is received by the command control 106, which provides internal commands so that read data from the memory array 112 is provided to the read/write amplifiers 120. The read data is output to outside from the data terminals DQ via the input/output circuit 126.
The device 100 may receive an access command which is a write command. When the write command is received, a bank address and a column address are timely supplied with the write command, write data supplied to the data terminals DQ is written to a memory cells in the memory array 112 corresponding to the row address and column address. The write command is received by the command control 106, which provides internal commands so that the write data is received by data receivers in the input/output circuit 126. Write clocks may also be provided to the external clock terminals for timing the receipt of the write data by the data receivers of the input/output circuit 126. The write data is supplied via the input/output circuit 126 to the read/write amplifiers 120, and by the read/write amplifiers 120 to the memory array 112 to be written into the memory cell MC.
The device 100 may also receive commands causing it to carry out refresh operations. A refresh signal AREF may be a pulse signal which is activated when the command control 106 receives a signal which indicates a refresh command. In some embodiments, the refresh command may be externally issued to the memory device 100. In some embodiments, the refresh command may be periodically generated by a component of the device. In some embodiments, when an external signal indicates a refresh entry command, the refresh signal AREF may also be activated. The refresh signal AREF may be activated once immediately after command input, and thereafter may be cyclically activated at desired internal timing. Thus, refresh operations may continue automatically. A self-refresh exit command may cause the automatic activation of the refresh signal AREF to stop and return to an IDLE state.
The refresh signal AREF is supplied to a refresh control circuit 116. In some embodiments, there may be a refresh control circuit 116 associated with each bank. The bank address BADD may indicate one or more of the refresh control circuits 116 to be activated. The refresh control circuits 116 may receive the refresh signal AREF in common, and may generate and provide one or more refresh row address(es) RXADD in order to perform one or more refresh operations in the associated memory bank. In some embodiments, a subset of the memory banks may be given refresh commands. For example, one or more additional signals may indicate which of the refresh control circuits 116 should provide refresh address(es) responsive to AREF. In another example, AREF may only be provided to refresh control circuits 116 which are associated with the subset of memory banks which are refreshing.
Focusing on the operation of a given refresh control circuit, the refresh control circuit 116 supplies a refresh row address RXADD to the row control 108, which may refresh one or more word lines WL indicated by the refresh row address RXADD. The refresh control circuit 116 may control a timing of the refresh operation based on the refresh signal AREF. In some embodiments, responsive to an activation of AREF, the refresh control circuit 116 may generate one or more activations of a pump signal, and may generate and provide a refresh address RXADD for each activation of the pump signal (e.g., each pump).
One type of refresh operation may be an auto-refresh operation. Responsive to an auto-refresh operation the memory bank may refresh a group of rows of the memory, and then may refresh a next group of rows of the memory bank responsive to a next auto-refresh operation. The refresh control circuit 116 may provide a refresh address RXADD which indicates a group of word lines in the memory bank. The refresh control circuit 116 may generate a sequence of refresh addresses RXADD such that over time the auto-refresh operation may cycle through all the word lines WL of the memory bank. The timing of refresh operations may be such that each word line is refreshed with a frequency based on a normal rate of data degradation in the memory cells.
Another type of refresh operation may be a targeted refresh operation. Repeated access to a particular row of memory (e.g., an aggressor row) may cause an increased rate of decay in neighboring rows (e.g., victim rows) due, for example, to electromagnetic coupling between the rows. In some embodiments, the victim rows may include rows which are physically adjacent to the aggressor row. In some embodiments, the victim rows may include rows further away from the aggressor row. Information in the victim rows may decay at a rate such that data may be lost if they aren't refreshed before the next auto-refresh operation of that row. In order to prevent information from being lost, it may be necessary to identify aggressor rows and then carry out a targeted refresh operation where a refresh address RXADD associated with one or more associated victim rows is refreshed.
The refresh control circuit 116 may receive the row addresses XADD provided by the address decoder 104 and may determine which word lines are being hammered based on the row addresses XADD. The refresh control circuit 116 may count accesses to the word lines based on the row address XADD and may determine which word lines are aggressors based on the count of the accesses. The refresh control circuit 116 may divide the total number of word lines into portions and have a counter value for each of the portions. For example, a first portion of the word lines may be associated with a first count value, a second portion of the word lines may be associated with a second count value, etc. In some embodiments, the portion of the word lines associated with the count value may be organized into one or more sections of word lines each of which contain one or more word lines which are physically adjacent to each other, but this is not required. Each count value may be updated any time any of the word lines in the portion represented by the count value is accessed. In this manner all accesses to all word lines may be tracked by the count values, but there may be fewer count values than the number of total word lines.
In some embodiments, word lines may be grouped together based on the row addresses associated with those word lines. If only a particular subset of the row address is specified (e.g., a particular value of that subset of bits) then all word lines which share the specified value of that subset as part of their row address may be identified. For example, each portion of the word lines tracked by a counter value may be specified by a particular value of a subset of the row address XADD. If a row address contains a first subset (e.g., a section address) specifying a section of word lines and a second subset (e.g., a word line address) specifying a particular word line within that section, then the word line address subset of the row address may be ignored, and the refresh control circuit 116 may have a counter value associated with the value of the section address. Accordingly, the count value may be updated anytime any word line within the section(s) associated with the section address. In some embodiments, the section address may be truncated (e.g., some of the bits of the section address may be ignored) into a multi-section address, which represents all of the word lines in a number of different sections. Each count value may be specified by a particular value of the grouped section address and may represent accesses to any word line in any of the sections associated with the multi-section address. It should be understood that a row address XADD may include many subsets describing many different levels of organization. Other methods associating groups of word lines with a counter value may be used in other embodiments.
When the refresh control circuit 116 determines that the count value for a portion of word lines exceeds a first threshold value, the refresh control circuit 116 may begin to count accesses to sub-portions of the portion of word lines associated with the count value. A count value may be associated with each sub-portion. Each count value may be updated any time any of the word lines in the sub-portion represented by the count value is accessed. In some examples, each sub-portion may include a single word line. When the refresh control circuit 116 determines that the count value for a sub-portion of word lines exceeds a second threshold value, one or more victim addresses associated with the word line(s) of the sub-portion may be provided. The refresh control circuit 116 may provide a number of victim addresses for each determined aggressor address. If the counter value represents a number of different word lines, victim addresses may be provided for each of the word lines in the group associated with a given counter value. In some applications, providing victim addresses for only a sub-portion of the portion of word lines may reduce a number of targeted refreshes required to be performed to mitigate row hammer effects. In some applications, this may reduce unnecessary refreshing of victim word lines.
The power supply terminals are supplied with power supply potentials VDD and VSS. The power supply potentials VDD and VSS are supplied to an internal voltage generator circuit 128. The internal voltage generator circuit 128 generates various internal potentials VPP, VOD, VARY, VPERI, and the like based on the power supply potentials VDD and VSS supplied to the power supply terminals. The internal potential VPP is mainly used in the row control 108, the internal potentials VOD and VARY are mainly used in the sense amplifiers SAMP included in the memory array 112, and the internal potential VPERI is used in many peripheral circuit blocks.
The power supply terminals are also supplied with power supply potentials VDDQ and VSSQ. The power supply potentials VDDQ and VSSQ are supplied to the input/output circuit 126. The power supply potentials VDDQ and VSSQ supplied to the power supply terminals may be the same potentials as the power supply potentials VDD and VSS supplied to the power supply terminals in an embodiment of the disclosure. The power supply potentials VDDQ and VSSQ supplied to the power supply terminals may be different potentials from the power supply potentials VDD and VSS supplied to the power supply terminals in another embodiment of the disclosure. The power supply potentials VDDQ and VSSQ supplied to the power supply terminals are used for the input/output circuit 126 so that power supply noise generated by the input/output circuit 126 does not propagate to the other circuit blocks.
According to principles of the present disclosure, sub-portions of a portion of the word lines 202 may be tracked by a second storage device 214. Box 216 indicates the portion of word lines 202 associated with count value C_Portion0 in storage device 204. As an example, this same portion of word lines 202 is illustrated in box 218. The second storage device 214 may store a number of count values C_Subportion0-3. Each count value C_Subportion0-3 may be associated with a portion of the word lines 202 in the portion of word lines 202 indicated by box 218. That is, each count value C_Subportion0-3 may be associated with a sub-portion of the word lines 202 of box 218. The portion of word lines 202 indicated by box 218 may include the second number of word lines. Each count value C_Subportion0-3 may be associated with a third number of word lines. The third number of word lines may be less than the second number. In the example shown in
Optionally, according to principles of the present disclosure, sub-portions of a sub-portion of the word lines 202 indicated by box 218 may be tracked by a third storage device 226. Box 228 indicates the portion of word lines 202 associated with count value C_SubPortion0 in storage device 214. As an example, this same portion of word lines 202 is illustrated in box 230. The third storage device 226 may store a number of count values C_SubSub0-1. Each count value C_SubSub0-1 may be associated with a portion of the word lines 202 in the portion of word lines 202 indicated by box 228, which is in turn a portion of the word lines 202 indicated by box 216. The portion of word lines 202 indicated by box 230 may include the third number of word lines. Each count value C_SubSub0-1 may be associated with a fourth number of word lines. The fourth number of word lines may be less than the second number. In the example shown in
As illustrated by
It should be noted that the accesses to particular word lines by particular count values in the storage devices 204 and 214 discussed above are provided for explanatory purposes only and the principles of the present disclosure are not limited to the examples discussed above. For example, any count value C_SubPortion0-3 of storage device 214 may be assigned to word lines associated with any of the count values C_Portions0-2 of storage device 204.
The refresh control circuit 300 includes a main counter stack 330 (and its associated decoder 331) which stores count values (C_Portion0-N), each associated with a portion of the word lines of the memory. A first counter logic circuit 334 may update a count value (e.g., C_Portion2) in the main counter stack 330 based on the row address XADD. In some embodiments the first counter logic circuit 334 may update the count value by incrementing the count value and may provide a signal Watch when the incremented count value exceeds a first threshold. In other embodiments the first counter logic circuit 334 may decrement the count value and may provide the signal Watch if the count value is below the first threshold. Other methods of updating and checking a value of the count values may be used in other embodiments. After the signal Watch is provided, the count value may be adjusted (e.g., reduced). In some embodiments, after the signal Watch is provided, the count value may be adjusted to a value between an initial value (e.g., 0) and the threshold value. For example, the count value may be set to a value of half the threshold value. In some embodiments, the first counter logic circuit 334 may receive a threshold signal (not shown), which may set a value of the first threshold.
The refresh control circuit 300 includes a sub-counter stack 346 (and its associated decoder 347) which stores count values (C_ADD0-M), each associated with a sub-portion of a portion of the word lines of the memory. The sub-counter stack 346 may receive the signal Watch from the first counter logic circuit 334. Based on the signal Watch, the sub-counter stack 346 may assign count values to sub-portions of the portion of the word lines of the memory whose count value exceeded the first threshold value in the main counter stack 230. For example, if the count value C_Portion2 of main counter stack 330 exceed the first threshold value, the count values C_ADD0-M may each be associated with different sub-portions of the portion of word lines whose accesses were tracked by the count value C_Portion2.
A second counter logic circuit 348 may update a count value (e.g., C_ADD1) in the sub-counter stack 346 based on the row address XADD. In some embodiments the second counter logic circuit 348 may update the count value by incrementing the count value and may provide a signal Capture when the incremented count value exceeds a second threshold. In other embodiments the second counter logic circuit 348 may decrement the count value and may provide the signal Capture if the count value is below the second threshold. Other methods of updating and checking a value of the count values may be used in other embodiments. In some embodiments, the second threshold value is greater than the first threshold value. After the signal Capture is provided, the count value may be reset to an initial value (e.g., 0 or the first threshold value). In some embodiments, the second counter logic circuit 348 may receive a threshold signal (not shown), which may set a value of the second threshold.
In some embodiments, instead of comparing the count values C_ADD0-M to a threshold value, the counter logic circuit 348 may compare the count values C_ADD0-M to one another and provide the address with the highest count value as the signal Capture.
In some embodiments, after the signal Capture is provided, the second counter logic circuit 348 may reset all of the count values C_ADD0-M in the sub-counter stack 346, not just the count value that triggered the signal Capture. This may indicate that the sub-counter stack 346 is available to monitor accesses to a different portion of word lines in the memory. However, if word lines in multiple sub-portions are being hammered, resetting all of the count values in sub-counter stack 346 may cause the refresh control circuit 300 to only respond to row hammers in a single sub-portion. This issue may be mitigated when, as described above, the first counter logic circuit 334 adjusts a count value in the main counter stack 330 to an intermediate value rather than resetting the count value. The intermediate value may permit the portion of word lines to again be monitored by the sub-counter stack 346 after a shorter period such that multiple row hammers in the portion of word lines may be mitigated by the refresh control circuit 300 before data in victim word lines is compromised.
In some embodiments, the sub-counter stack 346 may continue monitoring the portion of word lines of the memory for a period of time and provide the signal Capture as necessary until the period of time expires. For example, the period of time may be the time necessary for auto-refresh operations to cycle through all of the word lines in the memory or portion of word lines in the memory. After the period of time expires, all of the count values in the sub-counter stack 346 may be reset and the sub-counter stack 346 may be available to monitor another portion of word lines of the memory. In some embodiments, the count values of the sub-counter stack 346 may be reset and the sub-counter stack 346 may be available to monitor another portion of word lines of the memory if the signal Capture is not sent within a period of time.
An address circuit 336 may provide victim addresses based on the current row address XADD when the signal Capture is provided. The victim addresses are stored in a targeted refresh queue 338. With timing based on AREF, a refresh logic circuit 344 may provide either an auto-refresh address RXADD1 provided by an auto-refresh address circuit 342, or a targeted refresh address RXADD2 from the targeted refresh queue 338.
Since the two counter stacks 330 and 346 may generally function in a similar manner, for the sake of brevity, only the main counter stack 330 will described in detail. It should be understood that sub-counter stack 332 may function in a similar manner, except that it may include counter values which are associated with only one portion of the word lines of the memory.
The main counter stack 330 may be a stack of registers, each of which may store a count value. Each register (or ‘file’) of the main counter stack 330 may include a number of latch circuits, each of which may store a bit of information. The number of bits stored in each register may generally be referred to as a width of the stack 330. Together, the bits of each register may represent a number in binary. The number of bits used to represent the count value (e.g., the width of the registers) may be based on a threshold value. In some embodiments, the threshold may be about 3,000, and each register may include 12 latch circuits, and thus the count value may be stored as a 12 bit number (e.g., a number from 0 to 4,095). Other widths of the registers may be used in other example embodiments. In some embodiments, the registers in the main counter stack 330 and the registers in the sub-counter stack 346 may have different widths. In some embodiments, the first threshold value may be 1,000 and the second threshold value may be 3,000.
The decoder 331 may receive the row address XADD and provide one of the count values from the main counter stack 330 to the counter logic circuit 334 based on a value of a subset of the bits of the row address XADD. Each of the count values of the row counter stack 330 may be associated with a portion of the word lines of the memory. Each portion of the word lines may be specified by a value of the subset of the bits of the row address XADD. Each of the count values may be associated with a particular value of the subset of the bits of the row address. Thus, there may be a first count value for a first value of the subset of the row address, a second count value for a second value of the subset of the row address, etc. If the subset of the row address has N possible values, then the row count stack 330 may be N registers deep. In some embodiments, the main counter stack 330 may have a different number of registers (e.g., N) than the sub-counter stack 346 (e.g., M). In some embodiments, the main counter stack 330 and sub-counter stack 346 may have the same number of registers (e.g., N equals M). In some embodiments, M may be smaller than N.
For example, in some embodiments the row address may be 17 bits long to represent 2{circumflex over ( )}17 total word lines in a bank (not including the redundant word lines). The fourth through sixteenth bits (e.g., RA3-16) may be a section address which represents a particular section of the memory, with each section containing 8 word lines, which are addressed by the first through third bits (e.g., RA0-RA2) as a word line address. The decoder 331 may group some of the sections together by ignoring some of the bits of the section address, which may be considered to be a multi-section address. For example the decoder 331 may only pay attention to a multi-section address including the fourth through thirteenth bits of the row address (e.g., RA3-RA12) such that each multi-section address represents sixteen of the sections. Each count value in the main counter stack 330 may be associated with a value of the multi-section address (e.g., RA3-RA12). Thus the main counter stack 330 may be 1024 registers ‘deep’, one for each of the values of the multi-section address RA3-RA12 (e.g., 2{circumflex over ( )}10 total values). Each count value in such a stack may represent eight word lines (since the word line address is ignored) in each of 16 different sections of the memory (since the section address is truncated into a multi-section address). Thus, in this example embodiment, each count value represents 128 total word lines. Different organizations of the memory and the row address may be used in other examples. In other embodiments, the row address may have more (or fewer) bits to represent more or fewer word lines of a memory.
The sub-counter stack 346 may generally be identical to the main counter stack 330, except the count values in the sub-counter stack 346 may be associated with sub-portions of a portion of the word lines of the memory. Continuing the example from the previous paragraph, a portion of word lines includes 128 total word lines which may be divided equally between sub-portions of the sub-counter stack 346. For example, if accesses to individual word lines is desired, the sub-counter stack 346 may be 128 registers deep, where each count value is associated with a single word line. If a smaller stack is desired, multiple word lines may be included in each sub-portion. For example, the 128 word lines may be grouped into sub-portions including eight word lines. In this example, the sub-counter stack 346 may be 16 registers deep. The decoder 347 may receive the row address XADD and provide one of the count values from the sub-counter stack 346 to the counter logic circuit 348 based on a value of a subset of the bits of the row address XADD. In some embodiments, the subset of bits of the row address XADD may be based, at least in part, on the signal Watch provided by the first counter logic circuit 334. The signal Watch may indicate which portion of the word lines the sub-counter stack 346 is assigned to monitor and the subset of bits may be based on the portion assigned to the sub-counter stack 346. Thus, in some embodiments, the word lines of the memory associated with each count value in the sub-counter stack 346 may be dynamically assigned.
Responsive to the signal Capture provided by the second counter logic circuit 348, the address circuit 336 may determine and provide victim addresses based on the row address XADD (e.g., the same row address that caused Capture to be provided). The steal address circuit 336 may only receive (and/or only pay attention to) a subset of the bits of the row address XADD. In some embodiments, the address circuit 336 may use the same subset of the row address as the sub-counter stack 346. The address circuits 336 may provide a number of victim addresses which include victim addresses associated with all of the word lines represented by the subset of the row address. In some embodiments, each victim address may represent multiple word lines of the memory, and all of the word lines represented by a given victim address may be refreshed simultaneously. In some embodiments, each victim address may represent a single word line of the memory. In some applications, using the same subset of the bits of the row address XADD as the sub-counter stack 346 may result in the generation of a smaller number of victim row addresses than if the address circuit 336 used the same subset of the bits of the row address XADD as the main counter stack 330.
In other embodiments, the sub-counter stack 346, instead of having a decoder 347, may include additional fields for storing row addresses of word lines corresponding to the row address XADD. Each counter C_ADD0-M may be associated with a row address in the sub-counter stack 346. In these embodiments, instead of capturing the current row address XADD, the sub-counter stack 346 may provide one or more stored row addresses to the address circuit 336. The address circuit 336 may then use the received row address to generate the victim row addresses.
The targeted refresh queue 338 may be a register stack which stores the victim addresses provided by the address circuit 336. Each register of the targeted refresh queue 338 may include a number of bits to store a victim address provided by the address circuit 336. Each register of the targeted refresh queue 338 may also include one or more bits which represent an empty flag 339. In some embodiments, the empty flag 339 may be a single bit, which may be at a low logical level when a victim address is stored in that register which has not been refreshed (e.g., to indicate that the register is full), and may be at a high logical level when there is either no victim address stored in the register, or the victim address has already been refreshed (e.g., to indicate that the register is empty and ready to store a new victim address).
The targeted refresh queue 338 includes an extraction pointer 340 and an insertion pointer 341. The extraction pointer 340 indicates a register which is the next to provide a victim address as the targeted refresh address RXADD2. The insertion pointer 341 indicates a register where the next victim address should be added to the targeted refresh queue 338. After a victim address is extracted, the extraction pointer 340 may move to a next register in the targeted refresh queue 338. After an address is inserted into a register, the insertion pointer 341 may move to a next register in the targeted refresh queue 338. After reaching a last register in the targeted refresh queue 338, the pointers 340, 341 may return to a first register in the targeted refresh queue 338. In some embodiments, the targeted refresh queue 338 may be, for example, 100 registers deep.
Alternatively, in some embodiments, the positions of the address circuit 336 and targeted refresh queue 338 may be reversed. That is, the targeted refresh queue 338 may capture the current row address XADD responsive to the signal Capture and the aggressor rows may be stored in the targeted refresh queue 338. Then, for each targeted refresh operations, the address circuit 336 may receive an address from the targeted refresh queue 338 and calculate one or more victim addresses based on the aggressor address provided by the targeted refresh queue 338.
The refresh logic circuit 344 provides the refresh address RXADD with a timing based on the signal AREF. In some embodiments, the refresh logic circuit 344 may provide a refresh address RXADD each time there is an occurrence of AREF. In some embodiments, the refresh logic circuit 344 may provide multiple refresh addresses RXADD responsive to each occurrence of AREF. For example, the refresh logic circuit 344 may provide a set number of ‘pumps’ responsive to receiving an occurrence of AREF, and a refresh address RXADD may be provided for each pump.
Each time the refresh logic circuit 344 provides a refresh address RXADD, either an auto-refresh address RXADD1 or a targeted refresh address RXADD2 may be provided as the refresh address RXADD. The auto-refresh address RXADD1 may be provided by an auto-refresh address circuit 342. Each auto-refresh address RXADD1 may be associated with a number of word lines of the memory. After an auto-refresh address RXADD1 is provided, the auto-refresh address circuit 342 may provide a next auto-refresh address RXADD1 associated with a next group of word lines in a sequence. The auto-refresh address circuit 342 may provide the auto-refresh addresses RXADD1 in a sequence such that over time all the word lines of the memory array are refreshed by the auto-refresh addresses RXADD1. After a last auto-refresh address RXADD1 in the sequence is provided, the first auto-refresh address RXADD1 in the sequence may be provided again. In some embodiments, the auto-refresh address circuit 342 may determine the sequence of auto-refresh addresses with internal logic. For example, one or more portions of the auto-refresh address RXADD1 may be incremented after each auto-refresh address RXADD1 is provided to determine a next auto-refresh address RXADD1.
In some embodiments, the refresh logic circuit 344 may determine whether to provide an auto-refresh address RXADD1 or a targeted refresh address RXADD2 based on the state of the targeted refresh queue 338. In some embodiments, the refresh logic circuit 344 may provide targeted refresh addresses RXADD2 from the targeted refresh queue 338 as the refresh address RXADD as long as there is at least one victim address stored in the targeted refresh queue 338 and may provide the auto-refresh address RXADD1 as the refresh address RXADD if the targeted refresh queue 338 is empty. For example, the refresh logic circuit 344 may determine if the targeted refresh queue 338 is empty based on a state of the empty flags 339. If all of the empty flags 339 are at a high logical level, then it may indicate that the targeted refresh queue 338 is empty, and the refresh logic circuit 344 may provide an auto-refresh address RXADD1 as the refresh address RXADD.
Each targeted refresh address RXADD2 may be one of the victim addresses stored in the targeted refresh queue 338. Each time a targeted refresh address RXADD2 is provided, the empty flag 339 in the register of the targeted refresh queue 338 that contained that address RXADD2 may be raised to a high logical level to indicate that the register is now empty.
In other embodiments, the refresh logic circuit 344 may provide the refresh address RXADD with set timeslots for targeted refresh addresses RXADD2 and auto-refresh addresses RXADD1. For example, the refresh logic circuit 244 may provide the auto-refresh address RXADD1 a certain number of times, and then provide the targeted refresh RXADD2 a number of times, and then start providing auto-refresh addresses RXADD1 again. In some embodiments, when the targeted refresh queue 338 is empty and the refresh logic circuit 344 would provide a targeted refresh address RXADD2, the refresh logic circuit 344 may skip providing the targeted refresh address and provide an auto-refresh address instead. In other embodiments, when the targeted refresh queue 338 is empty, during a targeted refresh timeslot, no address may be provided, and a refresh operation may not be performed.
In some applications, multiple portions of word lines monitored by the main counter stack 330 may cross the first threshold value in a short period of time. Accordingly, it may be desirable to include multiple sub-counter stacks 346 to simultaneously monitor multiple portions of word lines. Furthermore, in some applications, the sub-portions of the sub-counter stack 346 may still correspond to a large number of word lines which require a significant number of victim addresses to be generated. Accordingly, it may be desirable to include multiple sub-counter stacks 346 to further prioritize the victim addresses to be generated.
The main counter stack 430 may have a structure and operation similar to that of main counter stack 330 shown in
If a second count value associated with another particular portion of word lines of the memory, for example, C_Portion2, crosses the first threshold value, accesses to sub-portions of the portion of word lines of the memory associated with C_Portion2 may also be tracked by one of the sub-counter stacks, for example, sub-counter stack 446B. Both sub-counter stacks 446A and 446B may provide Capture signals (e.g., via counter logic circuits not shown) as necessary when count values associated with sub-portions of the portion of word lines exceed a second threshold value.
Typically, the number of sub-counter stacks 446A-M is less than the number of count values in the main counter stack 430. Including multiple sub-counter stacks 446A-M may allow parallel tracking of accesses to different portions of word lines in the memory. This may permit mitigation of row hammers in different portions of word lines that occur simultaneously or in quick succession.
The main counter stack 530 may have a structure and operation similar to that of main counter stack 330 shown in
Including multiple sub-counter stacks 546A-Z in series with the main counter stack 530 may reduce a number of victim addresses required to be generated. For example, each count value C_Portion0-N may be associated with hundreds or possibly over 1,000 word lines. Continuing this example, each count value C_ADD0-M of sub-counter stack 546A may be associated with over a hundred word lines. Even if victim addresses are provided only for a single sub-portion of the word lines associated a count value CADD0-M of sub-counter stack 546A, this may still be more victim addresses than can be reasonably completed in the time allowed for targeted refresh operations. Furthermore, many of the word lines associated with the victim addresses are likely to not actually be victims of a row hammer. Providing additional sub-counter stacks 546B-Z may allow the sub-portion of word lines tracked by sub-counter stack 546A to be further sub-divided and tracked to reduce the number of victim addresses generated. For example, a number of word lines associated with a count value in sub-counter stack 546Z may be less than a number of word lines associated with a count value in sub-counter stack 546B. In some embodiments, the final sub-counter stack 546Z may have count values associated with individual word lines.
Furthermore, providing sub-counter stacks 546A-Z in series may allow the main counter stack 530 and/or sub-counter stacks 546A-Z to be shallower, that is, fewer registers may need to be included in the stack. The sizes of the main counter stack 530 and subsequent sub-counter stacks 546A-Z may be optimized based on the number of sub-counter stacks 546A-Z, threshold values, and/or number of victim addresses to be generated.
In some embodiments, the structure of the main counter stacks and sub-counter stacks shown in
At block 602, a step of “Tracking accesses to word lines in a memory” may be performed. Tracking accesses may include monitoring row addresses received from a row decoder and updating corresponding count values in a register stack in some embodiments. Each of the count values may be associated with a portion of the word lines in the memory. At block 604, a step of “Comparing count values to a first threshold value” may be performed. If one of the count values meets or exceeds the first threshold value, at block 606, a step of “Tracking accesses to a portion of the word lines” may be performed. Tracking accesses may include monitoring row addresses received from the row decoder and updating corresponding count values in a second register stack in some embodiments. Each of the count values may be associated with a sub-portion of the portion of word lines in the memory. In some embodiments, the sub-portions are mutually exclusive. That is, none of the sub-portions include the same word lines of the portion of word lines.
At block 608, a step of “Comparing count values to a second threshold value,” may be performed. In some embodiments, the second threshold value may be greater than the first threshold value. If one of the count values meets or exceeds the second threshold value, at block 610, a step of “Generating victim addresses” may be performed. In some embodiments, the victim addresses may be based off of the word lines of the sub-portion associated with the count value that exceeded the second threshold value.
In some embodiments, between blocks 604 and 606, the count value associated with the portion of the word lines that exceeded the first threshold value may be adjusted to a value between an initial value (e.g., 0) and the threshold value (e.g., 1,5000). In some embodiments, between blocks 608 and 610, the count value associated with the sub-portion of the word lines that exceeded the second threshold value may be reset to an initial value. In some embodiments, after block 610, the victim addresses may be provided to a targeted address queue for refreshing during subsequent refresh operations. In some embodiments, the steps in blocks 602 and 604 may continue to be performed as blocks 606, 608, and/or 610 are performed.
The apparatuses and methods described herein may allow for determining which sub-portion of a portion of word lines associated with a count value are being hammered and only refresh victim word lines associated with the sub-portion. This may reduce the number of victim addresses required to be generated and refreshed. In some applications, refreshing fewer victim word lines may reduce power consumption and/or operation time dedicated to targeted refresh operations. Furthermore, in some applications, by optimizing the size of the main counter stack and the one or more sub-counter stacks, the overall chip space required by the counter stack circuits may be reduced. In some applications, dividing the tracking between the main counter stack and the sub-counter stacks may provide flexibility when determining where to locate the counter stacks on the chip.
Of course, it is to be appreciated that any one of the examples, embodiments or processes described herein may be combined with one or more other examples, embodiments and/or processes or be separated and/or performed amongst separate devices or device portions in accordance with the present systems, devices and methods.
Finally, the above-discussion is intended to be merely illustrative of the present system and should not be construed as limiting the appended claims to any particular embodiment or group of embodiments. Thus, while the present system has been described in particular detail with reference to exemplary embodiments, it should also be appreciated that numerous modifications and alternative embodiments may be devised by those having ordinary skill in the art without departing from the broader and intended spirit and scope of the present system as set forth in the claims that follow. Accordingly, the specification and drawings are to be regarded in an illustrative manner and are not intended to limit the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
1158364 | Bibb | Oct 1915 | A |
3633175 | Harper | Jan 1972 | A |
5291198 | Dingwall et al. | Mar 1994 | A |
5299159 | Balistreri et al. | Mar 1994 | A |
5422850 | Sukegawa et al. | Jun 1995 | A |
5638317 | Tran | Jun 1997 | A |
5699297 | Yamazaki et al. | Dec 1997 | A |
5768196 | Bloker et al. | Jun 1998 | A |
5933377 | Hidaka | Aug 1999 | A |
5943283 | Wong et al. | Aug 1999 | A |
5970507 | Kato et al. | Oct 1999 | A |
5999471 | Choi | Dec 1999 | A |
6002629 | Kim et al. | Dec 1999 | A |
6011734 | Pappert | Jan 2000 | A |
6061290 | Shirley | May 2000 | A |
6212118 | Fujita | Apr 2001 | B1 |
6310806 | Higashi et al. | Oct 2001 | B1 |
6317381 | Gans et al. | Nov 2001 | B1 |
6373738 | Towler et al. | Apr 2002 | B1 |
6392952 | Chen et al. | May 2002 | B1 |
6424582 | Ooishi | Jul 2002 | B1 |
6434064 | Nagai | Aug 2002 | B2 |
6452868 | Fister | Sep 2002 | B1 |
6480931 | Buti et al. | Nov 2002 | B1 |
6515928 | Sato et al. | Feb 2003 | B2 |
6567340 | Nataraj et al. | May 2003 | B1 |
6950364 | Kim | Sep 2005 | B2 |
7027343 | Sinha et al. | Apr 2006 | B2 |
7057960 | Fiscus et al. | Jun 2006 | B1 |
7082070 | Hong | Jul 2006 | B2 |
7187607 | Koshikawa et al. | Mar 2007 | B2 |
7203113 | Takahashi et al. | Apr 2007 | B2 |
7203115 | Eto et al. | Apr 2007 | B2 |
7209402 | Shinozaki et al. | Apr 2007 | B2 |
7215588 | Lee | May 2007 | B2 |
7283380 | Srinivasan et al. | Oct 2007 | B1 |
7319602 | Srinivasan et al. | Jan 2008 | B1 |
7444577 | Best et al. | Oct 2008 | B2 |
7551502 | Dono et al. | Jun 2009 | B2 |
7565479 | Best et al. | Jul 2009 | B2 |
7830742 | Han | Nov 2010 | B2 |
8174921 | Kim et al. | May 2012 | B2 |
8400805 | Yoko | Mar 2013 | B2 |
8451677 | Okahiro et al. | May 2013 | B2 |
8625360 | Iwamoto et al. | Jan 2014 | B2 |
8681578 | Narui | Mar 2014 | B2 |
8756368 | Best et al. | Jun 2014 | B2 |
8811100 | Ku | Aug 2014 | B2 |
8862973 | Zimmerman et al. | Oct 2014 | B2 |
8938573 | Greenfield et al. | Jan 2015 | B2 |
9032141 | Bains et al. | May 2015 | B2 |
9047978 | Bell et al. | Jun 2015 | B2 |
9058900 | Kang | Jun 2015 | B2 |
9087554 | Park | Jul 2015 | B1 |
9087602 | Youn et al. | Jul 2015 | B2 |
9117544 | Bains et al. | Aug 2015 | B2 |
9123447 | Lee et al. | Sep 2015 | B2 |
9153294 | Kang | Oct 2015 | B2 |
9190137 | Kim et al. | Nov 2015 | B2 |
9190139 | Jung et al. | Nov 2015 | B2 |
9251885 | Greenfield et al. | Feb 2016 | B2 |
9286964 | Halbert et al. | Mar 2016 | B2 |
9299457 | Chun et al. | Mar 2016 | B2 |
9311985 | Lee et al. | Apr 2016 | B2 |
9324398 | Jones et al. | Apr 2016 | B2 |
9384821 | Bains et al. | Jul 2016 | B2 |
9390782 | Best et al. | Jul 2016 | B2 |
9412432 | Narui et al. | Aug 2016 | B2 |
9424907 | Fujishiro | Aug 2016 | B2 |
9484079 | Lee | Nov 2016 | B2 |
9514850 | Kim | Dec 2016 | B2 |
9570143 | Lim et al. | Feb 2017 | B2 |
9646672 | Kim et al. | May 2017 | B1 |
9672889 | Lee et al. | Jun 2017 | B2 |
9685240 | Park | Jun 2017 | B1 |
9691466 | Kim | Jun 2017 | B1 |
9697913 | Mariani et al. | Jul 2017 | B1 |
9734887 | Tavva | Aug 2017 | B1 |
9741409 | Jones et al. | Aug 2017 | B2 |
9741447 | Akamatsu | Aug 2017 | B2 |
9747971 | Bains et al. | Aug 2017 | B2 |
9761297 | Tomishima | Sep 2017 | B1 |
9786351 | Lee et al. | Oct 2017 | B2 |
9799391 | Wei | Oct 2017 | B1 |
9805782 | Liou | Oct 2017 | B1 |
9805783 | Ito et al. | Oct 2017 | B2 |
9818469 | Kim et al. | Nov 2017 | B1 |
9847118 | Won | Dec 2017 | B1 |
9865326 | Bains et al. | Jan 2018 | B2 |
9865328 | Desimone et al. | Jan 2018 | B1 |
9922694 | Akamatsu | Mar 2018 | B2 |
9934143 | Bains et al. | Apr 2018 | B2 |
9953696 | Kim | Apr 2018 | B2 |
10032501 | Ito et al. | Jul 2018 | B2 |
10083737 | Bains et al. | Sep 2018 | B2 |
10090038 | Shin | Oct 2018 | B2 |
10134461 | Bell et al. | Nov 2018 | B2 |
10147472 | Jones et al. | Dec 2018 | B2 |
10153031 | Akamatsu | Dec 2018 | B2 |
10170174 | Ito et al. | Jan 2019 | B1 |
10176860 | Mylavarapu | Jan 2019 | B1 |
10210925 | Bains et al. | Feb 2019 | B2 |
10297305 | Moon et al. | May 2019 | B1 |
10339994 | Ito et al. | Jul 2019 | B2 |
10381327 | Ramachandra et al. | Aug 2019 | B2 |
10387276 | Ryu et al. | Aug 2019 | B2 |
10446216 | Oh et al. | Oct 2019 | B2 |
10490251 | Wolff | Nov 2019 | B2 |
10600462 | Augustine et al. | Mar 2020 | B2 |
10600491 | Chou et al. | Mar 2020 | B2 |
10607686 | Akamatsu | Mar 2020 | B2 |
10629286 | Lee et al. | Apr 2020 | B2 |
10679710 | Hirashima et al. | Jun 2020 | B2 |
10705900 | Jin | Jul 2020 | B2 |
10770127 | Shore et al. | Sep 2020 | B2 |
10811066 | Jones et al. | Oct 2020 | B2 |
10832792 | Penney et al. | Nov 2020 | B1 |
10861519 | Jones et al. | Dec 2020 | B2 |
10867660 | Akamatsu | Dec 2020 | B2 |
10930335 | Bell et al. | Feb 2021 | B2 |
10943636 | Wu et al. | Mar 2021 | B1 |
10950289 | Ito et al. | Mar 2021 | B2 |
10964378 | Ayyapureddi et al. | Mar 2021 | B2 |
11011215 | Parry et al. | May 2021 | B1 |
11043254 | Enomoto et al. | Jun 2021 | B2 |
11139015 | Brown et al. | Oct 2021 | B2 |
11152050 | Morohashi et al. | Oct 2021 | B2 |
11158364 | Penney et al. | Oct 2021 | B2 |
11158373 | Penney et al. | Oct 2021 | B2 |
11200942 | Jenkinson et al. | Dec 2021 | B2 |
11222682 | Enomoto et al. | Jan 2022 | B1 |
11257535 | Shore et al. | Feb 2022 | B2 |
11264096 | Schreck et al. | Mar 2022 | B2 |
20010008498 | Ooishi | Jul 2001 | A1 |
20020007476 | Kishino | Jan 2002 | A1 |
20020078311 | Matsuzaki et al. | Jun 2002 | A1 |
20020080677 | Watanabe et al. | Jun 2002 | A1 |
20020181301 | Takahashi et al. | Dec 2002 | A1 |
20030063512 | Takahashi et al. | Apr 2003 | A1 |
20030067825 | Shimano et al. | Apr 2003 | A1 |
20030090400 | Barker | May 2003 | A1 |
20030123301 | Jang et al. | Jul 2003 | A1 |
20030193829 | Morgan et al. | Oct 2003 | A1 |
20030231540 | Lazar et al. | Dec 2003 | A1 |
20040004856 | Sakimura et al. | Jan 2004 | A1 |
20040008544 | Shinozaki et al. | Jan 2004 | A1 |
20040022093 | Lee | Feb 2004 | A1 |
20040052142 | Ikehashi et al. | Mar 2004 | A1 |
20040114446 | Takahashi et al. | Jun 2004 | A1 |
20040130959 | Kawaguchi | Jul 2004 | A1 |
20040174757 | Garverick et al. | Sep 2004 | A1 |
20040184323 | Mori et al. | Sep 2004 | A1 |
20040218431 | Chung et al. | Nov 2004 | A1 |
20050041502 | Perner | Feb 2005 | A1 |
20050105315 | Shin et al. | May 2005 | A1 |
20050243629 | Lee | Nov 2005 | A1 |
20050265104 | Remaklus et al. | Dec 2005 | A1 |
20060083099 | Bae et al. | Apr 2006 | A1 |
20060087903 | Riho et al. | Apr 2006 | A1 |
20060176744 | Stave | Aug 2006 | A1 |
20060262616 | Chen | Nov 2006 | A1 |
20070008799 | Dono et al. | Jan 2007 | A1 |
20070014174 | Ohsawa | Jan 2007 | A1 |
20070028068 | Golding et al. | Feb 2007 | A1 |
20070030746 | Best et al. | Feb 2007 | A1 |
20070033339 | Best et al. | Feb 2007 | A1 |
20070133330 | Ohsawa | Jun 2007 | A1 |
20070230264 | Eto | Oct 2007 | A1 |
20070237016 | Miyamoto et al. | Oct 2007 | A1 |
20070297252 | Singh | Dec 2007 | A1 |
20080028260 | Oyagi et al. | Jan 2008 | A1 |
20080931068 | Yoo et al. | Feb 2008 | |
20080062742 | Wang | Mar 2008 | A1 |
20080126893 | Harrand et al. | May 2008 | A1 |
20080130394 | Dono et al. | Jun 2008 | A1 |
20080181048 | Han | Jul 2008 | A1 |
20080224742 | Pomichter | Sep 2008 | A1 |
20080253212 | Iida et al. | Oct 2008 | A1 |
20080266990 | Loeffler | Oct 2008 | A1 |
20080288720 | Atwal et al. | Nov 2008 | A1 |
20080301362 | Cavanna et al. | Dec 2008 | A1 |
20080316845 | Wang et al. | Dec 2008 | A1 |
20090021999 | Tanimura et al. | Jan 2009 | A1 |
20090059641 | Jeddeloh | Mar 2009 | A1 |
20090077571 | Gara et al. | Mar 2009 | A1 |
20090161457 | Wakimoto | Jun 2009 | A1 |
20090168571 | Pyo et al. | Jul 2009 | A1 |
20090185440 | Lee | Jul 2009 | A1 |
20090201752 | Riho et al. | Aug 2009 | A1 |
20090213675 | Shino | Aug 2009 | A1 |
20090251971 | Futatsuyama | Oct 2009 | A1 |
20090296510 | Lee et al. | Dec 2009 | A1 |
20100005217 | Jeddeloh | Jan 2010 | A1 |
20100005376 | Laberge et al. | Jan 2010 | A1 |
20100054011 | Kim | Mar 2010 | A1 |
20100074042 | Fukuda et al. | Mar 2010 | A1 |
20100080074 | Ohmaru et al. | Apr 2010 | A1 |
20100110809 | Kobayashi et al. | May 2010 | A1 |
20100110810 | Kobayashi | May 2010 | A1 |
20100131812 | Mohammad | May 2010 | A1 |
20100157693 | Iwai et al. | Jun 2010 | A1 |
20100182863 | Fukiage | Jul 2010 | A1 |
20100329069 | Ito et al. | Dec 2010 | A1 |
20110026290 | Noda et al. | Feb 2011 | A1 |
20110051530 | Kushida | Mar 2011 | A1 |
20110055495 | Remaklus, Jr. et al. | Mar 2011 | A1 |
20110069572 | Lee et al. | Mar 2011 | A1 |
20110122987 | Neyer | May 2011 | A1 |
20110216614 | Hosoe | Sep 2011 | A1 |
20110225355 | Kajigaya | Sep 2011 | A1 |
20110286271 | Chen | Nov 2011 | A1 |
20110310648 | Iwamoto et al. | Dec 2011 | A1 |
20110317462 | Gyllenhammer et al. | Dec 2011 | A1 |
20120014199 | Narui | Jan 2012 | A1 |
20120059984 | Kang et al. | Mar 2012 | A1 |
20120151131 | Kilmer et al. | Jun 2012 | A1 |
20120213021 | Riho et al. | Aug 2012 | A1 |
20120254472 | Ware et al. | Oct 2012 | A1 |
20130003467 | Klein | Jan 2013 | A1 |
20130003477 | Park et al. | Jan 2013 | A1 |
20130057173 | Yao et al. | Mar 2013 | A1 |
20130107623 | Kavalipurapu et al. | May 2013 | A1 |
20130173971 | Zimmerman | Jul 2013 | A1 |
20130254475 | Perego et al. | Sep 2013 | A1 |
20130279284 | Jeong | Oct 2013 | A1 |
20130304982 | Jung et al. | Nov 2013 | A1 |
20140006703 | Bains et al. | Jan 2014 | A1 |
20140006704 | Greenfield et al. | Jan 2014 | A1 |
20140013169 | Kobla et al. | Jan 2014 | A1 |
20140013185 | Kobla et al. | Jan 2014 | A1 |
20140050004 | Mochida | Feb 2014 | A1 |
20140078841 | Chopra | Mar 2014 | A1 |
20140078842 | Oh et al. | Mar 2014 | A1 |
20140078845 | Song | Mar 2014 | A1 |
20140089576 | Bains et al. | Mar 2014 | A1 |
20140095780 | Bains et al. | Apr 2014 | A1 |
20140095786 | Moon et al. | Apr 2014 | A1 |
20140119091 | You et al. | May 2014 | A1 |
20140136763 | Li et al. | May 2014 | A1 |
20140143473 | Kim et al. | May 2014 | A1 |
20140177370 | Halbert et al. | Jun 2014 | A1 |
20140189215 | Kang et al. | Jul 2014 | A1 |
20140189228 | Greenfield et al. | Jul 2014 | A1 |
20140219043 | Jones et al. | Aug 2014 | A1 |
20140237307 | Kobla et al. | Aug 2014 | A1 |
20140241099 | Seo et al. | Aug 2014 | A1 |
20140254298 | Dally | Sep 2014 | A1 |
20140269021 | Yang et al. | Sep 2014 | A1 |
20140281206 | Crawford et al. | Sep 2014 | A1 |
20140281207 | Mandava et al. | Sep 2014 | A1 |
20140292375 | Angelini et al. | Oct 2014 | A1 |
20140293725 | Best et al. | Oct 2014 | A1 |
20140317344 | Kim | Oct 2014 | A1 |
20140355332 | Youn et al. | Dec 2014 | A1 |
20140369109 | Lee et al. | Dec 2014 | A1 |
20140379978 | Kim et al. | Dec 2014 | A1 |
20150049567 | Chi | Feb 2015 | A1 |
20150055420 | Bell et al. | Feb 2015 | A1 |
20150078112 | Huang | Mar 2015 | A1 |
20150089326 | Joo et al. | Mar 2015 | A1 |
20150155027 | Abe et al. | Jun 2015 | A1 |
20150162067 | Kirn et al. | Jun 2015 | A1 |
20150170728 | Jung et al. | Jun 2015 | A1 |
20150199126 | Jayasena et al. | Jul 2015 | A1 |
20150206572 | Lim et al. | Jul 2015 | A1 |
20150213872 | Mazumder et al. | Jul 2015 | A1 |
20150213877 | Darel | Jul 2015 | A1 |
20150228341 | Watanabe et al. | Aug 2015 | A1 |
20150243339 | Bell et al. | Aug 2015 | A1 |
20150255140 | Song | Sep 2015 | A1 |
20150262652 | Igarashi | Sep 2015 | A1 |
20150279441 | Greenberg | Oct 2015 | A1 |
20150279442 | Hwang | Oct 2015 | A1 |
20150294711 | Gaither et al. | Oct 2015 | A1 |
20150340077 | Akamatsu | Nov 2015 | A1 |
20150356048 | King | Dec 2015 | A1 |
20160019940 | Jang et al. | Jan 2016 | A1 |
20160027498 | Ware et al. | Jan 2016 | A1 |
20160027531 | Jones et al. | Jan 2016 | A1 |
20160027532 | Kim | Jan 2016 | A1 |
20160042782 | Narui | Feb 2016 | A1 |
20160078845 | Lin et al. | Mar 2016 | A1 |
20160078911 | Fujiwara et al. | Mar 2016 | A1 |
20160078918 | Hyun et al. | Mar 2016 | A1 |
20160086649 | Hong et al. | Mar 2016 | A1 |
20160086651 | Kim | Mar 2016 | A1 |
20160093402 | Kitagawa et al. | Mar 2016 | A1 |
20160099043 | Tu | Apr 2016 | A1 |
20160111140 | Joo et al. | Apr 2016 | A1 |
20160125931 | Doo et al. | May 2016 | A1 |
20160133314 | Hwang et al. | May 2016 | A1 |
20160140243 | Adams et al. | May 2016 | A1 |
20160163372 | Lee et al. | Jun 2016 | A1 |
20160172056 | Huh | Jun 2016 | A1 |
20160180917 | Chishti et al. | Jun 2016 | A1 |
20160180921 | Jeong | Jun 2016 | A1 |
20160196863 | Shin et al. | Jul 2016 | A1 |
20160202926 | Benedict | Jul 2016 | A1 |
20160211008 | Benedict et al. | Jul 2016 | A1 |
20160225433 | Bains et al. | Aug 2016 | A1 |
20160225461 | Tuers et al. | Aug 2016 | A1 |
20160336060 | Shin | Nov 2016 | A1 |
20160343423 | Shido | Nov 2016 | A1 |
20170011792 | Oh et al. | Jan 2017 | A1 |
20170076779 | Bains et al. | Mar 2017 | A1 |
20170092350 | Halbert et al. | Mar 2017 | A1 |
20170117030 | Fisch et al. | Apr 2017 | A1 |
20170133085 | Kim et al. | May 2017 | A1 |
20170139641 | Cha et al. | May 2017 | A1 |
20170140807 | Sun et al. | May 2017 | A1 |
20170140811 | Joo | May 2017 | A1 |
20170148504 | Saifuddin et al. | May 2017 | A1 |
20170177246 | Miller et al. | Jun 2017 | A1 |
20170186481 | Oh et al. | Jun 2017 | A1 |
20170213586 | Kang et al. | Jul 2017 | A1 |
20170221546 | Loh et al. | Aug 2017 | A1 |
20170263305 | Cho | Sep 2017 | A1 |
20170287547 | Ito et al. | Oct 2017 | A1 |
20170323675 | Jones et al. | Nov 2017 | A1 |
20170352399 | Yokoyama et al. | Dec 2017 | A1 |
20170371742 | Shim | Dec 2017 | A1 |
20170372767 | Kang et al. | Dec 2017 | A1 |
20180005690 | Morgan. et al. | Jan 2018 | A1 |
20180025770 | Ito et al. | Jan 2018 | A1 |
20180025772 | Lee et al. | Jan 2018 | A1 |
20180060194 | Ryu et al. | Mar 2018 | A1 |
20180061483 | Morgan | Mar 2018 | A1 |
20180082737 | Lee | Mar 2018 | A1 |
20180084314 | Koyama | Mar 2018 | A1 |
20180090199 | Kim et al. | Mar 2018 | A1 |
20180096719 | Tomishimna et al. | Apr 2018 | A1 |
20180102776 | Chandrasekar et al. | Apr 2018 | A1 |
20180107417 | Shechter et al. | Apr 2018 | A1 |
20180114561 | Fisch et al. | Apr 2018 | A1 |
20180114565 | Lee | Apr 2018 | A1 |
20180158504 | Akamatsu | Jun 2018 | A1 |
20180182445 | Lee et al. | Jun 2018 | A1 |
20180203621 | Ahn et al. | Jul 2018 | A1 |
20180218767 | Wolff | Aug 2018 | A1 |
20180261268 | Hyun et al. | Sep 2018 | A1 |
20180294028 | Lee et al. | Oct 2018 | A1 |
20180308539 | Ito et al. | Oct 2018 | A1 |
20180341553 | Koudele et al. | Nov 2018 | A1 |
20180366182 | Hyun et al. | Dec 2018 | A1 |
20190013059 | Akamatsu | Jan 2019 | A1 |
20190043558 | Suh et al. | Feb 2019 | A1 |
20190051344 | Bell et al. | Feb 2019 | A1 |
20190066759 | Nale | Feb 2019 | A1 |
20190066762 | Koya | Feb 2019 | A1 |
20190088315 | Saenz et al. | Mar 2019 | A1 |
20190088316 | Inuzuka et al. | Mar 2019 | A1 |
20190096492 | Cai | Mar 2019 | A1 |
20190103147 | Jones et al. | Apr 2019 | A1 |
20190130961 | Bell et al. | May 2019 | A1 |
20190139599 | Ito et al. | May 2019 | A1 |
20190147941 | Qin | May 2019 | A1 |
20190147964 | Yun et al. | May 2019 | A1 |
20190161341 | Howe | May 2019 | A1 |
20190172518 | Chen et al. | Jun 2019 | A1 |
20190196730 | Imran | Jun 2019 | A1 |
20190198078 | Hoang et al. | Jun 2019 | A1 |
20190198096 | Lee | Jun 2019 | A1 |
20190198099 | Mirichigni et al. | Jun 2019 | A1 |
20190205253 | Roberts | Jul 2019 | A1 |
20190207736 | Ben-tovim et al. | Jul 2019 | A1 |
20190228810 | Jones et al. | Jul 2019 | A1 |
20190228813 | Nale et al. | Jul 2019 | A1 |
20190228815 | Morohashi et al. | Jul 2019 | A1 |
20190237132 | Morohashi | Aug 2019 | A1 |
20190243708 | Cha | Aug 2019 | A1 |
20190252020 | Rios et al. | Aug 2019 | A1 |
20190267077 | Ito et al. | Aug 2019 | A1 |
20190279706 | Kim | Sep 2019 | A1 |
20190333573 | Shin et al. | Oct 2019 | A1 |
20190348100 | Smith et al. | Nov 2019 | A1 |
20190348102 | Smith et al. | Nov 2019 | A1 |
20190348103 | Jeong et al. | Nov 2019 | A1 |
20190348107 | Shin et al. | Nov 2019 | A1 |
20190349545 | Koh et al. | Nov 2019 | A1 |
20190362774 | Kuramori et al. | Nov 2019 | A1 |
20190371391 | Cha et al. | Dec 2019 | A1 |
20190385661 | Koo et al. | Dec 2019 | A1 |
20190385667 | Morohashi et al. | Dec 2019 | A1 |
20190386557 | Wang et al. | Dec 2019 | A1 |
20200005857 | Ito et al. | Jan 2020 | A1 |
20200075106 | Tokutomi et al. | Mar 2020 | A1 |
20200082873 | Wolff | Mar 2020 | A1 |
20200090760 | Purahmad et al. | Mar 2020 | A1 |
20200135263 | Brown et al. | Apr 2020 | A1 |
20200194050 | Akamatsu | Jun 2020 | A1 |
20200194056 | Sakurai et al. | Jun 2020 | A1 |
20200201380 | Murali et al. | Jun 2020 | A1 |
20200202921 | Morohashi et al. | Jun 2020 | A1 |
20200211626 | Hiscock et al. | Jul 2020 | A1 |
20200211633 | Okuma | Jul 2020 | A1 |
20200211636 | Hiscock et al. | Jul 2020 | A1 |
20200251158 | Shore et al. | Aug 2020 | A1 |
20200294576 | Brown et al. | Sep 2020 | A1 |
20200302994 | Enomoto et al. | Sep 2020 | A1 |
20200321049 | Meier et al. | Oct 2020 | A1 |
20200349995 | Shore et al. | Nov 2020 | A1 |
20200365208 | Schreck et al. | Nov 2020 | A1 |
20200381040 | Penney et al. | Dec 2020 | A1 |
20200395072 | Penney et al. | Dec 2020 | A1 |
20210005229 | Hiscock et al. | Jan 2021 | A1 |
20210005240 | Brown et al. | Jan 2021 | A1 |
20210020262 | Penney et al. | Jan 2021 | A1 |
20210026732 | Park et al. | Jan 2021 | A1 |
20210057012 | Ayyapureddi et al. | Feb 2021 | A1 |
20210057013 | Jenkinson et al. | Feb 2021 | A1 |
20210057021 | Wu et al. | Feb 2021 | A1 |
20210065755 | Kim et al. | Mar 2021 | A1 |
20210065764 | Cheng et al. | Mar 2021 | A1 |
20210142852 | Schreck et al. | May 2021 | A1 |
20210158851 | Ayyapureddi et al. | May 2021 | A1 |
20210158860 | Wu et al. | May 2021 | A1 |
20210158861 | Jeong et al. | May 2021 | A1 |
20210201984 | Khasawneh et al. | Jul 2021 | A1 |
20210225432 | Enomoto et al. | Jul 2021 | A1 |
20210241810 | Hollis et al. | Aug 2021 | A1 |
20210265504 | Ishizu et al. | Aug 2021 | A1 |
20210343324 | Brown et al. | Nov 2021 | A1 |
20210350844 | Morohashi et al. | Nov 2021 | A1 |
20210398592 | Penney et al. | Dec 2021 | A1 |
20210407583 | Penney et al. | Dec 2021 | A1 |
Number | Date | Country |
---|---|---|
1195173 | Oct 1998 | CN |
101038785 | Sep 2007 | CN |
101067972 | Nov 2007 | CN |
101331554 | Dec 2008 | CN |
101458658 | Jun 2009 | CN |
101622607 | Jan 2010 | CN |
102113058 | Jun 2011 | CN |
102483952 | May 2012 | CN |
104350546 | Feb 2015 | CN |
106710621 | May 2017 | CN |
107871516 | Apr 2018 | CN |
H0773682 | Mar 1995 | JP |
2005-216429 | Aug 2005 | JP |
2011-258259 | Dec 2011 | JP |
2011-258259 | Dec 2011 | JP |
4911510 | Jan 2012 | JP |
2013-004158 | Jan 2013 | JP |
20150002783 | Jan 2015 | KR |
20170058022 | May 2017 | KR |
1020180064940 | Jun 2018 | KR |
1020180085184 | Jul 2018 | KR |
20190048049 | May 2019 | KR |
2014120477 | Aug 2014 | WO |
2015030991 | Mar 2015 | WO |
2017171927 | Oct 2017 | WO |
2019222960 | Nov 2019 | WO |
2020010010 | Jan 2020 | WO |
2021003085 | Jan 2021 | WO |
Entry |
---|
US 11,264,075 B2, 03/2022, Bell et al. (withdrawn) |
Thomas, et al., “Voltage Source Based Voltage-to-Time Converter”, IEEE, 2020, p. All. |
U.S. Appl. No. 16/546,152 titled “Apparatuses and Methods for Analog Row Access Tracking” filed Aug. 20, 2019, pp. all. |
U.S. Appl. No. 16/548,027 titled “Apparatuses, Systems, and Methods for Analog Row Access Rate Determination” filed Aug. 22, 2019, pp. all. |
U.S. Appl. No. 16/549,942 titled “Apparatuses and Methods for Lossy Row Access Counting” filed Aug. 23, 2019, pp. all. |
U.S. Appl. No. 16/797,658, titled “Apparatuses and Methods for Controlling Refresh Operations”, dated Feb. 21, 2020; pp. all. |
U.S. Appl. No. 15/881,256 entitled ‘Apparatuses and Methods for Detecting a Row Hammer Attack With a Bandpass Filter’ filed Jan. 26, 2018, pp. all. |
U.S. Appl. No. 16/425,525 titled “Apparatuses and Methods for Tracking All Row Accesses” filed May 29, 2019, pp. all. |
U.S. Appl. No. 16/427,105 titled “Apparatuses and Methods for Priority Targeted Refresh Operations” filed May 30, 2019, pp. all. |
U.S. Appl. No. 16/427,140 titled “Apparatuses and Methods for Tracking Row Access Counts Between Multiple Register Stacks” filed May 30, 2019, pp. all. |
U.S. Appl. No. 16/437,811 titled “Apparatuses, Systems, and Methods for Determining Extremum Numerical Values” filed Jun. 11, 2019, pp. all. |
U.S. Appl. No. 15/789,897, entitled “Apparatus and Methods for Refreshing Memory”, filed Oct. 20, 2017; pp. all. |
U.S. Appl. No. 15/796,340, entitled: “Apparatus and Methods for Refreshing Memory” filed Oct. 27, 2017; pp. all. |
U.S. Appl. No. 16/012,679, titled “Apparatuses and Methods for Multiple Row Hammer Refresh Address Sequences”, filed Jun. 19, 2018, pp. all. |
U.S. Appl. No. 16/020,863, titled “Semiconductor Device”, filed Jun. 27, 2018, pp. all. |
U.S. Appl. No. 16/112,471 titled “Apparatuses and Methods for Controlling Refresh Operations” filed Aug. 24, 2018, pp. all. |
U.S. Appl. No. 16/160,801, titled “Apparatuses and Methods for Selective Row Refreshes” filed Oct. 15, 2018, pp. all. |
U.S. Appl. No. 16/176,932, titled “Apparatuses and Methods for Access Based Refresh Timing”, filed Oct. 31, 2018, pp. all. |
U.S. Appl. No. 16/231,327 titled “Apparatuses and Methods for Selective Row Refreshes”, filed Dec. 21, 2018, pp. all. |
U.S. Appl. No. 16/237,291, titled “Apparatus and Methods for Refreshing Memory”, filed Dec. 31, 2018, pp. all. |
U.S. Appl. No. 16/268,818, titled “Apparatuses and Methods for Managing Row Access Counts”, filed Feb. 6, 2019, pp. all. |
U.S. Appl. No. 16/358,587, titled “Semiconductor Device Having Cam That Stores Address Signals”, dated Mar. 19, 2019, pp. all. |
U.S. Appl. No. 16/411,573 titled “Apparatuses, Systems, and Methods for a Content Addressable Memory Cell” filed May 14, 2019, pp. all. |
U.S. Appl. No. 16/411,698 title “Semiconductor Device” filed May 14, 2019, pp. all. |
U.S. Appl. No. 16/427,330 titled “Apparatuses and Methods for Storing Victim Row Data” filed May 30, 2019, pp. all. |
U.S. Appl. No. 16/428,625 titled “Apparatuses and Methods for Tracking Victim Rows” filed May 31, 2019, pp. all. |
U.S. Appl. No. 16/805,197, titled “Apparatuses and Methods for Calculating Row Hammer Refresh Addresses in a Semiconductor Device”, dated Feb. 28, 2020, pp. all. |
U.S. Appl. No. 15/876,566 entitled ‘Apparatuses and Methods for Calculating Row Hammer Refresh Addresses in a Semiconductor Device’ filed Jan. 22, 2018, pp. all. |
U.S. Appl. No. 15/656,084, titled “Apparatuses and Methods for Targeted Refreshing of Memory”, filed Jul. 21, 2017; pp. all. |
PCT Application No. PCT/US18/55821 “Apparatus and Methods for Refreshing Memory” filed Oct. 15, 2018, pp. all. |
U.S. Appl. No. 15/715,846, entitled “Semiconductor Device”, filed Sep. 26, 2017, pp. all. |
U.S. Appl. No. 15/888,993, entitled “Apparatuses and Methods for Controlling Refresh Operations”, filed Feb. 5, 2018, pp. all. |
U.S. Appl. No. 16/190,627 titled “Apparatuses and Methods for Targeted Refreshing of Memory” filed Nov. 14, 2018, pp. all. |
U.S. Appl. No. 16/459,520 titled “Apparatuses and Methods for Monitoring Word Line Accesses”, filed Jul. 1, 2019, pp. all. |
U.S. Appl. No. 15/281,818, entitled: “Semiconductor Device” filed Sep. 30, 2016; pp. all. |
Kim, et al. “Flipping Bits in MemoryWithout Accessing Them: An Experimental Study of DRAM Disturbance Errors”, IEEE, Jun. 2014, 12 pgs. |
U.S. Appl. No. 16/818,981 titled “Apparatuses and Methods for Staggered Timing of Targeted Refresh Operations” filed Mar. 13, 2020, pp. all. |
U.S. Appl. No. 16/824,460, titled “Semiconductor Device Performing Row Hammer Refresh Operation”, dated Mar. 19, 2020, pp. all. |
U.S. Appl. No. 16/025,844, titled “Apparatus and Methods for Triggering Row Hammer Address Sampling”, filed Jul. 2, 2018, pp. all. |
U.S. Appl. No. 16/783,063, titled “Apparatus and Methods for Triggering Row Hammer Address Sampling”, dated Feb. 5, 2020, pp. all. |
U.S. Appl. No. 16/232,837, titled “Apparatuses and Methods for Distributed Targeted Refresh Operations”, filed Dec. 26, 2018, pp. all. |
U.S. Appl. No. 16/818,989, titled “Semiconductor Device Performing Row Hammer Refresh Operation”, dated Mar. 13, 2020, pp. all. |
International Application No. PCT/US19/64028, titled “Semiconductor Device Performing Row Hammer Refresh Operation”, dated Dec. 2, 2019, pp. all. |
International Application No. PCT/US20/26689, titled “Apparatuses and Methods for Staggered Timing of Targeted Refresh Operations”, dated Apr. 3, 2020, pp. all. |
U.S. Appl. No. 16/788,657, titled “Semiconductor Device Performing Row Hammer Refresh Operation”, dated Feb. 12, 2020, pp. all. |
U.S. Appl. No. 15/884,192 entitled ‘Semiconductor Device Performing Row Hammer Refresh Operation’ filed Jan. 30, 2018, pp. all. |
U.S. Appl. No. 16/537,981 titled “Apparatuses and Methods for Controlling Targeted Refresh Rates” filed Aug. 12, 2019, pp. all. |
U.S. Appl. No. 16/655,110 titled “Apparatuses and Methods for Dynamic Targeted Refresh Steals” filed Oct. 16, 2019, pp. all. |
U.S. Appl. No. 16/936,297 titled “Apparatuses and Methods for Managing Row Access Counts” filed Jul. 22, 2020, pp. all. |
U.S. Appl. No. 16/084,119, titled “Apparatuses and Methods for Pure-Time, Self Adopt Sampling for Row Hammer Refresh Sampling”, filed Sep. 11, 2018, pp. all. |
U.S. Appl. No. 16/208,217, titled “Semiconductor Device Performing Row Hammer Refresh Operation”, filed Dec. 3, 2018, pp. all. |
U.S. Appl. No. 16/230,300, titled “Apparatuses and Methods for Staggered Timing of Targeted Refresh Operations” filed Dec. 21, 2018, pp. all. |
U.S. Appl. No. 16/286,187 titled “Apparatuses and Methods for Memory Mat Refresh Sequencing” filed Feb. 26, 2019; pp. all. |
U.S. Appl. No. 16/290,730, titled “Semiconductor Device Performing Row Hammer Refresh Operation”, filed Mar. 1, 2019, pp. all. |
U.S. Appl. No. 16/374,623, titled “Semiconductor Device Performing Row Hammer Refresh Operation”, filed Apr. 3, 2019, pp. all. |
U.S. Appl. No. 16/375,716 titled “Stagger RHR Pumping Scheme Across Die Banks” filed Apr. 4, 2019; pp. all. |
U.S. Appl. No. 16/431,641 titled “Apparatuses and Methods for Controlling Steal Rates” filed Jun. 4, 2019, pp. all. |
U.S. Appl. No. 16/549,411 titled “Apparatuses and Methods for Dynamic Refresh Allocation” filed Aug. 23, 2019, pp. all. |
U.S. Appl. No. 16/682,606, titled “Apparatuses and Methods for Distributing Row Hammer Refresh Events Across a Memory Device”, filed Nov. 13, 2019, pp. all. |
U.S. Appl. No. 16/886,284, titled “Apparatuses and Methods for Access Based Refresh Timing”, dated May 28, 2020, pp. all. |
U.S. Appl. No. 17/102,266, titled “Apparatuses and Methods for Tracking Word Line Accesses”, dated Nov. 23, 2020, pp. all. |
U.S. Appl. No. 17/154,945 titled “Apparatuses, Systems, and Methods for a Content Addressable Memory Cell” filed Jan. 21, 2021, pp. all. |
U.S. Appl. No. 17/168,036 titled “Apparatuses and Methods for Analog Row Access Tracking” filed Feb. 4, 2021, pp. all. |
U.S. Appl. No. 17/170,616 titled “Apparatuses, Systems, and Methods for Analog Row Access Rate Determination” filed Feb. 8, 2021, pp. all. |
U.S. Appl. No. 16/886,284 titled “Apparatuses and Methods for Access Based Refresh Timing” filed May 28, 2020, pp. all. |
U.S. Appl. No. 17/444,925 titled “Apparatuses and Methods for Countering Memory Attacks” filed Aug. 12, 2021. |
U.S. Appl. No. 17/007,069 titled “Apparatuses and Methods for Providing Refresh Addresses” filed Aug. 31, 2020, pp. all. |
U.S. Appl. No. 17/443,056 titled “Apparatuses and Methods for Multiple Row Hammer Refresh Address Sequences” filed Jul. 20, 2021, pp. all. |
U.S. Appl. No. 17/153,555 titled “Apparatuses and Methods for Dynamically Allocated Aggressor Detection” filed Jan. 20, 2021, pp. all. |
U.S. Appl. No. 17/201,941 titled “Apparatuses and Methods for Sketch Circuits for Refresh Binning” filed Mar. 15, 2021, pp. all. |
U.S. Appl. No. 17/301,533 titled “Semiconductor Device Having Cam That Stores Address Signals” filed Apr. 6, 2021, pp. all. |
U.S. Appl. No. 17/375,817 titled “Apparatuses and Methods for Monitoring Word Line Accesses” filed Jul. 14, 2021, pp. all. |
U.S. Appl. No. 16/459,507 titled “Apparatuses and Methods for Adjusting Victim Data”, filed Jul. 1, 2019, pp. all. |
U.S. Appl. No. 17/446,710 titled “Apparatuses, Systems, and Methods for Determining Extremum Numericalvalues” filed Sep. 1, 2021. |
U.S. Appl. No. 17/470,883 titled “Apparatuses and Methods for Tracking Victim Rows” filed Sep. 9, 2021. |
U.S. Appl. No. 17/565,119 titled “Apparatuses and Methods for Row Hammer Counter Mat” filed Dec. 29. 2021. |
U.S. Appl. No. 17/565,187 titled “Apparatuses and Methods for Row Hammer Counter Mat” filed Dec. 29, 2021. |
U.S. Appl. No. 17/456,849 titled “Apparatuses, Systems, and Methods for Main Sketch and Slim Sketch Circuitfor Row Address Tracking” filed Nov. 29, 2021, pp. all pages of application as filed. |
Number | Date | Country | |
---|---|---|---|
20210020223 A1 | Jan 2021 | US |