Memory Interface Timing Verification System and Method

By constructing configurable timing behavior construction modules and verification interface modules, the verification problem of novel non-volatile memory under the DDR protocol stack was solved, realizing the modeling and real-time verification of long latency, asymmetry and state dependence, ensuring the protocol compliance and functional correctness of the controller.

CN122817018BActive Publication Date: 2026-11-10KINGTIGER TESTING TECH (SZ) LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202611323327.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2026-08-28
Publication Date
2026-11-10
Estimated Expiration
2046-08-28

AI Technical Summary

Technical Problem

Existing verification IPs based on the DFI interface cannot recognize the long-latency operations of new non-volatile memory, leading to verification logic failure, read/write timing asymmetry causing coverage loss, lack of proprietary command and state semantics causing verification blind spots, and background operation management logic being out of the verification loop. As a result, they cannot meet the verification requirements of new non-volatile memory under the DDR protocol stack.

Method used

The configurable timing behavior construction module and the verification interface module work together to construct timing data corresponding to the physical behavior of the target memory through signal command association, physical time interval measurement, state transition condition extraction and electrical characteristic measurement, and instantiate it into an index structure in memory. Then, violation checks and comparisons are performed to generate a verification report.

Benefits of technology

It achieves modeling and real-time verification of the physical characteristics of novel non-volatile memory under the DDR protocol stack, such as long latency, asymmetry, and state dependence, to ensure the protocol compliance and functional correctness of the controller in extreme scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122817018B_ABST
    Figure CN122817018B_ABST
Patent Text Reader

Abstract

This application relates to the field of memory design verification technology, and discloses a memory interface timing verification system and method. The system includes: a timing behavior construction module, used to construct timing data corresponding to the physical behavior of the target memory according to the physical timing specifications of the target memory; a verification interface module used to: acquire the timing data from the timing behavior construction module during the verification environment initialization phase, and instantiate the timing data into an index structure in memory; perform violation checks on the signal flow output by the memory controller under test via the DFI interface according to the index structure, and generate violation check results; simulate the physical response behavior of the target memory to the signal flow according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test via the DFI interface, and generate comparison results; and output a verification report based on the violation check results and comparison results.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of memory design verification technology, and in particular to a memory interface timing verification system and method. Background Technology

[0002] As new types of non-volatile memories such as phase-change memories and ferroelectric memories are gradually integrated into the DDR protocol stack, their asynchronous programming operations last for several microseconds to hundreds of microseconds, far exceeding the nanosecond-level timing scale of DRAM. Existing verification IPs based on the DFI interface are all designed for DRAM, with fixed built-in rules and mismatched magnitudes, making it impossible to identify the state persistence, pulse sequences, and proprietary commands caused by long-delay operations; at the same time, they lack the ability to model and verify the internal physical states during erasure and programming, and do not cover the timing dependencies of commands such as write pause / resume. Summary of the Invention

[0003] In view of this, embodiments of this application provide a memory interface timing verification system and method.

[0004] In a first aspect, embodiments of this application provide a memory interface timing verification system, comprising: The timing behavior construction module is used to construct timing data corresponding to the physical behavior of the target memory by constructing signal command association, measuring physical time interval, extracting state transition conditions, and measuring electrical characteristics according to the physical timing specifications of the target memory; wherein, the target memory is a non-volatile memory with asynchronous programming operation function that is connected to the DDR protocol stack through the DFI interface, and the duration of the asynchronous programming operation is greater than a preset time threshold. The verification interface module is used to obtain the timing data of the timing behavior construction module during the verification environment initialization phase, and instantiate the timing data into an index structure in memory. The verification interface module is also used to perform violation checks on the signal stream output by the memory controller under test through the DFI interface according to the index structure, and generate violation check results; The verification interface module is also used to simulate the physical response behavior of the target memory to the signal stream according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result. The verification interface module is also used to output a verification report based on the violation check results and the comparison results.

[0005] Secondly, embodiments of this application provide a memory interface timing verification method, applied to the aforementioned memory interface timing verification system, comprising: During the verification environment initialization phase, the timing data of the timing behavior construction module corresponding to the target memory is obtained; wherein, the timing data is data corresponding to the physical behavior of the target memory constructed according to the physical timing specifications of the target memory through signal command association construction, physical time interval measurement, state transition condition extraction and electrical characteristic measurement. The time-series data is instantiated into an index structure in memory; Based on the index structure, a violation check is performed on the signal stream output by the memory controller under test via the DFI interface, and a violation check result is generated. The physical response behavior of the target memory to the signal flow is simulated according to the index structure to generate expected response data, and the expected response data is compared with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result. A verification report is output based on the violation inspection results and the comparison results.

[0006] The embodiments of this application have the following beneficial effects: This application, by constructing a configurable timing behavior construction module and an index-based verification interface module, realizes the modeling and real-time verification of the physical characteristics of novel non-volatile memory under the DDR protocol stack, such as long latency, asymmetry, and state dependence. Specifically, the timing behavior construction module constructs timing data that strictly corresponds to the physical behavior of the target memory through signal-command association construction, physical time interval measurement, state transition condition extraction, and electrical characteristic measurement, based on the physical timing specifications of the target memory. The verification interface module acquires this timing data during the verification environment initialization phase, instantiates it as an index structure in memory, and then performs violation checks, simulates the physical response of the target memory, and compares the results based on this index structure, ultimately outputting a verification report. This overcomes the verification failure problem caused by hard-coded DRAM timing in traditional verification interface modules, ensuring the protocol compliance and functional correctness of the controller under extreme scenarios. Attached Figure Description

[0007] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0008] Figure 1 A first structural schematic diagram of a memory interface timing verification system according to an embodiment of this application is shown; Figure 2This paper shows a second structural schematic diagram of a memory interface timing verification system according to an embodiment of this application; Figure 3 This paper shows a third structural diagram of a memory interface timing verification system according to an embodiment of the present application; Figure 4 This paper shows a fourth structural schematic diagram of a memory interface timing verification system according to an embodiment of this application; Figure 5 This paper shows a fifth structural schematic diagram of a memory interface timing verification system according to an embodiment of this application; Figure 6 This paper shows a sixth structural schematic diagram of a memory interface timing verification system according to an embodiment of this application; Figure 7 A seventh structural schematic diagram of the memory interface timing verification system according to an embodiment of this application is shown; Figure 8 A flowchart illustrating a memory interface timing verification method according to an embodiment of this application is shown. Detailed Implementation

[0009] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0010] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0011] In the following text, the terms "comprising," "having," and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as primarily excluding the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more combinations thereof. Furthermore, the terms "first," "second," "third," etc., are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance.

[0012] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0013] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0014] With the continuous iteration of storage-class memory technology, new non-volatile memories such as phase-change memory (PCM) and ferroelectric memory (FeRAM) are gradually adopting the mature DDR protocol stack as the interconnect foundation. This DDR protocol stack includes one or more of DDR4, LPDDR4, and LPDDR5. Under this technology path, new non-volatile memories are connected to the DDR protocol stack through the DFI interface (DRAM Front-end Interface), forming a hybrid memory architecture with the central processing unit, graphics processing unit, and other computing units, thereby achieving high-speed interconnection and protocol compatibility with the existing computing ecosystem. However, while this hybrid architecture solves the physical layer interconnection problem, it also exposes a fundamental contradiction at the verification level: existing DFI verification interface modules and timing checkers are designed based on the physical characteristics of dynamic random access memory. Their built-in timing rules are centered on parameters such as tRCD (row address to column address delay), tRP (row precharge time), and tWR (write recovery time), with values ​​concentrated in the tens of nanosecond range. This differs by orders of magnitude from the actual operating timing of new non-volatile memories, resulting in the entire verification system being unable to adapt to their unique physical behavior.

