基于assertion的设计方法指南：从实践到规范

需积分: 12 144 浏览量更新于2024-07-15 收藏 4.03MB PDF 举报

《基于断言的设计（第二版）》是一本专注于系统级验证领域的专业书籍，由Harry Foster、Jasper Design Automation Inc.的Adam Krolnik以及来自LSI Logic Corporation的David Lacey共同编撰，由Kluwer Academic Publishers出版。本书的核心内容围绕Assertion-Based Design展开，主要探讨了在现代集成电路设计中的关键概念和技术。第一章是"Assertion Methodology"，介绍了断言方法论，包括如何在设计过程中有效地运用断言来检测和确保电路的行为符合预期。它强调了在RTL（ Register Transfer Level）设计阶段中，断言的重要性，它们作为验证策略的一部分，帮助设计师捕获和修复潜在的错误。第二章至第六章分别深入剖析了各个方面的断言技术： - Chapter 3 "Specifying RTL Properties"讲解如何精确地定义和表述RTL层次的属性，这些属性可能是信号状态、数据流或性能指标，以支持断言的编写。 - Chapter 4 "PLI-Based Assertions"着重于使用高级硬件描述语言（PLI，Programming Language Interface）来编写和管理断言，使得断言更加灵活和易于维护。 - "Functional Coverage"（Chapter 5）关注的是功能覆盖率，即通过断言来评估测试用例是否充分地覆盖了设计的各个方面，确保设计的完整性和正确性。 - Chapter 6 "Assertion Patterns"列举了一系列常见的断言模式，供读者理解和应用到实际设计中，这些模式涵盖了如边界条件检查、一致性检查等实用场景。 - 最后，"Assertion Cookbook"（Chapter 7）则提供了一个实践性的指南，通过具体的例子和最佳实践，帮助设计师在遇到问题时找到解决方案。第八章"Specifying Correct Behavior"探讨了如何从系统级别上定义和表达正确的行为，这对于建立健壮的断言系统至关重要，确保整个设计链路中的正确性。附录A "OpenVerification Library"展示了作者们所使用的开源验证库，这些工具为实现和管理断言提供了实用的资源和支持。整体而言，《基于断言的设计（第二版）》是一本综合性的参考书，旨在提升工程师们在设计过程中的断言能力，帮助他们更有效地进行验证和调试，确保产品的高质量和可靠性。书中强调了断言在现代电子设计中的核心地位，并提供了丰富的实践指导，适用于从事ASIC、FPGA或SoC设计的工程师们。

FOREWORD

There is much excitement in the design and verification

community about assertion-based design. The question is, who

should study assertion-based design? The emphatic answer is,

both design and verification engineers.

What may be unintuitive to many design engineers is that adding

assertions to RTL code will actually reduce design time, while

better documenting design intent.

Every design engineer should read this book! Design engineers

that add assertions to their design will not only reduce the time

needed to complete a design, they will also reduce the number of

interruptions from verification engineers to answer questions

about design intent and to address verification suite mistakes.

With design assertions in place, the majority of the interruptions

from verification engineers will be related to actual design

problems and the error feedback provided will be more useful to

help identify design flaws. A design engineer who does not add

assertions to the RTL code will spend more time with verification

engineers explaining the design functionality and intended

interface requirements, knowledge that is needed by the

verification engineer to complete the job of testing the design.

Every verification engineer should read this book! The smart

verification engineer will assist the design engineer to add

assertions to the RTL-design code because the sooner a design

engineer understands the usage and benefits of inserting assertions

into the design, the more valuable that design engineer will be to

the verification effort. A smart verification engineer is someone

who can help a designer to catch the vision and understand the

ease and value of assertion-based design. This is the first book to

comprehensively address and explain HDL assertion-based

design.

My colleague Harry Foster is the best-known name in the Verilog

verification and assertion-based methodology community. Along

with Lionel Bening, Harry pioneered the Verilog Open

Verification Library (OVL), a freely available set of verification-

focused Verilog modules that have been used in advanced design

and verification environments ever since they were introduced.

My colleague Adam Krolnik was the verification champion of the

Verilog-2001 Standards Group. I counted on Adam to promote

Foreword

Adam Krolnik—Accellera SystemVerilog Assertion

Committee committee member and major contributor in the

development of the System Verilog assertion constructs;

created assertion-based methodologies at Cyrix and LSI Logic

Corporation.

David Lacey—Chairs the Accellera Open Verification Library

committee; member of the System Verilog Assertion

Committee; created functional coverage and assertion-based

methodologies at Hewlett-Packard Company.

Fundamentals. Property specification is fundamental to an

assertion-based verification platform (that is, assertions,

constraints, and functional coverage). Once specified, properties

enable the following components, which may be included in your

assertion-based verification platform:

verifiable testplans through property specification (for

example, executable functional coverage models, which

help answer the question “what functionality has not been

exercised?”)

exhaustive and semi-exhaustive formal property checking

technology (for example, model checking and

bounded-model checking)

dynamic property checking technology (for example,

monitoring assertions in simulation) for improved

observability to reduce the time involved in debug

hardware verification languages (HVLs) for testbench

generation that leverage property specification to define

expected input (constraints) and output (assertions) behavior

constraint-driven stimulus generation based on interface

properties targeting block-level designs

assertion property synthesis to address silicon observability

challenges during chip bring-up in the lab, as well as

operational error detection required for high availability

(HA) class systems

In this book, we discuss the important role that property

specification plays in an assertion-based verification flow.

Evolution in levels of abstraction. The following figure

shows an evolution in levels of design notation and specification

abstraction. Each time we move up a level of abstraction, we

expand possibilities, increase productivity, and improve

communication of design intent. Perhaps most importantly, is the

growth our field has experienced in conceptualizing new forms of

specification, developing new technologies based on these new

forms of specification, and then developing standards, which in

turn opens new markets. For example, the development of

development of synthesis. However, it was the standardization of

xviii

Assertion - Based Design

剩余414页未读，继续阅读

rocky_123

粉丝: 0
资源: 4

基于assertion的设计方法指南：从实践到规范

assertion based design 2nd edition

systemverilog_assertion.pdf

如何将assertion集成到uvm环境中的例子

./nptl/pthread_mutex_lock.c:81:_pthread_mutex_lock: Assertionmutex->__data.__owner == 0 failed

jemeter结果导出json

如何在sv的test中使用assertion

httpserver: ../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.

error: (-215:Assertion failed) !_img.empty() in function 'imwrite'

final Assertion assertion = (Assertion) session.getAttribute(AbstractCasFilter.CONST_CAS_ASSERTION);

error: (-215:assertion failed) !_image.empty() && _image.type() == cv_8uc1 && (_image.ismat() || _image.isumat()) in function 'cv::houghcircles'

最新资源

./nptl/pthread_mutex_lock.c:81:_pthread_mutex_lock: Assertionmutex->data.owner == 0 failed

httpserver: ../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->data.owner == 0' failed.