In many devices, synchronous integrated circuits may be clocked by an external clock signal and perform operations at predetermined times relative to the rising and falling edges of the external clock signal. For example, in dynamic random access memories (“DRAMs”), the timing of external signals, such as command, address and write data signals, is determined by the external clock signal, and the memory device must latch these signals at the proper times to successfully capture the signals. To latch these applied signals, an internal clock signal may be developed based on the external clock signal, and may be conventionally applied to latches contained in the memory to clock the external signals into the latches. The internal clock signal and external clock signal must be synchronized to ensure the latches are clocked at the proper times to successfully capture the external signals.
When a read request is received at a memory, the memory must provide the associated data to a data bus at a time according to defined read latency, which is usually a predetermined number of external tCK after the read request is made by the memory controller. The memory may have its own internal clock system, which converts the external clock signal into one or more internal clock signals using internal clock generation circuits such as a clock buffer and a delay locked loop (“DLL”). Problems with maintaining read data latency arise in high speed DRAMs from the necessity to align data with the external clock using the one or more internal clock signal generated by the internal clock generation circuits.
In order to meet a specified read latency the memory device must be able to count clock signals upon receiving a read command, and activate an output latch to provide the requested data to an output bus relative to the read clock signal. The read command may be latched responsive to an internal clock signal which has a different phase relationship to the external system clock signal from the read clock. Therefore, the timing control must be required between the read clock signal and the internal clock signal when the memory device counts the latency.
Certain details are set forth below to provide a sufficient understanding of embodiments of the disclosure. However, it will be clear to one having skill in the art that embodiments of the disclosure may be practiced without these particular details. Moreover, the particular embodiments of the present disclosure described herein are provided by way of example and should not be used to limit the scope of the disclosure to these particular embodiments.
Referring to
The DLL 110 may provide the LCLK signal based on the PCLK signal. The DLL 110 may adjust a delay of the PCLK signal to provide the LCLK such that timing of the DQ output from the output driver 190 matches the phase of the CLK signal. The DLL 110 may include an adjustable delay line, circuitry that models delays of circuitry of the apparatus 100, and a phase detector that detects a phase difference between the LCLK signal fed through the model delays and the PCLK signal. The DLL 110 may adjust a delay of the adjustable delay line via the DCTL signal. The DCLT signal may also be provided to the latency control circuit 112 to control propagation of the RP signal.
The command decoder 150 may be configured to decode the CMD signal respective to the PCLK signal to provide a pulse on the RP signal to the latency control circuit 112. The CMD signal may be a memory access command, such as a read, write, or on die termination (ODT) command. The latency control circuit 112 may include a latch control circuit 120 coupled to a latch circuit 160. The latch control circuit 120 may receive the PCLK signal, the DCTL signal, and the LCLK signal. The latch control circuit 120 may provide control signals RSELI and RSELO to the latch circuit 160 responsive to the PCLK, DCTL, and LCLK signals. The latch control circuit 120 may include one or more adjustable delay lines that mirror the delay line of the DLL 110, with the delay of the one or more adjustable delay lines controlled by the DCTL signals. Thus, the relative timing of the RSELI control signals to the timing of the RSELO control signals may be related to the relative timing between the PCLK and LCLK signals.
The latch circuit 160 may include latches configured to propagate the RP signal pulse to the RL signal. In some embodiments, the latch circuit 160 may include a set of input latches configured to propagate the RP signal to a set of output latches responsive to the RSELI control signals and the set of output latches may be configured to propagate the RP signal to an output as the RL signal responsive to the RSELO control signals.
The latency control circuit 112 may further include a shifter 180 configured to receive the RL signal pulse from the latch circuit 160 and a count signal N and the LCLK signal from the DLL 110. The N signal may be provided to shifter 180 after the CLK and LCLK signals are synchronized through a series of delay elements of the adjustable delay line of the DLL 110. The N signal may be a count of the number of tCK calculated by the DLL 110 to achieve the locking condition (e.g., a tCK count indicating a latency between the CLK signal and the LCLK signal). The shifter 180 is further configured to receive latency information which indicates a specified latency CL. The shifter 180 may assert the OER/F signals based on the CL, the N signal, and the LCLK signal. The output driver 190 may receive the OER/F signals, the LCLK signal, and input data IDATA, and may propagate the IDATA to data DQ responsive to the OER/F signals and the LCLK signal.
In operation, the apparatus 100 may receive a CLK signal at the input buffer 104 and the CMD signal the command decoder 150, which may be received based on timing of the PCLK signal. When the CMD signal includes a read command, the apparatus 100 may operate according to the read latency CL. The read latency CL may specify a timing of output of the IDATA to the data DQ responsive to the read command based on the CLK signal, which includes time for data to be accessed and provided on an output bus (e.g., via a DQ pad). In an example, the read latency CL may be from 6-10 tCK. The read latency CL may be fixed in the apparatus 100 at a time of manufacture or may be set by a memory controller, such as via the CMD signal. The DLL 110 and the latency control circuit 112 may apply the read latency the IDATA and synchronize the IDATA with the CLK signal.
The DLL 110 may receive the PCLK signal from the input buffer 104, and may provide the LCLK signal, which may be used by the output driver 190 to latch the IDATA data to the DQ of the apparatus 100. The LCLK may have a timing relationship relative to the PCLK signal, which may be determined by the DLL 110, and provided at an output as the N signal. The N signal may be a count of the number of tCK to achieve the locking condition (e.g., a tCK latency between receipt of the CLK signal and the LCLK signal). The locking condition may be achieved such that the LCLK signal at an output of the apparatus 100 matches a phase of the CLK signal. The N signal may be provided to the shifter 180 after the locking condition is achieved. The DLL 110 may also generate the DCTL signal, which may be used to select the delay of the adjustable delay line of the DLL 110.
The command decoder 150 may decode the CMD signal and provide the decoded CMD signal to the latency control circuit 112 as the RP signal. The latency control circuit 112 may use the PCLK and LCLK signals to change timings of internal read command pulses from being relative to the PCLK signal to being relative to the LCLK signal during a memory read operation. The latch control circuit 120 may include a counter configured to count the PCLK signals, and the RSELI control signals may be asserted based on the count of the counter. For example, the latch control circuit 120 may include a decoder that is configured to assert a single one of the RSELI control signals with every clock cycle based on the count provided by the counter. The counter value may also be used to provide the RSELO signals. In one embodiment, the latch control circuit 120 may include one or more adjustable delay lines having delays selected by the DCTL signal that are configured to delay the counter signal values by the same delay as the delay applied to the PCLK signal to provide the LCLK signal. The RSELO control signals may be provided based on the delayed counter signal values. For example, the latch control circuit 120 may include a second decoder that is configured to assert a single one of the RSELO signals with every clock cycle based on the delayed counter signal values. In other embodiments, the RESLI signals may be directly delayed via the one or more adjustable delay lines to provide the RSELO signals.
The RSELI and RSELO signals may be received by the latch circuit 160, and may control propagation of the RP signal to the shifter 180 as the RL signal pulse. The RP signal pulse may be initially received and latched by the latch circuit 160 responsive to an asserted one of the RSELI signals. Subsequently, the latched RP signal may be propagated to the shifter 180 as the RL signal responsive to a corresponding asserted one of the RSELO signals. In response to receiving the combination of the RL signal from the latch circuit 160 and the N signal, the shifter 180 may assert the OER/F signals based on the read latency CL and the N signal. Because the N signal indicates a count of the tCK that have elapsed between receipt of the CLK signal and the LCLK signal, which is the same tCK count between receipt of the CMD signal and the RL signal, the value of the N signal may be subtracted from the CLK to account for the already elapsed tCK. Responsive to assertion of the OER/F signals, the output driver 190 may provide the IDATA as data DQ relative to the timing of the LCLK, and as required by the specified latency CL.
The latch control circuit 120 that times the RSELI and RSELO relative to a single counter may save complexity and improve reliability as compared with coordinating timing of the RSELI and RSELO signals between two different counters. Additional delay models that unnecessarily consume extra chip space are thereby reduced by utilizing the RSELI and RSELO signals that can be provided directly to the latch circuit 160. High speed operations may be better achieved by utilizing a clock-based control system such as the latency control circuit 112.
Referring to
The DLL 210 may include a delay line DLINED 211 configured to delay the PCLK signal received from the input buffer 204. The DLL 210 may set a delay of the delay line DLINED 211 based on a phase relationship between the PCLK signal and the LCLK signal after passing through circuitry configured to model a propagation path of the CLK signal through the apparatus 200, such as a model of the input buffer 204, the output driver 290, etc. The LCLK signal may be eventually passed on to the output driver 290 after locking is achieved at the DLL 210. The DLL 210 may generate a delay control signal DCTL that adjusts a delay of the delay line DLINED 211 to adjust the timing of the PCLK signal such that the phase of the LCLK will match the phase of the CLK signal at an output of the apparatus 200 (e.g., via the output driver 290). The DLL 210 may also provide a count signal N representing a count of the number of tCK used to adjust the PCLK signal in order to achieve the locked condition (e.g., a tCK latency the CLK signal and the LCLK signal.
The command decoder 250 may be configured to decode the CMD signal respective to the PCLK signal to provide a pulse on the RP signal to the latency control circuit 212. The CMD signal may be a memory access command, such as a read, write, or ODT command. The latency control circuit 212 may include a latch control circuit 220 coupled to a latch circuit 260. The latch control circuit 220 may receive the PCLK signal, the DCTL signal, and the LCLK signal. The latch control circuit 220 may provide control signals RSELI<7:0> and RSELO<7:0> to the latch circuit 260 responsive to the PCLK, DCTL, and LCLK signals. The latch control circuit 220 may include a counter/decoder circuit 224 configured to provide the RESELI<7:0> signals. The counter/decoder circuit 224 may include a counter 225 coupled to a decoder 226. The counter 225 may perform a count operation responsive to the PCLK signal to provide the B<2:0> signals, with each of the B<2:0> signal representing a binary bit of the counter. That is, the counter 225 may increment the B<2:0> signals responsive to the PCLK signal. The B<2:0> signals may indicate a count value ranging from ‘000’ to ‘111’ before wrapping back to ‘000’. The decoder 226 may decode the B<2:0> signal to assert a corresponding one of the RSELI<7:0> signals responsive to the PCLK signal. That is, each of the RSELI<7:0> signals may correspond to a particular count value indicated by the B<2:0> signals. Responsive to the PCLK signal, may assert the one of the RSELI<7:0> signals corresponding to the decoded count value.
The latch control circuit 220 may further include delay lines DLINE<2:0>222(2-0) coupled between the counter/decoder circuit 224 and a decoder 228. The DLINE<2:0> delay lines 222(2-0) may be configured to delay the B<2:0> signals to provide delayed B<2:0> signals BD<2:0>. The delay of each of the DLINE<2:0> delay lines 222(2-0) may be controlled by the DCTL signal received from the DLL 210. Thus, the delay applied to the B<2:0> signals may be a same delay that is applied to the PCLK signal to generate the LCLK signal. The decoder 228 may receive the BD<2:0> signals and, similar to the decoder 226, may decode the BD<2:0> signals to assert a corresponding one of the RSELO<7:0> signals responsive to the LCLK signal. That is, each of the RSELO<7:0> signals may correspond to a count value of the BD<2:0> signals. Responsive to the LCLK signal, the decoder 228 may assert the one of the RSELO<7:0> signals corresponding to the decoded count value.
The latch circuit 260 may include input latches 262(0-7) and output latches 264(0-7). Each of the input latches 262(0-7) may be coupled in series with a respective one of the output latches 264(0-7) to form input/output latch pairs (e.g., holding circuits HC0-HC7). For example, the input latch 262(0) may be coupled to the output latch 264(0) in series. The input latches 262(0-7) may be clocked by the RSELI<7:0> signals, and the output latches 264(0-7) may be clocked by the RSELO<7:0> signals. The input latches 262(0-7) may be configured to receive the RP signal from the command decoder 250 and one of the input latches 262(0-7) may latch the RP signal pulse responsive to the corresponding RSELI<7:0> signal. Further, the output latches 264(0-7) associated with the input latch 262(0-7) that has latched the RP signal pulse may latch the latched RP signal pulse as the RL signal responsive to the corresponding RSELO<7:0> signal.
The latency control circuit 212 may further include a shifter 280 configured to receive the RL signal pulse from the latch circuit 260 and a count signal N and the LCLK signal from the DLL 210. The shifter 280 may assert the OER and OEF signals responsive to receipt of the RL signal pulse and based on subtracting the N signal from the read latency CL. The output driver 290 may receive the asserted OER and OEF signals, the LCLK signal, and input data IDATA, and may propagate the IDATA to DQ responsive to the asserted OER and OEF signals and the LCLK signal.
In operation, the apparatus 200 may receive (e.g., from a memory controller) the external CLK signal at the input buffer 204 and the CMD signal at the command decoder 250 based on timing of the PCLK signal. When the CMD signal includes a read command, the apparatus 200 may operate according to the read latency CL. The DLL 210 and the latency control circuit 212 may be configured to apply the latency CL to the IDATA and synchronize the IDATA with the CLK signal.
The DLL 210 may receive the PCLK signal from the input buffer 204. The delay line DLINED 211 may delay the PCLK signal to provide the LCLK signal based on the DCTL signal. The delay selected by the DCTL signal may be based on a phase relationship between the PCLK signal and the LCLK signal passed through a model delay. The DLL 210 may determine a tCK latency between the CLK signal and the LCLK signal, and may provide the N signal having a value indicating the tCK latency. The N signal may be used by the shifter 280 to determine when to assert the OER and OEF signals.
The command decoder 250 may decode the CMD signal responsive to the PCLK signal and provide a pulse on the RP signal to the latch circuit 260. The PCLK and LCLK signals may be received by the latch control circuit 220 and used to change timings of read command pulses from being relative to the PCLK to being relative to the LCLK clock during a memory read operation.
For example, the counter 225 may receive the PCLK signal, and may increment a count with every clock cycle of the PCLK signal to provide the B<2:0> signals, where each of the B<2:0> represents a bit of the counter. The decoder 226 may decode the B<2:0> signals to assert a respective one of the RSELI<7:0> signals responsive to the PCLK signal. As the collective value of the B<2:0> signals change with each clock cycle of the PCLK, a different one of the RSELI<7:0> signals may be asserted with each clock cycle of the PCLK signal. For example, when the B<2:0> signals have logical values of ‘000’, the RSELI<0> signal may be asserted, and when the B<2:0> signals have logical values of ‘001’, the RSELI<l> signal may be asserted, etc.
The B<2:0> may also be provided to the delay lines DLINE<2:0>222(2-0). The delay lines DLINE<2:0>222(2-0) may delay the B<2:0> signals to provide the BD<2:0> signals. Similar to the decoder 226, the decoder 228 may decode the BD<2:0> signals to assert a respective one of the RSELO<7:0> signals responsive to the LCLK signal. The delay of the delay lines DLINE<2:0>222(2-0) may be selected based on the DCTL signal. The delay lines DLINE<2:0>222(2-0) may be identical to the delay line DLINED 211, and thus the DCTL signal may select the same delay for the B<2:0> signals as the delay applied to the PCLK signal. Based on having the same applied delay, the latency between the B<2:0> signals and the BD<2:0> signals may be the same as the latency between the PCLK and LCLK signals. Accordingly, the latency between the one of the RSELI<7:0> signals asserted based on the B<2:0> signals and the corresponding one of the RSELO<7:0> signals asserted based on the BD<2:0> signals may be the same as the latency between the PCLK and LCLK signals. By using a single counter 225 as a basis to assert the RSELI<7:0> and RSELO<7:0> signals (e.g., rather than separate counters for each), a synchronous relationship between the RSELI<7:0> and RSELO<7:0> signals may be inherently maintained. For example, if controlled by separate counters, the counters for each may become asynchronous relative to one another, and would thus require a reset to be re-synchronized.
The RSELI<7:0> and RSELO<7:0> signals may be received by the latch circuit 260, and may control propagation of the RP signal pulse to the shifter 280 via the RL signal. For example, the RP signal pulse may be received at an input of each of the input latches 262(0-7). After receipt of the RP signal pulse at the inputs of the input latches 262(0-7), a first one of the RSELI<7:0> to be asserted may clock a corresponding input latch 262(0-7) to latch the RP signal pulse therein. As previously described, the RSELI<7:0> signals may be sequentially asserted based on timing of the PCLK signal and the B<2:0> signals. Thus, each of the input latches 262(0-7) may be asserted once every 8 tCK of the PCLK signal in a round robin fashion. The latched RP signal pulse may be held in the one input latch 262(0-7) and provided to an output of the one input latch 262(0-7). After latching of the RP signal pulse by the one input latch 262(0-7), an output latch of the output latches 264(0-7) corresponding to the input latch that latched the RP signal pulse may latch the latched RP signal pulse and provide the latched RP signal pulse to an output as the RL signal responsive to a corresponding RSELO<7:0> signal. Because the timing relationship between corresponding RSELI<7:0> signals and RSELO<7:0> signals is equal to the timing relationship between the PCLK and LCLK signals, the timing relationship between the RP and RL signals is also equal to the latency between the PCLK and LCLK signals.
Responsive to receipt of the RL signal pulse, the shifter 280 may assert the OER and OEF signals based on the read latency CL. The shifter 280 may subtract the N signal value (e.g., elapsed time from receipt of the CMD signal to latching of the RL signal) plus 1 tCK (e.g., to allow 1 tCK for the output driver 290 to latch the IDATA) from the read latency CL, and may delay assertion of the OER and OEF signals responsive to the LCLK signal based on the calculation. After the delay, the shifter 280 may assert the OER and OEF signals. Responsive to receiving the asserted OER and OEF signals, the output driver 290 may provide the IDATA data to the data DQ responsive to the LCLK signal. The data DQ may provide the IDATA data to a data bus having timing synchronized with the CLK signal.
While
At time t0, a READ command may be received at the apparatus 200 via the CMD signal coincident with a rising edge of the CLK signal received at the input buffer 204. At time t1, the PCLK signal may be provided at an output of the input buffer 204. Coincident with the PCLK, the counter 225 may begin counting, thus toggling the B<2:0> signals starting from time t1. The decoder 226 may assert one of the RSELI<7:0> signals based on a value of the B<2:0> signals. For example, responsive to the PCLK signal, the RSELI<0> signal may be asserted when the B<2:0> has values of ‘000’ between time t1 and time t2. The RP signal may be asserted from the command decoder 250 starting between time between time t1 and t2, and may be de-asserted after time t2 (e.g., a pulse). Responsive to the RSELI<0> signal being asserted in this example between times t1 and t2, the RP signal may be latched at the input latch 262(0).
At time t3, the LCLK signal may start. Thus, the tCK count of the N signal may be equal to 3 tCK (e.g., time from receipt of read command to start of the LCLK signal). Coincident with the LCLK starting, the decoder 228 may begin receiving and decoding the BD<2:0> signals to assert the RSELO<7:0> signals. For example, responsive to the LCLK signal, the RSELO<0> signal may be asserted when the BD<2:0> has values of ‘000’ between time t3 and time t4. Responsive to the RSELO<0> signal being asserted in this example between times t3 and t4, the latched RP signal pulse may be latched as the RL signal at the output latch 264(0). Thus, using the latency control circuit 212 of
The shifter 280 may receive the RL signal pulse, along with the N signal, and begin counting a delay based on the read latency. The shifter may apply a delay that equal to the read latency CL minus the N value (e.g., 3tCK) minus 1. Thus, between times t7 and t8, the OER/F signals may be asserted. Responsive to the OER/OEF signals being asserted, the output driver may begin providing data at an output responsive to the LCLK signal at time t9. In this example, the read latency CL is equal to 9 tCK. Other read latencies CL may be used in other apparatuses.
The timing diagram 300 is exemplary, and actual relative timing relationships between signals may vary from the relationships depicted. Further, the length of pulses of signals of the timing diagram 300 may vary from depicted.
Referring to
The command decoder 250 may be configured to decode the CMD signal to provide a decoded command signal RP to the latency control circuit 412. The latency control circuit 412 may include a latch control circuit 420 coupled to the latch circuit 260. The latch control circuit 420 may receive the PCLK signal, the DCTL signal, and the LCLK signal. The latch control circuit 420 may provide control signals RSELI<7:0> and RSELO<7:0> to the latch circuit 260 responsive to the PCLK, DCTL, and LCLK signals. The latch control circuit 420 may include the counter/decoder circuit 224 configured to provide the RSELI<7:0> signals.
The latch control circuit 420 may further include delay lines DLINE<1:0> 422(1-0) coupled between the counter/decoder circuit 224 and the decoder 228. The DLINE<1:0> delay lines 422(1-0) may be configured to delay the B<1:0> signals to provide delayed B<1:0> signals BD<1:0>. The delay of each of the DLINE<1:0> delay lines 422(1-0) may be controlled by the DCTL signal received from the DLL 210. Thus, the delay applied to the B<1:0> signals may be a same delay that is applied to the PCLK signal to generate the LCLK signal. The latch control circuit 420 may further include delay 423 coupled between the counter/decoder circuit 224 and the decoder 228. The delay 423 may be configured to delay the B<2> signal to provide delayed B<2> signals BD<2>. The delay the delay 423 may be fixed. Because the B<2> signal is associated with the most significant bit of the counter 225 and only transitions 4 tCK, and because the RSELO<0:7> signals transition responsive to the LCLK signal, using the delay 423 in place of an adjustable delay line may reduce complexity and layout size while retaining the benefits of timing control using the latch circuit 260.
In operation, as previously described, the counter 225 may provide the B<2:0> signals and the decoder 226 may decode the B<2:0> signals to assert a respective one of the RSELI<7:0> signals responsive to the PCLK signal. The B<1:0> signals may also be provided to the delay lines DLINE<1:0>422(1-0) and the B<2> signal may be provided through the delay 423. The delay lines DLINE<1:0> 422(1-0) may delay the B<1:0> signals to provide the BD<1:0> signals based on the DCTL signal. The delay lines DLINE<1:0> 422(1-0) may be identical to the delay line DLINED 211, and thus the DCTL signal may select the same delay for the B<1:0> signals as the delay applied to the PCLK signal. The delay 423 may apply a fixed delay to the B<2> signal to provide the BD<2> signal. Based on having the same applied delay, the latency between the B<1:0> signals and the BD<1:0> signals may be the same as the latency between the PCLK and LCLK signals, and latency between the B<2> signal and the BD<2> signal may have a different latency. However, because the RSELO<7:0> signals are asserted responsive to the LCLK signal, the exact timing of receipt of the BD<2> signal relative to timing of receipt of the BD<1:0> signals may vary slightly (e.g., within one tCK) with no noticeable difference in the behavior of the RSELO<7:0> signals. Further, the BD<2> signal is the most significant bit of the count, so the signal may only toggles once every 4 tCK, thereby reducing an opportunity for error. By replacing an adjustable delay line with a fixed delay, the layout size and complexity may be reduced.
As previously described, the RSELI<7:0> and RSELO<7:0> signals may be received by the latch circuit 260, and may control propagation of the RP signal to the shifter 280 as the RL signal. Responsive to receipt of the RL signal, the shifter 280 may assert the OER and OEF signals based on the read latency CL. Responsive to receiving the asserted OER and OEF signals, the output driver 290 may provide the IDATA data to the DQ responsive to the LCLK signal. The DQ may provide the IDATA data to a data bus having timing synchronized with the CLK signal.
As previously described with reference to
Referring to
The command decoder 250 may be configured to decode the CMD signal to provide a decoded command signal RP to the latency control circuit 512. The latency control circuit 512 may include a latch control circuit 520 coupled to the latch circuit 260. The latch control circuit 520 may receive the PCLK signal, the DCTL signal, and the LCLK signal. The latch control circuit 520 may provide control signals RSELI<7:0> and RSELO<7:0> to the latch circuit 260 responsive to the PCLK, DCTL, and LCLK signals. The latch control circuit 520 may include the counter/decoder circuit 224 configured to provide the RESELI<7:0> signals.
The latch control circuit 520 may further include delay lines DLINE<1:0> 422(1-0) coupled between the counter/decoder circuit 224 and a latch 529. The DLINE<1:0> delay lines 422(1-0) may be configured to delay the B<1:0> signals to provide delayed B<1:0> signals BD<1:0>. The latch control circuit 520 may not apply any delay to the B<2> signal. The latch control circuit 520 may further include a latch 529 that is configured to receive the BD<1:0> signals from the delay lines DLINE<1:0> 422(1-0) and the B<2> signal directly from the counter/decoder circuit 224. The latch 529 may be clocked by the LCLK to latch the BD<1:0> and B<2> signals at an output as the BD<2:0> signals. That is, the latch 529 may recombine the B<2:0> signals at an output as the BD<2:0> signals.
The 528 may receive the BD<2:0> signals and may decode the BD<2:0> signals to assert a corresponding one of the RSELO<7:0> signals. Thus, each of the RSELO<7:0> signals may correspond to a count value of the BD<2:0> signals. The 528 may assert the one of the RSELO<7:0> signals corresponding to the decoded count value.
In operation, as previously described, the counter 225 may provide the B<2:0> signals and the decoder 226 may decode the B<2:0> signals to assert a respective one of the RSELI<7:0> signals responsive to the PCLK signal. The B<1:0> signals may also be provided to the delay lines DLINE<1:0> 422(1-0) to provide the BD<2:0> signals to the latch 529. The latch 529 may also receive the B<2> signal directly from the counter/decoder circuit 224. The latch 529 may latch the BD<1:0> and the B<2> signals at an output as the BD<2:0> signals. The 528 may decode the BD<2:0> signals to assert a respective one of the RSELO<7:0> signals responsive to the LCLK signal. Because the BD<2:0> signals are collectively provided to the 528 responsive to the LCLK signal, the exact timing of receipt of the B<2> signal at the latch 529 relative to timing of receipt of the BD<1:0> signals may vary slightly (e.g., within one tCK) with no noticeable difference in the behavior of the RSELO<7:0> signals provided from the 528. Further, the BD<2> signal is the most significant bit of the count, so the signal may only toggles once every 4 tCK, thereby reducing an opportunity for error. By replacing an adjustable delay line with latch, the layout size and complexity may be reduced.
As previously described, the RSELI<7:0> and RSELO<7:0> signals may be received by the latch circuit 260, and may control propagation of the RP signal to the shifter 280 as the RL signal. Responsive to receipt of the RL signal, the shifter 280 may assert the OER and OEF signals based on the read latency CL. Responsive to receiving the asserted OER and OEF signals, the output driver 290 may provide the IDATA data to the DQ responsive to the LCLK signal. The DQ may provide the IDATA data to a data bus having timing synchronized with the CLK signal.
As previously described with reference to
Referring to
The command decoder 250 may be configured to decode the CMD signal to provide a decoded command signal RP to the latency control circuit 612. The latency control circuit 612 may include a latch control circuit 620 coupled to the latch circuit 260. The latch control circuit 620 may receive the PCLK signal, the DCTL signal, and the LCLK signal. The latch control circuit 620 may provide control signals RSELI<7:0> and RSELO<7:0> to the latch circuit 260 responsive to the PCLK, DCTL, and LCLK signals. The latch control circuit 620 may include the counter/decoder circuit 224 configured to provide the RESELI<7:0> signals.
The latch control circuit 620 may further include delay lines DLINE<7:0> 622(7-0) coupled between the counter/decoder circuit 224 and a latch 629. The DLINE<7:0> delay lines 622(7-0) may be configured to delay the RSELI<7:0> signals to provide delayed RSELI<7:0> signals RSELID<7:0>. The delay of each of the DLINE<7:0> delay lines 622(7-0) may be controlled by the DCTL signal received from the DLL 210. Thus, the delay applied to the RSELI<7:0> signals may be a same delay that is applied to the PCLK signal to generate the LCLK signal. The latch control circuit 620 may further include the latch 629 that is configured to receive the RSELID<7:0> signals from the delay lines DLINE<7:0> 622(7-0). The latch 629 may be clocked by the LCLK to latch the RSELID<7:0> at an output as the RSELO<7:0> signals. Thus, rather than decoding the B<2:0> signals after a delay, the delay may be applied directly to the RSELI<7:0> signals, via the delay lines DLINE<7:0> 622(7-0), and the decoder may be replaced with a simple latch 629 to provide the RSELO<7:0> signals responsive to the LCLK signal.
In operation, as previously described, the counter 225 may provide the B<2:0> signals and the decoder 226 may decode the B<2:0> signals to assert a respective one of the RSELI<7:0> signals responsive to the PCLK signal. The RSELI<7:0> signals may also be provided to the delay lines DLINE<7:0> 622(7-0). The delay lines DLINE<7:0> 622(7-0) may delay the RSELI<1:0> signals to provide the RSELID <7:0> signals based on the DCTL signal. The delay lines DLINE<7:0> 622(7-0) may be identical to the delay line DLINED 211, and thus the DCTL signal may select the same delay for the RSELI<7:0> signals as the delay applied to the PCLK signal. Based on having the same applied delay, the latency between the RSELI<7:0> signals and the RSELID<7:0> signals may be the same as the latency between the PCLK and LCLK signals. The RSELID<7:0> signals may be provided to the latch 629. The latch 629 may latch the RSELID<7:0> signals at an output as the RSELO<7:0> signals. Rather than decoding the B<2:0> signals after a delay, the delay may be applied directly to the RSELI<7:0> signals, via the delay lines DLINE<7:0> 622(7-0), and the decoder may be replaced with a simple latch 629 to provide the RSELO<7:0> signals responsive to the LCLK signal.
As previously described, the RSELI<7:0> and RSELO<7:0> signals may be received by the latch circuit 260, and may control propagation of the RP signal to the shifter 280 as the RL signal. Responsive to receipt of the RL signal, the shifter 280 may assert the OER and OEF signals based on the read latency CL. Responsive to receiving the asserted OER and OEF signals, the output driver 290 may provide the IDATA data to the DQ responsive to the LCLK signal. The DQ may provide the IDATA data to a data bus having timing synchronized with the CLK signal.
As previously described with reference to
Referring to
The memory 700 includes a command decoder 706 that may receive memory commands through a command bus 708 and provide (e.g., generate) corresponding control signals within the memory 700 to carry out various memory operations. The command decoder 706 may include a command path 714 configured to control timing of the received CMD signal. The command path 714 may receive the PCLK, LCLK, and DCTL signals from the clock generator 713, and may generate the output enable rising OER and output enable falling OEF signals responsive to the PCLK, LCLK, DCTL, and CMD signals. The command path 714 may include the latency control circuit 112 of
Row and column address signals may be provided (e.g., applied) to an address latch 710 in the memory 700 through an address bus 720. The address latch 710 may then provide (e.g., output) a separate column address and a separate row address. The address latch 710 may provide row and column addresses to a row address decoder 722 and a column address decoder 728, respectively. The column address decoder 728 may select bit lines extending through the array 702 corresponding to respective column addresses. The row address decoder 722 may be connected to a word line driver 724 that activates respective rows of memory cells in the array 702 corresponding to received row addresses. The selected data line (e.g., a bit line or bit lines) corresponding to a received column address may be coupled to a read/write circuitry 730 to provide read data to an output data buffer 734 via an input-output data bus 740. The output data buffer 734 may provide the read data to the DQ responsive to the OER, OEF, and LCLK signals. Write data may be provided to the memory array 702 through an input data buffer 744 and the memory array read/write circuitry 730. The command decoder 706 may respond to memory commands provided to the command bus 708 to perform various operations on the memory array 702. In particular, the command decoder 706 may be used to provide internal control signals to read data from and write data to the memory array 702.
Those of ordinary skill would further appreciate that the various illustrative logical blocks, configurations, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software executed by a processor, or combinations of both. Various illustrative components, blocks, configurations, modules, circuits, and steps have been described above generally in terms of their functionality. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
The previous description of the disclosed embodiments is provided to enable a person skilled in the art to make or use the disclosed embodiments. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the principles defined herein may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope possible consistent with the principles and novel features as defined by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5004933 | Widener | Apr 1991 | A |
6111810 | Fujita | Aug 2000 | A |
6219384 | Kliza et al. | Apr 2001 | B1 |
6260128 | Ohshima et al. | Jul 2001 | B1 |
6275077 | Tobin et al. | Aug 2001 | B1 |
6327318 | Bhullar | Dec 2001 | B1 |
6424592 | Maruyama | Jul 2002 | B1 |
6438055 | Taguchi et al. | Aug 2002 | B1 |
6459313 | Godbee et al. | Oct 2002 | B1 |
6489823 | Iwamoto | Dec 2002 | B2 |
6510095 | Matsuzaki et al. | Jan 2003 | B1 |
6636110 | Ooishi et al. | Oct 2003 | B1 |
6687185 | Keeth et al. | Feb 2004 | B1 |
6710726 | Kim et al. | Mar 2004 | B2 |
6744285 | Mangum | Jun 2004 | B2 |
6781861 | Gomm et al. | Aug 2004 | B2 |
6839288 | Kim et al. | Jan 2005 | B1 |
6861901 | Prexl et al. | Mar 2005 | B2 |
6914798 | Kwon et al. | Jul 2005 | B2 |
6930955 | Johnson et al. | Aug 2005 | B2 |
6973008 | Krause | Dec 2005 | B2 |
6980479 | Park | Dec 2005 | B2 |
6988218 | Drexler | Jan 2006 | B2 |
7042799 | Cho | May 2006 | B2 |
7046060 | Minzoni et al. | May 2006 | B1 |
7058799 | Johnson | Jun 2006 | B2 |
7061941 | Zheng | Jun 2006 | B1 |
7065001 | Johnson et al. | Jun 2006 | B2 |
7111185 | Gomm et al. | Sep 2006 | B2 |
7119591 | Lin | Oct 2006 | B1 |
7170819 | Szczypinski | Jan 2007 | B2 |
7187599 | Schnell et al. | Mar 2007 | B2 |
7209396 | Schnell | Apr 2007 | B2 |
7248512 | Shin | Jul 2007 | B2 |
7268605 | Fang et al. | Sep 2007 | B2 |
7269754 | Ramaswamy et al. | Sep 2007 | B2 |
7280430 | Lee | Oct 2007 | B2 |
7336752 | Vlasenko et al. | Feb 2008 | B2 |
7340632 | Park | Mar 2008 | B2 |
7375560 | Lee et al. | May 2008 | B2 |
7411852 | Nishioka et al. | Aug 2008 | B2 |
7443216 | Gomm et al. | Oct 2008 | B2 |
7451338 | Lemos | Nov 2008 | B2 |
7463534 | Ku et al. | Dec 2008 | B2 |
7489172 | Kim | Feb 2009 | B2 |
7509517 | Matsumoto et al. | Mar 2009 | B2 |
7580321 | Fujisawa et al. | Aug 2009 | B2 |
7590013 | Yu et al. | Sep 2009 | B2 |
7593273 | Chu et al. | Sep 2009 | B2 |
7609584 | Kim et al. | Oct 2009 | B2 |
7616040 | Motomura | Nov 2009 | B2 |
7631248 | Zakharchenko et al. | Dec 2009 | B2 |
7643334 | Lee et al. | Jan 2010 | B1 |
7656745 | Kwak | Feb 2010 | B2 |
7660187 | Johnson et al. | Feb 2010 | B2 |
7663946 | Kim | Feb 2010 | B2 |
7671648 | Kwak | Mar 2010 | B2 |
7675439 | Chang et al. | Mar 2010 | B2 |
7698589 | Huang | Apr 2010 | B2 |
7715260 | Kuo et al. | May 2010 | B1 |
7716510 | Kwak | May 2010 | B2 |
7751261 | Cho | Jul 2010 | B2 |
7773435 | Cho | Aug 2010 | B2 |
7822904 | LaBerge | Oct 2010 | B2 |
7826305 | Fujisawa | Nov 2010 | B2 |
7826583 | Jeong et al. | Nov 2010 | B2 |
7872924 | Ma | Jan 2011 | B2 |
7885365 | Hagleitner et al. | Feb 2011 | B2 |
7913103 | Gold et al. | Mar 2011 | B2 |
7945800 | Gomm et al. | May 2011 | B2 |
7948817 | Coteus et al. | May 2011 | B2 |
7969813 | Bringivijayaraghavan et al. | Jun 2011 | B2 |
7983094 | Roge et al. | Jul 2011 | B1 |
8004884 | Franceschini et al. | Aug 2011 | B2 |
8018791 | Kwak | Sep 2011 | B2 |
8030981 | Kim | Oct 2011 | B2 |
8115529 | Shibata | Feb 2012 | B2 |
8116415 | Wada et al. | Feb 2012 | B2 |
8144529 | Chuang et al. | Mar 2012 | B2 |
8321714 | Wu et al. | Nov 2012 | B2 |
8358546 | Kim et al. | Jan 2013 | B2 |
8392741 | Kim et al. | Mar 2013 | B2 |
8441888 | Bringivijayaraghavan et al. | May 2013 | B2 |
8509011 | Bringivijayaraghavan | Aug 2013 | B2 |
8644096 | Bringivijayaraghavan | Feb 2014 | B2 |
8717078 | Idgunji et al. | May 2014 | B2 |
8732509 | Kwak | May 2014 | B2 |
8788896 | Tekumalla | Jul 2014 | B2 |
9001955 | Lamanna et al. | Apr 2015 | B2 |
9053815 | Bell | Jun 2015 | B2 |
9054675 | Mazumder et al. | Jun 2015 | B2 |
9166579 | Huber et al. | Oct 2015 | B2 |
9329623 | Vankayala | May 2016 | B2 |
20010015924 | Arimoto et al. | Aug 2001 | A1 |
20020057624 | Manning | May 2002 | A1 |
20030117864 | Hampel et al. | Jun 2003 | A1 |
20030147299 | Setogawa | Aug 2003 | A1 |
20030161210 | Acharya et al. | Aug 2003 | A1 |
20050024107 | Takai et al. | Feb 2005 | A1 |
20050047222 | Rentschler | Mar 2005 | A1 |
20050132043 | Wang et al. | Jun 2005 | A1 |
20050270852 | Dietrich et al. | Dec 2005 | A1 |
20060062341 | Edmondson et al. | Mar 2006 | A1 |
20060064620 | Kuhn | Mar 2006 | A1 |
20060155948 | Ruckerbauer | Jul 2006 | A1 |
20060182212 | Hwang et al. | Aug 2006 | A1 |
20060193194 | Schnell | Aug 2006 | A1 |
20070033427 | Correale, Jr. et al. | Feb 2007 | A1 |
20070046346 | Minzoni | Mar 2007 | A1 |
20070088903 | Choi | Apr 2007 | A1 |
20070192651 | Schoch | Aug 2007 | A1 |
20070291558 | Joo | Dec 2007 | A1 |
20080080267 | Lee | Apr 2008 | A1 |
20080080271 | Kim | Apr 2008 | A1 |
20080082707 | Gupta et al. | Apr 2008 | A1 |
20080126822 | Kim et al. | May 2008 | A1 |
20080137471 | Schnell et al. | Jun 2008 | A1 |
20080144423 | Kwak | Jun 2008 | A1 |
20080232179 | Kwak | Sep 2008 | A1 |
20080232180 | Kim et al. | Sep 2008 | A1 |
20080253205 | Park | Oct 2008 | A1 |
20090041104 | Bogdan | Feb 2009 | A1 |
20090232250 | Yamada et al. | Sep 2009 | A1 |
20090315600 | Becker et al. | Dec 2009 | A1 |
20100001762 | Kim | Jan 2010 | A1 |
20100066422 | Tsai | Mar 2010 | A1 |
20100124090 | Arai | May 2010 | A1 |
20100124102 | Lee et al. | May 2010 | A1 |
20100165769 | Kuroki | Jul 2010 | A1 |
20100165780 | Bains et al. | Jul 2010 | A1 |
20100195429 | Sonoda | Aug 2010 | A1 |
20100199117 | Kwak | Aug 2010 | A1 |
20100208534 | Fujisawa | Aug 2010 | A1 |
20100208535 | Fujisawa | Aug 2010 | A1 |
20100232213 | Hwang et al. | Sep 2010 | A1 |
20100254198 | Bringivijayaraghavan et al. | Oct 2010 | A1 |
20100327926 | Takahashi | Dec 2010 | A1 |
20110047319 | Jeon et al. | Feb 2011 | A1 |
20110055671 | Kim et al. | Mar 2011 | A1 |
20110057697 | Miyano | Mar 2011 | A1 |
20110102039 | Shin | May 2011 | A1 |
20110228625 | Bringivijayaraghavan | Sep 2011 | A1 |
20110238866 | Zitlaw | Sep 2011 | A1 |
20110238941 | Xu et al. | Sep 2011 | A1 |
20110298512 | Kwak | Dec 2011 | A1 |
20110314324 | Ozdemir | Dec 2011 | A1 |
20120084575 | Flores et al. | Apr 2012 | A1 |
20120124317 | Mirichigni et al. | May 2012 | A1 |
20120147692 | Nakamura | Jun 2012 | A1 |
20120212268 | Kim | Aug 2012 | A1 |
20120254873 | Bringivijayaraghavan | Oct 2012 | A1 |
20120269015 | Bringivijayaraghavan | Oct 2012 | A1 |
20120274376 | Gomm et al. | Nov 2012 | A1 |
20130002320 | Lin | Jan 2013 | A1 |
20130141994 | Ito et al. | Jun 2013 | A1 |
20130194013 | Kwak | Aug 2013 | A1 |
20130250701 | Bringivijayaraghavan et al. | Sep 2013 | A1 |
20130329503 | Bringivijayaraghavan | Dec 2013 | A1 |
20140010025 | Bringivijayaraghavan | Jan 2014 | A1 |
20140035640 | Kwak et al. | Feb 2014 | A1 |
20140055184 | Vankayala | Feb 2014 | A1 |
20140119141 | Tamlyn et al. | May 2014 | A1 |
20140176213 | Rylov | Jun 2014 | A1 |
20140177359 | Kumar et al. | Jun 2014 | A1 |
20140258764 | Kwak | Sep 2014 | A1 |
20140293719 | Jung | Oct 2014 | A1 |
20150156009 | Bogdan | Jun 2015 | A1 |
20150170725 | Kwak | Jun 2015 | A1 |
20150235691 | Kwak | Aug 2015 | A1 |
20150340072 | Mazumder | Nov 2015 | A1 |
20160056807 | Neidengard | Feb 2016 | A1 |
Number | Date | Country |
---|---|---|
101752009 | Jun 2010 | CN |
2013-222997 | Oct 2013 | JP |
201303735 | Jan 2013 | TW |
Entry |
---|
“Interfacing DDR SDRAM with Stratix II Devices”, Version 3.2, Altera Corp, Sep. 2008. |
Lee, “How to Implement DDR SGRAM in Graphic System”, Samsung Electric, 4Q1998. |
U.S. Appl. No. 15/139,102, entitled “Methods and Apparatuses Including Command Delay Adjustment Circuit”, filed Apr. 26, 2016 (no copy provided in accordance with the 1287 O.G. 163 waiver published Oct. 19, 2004). |
U.S. Appl. No, 15/139,120, entitled “Apparatuses and Methods for Adjusting a Delay of a Command Signal Path”, filed Apr. 26, 2016 (no copy provided in accordance with the 1287 O.G. 163 waiver published Oct. 19, 2004). |
U.S. Appl. No. 15/243,651, entitled “Apparatuses and Methods for Adjusting Delay of Command Signal Path”, filed. Aug. 22, 2016 (no copy provided in accordance with the 1287 O.G. 163 waiver published Oct. 19, 2004). |
Number | Date | Country | |
---|---|---|---|
20160322964 A1 | Nov 2016 | US |