SystemVerilog实战：构建测试平台

需积分: 9 122 浏览量更新于2024-07-26 收藏 2.02MB PDF 举报

"《Writing Testbenches - using SystemVerilog》是Janick Bergeron所著的一本书，由Synopsys, Inc.出版，主要探讨如何使用SystemVerilog编写测试平台。该书的Library of Congress Control Number为2005938214，ISBN号码包括纸质版和电子版。书中详细介绍了SystemVerilog在验证领域的应用，特别强调了测试平台的构建方法和技术。" SystemVerilog是一种高级的硬件描述语言，广泛用于系统级设计和验证。在集成电路设计流程中，测试平台（Testbench）是验证设计功能正确性的重要工具。这本书深入讲解了如何利用SystemVerilog来创建高效、可重用和可扩展的测试平台。 SystemVerilog提供了丰富的语言特性，如类（Classes）、接口（Interfaces）、覆盖（Coverage）、任务（Tasks）和函数（Functions），这些都极大地增强了测试平台的构造能力。在测试平台的编写中，作者可能会介绍如何： 1. **定义抽象类（Abstract Classes）**：用于创建通用的测试平台框架，使得不同模块的验证可以共享相同的行为。 2. **使用接口（Interfaces）**：定义和实现模块间的通信协议，使得测试平台与被测设计（DUT，Design Under Test）的交互更清晰。 3. **创建随机化激励（Randomized Stimuli）**：通过约束随机化技术生成各种可能的输入序列，以提高测试覆盖率。 4. **覆盖分析（Coverage Analysis）**：使用内置的覆盖点来跟踪和评估测试的全面性，确保关键设计路径和条件得到充分测试。 5. **环境构建（Environment Construction）**：构建包含激励源、监控器、仲裁器等组件的复杂验证环境，模拟真实系统的行为。 6. **断言（Assertions）**：利用SystemVerilog的断言语句，检查设计行为是否符合预期，早期发现潜在错误。 7. **事务（Transactions）**：定义和使用事务对象来组织和管理测试数据，提高测试效率和可读性。 8. **并行和并发控制（Concurrency and Synchronization）**：通过进程（Processes）和事件（Events）管理多个活动的并发执行，确保测试顺序的正确性。这本书的内容可能会涵盖以上各个主题，并通过实例讲解如何将这些概念应用到实际的设计验证项目中。对于任何希望深入理解和掌握SystemVerilog测试平台开发的工程师来说，这是一本非常有价值的参考资料。通过学习，读者将能够构建出更强大、更灵活的验证环境，提高验证的效率和质量。

What This Book Is About

Writing Testbenches using SystemVerilog xvii

These unfamiliar semantics become important in understanding

what makes a well-implemented and robust testbench and in pro-

viding the necessary control and monitor features.

I will also present techniques for applying stimulus and monitoring

the response of a design, by abstracting the physical-level transac-

tions into high-level procedures using bus-functional models. The

architecture of testbenches built around these bus-functional mod-

els is important to create a layer of abstraction relevant to the func-

tion being verified and to minimize development and maintenance

effort. I also show some strategies for making testbenches self-

checking.

Creating random testbenches involves more than calling the $ran-

dom system task. I will show how random stimulus generators,

built on top of bus-functional models, can be architected and

designed to be able to produce the desired stimulus patterns. Ran-

dom generators must be easily externally constrained to increase

the likelihood that a set of interesting patterns will be generated.

Transaction-level modeling is another important concept presented

in this book. It is used to parallelize the implementation and verifi-

cation of a design and to perform more efficient simulations. A

transaction-level model must adequately emulate the functionality

of a design while offering orders of magnitudes in simulation per-

formance over the RTL model. Striking the correct level of accu-

racy is key to achieving that performance improvement.

This book has one large omission: assertions and formal verifica-

tion. It is not that they are not important. SystemVerilog includes

constructs and semantics for writing assertions and coverage prop-

erties using temporal expressions. Formal verification is already an

effective methodology for verifying certain classes of designs. It is

simply a matter of drawing a line somewhere. There are already

books on assertions

or formal verification. This book focuses on

the bread-and-butter of verification for the foreseeable future:

dynamic functional verification using testbenches

1. Cohen, Venkataramanan and Kumari, "SystemVerilog Assertion Hand-

book", VhdlCohen Publishing, 2005

Preface

xviii Writing Testbenches using SystemVerilog

WHAT PRIOR KNOWLEDGE YOU SHOULD HAVE

This book focuses on the functional verification of hardware

designs using SystemVerilog. I expect the reader to have at least a

basic knowledge of VHDL, Verilog, OpenVera or e. Ideally, you

should have experience in writing models and be familiar with run-

ning a simulation using any of the available VHDL or Verilog sim-

ulators. There will be no detailed description of language syntax or

grammar. It may be a good idea to have a copy of a language-

focused textbook or the SystemVerilog Language Reference Manual

as a reference along with this book. I do not describe a synthesiz-

able subset, nor limit the implementation of the verification tech-

niques to using that subset. Verification is a complex task: The

power of the SystemVerilog language will be used to its fullest.

I also expect that you have a basic understanding of digital hard-

ware design. This book uses several hypothetical designs from var-

ious application domains (video, datacom, computing, etc.). How

these designs are actually specified, architected and then imple-

mented is beyond the scope of this book. The content focuses on the

