Options for Generating new Testbenches/Verification Projects

 UVM projects can be generated using various tools and frameworks, with UVMF being a prominent option. 

Here are some methods and alternatives for generating UVM projects:

1. UVMF (UVM Framework):
   UVMF is a powerful toolset that extends UVM capabilities, providing a structured approach to verification
   3
   . It offers:

• A UVM code generator that automates the creation of files, infrastructure, and interconnects for interface packages, environment packages, and project benches
  3
  .
• Pre-built components, utilities, and testbenches to accelerate the verification process
  3
  .
• Support for component-level verification reuse across projects and environment reuse from block through chip to system-level simulation
  3
  .

2. UVM Project Generators:
   Several EDA vendors and open-source communities offer UVM project generators, which create basic UVM testbench structures and components. Some examples are_ uvm_code_gen, Easier Code Generator by Doulos, , uvm_gen, HDL Verifier UVM Generator, uvmdvgen.  These tools typically provide:

• Template-based code generation for UVM components like agents, sequences, and environments.
• Configuration options to customize the generated code based on project requirements.

3. Script-based Generation:
   Some verification teams develop custom scripts (e.g., in Python or Perl) to generate UVM code based on predefined templates and project specifications. This approach offers:

• Flexibility to tailor the generated code to specific team or project needs.
• Automation of repetitive tasks in UVM testbench creation.

4. Integrated Development Environments (IDEs):
   Some EDA tools and IDEs provide built-in features for UVM project generation, offering:

• Wizards or GUI-based interfaces for creating UVM components and testbenches.
• Integration with simulation and debugging tools for a seamless workflow.

5. Open-source UVM Libraries:
   While not generators per se, open-source UVM libraries provide reusable components and utilities that can jumpstart UVM project development. These include:

• Pre-built UVM agents for common protocols.
• Utility classes and macros to simplify UVM code writing.

When choosing a UVM project generation method, a team needs to consider factors such as team expertise, project complexity, and available resources. 

It seems, currently, that UVMF offers a comprehensive solution with its code generator and pre-built components

3

4

, but other options may be more suitable depending on specific project requirements and constraints.

History of specman

http://asic-world.com/specman/history.html

History of specman:

Specman started to improve efficiency, productivity and quality of hardware design verification.

Main issues in focus are:
1. Task-based strategy of traditional verification (using HDL/C)
Traditional verification methods are based on debugging the design in compilor/simulator setup. Moreover, in traditional methods of verification, the test writing effort is high and information at higher levels of abstraction doesnot go into the testing functions and data.

2. Traditional verification cannot cope up with :
a. increasing complexity, gate counts of circuits
b. reducing time-to-market of design-implementation cycles
c. identification and constraining tests towards particular aspects of designs
d. the tremendous increase in importance of verification taking up 70% of overall project cycle.

3. As there is not an efficient way to direct tests towards particular testing areas, there is no way to be confident that all tests in that direction have been done and if not, how many tests failed.

So, Specman Elite came in and addressed these issues, with its multi-faceted, all-encompassing features.

Specman Elite with its Verification language 'e' have features like:
->Object-oriented programming
->Modularity
->Reusability
->Aspect-orientation

The Story of e:
Here is an excerpt from the book:
Design Verification with e
by Samir Palnitkar
Publisher: Prentice Hall

The e language was invented by the founder and CTO of Verisity, Yoav Hollander. It came into being at a time that Yoav was providing verification consulting for leading edge companies in his home country of Israel. While performing this work, he was frustrated by the fact that his efforts to create a verification environment were lost when he moved to a new project. Each environment was custom developed and not reusable. By the early '80s Yoav and his team were creating innovative verification environments using random test generation and repeatable generation of tests for several of their projects. By 1992 an early version of the e language and a prototype of Specman Elite were in experimental use at National Semiconductor and Digital Equipment Corporation. Verisity was formed (initially as InSpec) in late 1995 in order to bring Specman Elite to market. Specman Elite was introduced to the market during the Design Automation Conference of 1996.

Namaste

 Let's start... Restart..