The general file structure of the verification environment, its setup method, equipment, and media
By adopting a unified dv directory structure and hierarchical division in the verification environment, the problem of migration difficulties caused by differences in verification environment setup is solved, and the universality and efficient management of the verification environment are achieved.
Patent Information
- Application Number
- CN202611262677.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-19
- Publication Date
- 2026-11-10
AI Technical Summary
The existing verification environment relies on manual setup by individual engineers, resulting in significant differences between verification environments set up by different engineers. This makes migration time-consuming, labor-intensive, and difficult to manage.
A unified verification environment dv directory structure is adopted, which is divided into unit test, integration test and system test directories according to the verification level, and fixed subdirectories are configured under each directory to achieve unified archiving and classified storage of files.
It achieves universality and formatting of the verification environment, reduces the time cost of environment transfer, and provides a solid foundation for a general verification platform.
Smart Images

Figure CN123068366A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of integrated circuit verification technology, specifically to a general file architecture for a verification environment and its setup method, equipment, and media. Background Technology
[0002] As the scale of integrated circuit chip design continues to increase, EDA verification has become an indispensable part of chip development. Among the various challenges, setting up the verification environment is paramount. Currently, verification environments are built manually by engineers based entirely on their individual experience, resulting in significant differences between environments built by different engineers. This leads to the following problems:
[0003] Once an engineer has set up a verification environment, if it needs to be transferred to another engineer for management, the other engineers will need to invest a lot of time in the early stages to identify it because everyone's setup habits are different. Because the file structure is very different, it will take a lot of time and effort for others to find things in the verification environment. At the same time, the difficulty of managing the verification environment will also increase because everyone's verification environment is different. Summary of the Invention
[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a universal file architecture for a verification environment, as well as its construction method, device, and medium.
[0005] The objective of this invention is achieved through the following technical solution:
[0006] Firstly, this application discloses a method to uniformly aggregate all verification environments under the top-level verification environment dv directory, and to divide the verification environment dv directory into unit test directory UT, integration test directory IT, and system test directory ST according to the verification level. The unit test directory UT, integration test directory IT, and system test directory ST adopt the same lower-level subdirectory architecture, and each is configured with several Block_xx verification subdirectories. Each Block_xx verification subdirectory is an independent and simulable smallest verification unit.
[0007] Based on the first aspect, the Block_xx verification subdirectory is fixedly configured with thirteen subdirectories, specifically including:
[0008] The first subdirectory, cenv, is used to store the compilation environment files for the C code programs required for CPU verification.
[0009] The second subdirectory cfg is used to store configuration files related to electronic design automation (EDA) simulation tools and simulation scripts, as well as simulation file list and regression list files;
[0010] The third subdirectory, cov, is used to store coverage-related files, including configuration files used for coverage collection, coverage collection (covergroup) files used for functional coverage, data files for merging coverage, and files for excluding coverage.
[0011] The fourth subdirectory, define, is used to store macro-related files, including address macros and hierarchy define macros for modules in the design.
[0012] The fifth subdirectory, dft, is used to store files related to design for testability.
[0013] The sixth subdirectory, doc, is used to store non-code documents during the verification process, including Excel spreadsheets, Word documents, or TXT documents.
[0014] The seventh subdirectory, env, is used to store UVM-related files, including interface, component, object, agent, or UVC.
[0015] The eighth subdirectory, model, is used to store driver or device behavior model files;
[0016] The ninth subdirectory, rc, is used to store rc-type files saved by Verdi when saving the signal list;
[0017] The tenth subdirectory, seq, is used to store files related to uvm_sequense;
[0018] The eleventh subdirectory, sva, is used to store documentation related to SystemVerilog assertions.
[0019] The twelfth subdirectory, tc, is used to store documents related to test cases.
[0020] The thirteenth subdirectory, top, is used to store documents related to the top-level testing of the verification environment. The thirteenth subdirectory, top, can also be divided into post or upf subdirectories.
[0021] Based on the first aspect, the unit test directory UT is used for verification of low-level independent modules, the integration test directory IT is used for verification of multi-module integrated subsystems, and the system test directory ST is used for SoC full-chip system scenario verification. The three are progressively hierarchical; the Block_xx supports custom naming.
[0022] Secondly, this application discloses a method for building a verification environment. Using the general file architecture described above, a top-level verification environment directory dv is first created. Then, a subordinate unit test directory UT, integration test directory IT, and system test directory ST are created under this directory. For the unit test directory UT, integration test directory IT, and system test directory ST, several Block_xx verification subdirectories are configured respectively. Based on the classification rules of the subdirectories with fixed configurations within the Block_xx verification subdirectories, the verification resources are classified and archived, and finally the verification environment deployment is completed.
[0023] Thirdly, this application discloses an electronic device, the electronic device comprising:
[0024] A memory that stores a computer program;
[0025] The processor, which is communicatively connected to the memory, executes the steps of the above-described construction method when calling the computer program.
[0026] Fourthly, this application discloses a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described construction method.
[0027] The beneficial effects of this invention are:
[0028] 1) The file structure of this application is universal and can be adapted to verification environments at various levels and stages; it is suitable for building a general verification environment, realizes the formatting of the verification environment, saves the time cost of transferring the verification environment to others, and lays a solid foundation for the subsequent general verification platform. Attached Figure Description
[0029] Figure 1 This is a schematic diagram of the general file architecture of the verification environment in an embodiment of the present invention. Detailed Implementation
[0030] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. 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.
[0031] Here, we will explain the technical terms used in this application:
[0032] EDA stands for Electronic Design Automation. It can be understood as a suite of "computer-aided design software" for chips (integrated circuits) and electronic systems.
[0033] EDA verification environment: This is an automated testing platform built during the chip design process to ensure the functional correctness of the design. EDA auxiliary tools are required in this process.
[0034] SOC: System on Chip (SOC) refers to the integration of a complete electronic system onto a single chip, including modules such as processor (CPU / GPU / DSP), memory (RAM / Flash), peripheral interfaces (USB / Ethernet), and power management, to achieve the goal of "a single chip as a system".
[0035] IP: IP (Intellectual Property) refers to pre-designed, verified, and reusable functional modules (such as CPU cores and USB controllers) that are provided to chip designers in the form of "building blocks" to avoid redundant development.
[0036] UVM: Universal Verification Methodology is a standardized verification methodology based on SystemVerilog, specifically designed for digital circuit verification. It provides a reusable and scalable verification framework to help engineers efficiently build verification environments for complex chips (such as SoCs, ASICs, and FPGAs).
[0037] UVC: A general-purpose verification component developed based on UVM, typically consisting of one agent or one environment.
[0038] Verdi: Verdi refers to an EDA (Electronic Design Automation) tool from Synopsys, primarily used for integrated circuit design verification. This is a technical term. It is mainly used for hardware design debugging, capable of analyzing RTL code, viewing waveforms, tracing signals, etc.
[0039] POST: POST refers to using a netlist with an SDF for dynamic timing simulation.
[0040] PG: PG refers to using a netlist with power control related signals, along with an SDF, for timing simulation.
[0041] UPF: In the field of chip verification, UPF stands for Unified Power Format. It is not the verification method itself, but a standard specification document that describes the low-power design intent of a chip.
[0042] CPF: CPF provides a tool-independent, standardized language for explicitly describing a chip's power management architecture during the RTL (Register Transfer Level) design phase, including power domain partitioning, power switching control, signal isolation rules, and state preservation strategies. CPF is one of the core standards for low-power design flow, competing with another mainstream format, UPF (Unified PowerFormat, IEEE 1801). While both have similar functionalities, their syntax and ecosystems differ.
[0043] For example, this application discloses a general file architecture for a verification environment, as illustrated in the following diagram: Figure 1 As shown, all verification environments are uniformly grouped under the top-level verification environment dv (design verification) directory. The verification environment dv directory is divided according to the verification level into the unit test directory UT (Unit Test, the lowest level independent functional module in the entire chip design), the integration test directory IT (Integration Test, the top level of the chip or a subsystem formed by integrating multiple unit modules that have passed UT), and the system test directory ST (System Test, the behavior of the entire chip SoC in a near-real application scenario). The unit test directory UT, the integration test directory IT, and the system test directory ST adopt the same lower-level subdirectory architecture, each configured with several Block_xx verification subdirectories (used to distinguish each level and each module). Several Block_xx verification subdirectories, such as block_A, block_B... in the figure, are independent and simulable minimum verification units. The unit test directory UT, the integration test directory IT, and the system test directory ST are a bottom-up, local to global verification strategy. The relationship between the three is a progressive and complementary process.
[0044] For example, the Block_xx verification subdirectory is fixedly configured with thirteen subdirectories (which are the storage locations for numerous files in various verification environments), specifically including:
[0045] The first subdirectory, cenv, is used to store the compilation environment files for the C code programs required for CPU verification. Chips with CPUs must be verified, and the CPU must run C code programs.
[0046] The second subdirectory, cfg (config), is used to store configuration files related to electronic design automation (EDA) simulation tools and simulation scripts, as well as simulation file lists (filelist) and regression list files; it can also store other files that are not easy to categorize.
[0047] The third subdirectory, cov (coverage), is used to store coverage-related files, including configuration files used for coverage collection, coverage group files (covergroup is a keyword in SystemVerilog syntax) used for functional coverage, data files for merging coverage (merging coverages together), and files for excluding coverage (excluding coverages that do not need to be collected).
[0048] The fourth subdirectory, define, is used to store macro-related files, including address macros, hierarchy define macros for modules in the design, etc.
[0049] The fifth subdirectory, dft, is used to store files related to Design for Testability (i.e., proactively embedding dedicated test structures during the chip design phase, such as scan chains, built-in self-test BIST, boundary scan, etc.).
[0050] The sixth subdirectory, doc, is used to store non-code documents during the verification process, including Excel spreadsheets, Word documents, or TXT documents.
[0051] The seventh subdirectory, env (environment), is used to store UVM-related files, including interface, component, object, agent, or UVC (short for UVM verification component, representing a complete set of components that can be independently encapsulated and used; interface, component, object, and agent are keywords in SystemVerilog).
[0052] The eighth subdirectory, model, is used to store driver or device behavior model files;
[0053] The ninth subdirectory, rc, stores rc-type files saved by Verdi when saving signal lists. Verdi is an advanced digital circuit debugging and verification platform developed by Synopsys, used for viewing simulation waveforms (such as FSDB / VCD), tracing source code, signal analysis, coverage analysis, and assertion debugging. rc refers to the .rc file in Verdi, usually signal.rc or a custom-named .rc file, which is a waveform debugging configuration file used to save debugging states such as signal lists, groupings, display formats, and waveform view layouts for quick reuse.
[0054] The tenth subdirectory, seq, is used to store files related to uvm_sequense (a keyword in SystemVerilog);
[0055] The eleventh subdirectory, sva, is used to store documents related to SystemVerilog assertions (common statements in SystemVerilog);
[0056] The twelfth subdirectory, tc, is used to store documents related to test cases.
[0057] The thirteenth subdirectory, top, is used to store documents related to the top-level test of the verification environment. The thirteenth subdirectory, top, can also be divided into post or upf subdirectories (top represents the top level of the verification environment; post represents post-simulation; upf (Unified Power Format) refers to the unified power format).
[0058] For example, the unit test directory UT is used for verification of low-level independent modules, the integration test directory IT is used for verification of multi-module integrated subsystems, and the system test directory ST is used for SoC full-chip system scenario verification. The three are progressively hierarchical; the Block_xx supports custom naming.
[0059] For example, this application discloses a method for setting up a verification environment. Using the general file architecture described above, a dv folder is first created. Then, a unit test directory UT, an integration test directory IT, and a system test directory ST are created under this directory. Next, several Block_xx verification subdirectories are configured for each of the unit test directory UT, the integration test directory IT, and the system test directory ST. Based on the classification rules of the fixed subdirectories within the Block_xx verification subdirectories, verification resources are classified and archived, ultimately completing the deployment of the verification environment.
[0060] By way of example, the present invention also provides a computer-readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.
[0061] For example, the aforementioned computer-readable storage media may include, but are not limited to, various media capable of storing computer programs, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0062] By way of example, the present invention also provides an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.
[0063] For example, the above-mentioned electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.
[0064] The above description is merely a preferred embodiment of the present invention. It should be understood that the present invention is not limited to the forms disclosed herein and should not be construed as excluding other embodiments. It can be used in various other combinations, modifications, and environments, and can be altered within the scope of the concept described herein through the above teachings or related technologies or knowledge. Modifications and variations made by those skilled in the art that do not depart from the spirit and scope of the present invention should be within the protection scope of the appended claims.
Claims
1. A universal file architecture for a verification environment, characterized by: All verification environments are uniformly grouped under the top-level verification environment dv directory. The verification environment dv directory is divided into unit test directory UT, integration test directory IT, and system test directory ST according to the verification level. The unit test directory UT, integration test directory IT, and system test directory ST adopt the same subdirectory architecture and are each configured with several Block_xx verification subdirectories. Each Block_xx verification subdirectory is the smallest independent and simulable verification unit.
2. The general file architecture of the verification environment according to claim 1, characterized in that: The Block_xx verification subdirectory is configured with thirteen subdirectories, specifically including: The first subdirectory, cenv, is used to store the compilation environment files for the C code programs required for CPU verification. The second subdirectory cfg is used to store configuration files related to electronic design automation (EDA) simulation tools and simulation scripts, as well as simulation file list and regression list files; The third subdirectory, cov, is used to store coverage-related files, including configuration files used for coverage collection, coverage group files used for functional coverage, data files for merging coverage, and files for excluding coverage. The fourth subdirectory, define, is used to store macro-related files, including address macros and hierarchy define macros for modules in the design. The fifth subdirectory, dft, is used to store files related to design for testability. The sixth subdirectory, doc, is used to store non-code documents during the verification process, including Excel spreadsheets, Word documents, or TXT documents. The seventh subdirectory, env, is used to store UVM-related files, including interface, component, object, agent, or UVC. The eighth subdirectory, model, is used to store driver or device behavior model files; The ninth subdirectory, rc, is used to store rc-type files saved by Verdi when saving the signal list; The tenth subdirectory, seq, is used to store files related to uvm_sequense; The eleventh subdirectory, sva, is used to store documentation related to SystemVerilog assertions. The twelfth subdirectory, tc, is used to store documents related to test cases. The thirteenth subdirectory, top, is used to store documents related to the top-level testing of the verification environment. The thirteenth subdirectory, top, can also be divided into post or upf subdirectories.
3. The general file architecture of the verification environment according to claim 1, characterized in that: The Unit Test Directory (UT) is used for verification of low-level independent modules, the Integration Test Directory (IT) is used for verification of multi-module integrated subsystems, and the System Test Directory (ST) is used for SoC full-chip system scenario verification. The three are progressively hierarchical. The Block_xx directory supports custom naming.
4. A method for setting up a verification environment, using the general file architecture described in any one of claims 1-3, characterized in that: First, create the top-level verification environment directory dv. Then, create subordinate unit test directories UT, integration test directories IT, and system test directories ST under this directory. Next, configure several Block_xx verification subdirectories for each of the unit test directory UT, integration test directory IT, and system test directory ST. Based on the classification rules of the subdirectories with fixed configurations within the Block_xx verification subdirectories, classify and archive the verification resources, and finally complete the deployment of the verification environment.
5. An electronic device, characterized in that, The electronic device includes: A memory that stores a computer program; The processor, which is communicatively connected to the memory, executes the steps of the construction method of claim 4 when calling the computer program.
6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the construction method described in claim 4.
