A method and apparatus for automatically generating post-simulation timing masking configurations based on SpyGlassCDC rule type mapping
By parsing the SpyGlass CDC report and generating the notimingcheck.cfg configuration file, the problem of missing IP instance names was solved, achieving efficient and accurate post-simulation timing masking, and improving the efficiency and reliability of chip verification.
Patent Information
- Application Number
- CN202611284988.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-24
- Publication Date
- 2026-11-17
AI Technical Summary
In the existing technology, the notimingcheck configuration file generation method based on IP module instantiation name is difficult to cover all actual scenarios, resulting in the omission of asynchronous paths. Furthermore, the risk of omission increases when chip design is iterated or IP modules are updated, affecting the efficiency and reliability of post-simulation verification.
By directly utilizing the SpyGlass CDC check report, the system parses signal names, identifies DFT register instances, and performs hierarchical adaptation to generate the notimingcheck.cfg configuration file, thus achieving automated bridging from CDC check results to post-simulation masking commands.
It significantly reduced the asynchronous path omission rate, improved the efficiency and reliability of post-simulation verification, shortened the configuration time, and reduced labor costs.
Smart Images

Figure CN123117005A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of chip verification technology, and in particular relates to a method and apparatus for automatically generating post-simulation timing masking configurations based on SpyGlassCDC rule type mapping. Background Technology
[0002] In the chip design flow, post-simulation is a crucial step in timing simulation of the gate-level netlist after synthesis, placement, and routing. Post-simulation verifies whether the timing behavior of the chip after actual physical implementation meets the design expectations by back-annotating the SDF (Standard Delay Format) timing information onto the netlist.
[0003] In the post-simulation phase, due to phase and frequency differences between clock domains, cross-clock domain signals and asynchronous reset signals do not meet the traditional setup / hold or recovery / removal check conditions. This leads to numerous timing violation alarms and X-state (Unknown State) propagation during simulation, severely impacting simulation progress and result judgment. Therefore, post-simulation typically requires loading a notimingcheck (timing masking configuration) file to disable corresponding timing checks for asynchronous paths that have already undergone CDC checks.
[0004] The timing check masking requirements in the post-simulation stage are fundamentally different from the asynchronous path timing constraint requirements in the chip back-end physical implementation stage. In the back-end physical implementation stage, engineers typically use static timing analysis tools such as PrimeTime to extract asynchronous paths and generate timing constraint commands such as `set_max_delay`, which are written to the SDC (Synopsys Design Constraints) file. The purpose of the `set_max_delay` constraint is to set an upper limit on the transmission delay of the asynchronous path, constraining the back-end placement and routing tools to control trace length and delay during physical implementation, ensuring timing convergence of the asynchronous path in the back-end stage. The `set_max_delay` constraint does not disable timing checks; rather, it guides the back-end tools to optimize the physical implementation by setting a delay upper limit. In contrast, the `tcheck` commands in the post-simulation stage (such as `SETUPHOLD` and `RECREM`) completely disable timing checks for specified register instances, preventing setup / hold or recovery / removal violation alarms during post-simulation and thus avoiding X-state propagation interference with functional verification. The asynchronous path processing in the back-end stage is "constraining timing", while the asynchronous path processing in the post-simulation stage is "masking timing checks". The two have different technical purposes, output formats and application stages, and cannot be substituted for each other.
[0005] In existing technologies, the notimingcheck configuration file required for post-simulation is typically extracted based on IP modules (Intellectual Property Modules) using a unified instantiation name. Verification engineers establish a set of general instantiation name matching rules based on the design specifications and historical experience of each IP module. They then use scripts to retrieve register instances that match the rules from the gate-level netlist, thereby generating a list of tcheck commands. However, with the increasing scale of chips, SoC (System on Chip) designs contain hundreds or even thousands of IP modules. The instantiation relationships between these modules exhibit highly diverse and hierarchical characteristics. A unified instantiation name matching rule cannot cover all actual instantiation scenarios, leading to some asynchronous paths not being correctly identified and masked, resulting in omissions in the notimingcheck configuration file. When the design iterates or IP module versions are updated, the instantiation name rules need to be maintained synchronously, further increasing the risk of omissions and labor costs.
[0006] In the field of chip design verification, there is a long-standing technical bias: the industry generally believes that SpyGlass CDC check reports are a product of the front-end design verification stage, used only to find and locate cross-clock domain design defects in RTL (Register-Transfer Level) code. Its output format (CSV rule report) is designed for design engineers to review and fix code, and is not suitable for the post-simulation stage. Therefore, when generating notifyingcheck configuration files, verification engineers do not think of directly using SpyGlass CDC reports as a data source, but habitually rely on extraction methods based on IP module instantiation names. This technical bias has led to a long-standing but unresolved problem—how to automatically generate complete and accurate notifyingcheck configuration files based on the actual asynchronous path information of the design.
[0007] Overcoming the aforementioned technical biases and automatically generating a complete and accurate notimingcheck configuration file based on the actual asynchronous path report generated by SpyGlass CDC is a technical problem that urgently needs to be solved in the field of chip post-simulation. Summary of the Invention
[0008] The purpose of this invention is to solve the problem in the background art that the extraction of asynchronous paths based on IP module instance names is prone to omissions, resulting in incomplete notimingcheck configuration files. The invention proposes a method and device for automatically generating post-simulation timing masking configurations based on SpyGlassCDC rule type mapping.
[0009] An automatic generation method for post-simulation timing masking configuration based on SpyGlass CDC rule type mapping includes:
[0010] Obtain the rule report file generated by SpyGlass CDC inspection;
[0011] The rule report file includes cross-clock domain data, control signal synchronization rule report, and reset signal synchronization rule report; the rule report file is parsed to remove comment lines that start with comment symbols, and the signal names are extracted by matching columns with column headers of DES SIGNAL or containing target signal identifiers such as DEST, and the bus-format signal names are expanded into bit-level signal names;
[0012] Using SpyGlass's sg_shell command-line interface, the corresponding driver or load register instance is queried based on the name of each level signal. Simultaneously, sg_shell performs keyword matching on the register instance paths in the design netlist to identify DFT register instances containing DFT (Design for Testability) keywords such as scan, dft, and test. The register instance paths are then adapted hierarchically, replacing the prefix of the SpyGlass query path with the prefix of the top-level module of the post-simulation verification environment. Based on the type of the rule report file, the corresponding timing check masking command type is determined: for cross-clock domain data and control signal synchronization rule reports, setup / hold timing check masking commands are used; for reset signal synchronization rule reports, recovery or removal timing check masking commands are used; and for DFT register instances, all timing check masking commands are used.
[0013] When a register instance simultaneously satisfies both the DFT register instance condition and the mapping condition of a certain CDC rule report type, all timing check masking commands are preferentially used; the register instance is combined with the corresponding timing check masking command to generate a post-simulation timing check masking configuration file in notimingcheck.cfg format.
[0014] Based on the same inventive concept, this application also provides an automatic generation device for post-simulation timing masking configuration, including a report acquisition module, a signal parsing module, a register query module, a hierarchy adaptation module, a command mapping module, and a file generation module.
[0015] The modules collaborate in the order of data flow: the report acquisition module reads the rule report file from the SpyGlass CDC project; the signal parsing module extracts the signal name and performs bit width expansion; the register query module queries the gate-level register instance corresponding to each level signal through the sg_shell interface and identifies the DFT register; the hierarchical adaptation module completes the top-level prefix replacement of the register instance path; the command mapping module maps the rule report type and DFT marking results to three types of tcheck commands: SETUPHOLD, RECREM, or ALL; and finally, the file generation module merges and outputs the notimingcheck.cfg configuration file.
[0016] This solution can also be implemented using computer equipment and storage media: the computer equipment includes a memory and a processor, the storage media stores a computer program, and when the program is loaded and executed by the processor, it implements the steps of the above-mentioned automatic generation method for post-simulation timing masking configuration.
[0017] This application directly utilizes the SpyGlass CDC report to extract asynchronous paths, breaking the long-standing industry bias that CDC reports are merely front-end design inspection artifacts. The CDC report is generated based on comprehensive RTL-level static analysis, covering all cross-clock domain and asynchronous reset paths in the design, offering greater completeness compared to extraction methods based on IP instance names.
[0018] The core innovation of this application lies in establishing a semantic bridge across technology systems. CDC rule types (Ac_sync / Reset_sync) are categorized based on front-end design inspection standards, while tcheck commands (SETUPHOLD / RECREM / ALL) are categorized based on post-simulation timing inspection mechanisms. These belong to different technology systems and do not have a natural correspondence. This application achieves automated bridging from CDC check results to post-simulation masking commands by establishing a pre-defined mapping relationship between the two and a mapping from DFT keywords to ALL commands.
[0019] In the processing of DFT registers, this application realizes a shift in thinking from "passive exclusion" to "active inclusion and precise masking"—instead of removing DFT registers from the configuration, it actively identifies them through DFT keywords and uses the ALL command to disable all timing checks, which not only avoids the DFT logic from generating X-state interference in post-simulation, but also implements a differentiated masking strategy.
[0020] In large-scale SoC designs containing approximately 10 million gate-level cells, traditional extraction methods based on IP instance names require an average of 2 to 3 days for each post-simulation preparation, and approximately 5% to 10% of asynchronous paths are still missed. Using the method described in this application, the entire process can be completed in only about 1 to 2 hours, reducing the omission rate to near zero, and significantly improving the efficiency and reliability of post-simulation verification.
[0021] To more clearly illustrate the functional characteristics and structural parameters of the present invention, further explanation is provided below in conjunction with the accompanying drawings and specific embodiments. Attached Figure Description
[0022] Figure 1 A flowchart illustrating the automatic generation method for post-simulation timing masking configuration based on SpyGlass CDC rule type mapping provided in this application embodiment;
[0023] Figure 2 A schematic diagram illustrating the expanded signal name bit width provided in an embodiment of this application;
[0024] Figure 3 A schematic diagram of the structure of the automatic generation device for post-simulation timing masking configuration based on SpyGlass CDC rule type mapping provided in the embodiments of this application;
[0025] Figure 4 A schematic diagram illustrating hierarchical path adaptation provided in the embodiments of this application. Detailed Implementation
[0026] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0027] Please see Figure 1 , Figure 1 This is a flowchart illustrating the automatic generation method for post-simulation timing masking configuration based on SpyGlass CDC rule type mapping provided in this application embodiment. The method includes:
[0028] Step S101: Obtain the rule report file generated by SpyGlass CDC inspection.
[0029] During the chip front-end design verification phase, the SpyGlass tool is used to perform CDC checks on the RTL code and generate rule reports. The SpyGlass CDC check generates corresponding rule report files for different types of cross-clock domain and asynchronous reset issues. In this embodiment, the required rule report files are located in the clock-reset folder of the gate-level netlist SpyGlass CDC project, including three files: Ac_sync01.csv, Ac_sync02.csv, and Reset_sync02.csv.
[0030] Among them, Ac_sync01.csv and Ac_sync02.csv are cross-clock domain data and control signal synchronization rule reports, which record the path information for SpyGlass to read when data signals and control signals are transmitted across asynchronous clock domains in the design; Reset_sync02.csv is a reset signal synchronization rule report, which records the path information for SpyGlass to read when asynchronous reset signals are synchronized across clock domains in the design; the CSV files separate the fields with commas, and the column header of the signal name field is DES SIGNAL or contains the target signal identifier such as DEST.
[0031] Step S102: Parse the rule report file, extract the signal name, and expand the bit width.
[0032] Use a Python script to read a CSV file, remove comment lines that start with a hash symbol (#), and extract the signal name field from the data rows;
[0033] The column order of the CSV files output by different versions of the SpyGlass CDC tool varies. After splitting each row of data into fields using commas as delimiters, the column containing the signal name field is dynamically located by matching the column header name, including columns that identify the target signal, such as DES SIGNAL or DEST, to adapt to the output format of different versions of SpyGlass.
[0034] SpyGlass CDC reports are generated at the RTL level, and the recorded signal names include bit-width identifiers in bus format, such as data_bus[31:29]; in the gate-level netlist, each bit corresponds to an independent register instance, thus expanding the bus format into a bit-level format; see [link to relevant documentation]. Figure 2 , Figure 2 This is a schematic diagram of the signal name bit width expansion provided in the embodiments of this application. Taking the signal data_bus[31:29] as an example, the bit width identifier[31:29] at the end of the signal is identified, and each bit of the bit width identifier is expanded into an independent bit-level signal, namely three bit-level signals: data_bus
[31] , data_bus
[30] and data_bus
[29] . Each bit-level signal occupies a separate line, generating a list of bit-level signal names; scalar signals without bit width identifiers are output directly without changing them.
[0035] Step S103: Query and identify registers based on keywords through the SpyGlass query interface, and adapt the hierarchical path according to the post-simulation verification environment;
[0036] Step S103a: Query the register instance corresponding to each level signal through the SpyGlass query interface.
[0037] The list of bit-level signal names generated in step S102 is used as input, and the SpyGlass sg_shell command-line interface is called to query. sg_shell supports querying driver or load register instances based on signal names. In this embodiment, for each bit-level signal name, the corresponding gate-level register instance path is obtained through sg_shell. sg_shell directly operates on the SpyGlass parsed design database, which can accurately reflect the instance mapping relationship from RTL to gate-level synthesis, thereby ensuring the accuracy of the query results.
[0038] Step S103b: Identify the DFT register instance based on the DFT instance keyword.
[0039] In chip design, Design for Testability (DFT) logic includes scan chain registers and test clock control registers. These registers have independent clock paths and timing constraints in scan mode, exhibiting fundamentally different timing behavior compared to functional mode. During post-functional simulation, DFT registers can trigger timing violation alarms, requiring timing checks and masking.
[0040] In this embodiment, the register instances in the design netlist are traversed by sg_shell, and the register instances belonging to the DFT logic are identified by matching and filtering according to the preset DFT instance keywords. The DFT instance keywords include: scan, dft, test, tck, tdi, tdo, tms, trst.
[0041] Step S103c: Perform hierarchical path adaptation based on the post-simulation verification environment.
[0042] In SpyGlass CDC projects, the top-level instance of the design netlist is typically the chip design module itself (e.g., `top`). In post-simulation verification environments, verification engineers often wrap one or more testbenchwrappers (e.g., `tb_top.dut`) around the chip design module to provide simulation stimuli and monitoring interfaces. Therefore, the register instance path obtained by SpyGlass queries begins with the prefix `top`, while the path to the same register instance accessible in post-simulation tools begins with the prefix `tb_top.dut.top`. If the SpyGlass query path is directly written into `notificationcheck.cfg`, the post-simulation tool will be unable to locate the corresponding register instance, causing the `tcheck` command to fail.
[0043] To address the aforementioned issues, this application performs hierarchical adaptation processing on the register instance paths obtained from the SpyGlass query before generating the tcheck command. The prefix of the register instance path is replaced with the top-level module prefix of the post-simulation verification environment; for example, top.mod_a.submodule.ff_ctrl_sig_3_ is replaced with tb_top.dut.top.mod_a.submodule.ff_ctrl_sig_3_. The prefix replacement rules are specified through a configuration file. Different projects configure different top-level module prefixes according to the actual hierarchical structure of their post-simulation verification environment, thereby achieving universal adaptation across projects.
[0044] Step S104: Determine the timing check blocking command type based on the rule report type.
[0045] The type of SpyGlass CDC rule report directly reflects the timing violation characteristics of the corresponding asynchronous path; Ac_sync01 and Ac_sync02 rules address data / control signal synchronization issues across clock domains, with timing violation types being setup / hold violations; Reset_sync02 rules address reset signal synchronization issues, with timing violation types being recovery / removal violations; the tcheck command in the post-simulation tool needs to match the above timing violation types: setup / hold violations require the use of the SETUPHOLD type masking command, and recovery / removal violations require the use of the RECREM type masking command;
[0046] When generating the simulation timing check masking command, the mapping is distinguished according to the source type of the rule report and the DFT instance keyword matching results, based on the preset mapping relationship:
[0047] For paths originating from Ac_sync01.csv and Ac_sync02.csv, corresponding to setup / hold timing violations, the setup / hold timing check masking command format is used: add tcheck { before each register instance and add} at the end of the line. SETUPHOLD -msg -disable -xgen -disable -r;
[0048] For paths originating from Reset_sync02.csv, corresponding to recovery / removal timing violations, the recovery / removal timing check masking command format is as follows: add tcheck { before each register instance and add} at the end of the line: RECREM -msg -disable -xgen -disable -r;
[0049] For DFT register instances identified by DFT instance keywords, use the full timing check mask command format: add tcheck { before each register instance and} at the end of the line. ALL -msg -disable -xgen -disable -r;
[0050] In post-simulation tools, the ALL command covers the full semantics of SETUPHOLD and RECREM, and is suitable for scenarios where timing checks need to be completely disabled.
[0051] If the same register instance is hit by both the DFT keyword and a certain CDC rule report (e.g., a certain scan register appears in Ac_sync01.csv at the same time), the ALL command is used first to mask all timing checks, instead of using the SETUPHOLD or RECREM command corresponding to the CDC rule; the timing behavior of DFT registers in scan chain mode is quite different from that in functional mode, and masking only one type of setup / hold or recovery / removal is not enough to cover all violations;
[0052] The SpyGlass CDC tool itself does not output tcheck commands usable in post-simulation. The rule type classification (Ac_sync01 / 02, Reset_sync02) is based on the front-end design inspection standards, aiming to guide the repair of cross-clock domain defects in RTL. The classification of post-simulation tcheck commands (SETUPHOLD, RECREM, ALL) is based on the timing inspection mechanism of the simulation tool, aiming to control X-state generation. These two belong to different technical systems and have no inherent correspondence. Faced with post-simulation X-state problems, verification engineers typically start with the simulation tool itself (e.g., manually writing rules, batch extraction by IP instance name), and do not consider directly using the rule types in the front-end CDC report to determine the post-simulation masking commands. This solution establishes a mapping relationship between the two, as well as a mapping from DFT keywords to the ALL command, achieving automated bridging from CDC check results to post-simulation masking commands.
[0053] Step S105: Merge and generate the notimingcheck.cfg configuration file.
[0054] The timing check masking commands are merged into a single configuration file notimingcheck.cfg. The file is organized according to the syntax of post-simulation tools (such as VCS and Xcelium). By loading the configuration file, the post-simulation tools disable the corresponding timing checks for the register instances specified in the file, thereby avoiding X-state interference caused by cross-clock domains and asynchronous reset paths in the simulation.
[0055] In practical applications, before step S105, the register instances obtained from the sg_shell query can be validated to identify and exclude boundary registers belonging to the chip's input / output ports. The timing relationships of I / O ports follow specific interface protocol specifications and are managed by independent I / O timing constraints. DFT register instances have already been identified separately in step S103b and processed by the command mapping module using the ALL command; this is a functional processing rather than exclusion, and therefore not within the scope of this validation. Through the above validation, the asynchronous paths in the functional logic can be further focused on, improving the targeting and accuracy of the notimingcheck configuration file.
[0056] Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of the automatic generation device for post-simulation timing masking configuration based on SpyGlass CDC rule type mapping provided in this application embodiment. The device includes a report acquisition module 310, a signal parsing module 320, a register query module 330, a DFT recognition module 335, a hierarchy adaptation module 325, a command mapping module 340, and a file generation module 350;
[0057] The modules are connected sequentially according to the data flow order: the report acquisition module 310 reads the rule report file from the SpyGlass CDC project and hands it over to the signal parsing module 320 to extract the signal name and complete the bit width expansion;
[0058] Register lookup module 330 queries the gate-level register instance corresponding to each level signal through the sg_shell interface; DFT recognition module 335 traverses the design netlist through sg_shell, filters out DFT registers based on preset keywords and marks them.
[0059] The hierarchical adaptation module 325 replaces the prefix of the register instance path with the prefix of the top-level module of the post-simulation verification environment;
[0060] The command mapping module 340 maps the rule report type and DFT tagging results to three types of tcheck commands: SETUPHOLD, RECREM, or ALL. Finally, the file generation module 350 merges and outputs the notimingcheck.cfg configuration file.
[0061] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.
Claims
1. An automatic generation method for post-simulation timing masking configuration based on SpyGlassCDC rule type mapping, characterized in that, The method includes: Step S101: Obtain the rule report file generated by SpyGlass CDC inspection; Step S102: Parse the rule report file, extract the signal name, and expand the bit width; Step S103: Query and identify registers based on keywords through the SpyGlass query interface, and adapt the hierarchical path according to the post-simulation verification environment; Step S104: Determine the timing check blocking command type based on the rule report type; Step S105: Merge and generate the notimingcheck.cfg configuration file.
2. The method according to claim 1, characterized in that, Step S101: Obtain the rule report file generated by the SpyGlass CDC inspection; including: During the chip front-end design verification phase, the SpyGlass tool is used to perform CDC checks on the RTL code and generate rule reports. The SpyGlass CDC check generates corresponding rule report files for different types of cross-clock domain and asynchronous reset issues. The required rule report files are located in the clock-reset folder of the gate-level netlist SpyGlass CDC project, including three files: Ac_sync01.csv, Ac_sync02.csv, and Reset_sync02.csv. Among them, Ac_sync01.csv and Ac_sync02.csv are cross-clock domain data and control signal synchronization rule reports, which record the path information for SpyGlass to read when data signals and control signals are transmitted across asynchronous clock domains in the design; Reset_sync02.csv is a reset signal synchronization rule report, which records the path information for SpyGlass to read when asynchronous reset signals are synchronized across clock domains in the design; the CSV files separate the fields with commas, and the column header of the signal name field is DESSIGNAL or contains the target signal identifier such as DEST.
3. The method according to claim 2, characterized in that, Step S102: Parse the rule report file, extract the signal names and perform bit-width expansion, including: Use a Python script to read a CSV file, remove comment lines that start with a hash symbol (#), and extract the signal name field from the data rows; The column order of the CSV files output by different versions of the SpyGlass CDC tool varies. After splitting each row of data into fields using commas as delimiters, the column containing the signal name field is dynamically located by matching the column header name, including columns that identify the target signal, such as DES SIGNAL or DEST, to adapt to the output format of different versions of SpyGlass. SpyGlass CDC reports are generated at the RTL level, and the recorded signal names include a bit-width identifier in the form of a bus. In the gate-level netlist, each bit corresponds to an independent register instance, so the bus form is expanded into a bit-level form. Each bit of the bit-width identifier is expanded into an independent bit-level signal, with each bit-level signal occupying a separate line, generating a list of bit-level signal names. Scalar signals without bit-width identifiers are left unchanged and output directly.
4. The method according to claim 3, characterized in that, Step S103: Query and identify registers based on keywords through the SpyGlass query interface, and adapt the hierarchical path according to the post-simulation verification environment; include: Step S103a: Query the register instance corresponding to each level signal through the SpyGlass query interface; The list of bit-level signal names generated in step S102 is used as input to query the SpyGlass sg_shell command-line interface. sg_shell supports querying driver or load register instances based on signal names. For each bit-level signal name, the corresponding gate-level register instance path is obtained through sg_shell. sg_shell directly operates on the design database that SpyGlass has already parsed. Step S103b: Identify the DFT register based on the DFT instance keyword; In post-functional simulation, the DFT register will trigger a timing violation alarm, which needs to be masked by timing checks. The register instances in the design netlist are traversed by sg_shell, and the register instances belonging to the DFT logic are identified by matching and filtering according to the preset DFT instance keywords. The DFT instance keywords include: scan, dft, test, tck, tdi, tdo, tms, trst. Step S103c: Perform hierarchical path adaptation based on the post-simulation verification environment; The register instance path obtained by SpyGlass query starts with the prefix "top", while the same register instance path accessible in the simulation tool starts with the prefix "tb_top.dut.top". Before generating the tcheck command, the register instance paths obtained from the SpyGlass query are subjected to hierarchical adaptation processing. The prefix of the register instance path is replaced with the top-level module prefix of the post-simulation verification environment; top.mod_a.submodule.ff_ctrl_sig_3_ is replaced with tb_top.dut.top.mod_a.submodule.ff_ctrl_sig_3_. The prefix replacement rules are specified through the configuration file. Different projects configure different top-level module prefixes according to the actual hierarchical structure of their post-simulation verification environment, thereby achieving universal adaptation across projects.
5. The method according to claim 4, characterized in that, Step S104: Determine the timing check masking command type based on the rule report type, including: The type of SpyGlass CDC rule report directly reflects the timing violation characteristics of the corresponding asynchronous path; Ac_sync01 and Ac_sync02 rules address data / control signal synchronization issues across clock domains, with timing violation types being setup / hold violations; Reset_sync02 rules address reset signal synchronization issues, with timing violation types being recovery / removal violations; the tcheck command in the post-simulation tool needs to match the above timing violation types: setup / hold violations require the use of the SETUPHOLD type masking command, and recovery / removal violations require the use of the RECREM type masking command; When generating the simulation timing check masking command, the mapping is distinguished according to the source type of the rule report and the DFT instance keyword matching results, based on the preset mapping relationship: For paths originating from Ac_sync01.csv and Ac_sync02.csv, corresponding to setup / hold timing violations, the setup / hold timing check masking command format is used: add tcheck { before each register instance and add} at the end of the line. SETUPHOLD -msg -disable -xgen -disable -r; For paths originating from Reset_sync02.csv, corresponding to recovery / removal timing violations, the recovery / removal timing check masking command format is as follows: add tcheck { before each register instance and add} at the end of the line: RECREM -msg -disable -xgen -disable -r; For DFT register instances identified by DFT instance keywords, use the full timing check mask command format: add tcheck { before each register instance and} at the end of the line. ALL -msg -disable -xgen -disable -r; In post-simulation tools, the ALL command covers the full semantics of SETUPHOLD and RECREM, and is suitable for scenarios where timing checks need to be completely disabled. If the same register instance is hit by both the DFT keyword and a certain CDC rule report, the ALL command is used first to mask all timing checks, instead of using the SETUPHOLD or RECREM command corresponding to the CDC rule. The timing behavior of the DFT register in scan chain mode differs significantly from that in functional mode, and masking only one type of setup / hold or recovery / removal is insufficient to cover all violations.
6. The method according to claim 5, characterized in that, Step S105: Merge and generate the notimingcheck.cfg configuration file, including: The timing check masking commands are merged into a single configuration file notimingcheck.cfg. The file is organized according to the syntax of the post-simulation tool. By loading the configuration file, the post-simulation tool disables the corresponding timing checks for the register instances specified in the file, thereby avoiding X-state interference in the simulation caused by cross-clock domains and asynchronous reset paths.
7. An automatic generation device for post-simulation timing masking configuration based on SpyGlassCDC rule type mapping, the device being used to implement any one of the methods of claims 1 to 6, characterized in that, The device includes a report acquisition module (310), a signal parsing module (320), a register query module (330), a DFT recognition module (335), a hierarchy adaptation module (325), a command mapping module (340), and a file generation module (350). Each module is connected sequentially according to the data flow order: the report acquisition module (310) reads the rule report file from the SpyGlass CDC project and hands it over to the signal parsing module (320) to extract the signal name and complete the bit width expansion; The register lookup module (330) queries the gate-level register instances corresponding to each level signal through the sg_shell interface; the DFT recognition module (335) traverses the design netlist through sg_shell, filters out DFT registers based on preset keywords, and marks them. The hierarchical adaptation module (325) replaces the prefix of the register instance path with the prefix of the top-level module of the post-simulation verification environment; The command mapping module (340) maps the rule report type and DFT tagging results to three types of tcheck commands: SETUPHOLD, RECREM, or ALL. Finally, the file generation module (350) merges and outputs the notimingcheck.cfg configuration file.