[0015] Specifically, the failure of the verification manifests in four aspects: First, extremely long latency operations cause verification logic to collapse: The programming operations of the new non-volatile memory have asynchronous characteristics, and their duration can reach several microseconds to hundreds of microseconds, which is greater than the preset time threshold. Compared with the nanosecond-level response of dynamic random access memory, this latency is 3 to 5 orders of magnitude higher. The fixed waiting period mechanism preset by the traditional verification interface module (traditional DFI verification IP, traditional VIP) cannot identify the real state that the memory is still performing phase transition or pulse sequence after the command is issued, which causes the monitoring logic to misjudge timeout or allow illegal commands, resulting in command flow disorder and verification failure. The controller's scheduling capability and state synchronization mechanism for long latency scenarios cannot be verified.

[0016] Second, read / write timing asymmetry leads to missing coverage: The read operation latency of new non-volatile memory is typically hundreds of nanoseconds, while the write operation latency reaches the microsecond level. Moreover, the write operation contains a multi-stage voltage pulse sequence, including preheating pulse, programming pulse, and cooling pulse. The verification logic built by the traditional verification interface module based on the symmetric timing assumption cannot parse the timing structure of the pulse sequence, nor can it cover the read / write interval boundary. It is very easy to miss data sampling errors and write failures caused by timing mismatch.

[0017] Third, the lack of proprietary command and state semantics creates a verification blind spot. The new non-volatile memory extends the JEDECDDR standard command set, defining programming enable commands, programming confirmation commands, write pause commands, write resume commands, erase commands, and state read commands. These commands not only correspond to specific DFI interface signal combinations, but also trigger deterministic jumps in the finite state machine inside the memory. Traditional verification interface modules are not configured with their decoding rules and state constraints, and therefore cannot verify the correctness of the controller's implementation of command sequence dependencies, state change timing, and busy state avoidance logic.

[0018] Fourth, the background operation management logic is decoupled from the verification closed loop. The new non-volatile memory does not require charge refresh, but it needs to perform dedicated operations such as wear leveling, bad block marking, and background erasure. These operations are triggered and controlled through the DFI interface in the form of standard commands plus address parameters, and have strong asynchronicity and resource preemption. The traditional verification interface module treats it as irrelevant traffic and ignores it, which cannot verify the controller's ability to initiate, monitor, coordinate and fault-tolerantly handle background tasks under high foreground load, which may lead to abnormal degradation of memory life and silent data corruption.

[0019] Based on this, this embodiment provides a memory interface timing verification system and method to enable the externally configurable timing behavior construction module 100 to work in concert with the general verification interface module 200. Based on the index structure instantiated in memory, the system performs violation checks on the signal stream output by the memory controller under test via the DFI interface and generates violation check results, simulates the physical response of the target memory and generates comparison results, and finally outputs a verification report containing violation reports and coverage reports.

[0020] Specifically, the memory interface timing verification system will be described below with reference to some specific embodiments.

[0021] Figure 1 A schematic diagram of a memory interface timing verification system according to an embodiment of this application is shown. Exemplarily, the memory interface timing verification system includes a timing behavior construction module 100 and a verification interface module 200.

[0022] The timing behavior construction module 100 is used to construct timing data corresponding to the physical behavior of the target memory by means of signal command association construction, physical time interval measurement, state transition condition extraction and electrical characteristic measurement, based on the physical timing specifications of the target memory.

[0023] The target memory is a non-volatile memory that connects to the DDR protocol stack via the DFI interface and has asynchronous programming operation capabilities, but the duration of the asynchronous programming operation is greater than a preset time threshold. The preset time threshold is determined based on the upper limit of the typical timing parameters tRCD and tRP of dynamic random access memory, and is used to clearly distinguish the essential difference between traditional memory and the novel non-volatile memory of this embodiment in terms of operation latency. It can be understood that the preset time threshold is a reference value used to distinguish the operation latency of DRAM and novel non-volatile memory, and its value ranges from 50 nanoseconds to 200 nanoseconds; in some embodiments, the threshold can be set to 100 nanoseconds.

[0024] It can be understood that timing data is a set of structured data composed of signal mapping relationships constructed through signal command association based on the physical timing specifications of the target memory, command timing parameters obtained through physical time interval measurement, state dependency features extracted through state transition conditions, and electrical configuration parameters obtained through electrical characteristic measurement. This data fully characterizes the instruction recognition logic, timing constraint boundaries, internal physical state transition rules, and electrical drive requirements of the target memory on the DFI interface, and serves as the basis for verifying the high-fidelity physical behavior modeling and compliance checks of the interface module 200.

[0025] Specifically, such as Figure 2 As shown, the timing behavior construction module 100 includes signal mapping relationship 110, command timing parameters 120, state dependency features 130, and electrical configuration parameters 140.

[0026] The signal mapping relationship 110 is constructed by associating the control signals of the DFI interface with the extended operation commands of the target memory.

[0027] It should be noted that these extended operation commands are operation commands outside the JEDEC DDR standard command set; for example, extended operation commands include, but are not limited to, programming enable commands, programming confirm commands, write pause commands, write resume commands, erase commands, and status read commands.

[0028] In the specific implementation, the timing behavior construction module 100 performs signal-command association construction. Based on the datasheet analysis of the target memory and the measured waveform analysis of the DFI interface, it generates a signal mapping relationship 110. This signal mapping relationship 110 can define the DFI interface signal level combination corresponding to each extended operation command in the form of a truth table. For example, when the chip select signal cs_n is low, the row address strobe signal ras_n is low, the column address strobe signal cas_n is high, the write enable signal we_n is low, and the value of the command address bus ca is 5, this signal combination is identified as a programming enable command. As another example, when cs_n is low, ras_n is high, cas_n is low, we_n is low, and the value of ca is 6, this signal combination is identified as an erase command. It can be understood that the signal mapping relationship 110 is a mapping relationship constructed by the timing behavior construction module 100 by performing bit-to-bit matching of the level combination of the control signal and address signal of the DFI interface with a predefined truth table. It can realize the real-time identification of extended operation commands, thereby providing a basis for subsequent timing checks and status tracking.

[0029] The command timing parameter 120 specifies the minimum and maximum time interval parameters required between any two ordered operation commands. The operation commands include extended operation commands and JEDEC DDR standard operation commands.

[0030] It is understandable that the timing parameter 120 between commands is mainly used to define the minimum and maximum time interval parameters for each pair of ordered operation commands; for example, it can define the minimum and maximum time interval parameters for two ordered extended operation commands, two ordered JEDEC DDR standard operation commands, or two ordered extended operation commands and a JEDEC DDR standard operation command.

