UVM-based subsystem verification environment integration method and system, and computer program
Through the UVM-based subsystem verification environment integration method, the problem of subsystem verification environment integration and management in complex SoC design is solved, which improves verification efficiency and reliability, simplifies the integration process, and allows non-professional engineers to easily integrate submodules. .
Patent Information
- Application Number
- CN202411064921.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-05
- Publication Date
- 2024-11-19
AI Technical Summary
In complex SoC designs, there are difficulties in integrating and managing verification environments of multiple functional subsystems, resulting in inefficiency in verification and making it difficult for non-professional verification engineers to easily integrate submodules.
Using the UVM-based subsystem verification environment integration method, by building the simulation directory structure, creating the files required by the subsystem, instantiating and establishing connection relationships in the simulation directory, writing simulation scripts, integrating the subsystem into the verification environment, and using The rich functionality and ecosystem of UVM simplifies the integration process.
The unified verification environment integration of multiple functional subsystems is realized, which improves verification efficiency and reliability, and allows non-professional engineers to easily integrate submodules, simplifying the integration process of system submodules.
Smart Images

Figure CN118981399A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of chip verification, and in particular to a subsystem verification environment integration method based on UVM. Background Art
[0002] UVM (Universal Verification Methodology) is a universal verification methodology developed based on SystemVeri log language and is widely used in the field of chip design. UVM provides a structured verification environment design method and improves verification efficiency and reliability with its rich verification components and APIs.
[0003] In the final stage of integrated circuit design, it is usually necessary to verify the entire SoC (System on Chip). UVM can help verification engineers build a complex SoC-level verification environment to verify the correctness of the SoC through methods such as random testing and functional coverage analysis.
[0004] In SoC design, subsystem refers to various functional modules or components implemented inside SoC, which work together to realize the overall function of SoC. When designing complex SoC, it is necessary to integrate multiple functional subsystems into a unified verification environment to test the function and performance of the system more comprehensively. Summary of the invention
[0005] The invention provides a subsystem verification environment integration method based on UVM, which can integrate multiple functional subsystems into a unified verification environment, more effectively manage and maintain the verification environment, and improve verification efficiency.
[0006] To achieve the above object, the embodiments of the present invention adopt the following technical solutions:
[0007] A subsystem verification environment integration method based on UVM comprises the following steps:
[0008] Build simulation directory structure;
[0009] Create the files required for the subsystem;
[0010] Create a subsystem directory in the simulation directory structure;
[0011] Add the required files of the subsystem to the subsystem directory, instantiate it and establish the connection relationship;
[0012] Write simulation scripts for subsystem integration into the verification environment based on subsystem catalogs, instances, and connection relationships;
[0013] Start the simulation process by running the simulation script to integrate the subsystem into the verification environment structure.
[0014] According to one aspect of the present invention, the simulation directory structure includes: a directory rtl for storing design codes, and a simulation entry directory sim.
[0015] According to one aspect of the present invention, the simulation entry directory sim includes: a directory comp_result for storing design code compilation results, a directory sim_result for storing simulation results, a directory cmdfile for storing simulation scripts, and a directory tb for storing verification files.
[0016] According to one aspect of the present invention, the directory tb for storing verification files includes: a directory vip for storing VIP and shared content that may be used in the simulation, a directory fl for storing the top-level filelist, a directory src for storing top-level tb related files, and a directory module for storing each subsystem.
[0017] According to one aspect of the present invention, the directory of the subsystem includes: a directory tests for storing test cases belonging to the subsystem, a directory fl for storing filelist for verifying the subsystem, a directory base_test for storing the module_base_test file of the subsystem, a directory env for storing all files related to the subsystem environment, a directory src for storing the testbench file of the subsystem, and a directory other_file for storing other files.
[0018] According to one aspect of the present invention, the files required by the subsystem include: UVM verification component files, test case files, subsystem environment files, subsystem testbench files, macro definition files, and test parameter files.
[0019] According to one aspect of the present invention, the steps of creating a subsystem directory in a simulation directory structure, adding files required by the subsystem to the subsystem directory, and instantiating and establishing a connection relationship include the following steps:
[0020] Create a new subsystem directory a under tb / module / , and create subdirectories under the a directory according to the simulation directory structure requirements;
[0021] Add the file tb_a_wrappe in the tb / module / a / src directory, instantiate the required interface, and write other required code;
[0022] Connect the interface in tb_a_wrappe to dut in the tb / src / tb_top file;
[0023] Add a_base_test file in tb / module / a / base_test. a_base_test inherits from core_base_test and instantiates the verification components required by the subsystem.
[0024] Add a.lst to tb / module / a / fl / and organize the files required for the subsystem verification into it;
[0025] Finally, add a.lst to tb / fl / tb.lst.
[0026] According to one aspect of the present invention, the simulation process includes: compiling, loading test data, and running simulation.
[0027] A subsystem verification environment integration system based on UVM, based on the subsystem verification environment integration method based on UVM as described above, comprising:
[0028] A simulation directory building module is used to build a simulation directory structure;
[0029] Subsystem file creation module, used to create files required by the subsystem;
[0030] A subsystem creation module is used to create a subsystem directory in the simulation directory structure;
[0031] The subsystem building module is used to add the files required by the subsystem to the subsystem directory, instantiate it, and establish a connection relationship;
[0032] The script writing module is used to write simulation scripts for integrating subsystems into the verification environment based on the subsystem catalog, instances, and connection relationships;
[0033] The simulation verification module is used to start the simulation process by running the simulation script and integrate the subsystem into the verification environment structure.
[0034] A computer program, when executed, implements the steps of the UVM-based subsystem verification environment integration method as described above.
[0035] Advantages of the present invention:
[0036] The present technical solution provides a UVM-based subsystem verification environment integration method, which can more effectively manage and maintain the verification environment and improve verification efficiency by integrating multiple functional subsystems into a unified verification environment.
[0037] This method can solve the problem of integration and management of verification environment of each subsystem in a complex system, so that non-professional verification engineers can easily integrate submodules, thereby improving verification efficiency and reliability. This method allows other team members to integrate submodules by simply following the documentation without having to deeply understand the details of the entire verification environment, thereby accelerating the integration process of system submodules.
[0038] This method uses UVM as the basis for building a verification environment, combined with its rich functions and mature ecosystem, to achieve an efficient verification environment integration method. By providing detailed documentation and script automation tools, other team members do not need to deeply understand the details of the entire verification environment, but only need to integrate submodules according to the documentation, thereby simplifying the integration process. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0040] Figure 1 A flow chart of a subsystem verification environment integration method based on UVM according to the present invention;
[0041] Figure 2 The simulation directory structure described in the present invention;
[0042] Figure 3 The Testbench structure of the verification environment structure of the present invention;
[0043] Figure 4 This is a test case structure of the verification environment structure described in the present invention. DETAILED DESCRIPTION
[0044] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0045] Embodiment 1
[0046] like Figure 1 As shown, a subsystem verification environment integration method based on UVM includes the following steps:
[0047] S1: Build simulation directory structure.
[0048] The simulation directory structure is as follows Figure 2 shown.
[0049] The simulation directory structure includes: a directory rtl for storing design codes and a simulation entry directory sim.
[0050] The simulation entry directory sim includes: a directory comp_result for storing the design code compilation results, a directory sim_result for storing the simulation results, a directory cmdfile for storing the scripts used for simulation, and a directory tb for storing the verification files.
[0051] The directory tb storing verification files includes: a directory vip storing VIP and shared content that may be used in the simulation, a directory fl storing top-level filel ist, a directory src storing top-level tb related files, and a directory module storing each subsystem.
[0052] The subsystem directory includes: a directory tests for storing the test cases belonging to the subsystem, a directory fl for storing the filelist of verification-related files of the subsystem, a directory base_test for storing the module_base_test files of the subsystem, a directory env for storing all files related to the subsystem environment, a directory src for storing the testbench files of the subsystem, and a directory other_file for storing other files.
[0053] S2: Create the files required for the subsystem.
[0054] The files required for the subsystem include: UVM verification component files, test case files, subsystem environment files, subsystem testbench files, macro definition files, and test parameter files.
[0055] S3: Create a subsystem directory in the simulation directory structure.
[0056] S4: Add the files required by the subsystem to the subsystem directory, instantiate it, and establish a connection relationship.
[0057] The steps of creating a subsystem directory in the simulation directory structure, adding files required by the subsystem in the subsystem directory, and instantiating and establishing a connection relationship include the following steps:
[0058] Create a new subsystem directory a under tb / module / , and create subdirectories under the a directory according to the simulation directory structure requirements;
[0059] Add the file tb_a_wrappe in the tb / module / a / src directory, instantiate the required interface, and write other required code;
[0060] Connect the interface in tb_a_wrappe to dut in the tb / src / tb_top file;
[0061] Add a_base_test file in tb / module / a / base_test. a_base_test inherits from core_base_test and instantiates the verification components required by the subsystem.
[0062] Add a.lst to tb / module / a / fl / and organize the files required for the subsystem verification into it;
[0063] Finally, add a.lst to tb / fl / tb.lst.
[0064] a.lst is a filel ist file, which is used to list all the files needed for chip design and verification, and help the system know which files to compile and simulate.
[0065] S5: Based on the subsystem catalog, instances and connection relationships, write a simulation script to integrate the subsystem into the verification environment.
[0066] S6: Start the simulation process by running the simulation script to integrate the subsystem into the verification environment structure.
[0067] The simulation process includes: compiling, loading test data, and running simulation.
[0068] The verification environment structure includes the architecture and components of the entire verification system.
[0069] Among them, the Testbench structure is as follows Figure 3 As shown, it consists of TB_top, TB_core_wrapper and TB_module_wrapper. The purpose is to separate the design code from the verification code. TB_top is responsible for instantiating the design and connecting the interfaces. TB_core_wrapper instantiates the interfaces related to the CPU. This module is responsible for simulating the CPU behavior. Except for the environment maintenance personnel, other verification personnel do not need to care about the content of this module. TB_module_wrapper is responsible for instantiating the corresponding subsystem interface and other content related to the verification environment of the subsystem.
[0070] The test case structure is as follows: Figure 4As shown, all subsystems will have their own base_test, namely module_base_test. All relevant verification components are instantiated in their module_base_test, and module_base_test inherits core_base_test. Core_base_test is related to TB_core_wrapper, which implements the simulation of the CPU and performs a series of initialization operations, such as power-on, reset, and configuration operations on the subsystem. In addition to the environment maintenance personnel, other verification personnel do not need to care about this part. They only need to call the methods in this component to implement some CPU functions, such as configuring the subsystem registers.
[0071] The beneficial effect of this embodiment is that the method can more effectively manage and maintain the verification environment and improve verification efficiency by integrating multiple functional subsystems into a unified verification environment.
[0072] Embodiment 2
[0073] A subsystem verification environment integration system based on UVM, based on the subsystem verification environment integration method based on UVM as described above, comprising:
[0074] A simulation directory building module is used to build a simulation directory structure;
[0075] Subsystem file creation module, used to create files required by the subsystem;
[0076] A subsystem creation module is used to create a subsystem directory in the simulation directory structure;
[0077] The subsystem building module is used to add the files required by the subsystem to the subsystem directory, instantiate it, and establish a connection relationship;
[0078] The script writing module is used to write simulation scripts for integrating subsystems into the verification environment based on the subsystem catalog, instances, and connection relationships;
[0079] The simulation verification module is used to start the simulation process by running the simulation script and integrate the subsystem into the verification environment structure.
[0080] Embodiment 3
[0081] A computer program, when executed, implements the steps of the subsystem verification environment integration method based on UVM as described in the first embodiment.
[0082] Embodiment 4
[0083] A readable storage medium stores a computer program as described in Example 5, and when the computer program is executed, the steps of the subsystem verification environment integration method based on UVM as described in Example 1 are implemented.
[0084] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with the art within the technical scope disclosed in the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.
Claims
1. A subsystem verification environment integration method based on UVM, characterized in that: The following steps are involved: Build simulation directory structure; Create the files required for the subsystem; Create a subsystem directory in the simulation directory structure; Add the files required by the subsystem to the subsystem directory, instantiate it and establish a connection relationship; Write simulation scripts for subsystem integration into the verification environment based on subsystem catalogs, instances, and connection relationships; Start the simulation process by running the simulation script to integrate the subsystem into the verification environment structure.
2. The subsystem verification environment integration method based on UVM according to claim 1, characterized in that, The simulation directory structure includes: a directory rtl for storing design codes and a simulation entry directory sim.
3. The subsystem verification environment integration method based on UVM according to claim 2, characterized in that, The simulation entry directory sim includes: a directory comp_result for storing design code compilation results, a directory sim_result for storing simulation results, a directory cmdfile for storing simulation scripts, and a directory tb for storing verification files.
4. The subsystem verification environment integration method based on UVM according to claim 3, characterized in that, The directory tb storing verification files includes: a directory vip storing VIP and shared content that may be used in the simulation, a directory fl storing the top-level filelist, a directory src storing top-level tb related files, and a directory module storing each subsystem.
5. The subsystem verification environment integration method based on UVM according to claim 4, characterized in that, The subsystem directory includes: a directory tests for storing the test cases belonging to the subsystem, a directory fl for storing the filelist of verification-related files of the subsystem, a directory base_test for storing the module_base_test files of the subsystem, a directory env for storing all files related to the subsystem environment, a directory src for storing the testbench files of the subsystem, and a directory other_file for storing other files.
6. The subsystem verification environment integration method based on UVM according to claim 5, characterized in that, The files required for the subsystem include: UVM verification component files, test case files, subsystem environment files, subsystem testbench files, macro definition files, and test parameter files.
7. The subsystem verification environment integration method based on UVM according to claim 6, characterized in that, The steps of creating a subsystem directory in the simulation directory structure, adding files required by the subsystem in the subsystem directory, and instantiating and establishing a connection relationship include the following steps: Create a new subsystem directory a under tb / module / , and create subdirectories under the a directory according to the simulation directory structure requirements; Add the file tb_a_wrappe in the tb / module / a / src directory, instantiate the required interface, and write other required code; Connect the interface in tb_a_wrappe to dut in the tb / src / tb_top file; Add a_base_test file in tb / module / a / base_test. a_base_test inherits from core_base_test and instantiates the verification components required by the subsystem. Add a.lst to tb / module / a / fl / and organize the files required for the subsystem verification into it; Finally, add a.lst to tb / fl / tb.lst.
8. The subsystem verification environment integration method based on UVM according to claim 7, characterized in that, The simulation process includes: compiling, loading test data, and running simulation.
9. A subsystem verification environment integration system based on UVM, characterized in that: The UVM-based subsystem verification environment integration method according to any one of claims 1 to 8 comprises: A simulation directory building module is used to build a simulation directory structure; Subsystem file creation module, used to create files required by the subsystem; A subsystem creation module is used to create a subsystem directory in the simulation directory structure; The subsystem building module is used to add the files required by the subsystem to the subsystem directory, instantiate it, and establish a connection relationship; The script writing module is used to write simulation scripts for integrating subsystems into the verification environment based on the subsystem catalog, instances, and connection relationships; The simulation verification module is used to start the simulation process by running the simulation script and integrate the subsystem into the verification environment structure.
10. A computer program, characterized in that When the computer program is executed, the steps of the UVM-based subsystem verification environment integration method according to any one of claims 1 to 8 are implemented.
