ch1 Overview of Digital Design with Verilog" HDL
1.1 Evolution of Computer Aided Digital Design
Digital circuit design has evolved rapidly over the last 25 years.
With the advent of VLSI (Very Large Scale Integration) technology, designers could
design single chips with more than 100,000 transistors.
(page 7)
1.2 Emergence of HDLs
For a long time, programming languages such as FORTRAN, Pascal, and C were being used to describe computer programs that were sequential in nature.
Even though HDLs were popular for logic verification, designers had to manually translate the HDL-based design into a schematic circuit with interconnections between gates.
Thus, logic synthesis pushed the HDLs into the forefront of digital design.
HDLs also began to be used for system-level design.
(p8)
1.3 Typical Design Flow
A typical design flow for designing VLSI IC circuits is shown in Figure 1-
(p9)
The behavioral description is manually converted to an RTL description in an
HDL.
Friday, September 3, 2010
Thursday, September 2, 2010
std 1801 UPF
(page 4)
Abstract: The power supplied to elements in an electronic design affects the way circuits operate.
This standard provides an HDL-independent way of
annotating a design with power intent
Introduction
The purpose of this standard is to provide portable low power design specifications that can be used with a variety of commercial products throughout an electronic system design, analysis, verification, and implementation flow.
(page 6)
When the electronic design automation (EDA) industry began creating standards for use in specifying, simulating and implementing functional specifications of digital electronic circuits in the 1980s, the primary design constraint was the transistor area necessary to implement the required functionality in the prevailing process technology at that time.
As the process technology for manufacturing electronic circuits continued to advance, power (as a design constraint) continually increased in importance.
With process technologies below 100 nm, static power consumption has become a prominent and, in many cases, dominant design constraint.
The EDA industry responded with multiple vendors developing proprietary low power specification capabilities for different tools in the design and implementation flow.
(page 7)
Automation Conference (DAC) in June 2006, several semiconductor/electronics companies challenged the EDA industry to define an open, portable power specification standard.
(page 17)
1. Overview
1.1 Scope
This standard establishes a format used to define the low power design intent for electronic systems and electronic intellectual property.
1.2 Purpose
1.3 Key characteristics of the Unified Power Format (UPF)
p18
Abstract: The power supplied to elements in an electronic design affects the way circuits operate.
This standard provides an HDL-independent way of
annotating a design with power intent
Introduction
The purpose of this standard is to provide portable low power design specifications that can be used with a variety of commercial products throughout an electronic system design, analysis, verification, and implementation flow.
(page 6)
When the electronic design automation (EDA) industry began creating standards for use in specifying, simulating and implementing functional specifications of digital electronic circuits in the 1980s, the primary design constraint was the transistor area necessary to implement the required functionality in the prevailing process technology at that time.
As the process technology for manufacturing electronic circuits continued to advance, power (as a design constraint) continually increased in importance.
With process technologies below 100 nm, static power consumption has become a prominent and, in many cases, dominant design constraint.
The EDA industry responded with multiple vendors developing proprietary low power specification capabilities for different tools in the design and implementation flow.
(page 7)
Automation Conference (DAC) in June 2006, several semiconductor/electronics companies challenged the EDA industry to define an open, portable power specification standard.
(page 17)
1. Overview
1.1 Scope
This standard establishes a format used to define the low power design intent for electronic systems and electronic intellectual property.
1.2 Purpose
1.3 Key characteristics of the Unified Power Format (UPF)
p18
Tuesday, August 31, 2010
std 1666 system c
Abstract: SystemC® is defined in this standard. SystemC is an ANSI standard C++ class library
for system and hardware design for use by designers and architects who need to address complex
systems that are a hybrid between hardware and software
(page iv )
Introduction
As the electronics industry builds more complex systems involving large numbers of components including software, there is an increasing need for a modeling language that can manage the complexity and size of these systems.
Stakeholders in SystemC include Electronic Design Automation (EDA) companies who implement SystemC class libraries and tools, Integrated Circuit (IC) suppliers who extend those class libraries and use SystemC to model their intellectual property, and end users who use SystemC to model their systems
1.2 Purpose
1.4 Relationship with C++
This standard is closely related to the C++ programming language and adheres to the terminology used in ISO/IEC 14882:2003. This
This standard defines the public interface to the SystemC class library and the constraints on how those classes may be used.
A C++ class library may be extended using the mechanisms provided by the C++ language.
(page 20)
1.5 Guidance for readers
Clause 4, “Elaboration and simulation semantics,” defines the behavior of the SystemC kernel and is central to an understanding of SystemC.
The clauses from Clause 5 onward define the public interface to the SystemC class library.
p22
for system and hardware design for use by designers and architects who need to address complex
systems that are a hybrid between hardware and software
(page iv )
Introduction
As the electronics industry builds more complex systems involving large numbers of components including software, there is an increasing need for a modeling language that can manage the complexity and size of these systems.
Stakeholders in SystemC include Electronic Design Automation (EDA) companies who implement SystemC class libraries and tools, Integrated Circuit (IC) suppliers who extend those class libraries and use SystemC to model their intellectual property, and end users who use SystemC to model their systems
1.2 Purpose
1.4 Relationship with C++
This standard is closely related to the C++ programming language and adheres to the terminology used in ISO/IEC 14882:2003. This
This standard defines the public interface to the SystemC class library and the constraints on how those classes may be used.
A C++ class library may be extended using the mechanisms provided by the C++ language.
(page 20)
1.5 Guidance for readers
Clause 4, “Elaboration and simulation semantics,” defines the behavior of the SystemC kernel and is central to an understanding of SystemC.
The clauses from Clause 5 onward define the public interface to the SystemC class library.
p22
std 1800 system verilog
Abstract: This standard provides a set of extensions to the IEEE 1364™ Verilog® hardware
description language (HDL) to aid in the creation and verification of abstract architectural level
models.
(page iii)
Introduction
The purpose of this standard is to provide the electronic design automation (EDA), semiconductor, and system design communities with a well-defined and official IEEE unified hardware design, specification, and verification standard language. The language is designed to coexist and enhance the hardware description languages (HDLs) presently used by designers while providing the capabilities lacking in those languages.
Introduction
The purpose of this standard is to provide the electronic design automation (EDA), semiconductor, and system design communities with a well-defined and official IEEE unified hardware design, specification, and verification standard language
(Comments: S-verilog is meant to be a complement to verilog)
SystemVerilog is a unified hardware design, specification, and verification language that is based on the Accellera SystemVerilog 3.1a extensions to the Verilog HDL [B1]a, published in 2004.
(page 5)
SystemVerilog enables the use of a unified language for abstract and detailed specification of the design, specification of assertions, coverage, and testbench verification that is based on manual or automatic methodologies
(page 17)
1. Overview
1.1 Scope
This standard specifies extensions for a higher level of abstraction for modeling and verification with the Verilog® hardware description language (HDL).
1.2 Purpose
SystemVerilog is built on top of IEEE Std 1364.
(page 18)
SystemVerilog adds extended and new constructs to Verilog, including the following Extensions to data types for better encapsulation and compactness of code and for tighter specification Extended operators for concise description
Extended procedural statements
Enhanced process control
description language (HDL) to aid in the creation and verification of abstract architectural level
models.
(page iii)
Introduction
The purpose of this standard is to provide the electronic design automation (EDA), semiconductor, and system design communities with a well-defined and official IEEE unified hardware design, specification, and verification standard language. The language is designed to coexist and enhance the hardware description languages (HDLs) presently used by designers while providing the capabilities lacking in those languages.
Introduction
The purpose of this standard is to provide the electronic design automation (EDA), semiconductor, and system design communities with a well-defined and official IEEE unified hardware design, specification, and verification standard language
(Comments: S-verilog is meant to be a complement to verilog)
SystemVerilog is a unified hardware design, specification, and verification language that is based on the Accellera SystemVerilog 3.1a extensions to the Verilog HDL [B1]a, published in 2004.
(page 5)
SystemVerilog enables the use of a unified language for abstract and detailed specification of the design, specification of assertions, coverage, and testbench verification that is based on manual or automatic methodologies
(page 17)
1. Overview
1.1 Scope
This standard specifies extensions for a higher level of abstraction for modeling and verification with the Verilog® hardware description language (HDL).
1.2 Purpose
SystemVerilog is built on top of IEEE Std 1364.
(page 18)
SystemVerilog adds extended and new constructs to Verilog, including the following Extensions to data types for better encapsulation and compactness of code and for tighter specification Extended operators for concise description
Extended procedural statements
Enhanced process control
std1364 verilog std
(page i)
Abstract: The Verilog® Hardware Description Language (HDL) is defined in this standard.
(page 6)
Introduction
The Verilog® Hardware Description Language (Verilog HDL) became an IEEE standard in 1995 as IEEEStd 1364-1995. It was designed to be simple, intuitive, and effective at multiple levels of abstraction in a standard textual format for a variety of design tools, including verification simulation, timing analysis, test analysis, and synthesis. It is because of these rich features that Verilog has been accepted to be the language of choice by an overwhelming number of IC designers.
Verilog contains a rich set of built-in primitives, including logic gates, user-definable primitives, switches, and wired logic.
The mixing of abstract levels is essentially provided by the semantics of two data types: nets and variables.
The Verilog language is extensible via the Programming Language Interface (PLI) and the Verilog Procedural Interface (VPI) routines
The language that influenced Verilog HDL the most was HILO-2, which was developed at Brunel University in England under a contract to produce a test generation system for the British Ministry of Defense
Objective of the IEEE Std 1364-2001 effort
(page 7)
Achievements
Over a period of four years the 1364 Verilog Standards Group (VSG) has produced five drafts of the LRM.
Three new sections have been added. Clause 13, “Configuring the contents of a design,” deals with configuration management and has been added to facilitate both the sharing of Verilog designs between designers and/or design groups and the repeatability of the exact contents of a given simulation session.
Extreme care has been taken to enhance the VPI routines to handle all the enhancements in the Behavioral and other areas of the LRM.
The IEEE Std 1364-2001 Verilog Standards Group organization
(p24)
1. Overview
1.1 Objectives of this standard
1.2 Conventions used in this standard
Abstract: The Verilog® Hardware Description Language (HDL) is defined in this standard.
(page 6)
Introduction
The Verilog® Hardware Description Language (Verilog HDL) became an IEEE standard in 1995 as IEEEStd 1364-1995. It was designed to be simple, intuitive, and effective at multiple levels of abstraction in a standard textual format for a variety of design tools, including verification simulation, timing analysis, test analysis, and synthesis. It is because of these rich features that Verilog has been accepted to be the language of choice by an overwhelming number of IC designers.
Verilog contains a rich set of built-in primitives, including logic gates, user-definable primitives, switches, and wired logic.
The mixing of abstract levels is essentially provided by the semantics of two data types: nets and variables.
The Verilog language is extensible via the Programming Language Interface (PLI) and the Verilog Procedural Interface (VPI) routines
The language that influenced Verilog HDL the most was HILO-2, which was developed at Brunel University in England under a contract to produce a test generation system for the British Ministry of Defense
Objective of the IEEE Std 1364-2001 effort
(page 7)
Achievements
Over a period of four years the 1364 Verilog Standards Group (VSG) has produced five drafts of the LRM.
Three new sections have been added. Clause 13, “Configuring the contents of a design,” deals with configuration management and has been added to facilitate both the sharing of Verilog designs between designers and/or design groups and the repeatability of the exact contents of a given simulation session.
Extreme care has been taken to enhance the VPI routines to handle all the enhancements in the Behavioral and other areas of the LRM.
The IEEE Std 1364-2001 Verilog Standards Group organization
(p24)
1. Overview
1.1 Objectives of this standard
1.2 Conventions used in this standard
Subscribe to:
Comments (Atom)