[0031] The values ​​of the minimum and maximum time interval parameters are determined by the combination of the types of two ordered operation commands. In this embodiment, the command timing parameter 120 is stored in memory in the form of a two-dimensional matrix. The row and column indices of this two-dimensional matrix correspond to the operation command types, and the matrix cells store the minimum and maximum time interval parameters corresponding to the ordered command pairs consisting of row and column commands. For example, when the row command is an erase command and the column command is a status read command, the minimum time interval parameter stored in the corresponding cell can be 200,000 nanoseconds, and the maximum time interval parameter can be infinity; when the row command is a programming enable command and the column command is a programming confirmation command, the minimum time interval parameter stored in the corresponding cell can be 10 nanoseconds, and the maximum time interval parameter can be 100 nanoseconds; when the row command is an activation command and the column command is a write command, the minimum time interval parameter stored in the corresponding cell can be 50 nanoseconds, and the maximum time interval parameter can be 100 nanoseconds.

[0032] When executing different operation commands, the target memory needs to complete physical processes such as internal level establishment, signal stabilization, material phase transition, or charge migration. If a subsequent command is executed before the preceding command has completed its physical effect, the internal circuitry of the chip will be in an unstable state, leading to data read errors or write failures. For example, if a read operation is executed before the word line voltage reaches the threshold after the activation command is issued, the sampling signal will be in a metastable state, resulting in unreliable data output. Similarly, if a programming confirmation command is executed before the phase change material temperature reaches the crystallization threshold after the programming enable command is issued, the phase change will be incomplete, resulting in data loss. Therefore, the command timing parameter 120 in this embodiment sets a minimum time interval parameter for each pair of ordered operation commands, forcing the controller to allow sufficient physical response time in command scheduling. At the same time, by setting a maximum time interval parameter, it prevents state machine stagnation or resource deadlock caused by waiting timeout, thereby ensuring that the controller can maintain deterministic behavior in long-latency scenarios.

[0033] State-dependent feature 130 is used to specify the internal physical state of memory on which the execution of extended operation commands depends.

[0034] The internal physical states include busy state, erasing state, and programming state.

[0035] It is understood that in this embodiment, the state dependency feature 130 can be stored in memory in the form of a state transition rule lookup table. The lookup table is composed of the current internal physical state and the next operation command that is allowed to be executed. When the current operation command is determined, the lookup table is queried to determine whether the operation command is allowed to be executed under the current internal physical state of the target memory.

[0036] In this embodiment, it may also be specified that when the target memory is in a busy state, only a status read command is allowed to be received; when the target memory is in an erasure state, a status read command or a write pause command is allowed to be received; when the target memory is in a programming state, a status read command or a write resume command is allowed to be received; and when the target memory is in an idle state, an activation command, a programming enable command, an erase command, and a write pause command are allowed to be received.

[0037] It should be noted that changes in the internal physical state of the memory are determined by its own physical operation process. For example, when the verification interface module 200 detects a programming enable command, it updates the internal physical state of the target memory to the programming state based on the state dependency feature 130. When a programming confirmation command is subsequently received and its response signal indicates that the phase transition is complete, the internal physical state is then updated to the idle state. The state transition rule lookup table establishes a deterministic mapping relationship between the internal physical state and the operation command, ensuring that the controller is only allowed to issue the corresponding command when the memory has the physical execution conditions, thereby avoiding command discarding, abnormal response, or hardware damage caused by state mismatch. For example, if the controller forcibly issues a write command before the erase operation is completed, the erase voltage and write voltage will be superimposed on the memory cell, which may break down the dielectric layer. Similarly, receiving an activation command before exiting the programming state will cause word line drive conflicts, resulting in row decoding errors.

[0038] Electrical configuration parameter 140 specifies the level requirements for control signals of the DFI interface and the configuration parameters of the on-chip termination resistor during long delay wait periods.

[0039] Specifically, the electrical configuration parameter 140 can be stored in memory as an electrical parameter configuration register set. This register set includes multiple configuration fields, corresponding to the configuration values ​​of the clock enable signal cke, chip select signal cs_n, reference voltage signal vref, on-chip termination resistor odt, and zq calibration signal zqc, respectively. It can be understood that the values ​​of each configuration parameter can be set through this electrical configuration parameter 140 when performing different operations.

[0040] The control signal level and physical layer parameter configuration of the DFI interface directly affect the stability and reliability of the internal circuitry of the novel non-volatile memory. If the control signal level unexpectedly changes during long-delay operations, it will cause word line or bit line drive abnormalities, leading to incorrect writes or data leaks. If the reference voltage offset exceeds the tolerance, it will cause read threshold drift, resulting in erroneous data output. If the on-chip termination resistor configuration is mismatched, it will cause signal reflection and overshoot, reducing signal integrity, especially exacerbating the bit error rate under high-frequency DFI interfaces. Therefore, in this embodiment, the electrical configuration parameter 140 binds deterministic combinations of electrical parameters to different long-delay operations, thereby ensuring that the controller can maintain the drive capability adapted to the physical characteristics of the target memory during command scheduling intervals, avoiding functional abnormalities or device damage caused by electrical mismatch.

[0041] The verification interface module 200 is used to acquire timing data from the timing behavior construction module 100 during the verification environment initialization phase, and instantiate the timing data into an index structure in memory; it is also used to perform violation checks on the signal flow output by the memory controller under test via the DFI interface according to the index structure, and generate violation check results; it is also used to simulate the physical response behavior of the target memory to the signal flow according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test via the DFI interface, and generate comparison results; it is also used to output a verification report based on the violation check results and comparison results; the verification report includes a violation report and a coverage report.

[0042] Specifically, such as Figure 3 As shown, the verification interface module 200 includes a timing data acquisition unit 210, a protocol monitoring and inspection unit 220, and a memory behavior model 230.

[0043] The timing data acquirer 210 is used to acquire timing data from the timing behavior construction module 100 during the verification environment initialization phase and instantiate the timing data into an index structure in memory.

[0044] Timing data reflects the physical behavior characteristics of the target memory. The verification interface module instantiates the timing data into an index structure in memory and performs violation checks on the DFI interface signal stream based on this index structure, achieving real-time verification of the physical characteristics of the novel non-volatile memory. Simultaneously, the verification interface module simulates the physical response behavior of the target memory based on the same index structure, generating expected response data and comparing it with the actual response data. Since the expected response data and violation checks are based on the same set of timing data, they maintain consistency in physical behavior modeling, and the comparison results accurately reflect the correctness of the tested memory controller's functional implementation.

[0045] For example, the time series data acquirer 210 is used to parse the time series behavior construction module 100. It should be noted that the time series behavior construction module 100 is a machine-readable configuration file (such as a JSON format configuration file). Parsing the time series behavior construction module 100 by the time series data acquirer 210 means parsing the content in the corresponding readable configuration file.

[0046] The parsing process includes, but is not limited to, syntax validation, field extraction, and data type conversion. The parsing process is the same as existing parsing methods and will not be described further here. After parsing, the signal mapping relationship 110, command timing parameters 120, state dependency features 130, and electrical configuration parameters 140 mentioned above can be obtained.

