Scribd Logo
Upload

Welcome to Scribd!

  • 69 views

    Cummings Why Use Classes For UVM Transactions

    Uploaded by

    vishwalatha s
    (1) Classes are preferred over structs for representing transactions in UVM because they allow for randomizable fields, randomization constraints, and important user-defined methods like copy and compare. (2) A key difference is that classes are dynamic types that can be generated on demand, while structs require all types to be declared up front. (3) Classes can easily be extended to create new versions with added fields and methods, while new versions of structs require completely recreating the type.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Cummings Why Use Classes For UVM Transactions

    Uploaded by

    vishwalatha s
    69 views2 pages
    (1) Classes are preferred over structs for representing transactions in UVM because they allow for randomizable fields, randomization constraints, and important user-defined methods like copy and compare. (2) A key difference is that classes are dynamic types that can be generated on demand, while structs require all types to be declared up front. (3) Classes can easily be extended to create new versions with added fields and methods, while new versions of structs require completely recreating the type.

    Original Description:

    why we use classes to represent uvm transactions?

    Original Title

    Cummings Why Use Classes for UVM Transactions

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    (1) Classes are preferred over structs for representing transactions in UVM because they allow for randomizable fields, randomization constraints, and important user-defined methods like copy and compare. (2) A key difference is that classes are dynamic types that can be generated on demand, while structs require all types to be declared up front. (3) Classes can easily be extended to create new versions with added fields and methods, while new versions of structs require completely recreating the type.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    69 views2 pages

    Cummings Why Use Classes For UVM Transactions

    Uploaded by

    vishwalatha s
    (1) Classes are preferred over structs for representing transactions in UVM because they allow for randomizable fields, randomization constraints, and important user-defined methods like copy and compare. (2) A key difference is that classes are dynamic types that can be generated on demand, while structs require all types to be declared up front. (3) Classes can easily be extended to create new versions with added fields and methods, while new versions of structs require completely recreating the type.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    World Class SystemVerilog & UVM Training

    Why Use Classes to Represent UVM Transactions?

    Clifford E. Cummings
    Sunburst Design, Inc.
    [email protected]
    www.sunburst-design.com

    Why Use Classes?

    When I learned SystemVerilog class-based verification techniques, the first unanswered


    questions that I had were, "Why use classes to represent transactions? Why not use structs?"

    I was clearly not the only engineer that had this question, and this is still a Frequently Asked
    Question (FAQ) in my training classes. This Cliff-note will answer that question.

    Cummings 2015 1 Why Use Classes to Represent


    Rev 1.0 UVM Transactions?
    Classes ‐vs‐ Structs
    To understand the reason for using classes to represent transactions, the following side-by-side
    comparison is what I needed to see, and should prove useful to the reader. This information is
    also outlined in my paper, "UVM Transaction - Definitions, Methods and Usage" but since that
    paper is 72 pages long (who writes 72-page papers on ... data?!), the comparison is shown below:

    Classes Structs
     Can have multiple fields.  Can have multiple fields.
     Can have randomizable fields.  CANNOT have automatically
    randomizable fields.
     Can include randomization  CANNOT include randomization
    constraints. constraints.
     Have a built-in randomize() method.  DO NOT HAVE a built-in randomize()
    method.
     Can include important user-defined  CANNOT include user-defined methods.
    methods (such as copy, compare and
    print-my-contents).
     Are a dynamic type that can be  Are a static type that requires all user-
    generated on demand. defined structs to be declared at the
    beginning of the simulation.
     Class types can be extended to easily  New versions of structs require a user to
    create a new version with added fields completely copy the original into a new
    and methods. struct and then add new fields.
     Classes can be put into a UVM  Non-dynamic structs cannot be put into a
    factory for easy runtime substitution. UVM factory.

    Classes are basically dynamic, ultra-flexible structs that can be easily randomized, easily control
    the randomization, and be created whenever they are needed. Classes have the multiple field
    encapsulation capability that exists in structs, plus so much more. That is why classes are the
    preferred structure to represent testbench transactions.

    References
    Clifford E. Cummings, "UVM Transactions - Definitions, Methods and Usage," SNUG-SV 2014
    - www.sunburst-design.com/papers/CummingsSNUG2014SV_UVM_Transactions.pdf

    AUTHOR & CONTACT INFORMATION


    Cliff Cummings , President of Sunburst Design, Inc., is an independent EDA consultant and
    trainer with 32 years of ASIC, FPGA and system design experience and 23 years of
    SystemVerilog, synthesis and methodology training experience.

    Sunburst Design, Inc. offers World Class SystemVerilog & UVM training courses. For more
    information, visit the www.sunburst-design.com web site.
    Email address: [email protected]

    Cummings 2015 2 Why Use Classes to Represent


    Rev 1.0 UVM Transactions?

    You might also like