Packaging method and device for reusable UVM verification environment, equipment and medium

Abstract

The invention provides a packaging method and device for a reusable UVM verification environment, equipment and a medium, and the method comprises the steps: executing a configured first script file to achieve the automatic packaging of an interface, so as to generate an agent packaging file, wherein the first script file is configured with a data member and a bit width on an interface, and the agent packaging file is a subclass of uv_magent in a UVM class library file and belongs to a verification component type; executing a configured second script file to perform semi-automatic packaging on the agent packaging file so as to generate an env packaging file, wherein the second script file comprises a path where an agent contained in specified instantiation is located, a path where the second script file is located, and the number of required instantiation; and generating a UVM verification environment according to the agent packaging file and the env packaging file. The working efficiency of developers is greatly improved, and the effect of accelerating the project progress is achieved, so that the tape-out time of the chip project is ensured.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular to a packaging method, device, equipment and medium for a reusable UVM verification environment. Background technique [0002] Usually, when verifying RTL, the widely used verification methodology is UVM (Universal Verification Methodology), which is a verification platform developed based on TLM (Transaction-Level Modeling) communication. Simply put, it is a class library file that can help verification developers easily build a configurable and reusable verification environment. This methodology has encapsulated many low-level interfaces into individual objects, and developers only need to use them according to the grammatical rules. [0003] Such as figure 1 as shown, figure 1 Typical architecture for existing UVM verification platforms. In theory, only the UVM agent, scoreboard and basic transaction (sequence), as well as the sequence and sequencelibrary containing...

AI Technical Summary

Problems solved by technology

[0005] (1) Need to manually write each component or object class file, which is time-consuming and laborious

[0006] (2) Although there is already a set of UVM frameworks, there are differences in the code writing habits of everyone in the team, and it is still difficult to locate problems when they occur

[0007] (3) When verifying complex RTL, existing code needs to be reused, but because everyone does not follow a unified reusable structure, there are many problems in the actual reusable process

[0029] It can be seen that there are a lot of class files that need to be manually written, and the codes of the input and output interfaces are mixed together. The code writing method is relatively free, which is not conducive to code reuse in the top-level verification environment.

Images