[0047] After obtaining the signal mapping relationship 110, command timing parameters 120, state dependency features 130, and electrical configuration parameters 140, the signal mapping relationship 110 can be filled into the command truth table mapping hash table, the command timing parameters 120 can be filled into the two-dimensional timing constraint matrix, the state dependency features 130 can be filled into the state jump rule lookup table, and the electrical configuration parameters 140 can be filled into the electrical parameter configuration register group.

[0048] It is understood that the timing data acquisition unit 210 completes the above-mentioned parsing and filling operations during the verification environment initialization phase, enabling the verification interface module 200 to adapt to different new types of non-volatile memories without recompilation. Exemplarily, when the verification target is switched from phase-change memory to ferroelectric memory, only the corresponding machine-readable configuration file needs to be replaced. The timing data acquisition unit 210 automatically acquires the new rules and fills the new timing data into the same set of memory data structures. The existing protocol monitor and inspector 220, memory behavior model 230, and test vector generator 240 do not require code modification and can perform verification based on the new rules. This method in this embodiment enables cross-memory reuse of verification assets, thereby shortening the verification environment setup cycle.

[0049] Protocol monitor and inspector 220 is used to perform real-time decoding, timing compliance checks, and status legality checks on the signal stream output by the memory controller under test via the DFI interface, based on the index structure, in order to obtain violation check results.

[0050] Specifically, such as Figure 4 As shown, the protocol monitor and inspector 220 includes: a command decoder 221, a timing state tracker 222, and a dynamic rule inspection engine 223.

[0051] Command decoder 221 is used to perform truth table matching on the level combination of control signals and address signals of the DFI interface at each DFI clock sampling edge according to signal mapping relationship 110, and to identify the operation command issued by the memory controller under test in the current clock cycle. Specifically, the identification process is a "truth table alignment" operation: the command decoder 221 samples the chip select signal cs_n, row address strobe signal ras_n, column address strobe signal cas_n, write enable signal we_n, address bus ca, and memory address signal bank at each rising edge of the DFI interface clock; it performs a bit-to-bit comparison between the sampled signal level combination and the feature codes of each extended operation command pre-stored in the command truth table mapping hash table; when the level state of all sampled signals is completely consistent with the feature code of a certain extended operation command, it is determined that the operation command issued in that clock cycle is the extended operation command.

[0052] It is understandable that the recognition result of the command decoder 221 is the basis for all subsequent timing compliance checks and state legality checks. Only by accurately identifying the type of the current operation command and the storage and row address of its function can the dynamic rule checking engine 223 query the minimum time interval parameter of the corresponding ordered command pair from the two-dimensional timing constraint matrix, and determine from the state jump rule lookup table whether the command is allowed to be executed in the current internal physical state.

[0053] The timing state tracker 222 is used to maintain the timestamp of the most recent relevant operation command issued for each bank and each row of the target memory, as well as the internal physical state of the target memory at the current bank and the current row of the target memory.

[0054] Specifically, the timing state tracker 222 configures an independent state register group for each memory bank. Each state register group contains the same number of state record units as the number of rows in the memory bank. Each state record unit stores the internal physical state value of the corresponding row and the timestamp of the most recent related operation command issued for that row. The internal physical state values ​​include, but are not limited to, busy state, erasing state, programming state, active state, and idle state. The related operation commands include, but are not limited to, activation command, programming enable command, erase command, write pause command, write resume command, and status read command.

[0055] For example, when the command decoder 221 identifies an activation command for row 256 in memory bank 0, the timing status tracker 222 updates the status record cell corresponding to row 256 in the status register group of memory bank 0 to the active state and writes the current DFI interface clock cycle count value into the timestamp field of that cell; when a subsequent programming enable command for the same row in the same memory bank is identified, the timing status tracker 222 updates the status of that row to the programming state and updates the timestamp; when a status read command is identified and its response data is confirmed to contain a busy flag, the timing status tracker 222 maintains the status of that row as the programming state and does not update the timestamp; when a programming confirmation command is identified and its response indicates that the phase transition is complete, the timing status tracker 222 updates the status of that row to the idle state and updates the timestamp.

[0056] In this embodiment, the timing state tracker 222 establishes independent, addressable state and timestamp records for each storage unit and each row, thereby ensuring that the dynamic rule checking engine 223 can obtain physical state information and time references accurate to the row level when performing timing compliance checks and state legality checks.

[0057] The dynamic rule checking engine 223 performs the following checks in response to operation commands identified by the command decoder 221: The actual time interval is calculated based on the command timing parameter 120 and compared with the minimum time interval parameter to perform a timing compliance check.

[0058] Based on state dependency feature 130, determine whether the current internal physical state allows the execution of operation commands, and perform state validity checks.

[0059] Specifically, the dynamic rule checking engine 223 queries the minimum time interval parameter corresponding to the ordered command pair consisting of the preceding related operation command and the current operation command based on the two-dimensional timing constraint matrix. It calculates the actual time interval between the preceding related operation command and the current operation command, and compares the actual time interval with the minimum time interval parameter. If the actual time interval is less than the minimum time interval parameter, it is determined to be a timing violation. Based on the state transition rule lookup table, it queries the execution permission of the current operation command in the current internal physical state of the target memory. If the current internal physical state does not meet the execution conditions specified in the state transition rule lookup table, it is determined to be a state violation. When a timing violation or state violation is determined, the dynamic rule checking engine 223 generates a violation check result. This violation check result includes, but is not limited to, the violation type, the two operation commands that caused the violation, the actual time interval value, the corresponding minimum time interval parameter value, the timestamp of the violation occurrence, the memory bank number where the violation occurred, the row address where the violation occurred, and a complete signal snapshot of the DFI interface at that moment.

[0060] The memory behavior model 230 is used to simulate the physical response behavior of the target memory to the signal flow according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result.

[0061] In this embodiment, the memory behavior model 230 is a parameterized and configurable digital behavior model, whose internal state machine strictly corresponds to the physical behavior of the target memory. The memory behavior model 230 receives the same DFI interface signal stream as the memory controller under test, then identifies the operation command according to the signal mapping relationship 110, determines the completion time of each operation according to the timing parameters between commands 120, updates the internal physical state according to the state dependency features 130, determines the drive parameter configuration of each stage according to the electrical configuration parameters 140, and generates expected response data that conforms to physical laws based on the above information.

[0062] For example, when the command decoder 221 recognizes a programming enable command for row 256 in memory bank 0, the memory behavior model 230 updates the physical state of that row to the programming state and starts an internal timer. When the timer reaches the duration specified by the minimum time interval parameter corresponding to "programming enable command → programming confirmation command" in the two-dimensional timing constraint matrix, the memory behavior model 230 generates a programming confirmation response. If a status read command is received within this duration, the memory behavior model 230 returns a status register value containing a busy flag. If a read command is received after this duration, the memory behavior model 230 returns valid data after error correction encoding. When the command decoder 221 recognizes an erase command, the memory behavior model 230 marks the corresponding memory bank and row address as being in the erasure state, and after the erasure completion time specified by the two-dimensional timing constraint matrix, updates the state of that area to the idle state and clears all associated data bits. The expected response data generated by the memory behavior model 230 includes the status register value, the valid data on the data bus dqi, the phase information of the data strobe signal dqs, and the error check code; the comparison result is the bit-by-bit comparison result between the expected response data and the actual response data on each bit, each clock, and each signal; when any bit does not match at any time, the comparison result is determined to be functionally inconsistent.