specification, architecture, then implementation of the verification

of these same designs.

Once you are satisfied with the content of this book and wish to put

it in practice, I recommend you pick up a copy of the Verification

Methodology Manual for SystemVerilog

(VMM). It is a book I co-

authored and wrote as a series of very specific guidelines on how to

implement testbenches using SystemVerilog. It uses all of the pow-

erful concepts introduced here. It also includes a set of base classes

that implements generic functionality that every testbench needs.

Why re-invent the wheel? I will refer to the first edition of the

VMM at relevant points in this book where further techniques,

guidelines or support can be found.

READING PATHS

You should really read this book from cover to cover. However, if

you are pressed for time, here are a few suggested paths.

1. Janick Bergeron, Eduard Cerny, Alan Hunter and Andrew Nightingale,

"Verification Methodology Manual for SystemVerilog", Springer 2005,

ISBN 0-387-25538-9

Preface

xx Writing Testbenches using SystemVerilog

ilog, being a superset of Verilog, benefits from the same smooth ini-

tial learning curve. However—like VHDL—Verilog and

SystemVerilog provide similar concepts: sequential statements, par-

allel constructs, structural constructs and the illusion of parallelism.

These concepts must be learned. Because of its lax requirements,

Verilog lulls the user into a false sense of security. The user believes

that he or she knows the language because there are no syntax

errors or because the simulation results appear to be correct. Over

time, and as a design grows, race conditions and fragile code struc-

tures become apparent, forcing the user to learn these important

concepts. Languages have the same area under the learning curve.

VHDL’s is steeper but Verilog’s goes on for much longer. Some

sections in this book take the reader farther down the Verilog learn-

ing curve.

SystemVerilog continues in Verilog’s footstep. Does that mean that

VHDL is dead? Technically, all VHDL capabilities are directly

available in SystemVerilog. And with the many capabilities avail-

able in SystemVerilog not available in VHDL, there are no longer

any technical reasons to use VHDL

. However, that decision is

never a purely technical one. There will be VHDL legacy code for

years to come. And companies with large VHDL legacies will con-

tinue to use it, if only in a co-simulation capacity. There is also an

effort by the VHDL IEEE Working Group to add these missing

capabilities to VHDL, known as VHDL-200x. Whether or not you

wish—or can afford—to wait for a me too language is again a busi-

ness decision.

Hardware Verification Languages

Hardware verification languages (HVLs) are languages that were

specifically designed to implement testbenches efficiently and pro-

ductively. Commercial solutions include OpenVera from Synopsys

and e from Cadence. Open-source solutions include the SystemC

Verification Library (SCV) from Cadence and Jeda from Juniper

Networks. There are also a plethora of home-grown solutions based

on Perl, SystemC, C++ or TCL. SystemVerilog includes all of the

1. Before anyone paints me as a Verilog bigot, I wish to inform my readers

that I learned VHDL first and have always had a slight preference

toward VHDL over Verilog.

Code Examples

Writing Testbenches using SystemVerilog xxi

features of a hardware verification language. When using System-

Verilog, it is no longer necessary to use a separate language for ver-

ification.

Making use of the verification features of SystemVerilog involves

more than simply learning a new syntax. Although one can con-

tinue to use a Verilog-like directed methodology with SystemVer-

ilog, using it appropriately requires a shift in the way verification is

approached and testbenches are implemented. The directed verifi-

cation strategy used with Verilog is the schematic capture of verifi-

cation. Using SystemVerilog with a constraint-driven random

verification strategy is the synthesis of verification. When used

properly, it is an incredible productivity boost (see Figure 2-16 on

page 56).

Does SystemVerilog mean that OpenVera, e and the other propri-

etary verification and assertion languages are going to die? The

answer is a definite no. SystemVerilog was created by merging

donated features and technologies from proprietary languages. It

did not invent nor create anything new other than integrating these

features and technologies under a consistent syntax and semantics.

The objectives of SystemVerilog are to lower the adoption and

ownership cost of verification tools and to create a broader market-

place through industry-wide support.

SystemVerilog accomplishes these objectives by being an industry

standard. But the problem with industry standards is that they

remain static while the semiconductor technologies continue to

advance. SystemVerilog will more than meet the needs of 90 per-

cent of the users for years to come. But leading edge users, who

have adopted HVLs years ago and are already pushing their limits,

will not be satisfied by SystemVerilog for very long. Proprietary

tools and languages will continue to evolve with those leading edge

projects. Hopefully, their trail-blazing efforts will be folded back

into a future version of SystemVerilog, where their art can become

science.

CODE EXAMPLES

A common complaint I received about the first edition was the lack

of complete examples. You’ll notice that in this book, like the first

two, code samples are still provided only as excerpts. I fundamen-

剩余431页未读，继续阅读

huoyunjie_zky

粉丝: 0
资源: 2

SystemVerilog实战：构建测试平台

Writing Testbenches using System Verilog

Writing Testbenches using SystemVerilog

Writing-Testbenches-using-SystemVerilog.pdf

Writing testbenches using SystemVerilog pdf

Writing Testbenches using System Verilog _systemverilog_

writing testbench using systemverilog

使用SystemVerilog构建测试平台

使用SystemVerilog编写测试平台

SystemVerilog测试平台编写实战指南

使用SystemVerilog进行验证：基础培训

最新资源