[0063] In some implementations, such as Figure 5 As shown, the verification interface module 200 also includes a test vector generator 240.

[0064] The test vector generator 240 is used to generate a constrained random test sequence based on the index structure and apply the constrained random test sequence as an stimulus to the memory controller under test.

[0065] Specifically, such as Figure 6As shown, the test vector generator 240 includes a coverage model builder 241 and a constraint random stimulus generator 242.

[0066] Coverage model builder 241 is used to generate coverage points based on signal mapping relationship 110, command timing parameters 120, and state dependency features 130. The coverage points include all extended operation command types, test scenarios for all ordered extended operation command pairs under minimum time interval parameter boundary conditions, and all state transition paths defined by state dependency features 130.

[0067] In this embodiment, the coverage model builder 241 traverses all extended operation commands defined in the signal mapping relationship 110, treating each command type as an independent coverage point; it traverses all ordered command pairs defined in the command timing parameter 120, generating a preset number (e.g., 3) coverage points for each ordered command pair. If there are 3, they correspond to three boundary scenarios: minimum time interval parameter minus 1 period, equal to the minimum time interval parameter, and plus 1 period; it traverses all state transition paths defined in the state dependency feature 130, treating each valid transition from the current internal physical state to the next internal physical state as a coverage point.

[0068] The coverage points include six extended operation command types: programming enable command, programming confirmation command, write pause command, write resume command, erase command, and status read command; three ordered extended operation command pairs: erase command and status read command, programming enable command and programming confirmation command, and activation command and write command. Each pair generates three coverage points: minimum time interval parameter minus one cycle, equal to the minimum time interval parameter, and plus one cycle; and four state transition paths: idle state to programming state, programming state to busy state, busy state to idle state, and erase state to idle state. The coverage model builder 241 registers all coverage points to the coverage collection engine. The coverage collection engine counts whether each coverage point is triggered in real time during the verification process and generates a coverage report after the simulation ends. The coverage report includes three indicators: command type coverage, ordered command pair boundary coverage, and state transition path coverage. When any indicator is lower than a preset value (such as 95%), it is determined that the coverage is insufficient, and the test generation strategy needs to be adjusted or targeted test cases need to be added.

[0069] The constraint random stimulus generator 242 is used to generate a constraint random test sequence based on the coverage point and apply the constraint random test sequence as a stimulus to the memory controller under test.

[0070] In this embodiment, the constraint random excitation generator 242 can generate test sequences using a constraint randomization method; its inputs include a set of coverage points generated by the coverage model builder 241, a two-dimensional timing constraint matrix, a state transition rule lookup table, and an electrical parameter configuration register set; its output is a command sequence that conforms to all physical constraints, wherein the type, issuance time, target memory, and row address of each operation command in the sequence all satisfy the corresponding constraint conditions.

[0071] The operation of the constrained random stimulus generator 242 includes the following steps: First, it randomly selects an operation command from a predefined command pool. This command pool includes programming enable commands, programming confirmation commands, write pause commands, write resume commands, erase commands, state read commands, activation commands, and write commands. Then, based on the selected operation command, it queries a two-dimensional timing constraint matrix to obtain the preceding and following constraints related to the command. Next, it queries a state transition rule lookup table to obtain the current internal physical state upon which the command execution depends. Finally, it transforms the above constraints into boundary limits for random variables and calls a random number generator to generate the next operation command and its issuance time within the legal range. The constrained random stimulus generator 242 only generates test sequences that satisfy all constraints, ensuring that the generated stimuli possess both random coverage and strict adherence to the physical behavior of the novel non-volatile memory.

[0072] For example, when the constraint random excitation generator 242 randomly selects a programming enable command, it queries the two-dimensional timing constraint matrix to determine that the minimum time interval between it and the subsequent programming confirmation command is 10 nanoseconds, which corresponds to 25 clock cycles (assuming the DFI interface operates at a frequency of 2.5 GHz). Therefore, in subsequent generation, the constraint random excitation generator 242 enforces that the programming confirmation command must not be earlier than the 25th clock cycle after the programming enable command. When the constraint random excitation generator 242 randomly selects an erase command, it queries the state transition rule lookup table to determine that the erase command can only be executed in the idle state. Then, the constraint random excitation generator 242 backtracks to check the internal physical state caused by the preceding command. If the current state is not idle, it automatically inserts a state read command to confirm the state, and generates the erase command only after confirming that the state is idle. When the constraint random excitation generator 242 generates a write command, it queries the electrical parameter configuration register group to determine that the on-chip termination resistor needs to be configured to 60 ohms during the write operation. Therefore, before issuing the write command, the constraint random excitation generator 242 automatically inserts a control command to configure the on-chip termination resistor.

[0073] It is understood that the constrained random test sequence in this embodiment can achieve high-intensity verification of the physical characteristics of novel non-volatile memory, such as long latency, asymmetric read / write, strong state dependence, and complex background operations, by covering all coverage points.

[0074] Protocol monitor and inspector 220 is also used to perform timing compliance checks and status legality checks on the signal stream output by the memory controller under test via the DFI interface according to a constrained random test sequence.

[0075] Exemplary, after the constraint random test sequence is used as an incentive to drive the memory controller under test, the memory controller under test generates a corresponding DFI interface signal stream based on the sequence. The protocol monitor and inspector 220 continuously monitors the signal stream, performs command identification, timestamp recording, and state updates at each DFI interface clock sampling edge, and simultaneously performs timing compliance checks and state validity checks. The timing compliance check covers all ordered extended operation command pairs in three boundary scenarios: minus one period of the minimum time interval parameter, equal to the minimum time interval parameter, and plus one period. The state validity check covers all state transition paths defined by state dependency feature 130. When the constraint random test sequence triggers any uncovered coverage point, the protocol monitor and inspector 220 generates a corresponding violation check result. The memory behavior model 230 is also used to receive a constrained random test sequence and simulate the physical response behavior of the target memory according to the index structure to generate expected response data.

[0076] It is understood that the memory behavior model 230 takes a constrained random test sequence that is exactly the same as that of the memory controller under test as input, identifies the command type according to the signal mapping relationship 110, determines the completion time of each operation according to the two-dimensional timing constraint matrix, updates the internal physical state according to the state jump rule lookup table, configures the drive parameters according to the electrical parameter configuration register group, and generates expected response data that strictly corresponds to the physical behavior. The expected response data includes the status register value, the valid data on the data bus dqi, the valid edge position of the data strobe signal dqs, and the error check code. The expected response data generated by the memory behavior model 230 is compared bit by bit with the actual response data output by the memory controller under test under the same excitation to generate a comparison result.

[0077] For example, when a constrained random test sequence includes a programming enable command followed immediately by a programming confirmation command issued one cycle less than the minimum time interval parameter, the protocol monitor and checker 220 determines it as a timing violation and generates a violation check result including the command pair, the actual time interval, the minimum time interval parameter, and a signal snapshot. Simultaneously, the memory behavior model 230, detecting that the programming confirmation command is earlier than the physical completion time, returns a status register value containing a busy flag as the expected response data. If the memory controller under test outputs valid data instead of a busy flag at that moment, the comparison result is determined to be functionally inconsistent. Similarly, when a constrained random test sequence includes an erase command followed immediately by a write command issued before the erase is complete, the protocol monitor and checker 220 determines it as a state violation. The memory behavior model 230, detecting that the write command is issued while erasing, returns a write failure flag as the expected response data. If the memory controller under test does not return a failure flag, the comparison result is also determined to be functionally inconsistent. This collaborative verification mechanism ensures that the constrained random test sequence can expose not only protocol violations at the timing and state levels but also logical defects at the functional implementation level.

[0078] In some implementations, such as Figure 7 As shown, the verification interface module 200 also includes a physical limit analysis module 250, which is used to determine the effective maximum time interval based on the system refresh cycle, the maximum row activation time and the preset timeout threshold when there is a maximum time interval parameter with no upper limit in the command timing parameter 120.

[0079] Exemplary, the physical limit analysis module 250 receives three input parameters: system refresh cycle tREF, maximum row activation time tRAS_max, and preset timeout threshold. When the maximum time interval parameter corresponding to an ordered command pair in the two-dimensional timing constraint matrix is ​​marked as infinite, the physical limit analysis module 250 performs a minimum value operation, that is, calculates effective_max_cycles = min(tREF, tRAS_max, preset timeout threshold), and uses the calculation result as the effective maximum time interval of the ordered command pair.

[0080] For example, when the maximum time interval parameter corresponding to the erase command and the status read command in the two-dimensional timing constraint matrix is ​​infinite, and the system refresh cycle tREF is 64 milliseconds, the maximum row activation time tRAS_max is 60 microseconds, and the preset timeout threshold is 1 millisecond, the physical limit analysis module 250 calculates effective_max_cycles = min(64000000 ns, 60000 ns, 1000000 ns) = 60000 ns, and takes 60,000 nanoseconds as the effective maximum time interval between the erase command and the status read command.

[0081] It is understood that when generating a test sequence covering the command pair, the constrained random excitation generator 242 no longer randomly samples within an infinite interval, but generates random delay values ​​within a finite interval consisting of the minimum time interval parameter and 60,000 nanoseconds, thereby ensuring that the generated test sequence is both extremely stressful and within a reasonable range that is physically survivable in memory and tolerable in system operation.

[0082] Furthermore, the constrained random excitation generator 242 is also used to generate a constrained random test sequence within a finite interval formed by the minimum time interval and the maximum effective time interval, based on the maximum effective time interval.

[0083] It is understandable that when the constraint random excitation generator 242 needs to generate the issuance time of the successor command for a certain ordered command pair, if the maximum time interval parameter of the command pair is infinite, the constraint random excitation generator 242 calls the physical limit analysis module 250 to obtain the corresponding effective maximum time interval, and uses the effective maximum time interval to replace infinity as the upper bound for random number generation; the constraint random excitation generator 242 then uniformly samples within the closed interval from the minimum time interval parameter to the effective maximum time interval to generate random delay values ​​that satisfy physical constraints and system constraints, and determines the issuance time of the successor command accordingly.

[0084] This embodiment decouples the physical behavior rules of the target memory from the verification logic and structures them into a configurable timing behavior construction module 100. Combined with a general verification interface module 200 supported by an index structure, it achieves high-fidelity verification of novel non-volatile memories such as phase-change memories and ferroelectric memories. Its core effect is that it solves the fundamental problems of traditional VIPs caused by hard-coded DRAM timing, such as long latency adaptation failure, insufficient asymmetric read / write coverage, inability to recognize proprietary commands, and lack of background operation verification. Furthermore, through mechanisms such as dynamic acquisition, dual-track checking (parallel timing compliance and state legality), and coordinated constraint random excitation and physical limit analysis, it supports rapid verification and reuse of multiple types of novel memories without modifying the code. The verification process covers all dimensions of instruction combinations, boundary timing, state transitions, and electrical drives, thereby significantly improving coverage and defect detection rate, shortening the verification cycle, and reducing controller design risk.

[0085] Figure 8 A schematic flowchart of a memory interface timing verification according to an embodiment of this application is shown. Exemplarily, this memory interface timing verification method is applied to the aforementioned memory interface timing verification system, including steps S100-S500: Step S100: During the verification environment initialization phase, obtain the timing data of the timing behavior construction module 100 corresponding to the target memory.

[0086] The timing data is constructed based on the physical timing specifications of the target memory, through signal command association, physical time interval measurement, state transition condition extraction, and electrical characteristic measurement, and corresponds to the physical behavior of the target memory.

[0087] Step S200: Instantiate the time-series data into an index structure in memory.

[0088] Specifically, this step includes: parsing the timing behavior construction module 100 to obtain the signal mapping relationship 110, the inter-command timing parameters 120, the state dependency features 130 and the electrical configuration parameters 140, and filling the signal mapping relationship 110, the inter-command timing parameters 120, the state dependency features 130 and the electrical configuration parameters 140 into the corresponding index structures in memory.

[0089] The index structure includes a command truth table mapping hash table, a two-dimensional timing constraint matrix, a state transition rule lookup table, and an electrical parameter configuration register group. Signal mapping relationships 110 are filled into the command truth table mapping hash table; inter-command timing parameters 120 are filled into the two-dimensional timing constraint matrix, where the row and column indices correspond to the operation command types, and the matrix cells store the minimum and maximum time interval parameters uniquely determined by the combination of two ordered operation command types; state dependency features 130 are filled into the state transition rule lookup table; and electrical configuration parameters 140 are filled into the electrical parameter configuration register group.

[0090] Step S300: Perform violation checks on the signal stream output by the memory controller under test via the DFI interface according to the index structure, and generate violation check results.

[0091] Step S400: Simulate the physical response behavior of the target memory to the signal flow according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result.

[0092] Step S500: Output a verification report based on the violation inspection results and comparison results; the verification report includes a violation report and a coverage report.

[0093] In some implementations, the timing behavior construction module 100 includes: a signal mapping relationship 110, used to map the control signals of the DFI interface to extended operation commands of the target memory; wherein, the extended operation commands are operation commands outside the JEDEC DDR standard command set, and the extended operation commands include programming enable commands, programming confirmation commands, write pause commands, write resume commands, erase commands, and status read commands; The timing parameter 120 between commands specifies the minimum and maximum time interval parameters required between any two ordered operation commands; the operation commands include extended operation commands and JEDEC DDR standard operation commands. State-dependent feature 130 is used to specify the internal physical state of the memory on which the extended operation command depends; wherein, the internal physical state includes busy state, erasing state, and programming state.

[0094] Electrical configuration parameter 140 specifies the level requirements for control signals of the DFI interface and the configuration parameters of the on-chip termination resistor during long delay wait periods.

[0095] In some implementations, the verification interface module 200 includes a timing data acquirer 210, a protocol monitor and inspector 220, and a memory behavior model 230.

[0096] The timing data acquirer 210 is used to acquire the timing behavior construction module 100 during the verification environment initialization phase and instantiate the timing data into an index structure in memory.

[0097] Protocol monitor and inspector 220 is used to perform real-time decoding, timing compliance checks, and status legality checks on the signal stream output by the memory controller under test via the DFI interface, based on the index structure, in order to obtain violation check results.

[0098] The memory behavior model 230 is used to simulate the physical response behavior of the target memory to the signal flow according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result.

[0099] In some implementations, the protocol monitor and inspector 220 includes a command decoder 221, a timing state tracker 222, and a dynamic rule checking engine 223.

[0100] Command decoder 221 is used to perform truth table matching on the level combination of control signals and address signals of the DFI interface at each DFI clock sampling edge according to signal mapping relationship 110, and to identify the operation command issued by the memory controller under test in the current clock cycle.

[0101] The timing state tracker 222 is used to maintain the timestamp of the most recent relevant operation command issued for each bank and each row of the target memory, as well as the internal physical state of the target memory at the current bank and the current row of the target memory. The dynamic rule checking engine 223 performs the following checks in response to operation commands identified by the command decoder 221: The actual time interval is calculated based on the command timing parameter 120 and compared with the minimum time interval parameter to perform a timing compliance check.

[0102] Based on state dependency feature 130, determine whether the current internal physical state allows the execution of operation commands, and perform state validity checks.

[0103] Specifically, violation checks are performed, including: at each DFI clock sampling edge, truth table matching is performed on the level combinations of control signals and address signals of the DFI interface to identify the operation command issued by the memory controller under test in the current clock cycle; in response to the identified operation command, the following parallel checks are performed: according to the two-dimensional timing constraint matrix, the minimum time interval parameter corresponding to the ordered command pair consisting of the preceding related operation command and the current operation command is queried; the actual time interval between the preceding related operation command and the current operation command is calculated; and the actual time interval is compared with the minimum time interval parameter. If the actual time interval is less than the minimum time interval parameter, it is determined to be a timing violation; according to the state jump rule lookup table, the execution permission of the current operation command in the current internal physical state of the target memory is queried; if the current internal physical state does not meet the execution conditions specified in the state jump rule lookup table, it is determined to be a state violation. When a timing violation or state violation is determined, a violation check result is generated.

[0104] In some implementations, the verification interface module 200 further includes a test vector generator 240; the test vector generator 240 is used to generate a constrained random test sequence according to the index structure and apply the constrained random test sequence as an incentive to the memory controller under test. Furthermore, the protocol monitor and inspector 220 is also used to perform timing compliance checks and state legality checks on the signal stream output by the memory controller under test via the DFI interface according to the constrained random test sequence. The memory behavior model 230 is also used to receive the constrained random test sequence and simulate the physical response behavior of the target memory according to the index structure to generate expected response data.

[0105] In some implementations, the test vector generator 240 includes a coverage model builder 241 and a constrained random stimulus generator 242; the coverage model builder 241 is used to generate coverage points based on the signal mapping relationship 110, the command timing parameters 120, and the state dependency features 130; wherein, the coverage points include all extended operation command types, all ordered extended operation command pairs under the minimum time interval parameter boundary condition test scenarios, and all state transition paths defined by the state dependency features 130.

[0106] Furthermore, the constraint random stimulus generator 242 is used to generate a constraint random test sequence based on the coverage point, and apply the constraint random test sequence as a stimulus to the memory controller under test.

[0107] In some implementations, the verification interface module 200 further includes a physical limit analysis module 250; the physical limit analysis module 250 is used to determine the effective maximum time interval based on the system refresh cycle, the maximum row activation time, and a preset timeout threshold when there is a maximum time interval parameter with no upper limit in the command timing parameter 120; furthermore, the constraint random excitation generator 242 is also used to generate a constraint random test sequence within a finite interval formed by the minimum time interval and the effective maximum time interval according to the effective maximum time interval.

[0108] In some implementations, the constraint random stimulus generator 242 is an adaptive constraint random stimulus generator. The adaptive constraint random stimulus generator is used to dynamically adjust the generation strategy of the constraint random test sequence based on the trigger state feedback of the coverage point during the application of the constraint random test sequence to the memory controller under test.

[0109] Specifically, after the coverage model builder 241 registers all coverage points to the coverage collection engine, the coverage collection engine continuously monitors the triggering status of each coverage point during the verification process, i.e., whether each coverage point has been triggered by the constrained random test sequence. When generating the next operation command, the adaptive constrained random excitation generator queries the coverage collection engine to obtain the set of currently untriggered coverage points; then, it queries the timing parameter matrix and the state transition condition index table to determine the timing boundary conditions and unexplored state transition paths corresponding to the untriggered coverage points. For example, if the test scenario of "erasing command and state read command under the minimum time interval parameter boundary condition" in the coverage points has not yet been triggered, the adaptive constrained random excitation generator prioritizes inserting the combination of erasing command and state read command into the constrained random test sequence, and constrains the random delay value between the erasing command and the state read command within the boundary range of minimum time interval parameter minus one period, equal to minimum time interval parameter plus one period. For example, if the state transition path from "programming state to busy state" has not yet been explored, the adaptive constraint random excitation generator will prioritize generating a combination sequence of programming enable commands and state read commands to drive the target memory into the programming state and trigger the transition to the busy state.

[0110] It is understandable that the adaptive constraint random stimulus generator obtains the trigger state feedback of coverage points in real time and dynamically adjusts the generation strategy of constraint random test sequences based on the timing parameter matrix and state transition condition index table stored in the runtime index structure. It prioritizes covering untriggered coverage points and unexplored state transition paths, thus avoiding the coverage blind spots caused by purely random sampling in traditional constraint random test generation. Especially in the long-latency, multi-state scenarios of novel non-volatile memories, the trigger probability of some coverage points (such as extreme boundary timing conditions and rare state transition paths) is extremely low. The adaptive mechanism significantly improves the coverage convergence speed and shortens the verification cycle by guiding the generation of test sequences in a targeted manner.

[0111] It is understood that the specific implementation of the memory interface timing verification system also applies to this embodiment (memory interface timing verification method), so it will not be described again here.

[0112] This application also provides a terminal device, exemplary of which includes a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program to enable the terminal device to perform the functions of the various modules in the memory interface timing verification method or the memory interface timing verification system described above.

[0113] The processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including at least one of a Central Processing Unit (CPU), Graphics Processing Unit (GPU), Network Processor (NP), Digital Signal Processor (DSP), Application-Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor can be a microprocessor or any conventional processor, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application.

[0114] The memory can be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory is used to store computer programs, and the processor can execute the computer programs accordingly after receiving execution instructions.

[0115] This application also provides a computer-readable storage medium for storing the computer program used in the aforementioned terminal device. For example, the computer-readable storage medium may include, but is not limited to, various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0116] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that, in alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0117] In addition, the functional modules or units in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0118] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a smartphone, personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

[0119] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A memory interface timing verification system, characterized in that, include: The timing behavior construction module is used to construct timing data corresponding to the physical behavior of the target memory by constructing signal command association, measuring physical time interval, extracting state transition conditions, and measuring electrical characteristics according to the physical timing specifications of the target memory; wherein, the target memory is a non-volatile memory with asynchronous programming operation function that is connected to the DDR protocol stack through the DFI interface, and the duration of the asynchronous programming operation is greater than a preset time threshold. The verification interface module is used to obtain the timing data of the timing behavior construction module during the verification environment initialization phase, and instantiate the timing data into an index structure in memory. The verification interface module is also used to perform violation checks on the signal stream output by the memory controller under test through the DFI interface according to the index structure, and generate violation check results; The verification interface module is also used to simulate the physical response behavior of the target memory to the signal stream according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result. The verification interface module is also used to output a verification report based on the violation check results and the comparison results; The verification interface module performs real-time verification of the DFI signal stream based on the index structure, and at the same time, the verification interface module relies on the same index structure to simulate the physical response behavior of the target memory.

2. The memory interface timing verification system according to claim 1, characterized in that, The timing behavior construction module includes: The signal mapping relationship is constructed by associating the control signals of the DFI interface with the extended operation commands of the target memory; wherein, the extended operation commands are operation commands outside the JEDEC DDR standard command set; Inter-command timing parameters are used to specify the minimum and maximum time interval parameters required between any two ordered operation commands; wherein, the operation commands include extended operation commands and JEDEC DDR standard operation commands; State-dependent features are used to specify the internal physical state of the memory on which the execution of the extended operation command depends; wherein, the internal physical state includes a busy state, an erasing state, and a programming state; Electrical configuration parameters specify the level requirements for the control signals of the DFI interface and the configuration parameters of the on-chip termination resistors during long delay wait periods.

3. The memory interface timing verification system according to claim 2, characterized in that, The verification interface module includes: a timing data acquirer, a protocol monitor and inspector, and a memory behavior model; The timing data acquisition unit is used to acquire the timing data of the timing behavior construction module during the verification environment initialization phase, and instantiate the timing data into the index structure in memory; The protocol monitor and inspector is used to perform real-time decoding, timing compliance checks, and state legality checks on the signal stream output by the memory controller under test through the DFI interface, based on the index structure, in order to obtain the violation check results. The memory behavior model is used to simulate the physical response behavior of the target memory to the signal flow according to the index structure, generate expected response data, and compare the expected response data with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result.

4. The memory interface timing verification system according to claim 3, characterized in that, The protocol monitor and inspector includes: a command decoder, a timing state tracker, and a dynamic rule inspection engine; The command decoder is used to perform truth table matching on the level combination of the control signal and address signal of the DFI interface at each DFI clock sampling edge according to the signal mapping relationship, and to identify the operation command issued by the memory controller under test in the current clock cycle. The timing state tracker is used to maintain the timestamp of the most recent relevant operation command issued for each memory bank and each row of memory unit of the target memory, as well as the internal physical state of the target memory at the current memory bank and the current row of memory unit. The dynamic rule checking engine is used to perform the following checks in response to the operation command identified by the command decoder: The actual time interval is calculated based on the command timing parameters and compared with the minimum time interval parameter to perform a timing compliance check. Based on the state dependency characteristics, determine whether the current internal physical state allows the execution of the operation command, and perform a state validity check.

5. The memory interface timing verification system according to claim 3, characterized in that, The verification interface module also includes a test vector generator; The test vector generator is used to generate a constrained random test sequence according to the index structure, and apply the constrained random test sequence as an incentive to the memory controller under test. The protocol monitor and inspector is also used to perform the timing compliance check and the state legality check on the signal stream output by the memory controller under test through the DFI interface according to the constraint random test sequence. The memory behavior model is also used to receive the constrained random test sequence and simulate the physical response behavior of the target memory according to the index structure to generate the expected response data.

6. The memory interface timing verification system according to claim 5, characterized in that, The test vector generator includes: a covered model builder and a constrained random stimulus generator; The coverage model builder is used to generate coverage points based on the signal mapping relationship, the command timing parameters, and the state dependency features; wherein, the coverage points include all extended operation command types, all ordered extended operation command pairs under the minimum time interval parameter boundary condition, and all state transition paths defined by the state dependency features. The constraint random stimulus generator is used to generate a constraint random test sequence covering the coverage point based on the coverage point, and to apply the constraint random test sequence as a stimulus to the memory controller under test.

7. The memory interface timing verification system according to claim 6, characterized in that, The verification interface module also includes a physical limit analysis module; The physical limit analysis module is used to determine the effective maximum time interval based on the system refresh cycle, the maximum row activation time, and a preset timeout threshold when there is a maximum time interval parameter with no upper limit in the command timing parameters. The constrained random stimulus generator is further configured to generate the constrained random test sequence within a finite interval formed by the minimum time interval and the maximum effective time interval, based on the maximum effective time interval.

8. A memory interface timing verification method, characterized in that, The memory interface timing verification system according to any one of claims 1-7 includes: During the verification environment initialization phase, the timing data of the timing behavior construction module corresponding to the target memory is obtained; wherein, the timing data is data corresponding to the physical behavior of the target memory constructed according to the physical timing specifications of the target memory through signal command association construction, physical time interval measurement, state transition condition extraction and electrical characteristic measurement. The time-series data is instantiated into an index structure in memory; Based on the index structure, a violation check is performed on the signal stream output by the memory controller under test via the DFI interface, and a violation check result is generated. The physical response behavior of the target memory to the signal flow is simulated according to the index structure to generate expected response data, and the expected response data is compared with the actual response data output by the memory controller under test through the DFI interface to generate a comparison result. A verification report is output based on the violation inspection results and the comparison results.

9. The memory interface timing verification method according to claim 8, characterized in that, The instantiation of the time-series data into an in-memory index structure includes: The timing behavior construction module is parsed to obtain signal mapping relationships, inter-command timing parameters, state dependency features, and electrical configuration parameters. The signal mapping relationships, inter-command timing parameters, state dependency features, and electrical configuration parameters are then filled into the corresponding index structures in memory. The index structures include a command truth table mapping hash table, a two-dimensional timing constraint matrix, a state transition rule lookup table, and an electrical parameter configuration register group. The command truth table mapping hash table is used to populate the signal mapping relationship; The timing parameters between commands are filled into a two-dimensional timing constraint matrix. The row index and column index of the two-dimensional timing constraint matrix correspond to the operation command type, respectively. The matrix cell stores the minimum time interval parameter and the maximum time interval parameter, which are uniquely determined by the combination of the types of two ordered operation commands. The state dependency features are populated into the state transition rule lookup table; The electrical configuration parameters are populated into the electrical parameter configuration register group.

10. The memory interface timing verification method according to claim 9, characterized in that, The violation checks include timing compliance checks and status legality checks; The execution of violation checks includes: At each DFI clock sampling edge, truth table matching is performed on the level combination of the control signal and address signal of the DFI interface to identify the operation command issued by the memory controller under test in the current clock cycle; In response to the identified operation command, the following parallel checks are performed: Based on the two-dimensional timing constraint matrix, query the minimum time interval parameter corresponding to the ordered command pair consisting of the preceding related operation command and the current operation command, calculate the actual time interval between the preceding related operation command and the current operation command, and compare the actual time interval with the minimum time interval parameter. If the actual time interval is less than the minimum time interval parameter, it is determined to be a timing violation. According to the state transition rule lookup table, the execution permission of the current operation command in the current internal physical state of the target memory is queried; if the current internal physical state does not meet the execution conditions specified in the state transition rule lookup table, it is determined to be a state violation. When a timing violation or state violation is determined, a violation check result is generated.

Citation Information

Patent Citations

  • DRAM (Dynamic Random Access Memory) state management method and system and terminal equipment

    CN121996465A

  • Time sequence verification method and device, electronic equipment and storage medium

    CN122412266A