The System Designer's Guide to VHDL-AMS: Analog, Mixed-Signal, and Mixed-Technology Modeling

pioneer

Preface

VHDL-AMS is a language for describing digital, analog and mixed-signal systems. It is an extension of the digital hardware description language VHDL, which arose out of the United States government’s Very High Speed Integrated Circuits (VHSIC) program. In the course of this program, it became clear that there was a need for a standard language for describing the structure and function of integrated circuits (ICs). Hence the VHSIC Hardware Description Language (VHDL) was developed. It was subsequently developed further under the auspices of the Institute of Electrical and Electronic Engineers (IEEE) and adopted in the form of the IEEE Standard 1076, Standard VHDL Language Reference Manual, in 1987. This first standard version of the language is often referred to as VHDL-87.

Like all IEEE standards, the VHDL standard is subject to review every five years. Comments and suggestions from users of the 1987 standard were analyzed by the IEEE working group responsible for VHDL, and in 1992 a revised version of the standard was proposed. This was eventually adopted in 1993, giving us VHDL-93. A second round of revision of the standard was started in 1998. That process was completed in 2001, giving us the current version of the digital language, VHDL-2001.

In the early 1990s, the need for a hardware description language supporting analog and mixed-signal modeling became apparent, and an IEEE Working Group was established. The Working Group developed a set of design objectives for an extension to VHDL and completed a draft Language Reference Manual in 1997. The draft was refined and subsequently approved in 1999, becoming IEEE Standard 1076.1 Definition of Analog and Mixed Signal Extensions to IEEE Standard VHDL.

VHDL-AMS is designed to fill a number of needs in the design process. First, it allows description of the structure of a system, that is, how it is decomposed into subsystems and how those subsystems are interconnected. Second, it allows the specification of the function of a system using familiar programming language and equation forms. Third, as a result, it allows the design of a system to be simulated before being manufactured, so that designers can quickly compare alternatives and test for correctness without the delay and expense of hardware prototyping. Fourth, it allows the detailed structure of a design to be synthesized from a more abstract specification, allowing designers to concentrate on more strategic design decisions and reducing time to market.

This book presents a structured guide to the modeling facilities offered by the VHDL-AMS language, showing how they can be used for the design of digital, analog, mixed-signal and mixed-technology systems. The book does not purport to teach engineering design, since that topic is large enough by itself to warrant several textbooks covering its various aspects. Instead, the book assumes that the reader has at least a basic grasp of electronics design concepts, such as might be gained from a first course in electronics design in an engineering degree program. Some exposure to computer programming and to analog and radio-frequency system design will also be beneficial. An understanding of multidisciplinary engineering will be useful for those interested in using VHDL-AMS for mechatronics design. Unlike some other books on VHDL-AMS, this book does not assume the reader is already familiar with VHDL for digital system modeling. Instead, it presents the whole of VHDL-AMS as a unified language for digital, analog and mixed-signal modeling. This book is suitable for use in an intermediate or advanced-level course in analog and mixed-signal circuit design or mechatronics design. It will also serve practicing engineers who need to acquire VHDL-AMS fluency as part of their changing job requirements.

One pervasive theme running through the presentation in this book is that modeling a system using a hardware description language is essentially a software design exercise. This implies that good software engineering practice should be applied. Hence the treatment in this book draws directly from experience in software engineering. There are numerous hints and techniques from small-scale and large-scale software engineering presented throughout the book, with the sincere intention that they might be of use to readers.

We are particularly pleased to be able to include this book in the Morgan Kaufmann Series in Systems on Silicon. Modeling for simulation and synthesis is a vital part of a design methodology for large-scale systems. VHDL-AMS allows models to be expressed at a range of levels of abstraction, from device level up to algorithmic and architectural levels. It will play an important role in future design processes for analog, mixed-signal and mixed-technology systems, many of which must function correctly in environments that are neither digital nor electronic.

Structure of the Book

The Designer’s Guide to VHDL-AMS is organized so that it can be read linearly from front to back. This path offers a graduated development, with each chapter building on ideas introduced in the preceding chapters. Each chapter introduces a number of related concepts or language facilities and illustrates each one with examples. Scattered throughout the book are five case studies, which bring together preceding material in the form of extended worked examples.

Chapter 1 introduces the idea of a hardware description language and outlines the reasons for its use and the benefits that ensue. It then proceeds to introduce the basic concepts underlying VHDL-AMS, so that they can serve as a basis for examples in subsequent chapters. The next three chapters cover the aspects of VHDL-AMS that are most like conventional programming languages. These may be used to describe the behavior of a system in algorithmic terms. Chapter 2 explains the basic type system of the language and introduces the scalar data types. Chapter 3 describes the sequential control structures, and Chapter 4 covers composite data structures used to represent collections of data elements.

In Chapter 5, the main facilities of VHDL-AMS used for modeling digital hardware are covered in detail. These include facilities for modeling the basic behavioral elements in a design, the signals that interconnect them and the hierarchical structure of the design. In Chapter 6, the facilities of VHDL-AMS used for modeling analog and mixed-signal hardware are covered. These include facilities for modeling the equations that represent analog behavior, the terminals and quantities that interconnect parts of a design and the facilities for expressing the interaction between the analog and digital portions of a design. Chapter 7 describes the way in which VHDL-AMS models are processed for simulation or other forms of analysis and discusses execution of models and solution of equations. The combination of facilities described in these early chapters is sufficient for many modeling tasks, so Chapter 8 brings them together in the first case study.

The next group of chapters extends this basic set of facilities with language features that make modeling of large systems more tractable. Chapter 9 introduces procedures and functions, which can be used to encapsulate behavioral aspects of a design. Chapter 10 introduces the package as a means of collecting together related parts of a design or of creating modules that can be reused in a number of designs. It also describes a number of packages standardized by the IEEE for use in VHDL-AMS designs. Chapter 11 then covers aliases as a way of managing the large number of names that arise in a large model. Chapter 12 describes generic constants as a means of parameterizing the behavior and structure of a design. Chapter 13 deals with Laplace and discrete transforms for frequency domain modeling and with small-signal noise modeling. The material in this group of chapters is brought together in the next case study in Chapter 14.

The third group of chapters covers advanced modeling features in VHDL-AMS. Chapter 15 deals with the important topic of resolved signals. While this language facility forms the basis of many real-world models, its treatment in this book is left to this late chapter. Experience has shown that the ideas can be difficult to understand without a solid foundation in the more basic language aspects. Chapter 16 deals with the topics of component instantiation and configuration. These features are also important in large real-world models, but they can be difficult to understand. Hence this book introduces structural modeling through the mechanism of direct instantiation in earlier chapters and leaves the more general case of component instantiation and configuration until this later chapter. In Chapter 17, generated regular structures are covered. Chapter 18 brings the material in this group of chapters together in the third case study.

The fourth group of chapters covers language facilities generally used for system-level modeling. Chapter 19 is a detailed treatment of the related topics of guarded signals and blocks. Chapter 20 introduces the notion of access types (or pointers) and uses them to develop linked data structures. This leads to a discussion of abstract data types as a means of managing the complexity associated with linked data structures. Chapter 21 covers the language facilities for input and output using files, including binary files and text files. Chapter 22 describes the attribute mechanism as a means of annotating a design with additional information. Chapter 23 then presents the fourth case study.

The last group of chapters draws the tour of VHDL-AMS to a close by covering the remaining language facilities and addressing system design issues. Chapter 24 is a miscellany of advanced topics not covered in the previous chapters. Chapter 25 discusses the use of VHDL-AMS features for modeling the integrated system of analog and digital subsystems and their interactions. Chapter 26 concludes with the final case study.

The Case Studies

The case studies explore the design of a radio-controlled (RC), electric-powered airplane system. They are intended for educational purposes and include analog, mixed-signal and mixed-technology models. They demonstrate VHDL-AMS language features and embody clear guidelines for system design and analysis.

The system from which all of the case studies are derived is shown in Figure P-1. The overall system works as follows. The ground-based operator gives analog throttle (propeller) and rudder commands using control joysticks as shown in the upper left-hand corner of the diagram. The command signals are digitized, encoded into a serial format and transmitted over an FM radio link. The signals are picked up by receiver electronics on the airplane, decoded and converted to pulse-width modulated signals that are proportional to the original analog control settings. These varying pulse-width signals are converted back to analog signals and sent to the amplifiers and servos controlling the propeller speed and rudder position. The system architecture provides an expandable design to which channels for control surfaces or other functions can easily be added.

FIGURE P-1 System diagram for the RC airplane system.

At first glance this may appear to be a rather simple system. However, under closer inspection, it contains a wide variety of modeling challenges: digital, analog, mixed-signal, mixed-technology, as well as behavioral and structural VHDL-AMS models, represented with multiple levels of hierarchy. Various aspects of the RC airplane system are explored in this book in five case studies. Each case study is designed to illustrate specific uses of VHDL-AMS.

Case Study 1: Mixed-Signal Focus

The first case study focuses on the encoding, transmission and decoding of the analog throttle and rudder command signals as they make their way through the system. Analog-to-digital and digital-to-analog conversions are highlighted to show mixed-signal modeling with VHDL-AMS.

Case Study 2: Mixed-Technology Focus

This case study focuses on the mixed-technology (mixed-domain) capabilities of VHDL-AMS. In particular, the s-domain servo control blocks and the electrical and mechanical system components are discussed.

Case Study 3: Power Systems Focus

This case study shows how power systems can be modeled with VHDL-AMS. A buck converter is modeled with two useful levels of abstraction, and the effects of power fluctuations on the system are simulated.

Case Study 4: Communications System Focus

This case study compares phase-locked loop and discrimination methods for signal recovery in the RF receiver.

Case Study 5: Full System Analysis

This case study looks at the RC airplane as an entire system. It also highlights how different modeling abstraction levels may be used to make large system simulations as efficient as possible. The value of early requirements exploration, frequent subsystem integration and validation, and bottom-up design verification are explored.

Notes to Instructors

Whereas a complete reading of this book provides a complete coverage of the language, there are several shorter paths through the material. Some suggested minimal paths for readers with different requirements are as follows:

• For an introductory course in modeling using VHDL-AMS: Chapters 1 to 7, 9, 10, 12 and 15, plus the case study in Chapter 8. Chapter 11 may be included if time permits.

• For a more advanced course: add Chapters 13, 16 and 17; the case studies in Chapters 14 and 18; and a selection of the remaining chapters as time permits. Chapter 25 will be helpful in formulating a modeling flow around VHDL-AMS.

• For readers who wish to focus primarily on analog modeling: Chapters 1, 2, 6, 7, 13 and 25 are the most relevant.

• For readers proficient in using conventional programming languages: treat Chapters 2 to 4 as review.

• For readers with some previous introductory-level background in VHDL-AMS: treat Chapters 1 to 4 as review.

Each chapter in the book is followed by a set of exercises designed to help the reader develop understanding of the material. Where an exercise relates to a particular topic described in the chapter, the section number is included in square brackets. An approximate difficulty rating is also provided, expressed using the following symbols:

] quiz-style exercise, testing basic understanding

] basic modeling exercise—10 minutes to half an hour effort

] advanced modeling exercise—one half to two hours effort

] modeling project—half a day or more effort

Answers for the first category of exercises are provided in Appendix F. The remaining categories involve developing VHDL-AMS models. Readers are encouraged to test correctness of their models by running them on a VHDL-AMS simulator. This is a much more effective learning exercise than comparing paper models with paper solutions.

CD-ROM

This book includes a CD-ROM containing source code of all of the case study and example models in the book, supplemental resources related to the text and examples and a library of models that are useful building blocks for building larger systems or for learning the power of VHDL-AMS by example. The case studies and model library have been coordinated to work with the SystemVision simulation and modeling environment offered as a commercial product by Mentor Graphics Corporation. The SystemVision environment includes a schematic entry tool, a VHDL-AMS simulator and a waveform viewing facility. Full hierarchical SystemVision schematics are available for the case studies in this book. To learn more, you can visit the Web site mentor.com/SystemVision. A downloadable version of the environment, for educational purposes, is available from this Web site. The limited-capacity educational-version tools allow you to experiment with the example models and to verify designs suggested in the exercises. They can also be used with selected portions of the case studies.

Resources for Help and Information

While this book attempts to be comprehensive in its coverage of VHDL-AMS, there will no doubt be questions that it does not answer. For these, the reader will need to seek other resources. A valuable source of experience and advice, often overlooked, is one’s colleagues, either at the workplace or in user groups. User groups generally hold regular meetings that either formally or informally include a time for questions and answers. Many also run e-mail lists and on-line discussion groups for problem solving.

Accellera, an EDA industry association, sponsors the EDA Industry Working Groups Web server (www.eda.org). The server has links to Web pages and repositories of several VHDL standards groups and user groups. Another Web site of interest is www.vhdl-ams.com, hosted by Avant! Systems. It provides tutorial material and example models provided by VHDL-AMS tool vendors.

Readers who have access to the Usenet electronic news network will find the news group comp.lang.vhdl a valuable resource. This discussion group is a source of announcements, sample models, questions and answers and useful software. Participants include VHDL and VHDL-AMS users and people actively involved in the language standard working group and in VHDL and VHDL-AMS tool development. The frequently asked questions (FAQ) file for this group is a mine of useful pointers to books, products and other information. It is archived at www.eda.org.

One resource that must be mentioned is IEEE Standard 1076.1, Definition of Analog and Mixed Signal Extensions to IEEE Standard VHDL. It extends the standard for digital VHDL, IEEE Standard 1076, IEEE Standard VHDL Language Reference Manual. Together, the two standards are the authoritative sources of information about VHDL and VHDL-AMS. However, since they are definitional documents, not a tutorial, they are written in a complex legalistic style. This makes them very difficult to use to answer the usual questions that arise when writing VHDL-AMS models. They should only be used once you are somewhat familiar with VHDL-AMS. They can be ordered from the IEEE at standards.ieee.org.

This book contains numerous examples of VHDL-AMS models that may also serve as a resource for resolving questions. The VHDL-AMS source code for these examples and the case studies, as well as other related information, is available for on-line access at

www.mkp.com/vhdl-ams

Although we have been careful to avoid errors in the example code, there are no doubt some that we have missed. We would be pleased to hear about them, so that we can correct them in the on-line code and in future printings of this book. Errata and general comments can be e-mailed to us at

vhdl-book@ashenden.com.au

Acknowledgments

The development of this book has been very much a team effort, and the authors are extremely grateful to all who have contributed. Most important, we would like to acknowledge the generous support of Mentor Graphics Corporation, for contributing staff time and other resources to the development of the case studies. After we decided on the RC airplane as the system to be designed, Mike Donnelly developed the system specification and detailed architecture. He created the original back of the napkin sketch and worked out how to partition the system into the individual case studies. From this starting point, Scott Cooper and Tom Egel worked through the detailed design and drafted the case study chapters. Scott also took on the Herculean effort of testing the code examples, not only in the case study chapters, but in other chapters also. In addition, Rehan Shaukat from Portland State University assisted with preparation of the CD-ROM during his internship at Mentor. Without the efforts of these people and the support provided by Mentor, the case studies, which are central to the book, would not have been possible.

We are also grateful to Ken Bakalar, one of the developers of VHDL-AMS, for helping us to resolve questions of interpretation of the language definition and to formulate modeling guidelines. Gary Pratt also helped us with modeling guidelines and suggestions for examples to illustrate them. Thanks are due to Alan Mantooth of the University of Arkansas, who used a draft of this book in his course.

This book has also benefited greatly from the input of the reviewers: Gary Pratt and Maged Fikry of Mentor Graphics, Steve Drager of Air Force Research Labs, Peter Wilson of the University of Southampton, Peter Frey of Cadence, Paul Menchini, Jim Barby of the University of Waterloo and David Barton of AverStar. Also, Hal Carter of the University of Cincinnati helped to shape the structure of the book. Any remaining errors or omissions are our fault.

Finally, and by no means least, we would like to thank the staff at Morgan Kaufmann Publishers, led by Senior Editor Denise Penrose, for their support for this project. Denise has kept us focused, and her commitment to quality has been an inspiration to us.

chapter one

Fundamental Concepts

In this introductory chapter, we describe what we mean by digital, analog and mixed-signal system modeling and see why modeling and simulation are an important part of the design process. We see how the hardware description language VHDL-AMS can be used to model digital, analog and mixed-signal systems and introduce some of the basic concepts underlying the language. We complete this chapter with a description of the basic lexical and syntactic elements of the language, to form a basis for the detailed descriptions of language features that follow in later chapters.

1.1 Modeling Systems

If we are to discuss the topic of modeling digital, analog and mixed-signal systems, we first need to agree on what we mean by each of these terms. Different engineers would come up with different definitions, depending on their background and the field in which they were working. The primary difference between digital and analog systems is their representation of values and behavior with respect to time.

First, we focus on what we mean by a digital system. Some designers may consider a single VLSI circuit to be a self-contained digital system. Others might take a larger view and think of a complete computer, packaged in a cabinet with peripheral controllers and other interfaces, as a system. In both of these cases, it is not the size or complexity of the system that makes it digital; rather, it is how data values are represented. For the purposes of this book, we consider any digital circuit that processes or stores information quantized over time into discrete values to be a digital system. We thus consider both the system as a whole and the various parts from which it is constructed.

With this definition of digital systems in mind, we now turn to analog systems. In contrast to digital systems, information in analog systems has values that vary continuously with time. We often use continuous ordinary differential and algebraic equations to describe the varying values within analog systems. Like a digital system, we can consider an analog system as a whole or as an assembly of constituent components. An analog system may be a single device, such as a resistor or capacitor, or it may be a complete system including components such as mixers, oscillators, filters and amplifiers.

Given these definitions of digital and analog systems, we now consider how these systems interact. We call combined analog and digital systems mixed-signal systems. In such systems, the analog and digital portions interact via analog-to-digital and digital-to-analog converters. An example of a mixed-signal system is a chemical-process control system with analog sensors, filters and actuators combined with digital computers to determine flow rates for different fluids. The interactions between the digital and analog portions of the system are accomplished by analog-to-digital converters that sample sensor values for processing by the computer and by digital-to-analog converters that enable the computers to control actuators and thus fluid flow.

In addition to electronic systems, we can also consider mechanical, optical, fluidic, thermal and electromagnetic systems, since they also represent information in continuously varying form. Note that we may view a particular system from more than one of these perspectives. For example, a microelectromechanical accelerometer used to control deployment of an automobile’s airbag may include digital and analog electrical, mechanical and thermal functionality. Similarly, the thermal effects on the operation of a transistor involve multiple domains in a single component. Thus our discussion covers a range of systems modeled in different energy domains and spanning levels of abstraction from the low-level devices that make up the components to the top-level functional units.

If we are to encompass this range of views of digital, analog and mixed-signal systems, we must recognize the complexity with which we are dealing. It is not humanly possible to comprehend such complex systems in their entirety. We need to find methods of dealing with the complexity, so that we can, with some degree of confidence, design components and systems that meet their requirements.

The most important way of meeting this challenge is to adopt a systematic methodology of design. If we start with a requirements document for the system, we can design an abstract structure that meets the requirements. We can then decompose this structure into a collection of components that interact to perform the same function. Each of these components can in turn be decomposed until we get to a level where we have some ready-made, primitive components that perform a required function. The result of this process is a hierarchically composed system, built from the primitive elements.

The advantage of this methodology is that each subsystem can be designed independently of others. When we use a subsystem, we can think of it as an abstraction rather than having to consider its detailed composition. So at any particular stage in the design process, we only need to pay attention to the small amount of information relevant to the current focus of design. We are saved from being overwhelmed by masses of detail.

We use the term model to mean our understanding of a system. The model represents that information which is relevant and abstracts away from irrelevant detail. The implication of this is that there may be several models of the same system, since different information is relevant in different contexts. One kind of model might concentrate on representing the function of the system, another kind might represent the way in which the system is composed of subsystems, and further kinds might focus on different energy domains. We will come back to this idea in more detail in the next section.

There are a number of important motivations for formalizing this idea of a model. First, when a system is needed, the requirements of the system must be specified. The job of the engineers is to design a system that meets these requirements. To do that, they must be given an understanding of the requirements, hopefully in a way that leaves them free to explore alternative implementations and to choose the best according to some criteria. One of the problems that often arises is that requirements are incompletely and ambiguously spelled out, and the customer and the design engineers disagree on what is meant by the requirements document. This problem can be avoided by using a formal model to communicate requirements.

A second reason for using formal models is to communicate understanding of the function of a system to a user. The designer cannot always predict every possible way in which a system may be used, and so is not able to enumerate all possible behaviors. If the designer provides a model, the user can check it against any given set of inputs and determine how the system behaves in that context. The ability to model interactions between multiple energy domains provides a particularly powerful tool for expressing system functionality in emerging technology areas, such as mixed-signal systems on a chip or mixed-technology nanotechnology devices. Thus a formal model is an invaluable tool for documenting a system.

A third motivation for modeling is to allow testing and verification of a design using simulation. If we start with a requirements model that defines the behavior of a system, we can simulate the behavior using test inputs and note the resultant outputs of the system. According to our design methodology, we can then design a circuit from subsystems, each with its own model of behavior. We can simulate this composite system with the same test inputs and compare the outputs with those of the previous simulation. If they are the same (within some tolerances), we know that the composite system meets the requirements for the cases tested. Otherwise we know that some revision of the design is needed. We can continue this process until we reach the bottom level in our design hierarchy, where the components are real devices whose behavior we know. Subsequently, when the design is manufactured, the test inputs and outputs from simulation can be used to verify that the physical circuit functions correctly. This approach to testing and verification of course assumes that the test inputs cover all of the circumstances in which the final circuit will be used. The issue of test coverage is a complex problem in itself and is an active area of research.

When we are modeling for testing or verification, it is instructive to remember that digital designs are abstractions or approximations of analog circuits. In reality, the high and low voltage levels used to encode digital binary signal values are analog and vary continuously. By using rigorous design methodologies, such as that embodied in synchronous digital design, we can normally ensure that the digital abstraction is consistent with the behavior of the fabricated circuit. However, as feature sizes shrink or the operating frequency increases, the digital model of a circuit may no longer be accurate. In such cases, we can resort to more detailed analog models to achieve the necessary modeling fidelity to test our design.

A fourth motivation for modeling is to allow formal verification of the correctness of a design. Formal verification requires a mathematical statement of the required function of a system. This statement may be expressed in the notation of a formal logic system, such as temporal logic. Formal verification also requires a mathematical definition of the meaning of the modeling language or notation used to describe a design. The process of verification involves application of the rules of inference of the logic system to prove that the design implies the required function. While formal verification is not yet in everyday use, it is an active area of research. There have already been significant demonstrations of formal verification techniques in real design projects, and the promise for the future is bright. In recent years, a number of commercial formal verification tools have become available for digital models. The most common type of tool provides equivalency checking between two digital models. This allows designers to ensure that detailed implementations have equivalent functionality as a more abstract model serves as a specification. The application of formal verification to analog designs is not as mature, but it is an active area of research. There have already been significant demonstrations of formal verification techniques in real analog design projects, particularly in the area of symbolic analysis.

One final, but equally important, motivation for modeling is to allow automatic synthesis of circuits. If we can formally specify the function required of a system, it is in theory possible to translate that specification into a circuit that performs the function. The advantage of this approach is that the human cost of design is reduced, and engineers are free to explore alternatives rather than being bogged down in design detail. Also, there is less scope for errors being introduced into a design and not being detected. If we automate the translation from specification to implementation, we can be more confident that the resulting circuit is correct.

The application of synthesis to digital design is now commonplace, with typical development projects using a synthesis-based design flow. The analog synthesis technology is not as mature, although there has been explosive growth in recent years. A number of research tools exist that successfully synthesize analog circuits, and there are several forthcoming commercial tools for analog synthesis. Mixed-signal synthesis is also an emerging technology based on work leveraging the more mature digital synthesis algorithms. As analog synthesis capabilities improve, mixed-signal synthesis capabilities will leverage these improvements as well. For mixed-technology systems, synthesis research promises the ability to automate the implementation of microelectromechanical or nanotechnology machines.

The unifying factor behind all of these arguments is that we want to achieve maximum reliability in the design process for minimum cost and design time. We need to ensure that requirements are clearly specified and understood, that subsystems are used correctly and that designs meet the requirements. A major contributor to excessive cost is having to revise a design after manufacture to correct errors. By avoiding errors, and by providing better tools for the design process, costs and delays can be contained.

1.2 Domains and Levels of Modeling

In the previous section, we mentioned that there may be different models of a system, each focusing on different aspects. We can classify these models into three domains: function, structure and geometry. The functional domain is concerned with the operations performed by the system. In a sense, this is the most abstract domain of description, since it does not indicate how the function is implemented. The structural domain deals with how the system is composed of interconnected subsystems. The geometric domain deals with how the system is laid out in physical space.

Each of these domains can also be divided into levels of abstraction. At the top level, we consider an overview of function, structure or geometry, and at lower levels we introduce successively finer detail. Figure 1-1 (devised by Gajski and Kuhn, see reference 18) represents the domains on three independent axes and represents the levels of abstraction by the concentric circles crossing each of the axes. Figure 1-2, inspired by this work, shows a similar Y-chart representing domains for analog systems.

FIGURE 1-1 Domains and levels of abstraction. The radial axes show the three different domains of modeling. The concentric rings show the levels of abstraction, with the more abstract levels on the outside and more detailed levels toward the center.

FIGURE 1-2 Analog domains and levels of abstraction.

Let us look at these classifications in more detail, showing how at each level we can create models in each domain. We start with a digital example, a single-chip microcontroller system used as the controller for some measurement instrument, with data input connections and some form of display outputs. We then consider as an analog example circuitry used to condition the inputs from a sensor. Finally, we consider a mixed-signal example combining these digital and analog systems and including mixed-signal converter circuitry.

Digital Modeling Example

At the most abstract level, the function of a digital system may be described in terms of an algorithm, much like an algorithm for a computer program. This level of functional modeling is often called behavioral modeling, a term we shall adopt when presenting abstract descriptions of a system’s function. A possible algorithm for our instrument controller is shown in Figure 1-3. This model describes how the controller repeatedly scans each data input and writes a scaled display of the input value.

FIGURE 1-3 An algorithm for a measurement instrument controller.

At this top level of abstraction, the structure of a system may be described as an interconnection of such components as processors, memories and input/output devices. This level is sometimes called the Processor Memory Switch (PMS) level, named after the notation used by Bell and Newell (see reference 4). Figure 1-4 shows a structural model of the instrument controller drawn using this notation. It consists of a processor connected via a switch to a memory component and to controllers for the data inputs and display outputs.

FIGURE 1-4 A PMS model of the controller structure. It is constructed from a processor (P), a memory (M), an interconnection switch (S) and two input/output controllers (Kio).

In the geometric domain at this top level of abstraction, a system to be implemented as a VLSI circuit may be modeled using a floor plan. This shows how the components described in the structural model are arranged on the silicon die. Figure 1-5 shows a possible floor plan for the instrument controller chip. There are analogous geometric descriptions for digital systems integrated in other media. For example, a personal computer system might be modeled at the top level in the geometric domain by an assembly diagram showing the positions of the motherboard and plug-in expansion boards in the desktop cabinet.

FIGURE 1-5 A floor plan model of the controller geometry.

The next level of abstraction in modeling, depicted by the second ring in Figure 1-1, describes the system in terms of units of data storage and transformation. In the digital structural domain, this is often called the register-transfer level, composed of a data path and a control section. The data path contains data storage registers, and data is transferred between them through transformation units. The control section sequences operation of the data path components. For example, a register-transfer-level structural model of the processor in our controller is shown in Figure 1-6.

FIGURE 1-6 A register-transfer-level structural model of the controller processor. It consists of a general-purpose register (GPR) file; registers for the program counter (PC), memory address (MAR), memory data (MDR), temporary values (Temp) and fetched instructions (IR); an arithmetic unit; bus drivers and the control section.

In the functional domain, a register-transfer language (RTL) is often used to specify the operation of a system at this level. Storage of data is represented using register variables, and transformations are represented by arithmetic and logical operators. For example, an RTL model for the processor in our example controller might include the following description:

This section of the model describes the operations involved in fetching an instruction from memory. The contents of the PC register are transferred to the memory address register, and the memory_read signal is asserted. Then the value from the PC register is transformed (incremented in this case) and transferred back to the PC register. When the ready input from the memory is asserted, the value on the memory data input is transferred to the instruction register. Finally, the memory_read signal is negated.

In the geometric domain, the kind of model used depends on the physical medium. In our example, standard library cells might be used to implement the registers and data transformation units, and these must be placed in the areas allocated in the chip floor plan.

The third level of abstraction shown in Figure 1-1 is the conventional logic level. At this level, structure is modeled using interconnections of gates, and function is modeled by Boolean equations or truth tables. In the physical medium of a custom integrated circuit, geometry may be modeled using a virtual grid, or sticks, notation.

At the most detailed level of abstraction, we can model structure using individual transistors, function using the differential equations that relate voltage and current in the circuit, and geometry using polygons for each mask layer of an integrated circuit. Most digital designers do not need to work at this detailed level, as design tools are available to automate translation from a higher level. However, should the need arise to model detailed effects at this level, we can use analog and mixed-signal modeling techniques.

Analog Modeling Example

We illustrate analog modeling by considering a sensor system that includes filtering and amplifier circuitry to condition the input signal. As with the digital system discussed above, the function of an analog system may be described in terms of an algorithm or a set of characteristic equations. This level of functional modeling of analog systems is also known as behavioral modeling.

VHDL-AMS supports modeling continuous time systems described with sets of simultaneous equations. These equations are differential and algebraic equations with sets of unknowns that are continuous, analytic functions of time. We can model the function of analog systems at different levels of abstraction in ways similar to those just discussed for digital systems. First we can form system-level models using transfer functions as with digital design. We can then decompose the system into subsystems and employ a set of macro-models for each. Finally, we can further decompose the macro-models into device-level models. The complexity of the models grows as more detailed models are developed and representations of the structural, functional and geometrical views are refined.

Structural aspects of a system are refined from abstract views that may consist of a set of connected functional blocks or system transfer functions, to a collection of macro-models and nets, then to ideal sources, devices and interconnects, and finally to primitive devices including wires and channels. Similarly, the functional aspects of a system are refined from abstract models using simple equations, to equations representing ideal components, then to more complex modeling equations that include device second-order effects. The physical aspects of a system may span from circuit boards or multichip modules, to floor-planned cells, then to device layout, and finally to polygons as we saw with digital designs.

At the highest level of abstraction, the function of an analog system may be described using transfer functions or some other mathematical description. Typically we express the function not with a single, complex transfer function, but rather by using a collection of steps or stages, with a transfer function associated with each. The corresponding structure of the system can be represented using an interconnection of such n-port devices or of functional blocks. A structural block diagram illustrating analog conditioning circuitry to filter and amplify sensor inputs is shown in Figure 1-7. In the case of a simple one-pole low-pass filter, a transfer function describing its function is shown in Figure 1-8.

FIGURE 1-7 A block diagram for analog conditioning circuitry.

FIGURE 1-8 The transfer function for a low-pass filter.

Because the system will be implemented as a VLSI circuit or multichip module (MCM), the abstract geometric domain for this analog system may be represented using a floor plan like that used for a digital system. The arrangement of the functional blocks on one or more dice, MCMs or boards is illustrated in this manner.

The next levels of abstraction in modeling analog systems are macro-modeling and device-level modeling. The transfer-function description gives a functional model for the circuit, then models at lower levels of abstraction flesh out the details of the implementation. For example, a device-level model of the circuit for the simple one-pole low-pass filter is shown in Figure 1-9.

FIGURE 1-9 A circuit for a simple low-pass filter.

The low-pass filter circuit can be structurally modeled using the resistor and capacitor devices as shown. As with digital modeling, we can consider the function, structure and geometry for an analog system at different levels of abstraction.

Mixed-Signal Modeling Example

Having considered both digital and analog systems, we now turn to modeling mixed-signal systems. Mixed-signal models include both analog and digital components, and often focus on the interface between analog and digital systems. For example, a sensor system could include an analog front end that conditions the signal as discussed above, analog-to-digital conversion circuitry and digital processing of the resulting data. Figure 1-10 illustrates such a mixed-signal sensor system with analog and digital subsystems as well as an analog-to-digital converter subsystem that is a mixed-signal system itself. The block diagram presents an abstract functional view of the system with some structure implied by the blocks and their interconnection.

FIGURE 1-10 A block diagram for a mixed-signal sensor system.

As with the digital processor and analog conditioning circuitry examples above, the function, structure and geometry can be expressed in models. They may be refined from initial abstract representations to more detailed representations as implementation decisions are made during the design process. A simple behavioral model of an analog-to-digital converter is shown in Figure 1-11. We will revisit this analog-to-digital converter block in Section 1.4.

FIGURE 1-11 A behavioral model of an analog-to-digital converter.

Energy Domains and Conservation

In Figures 1-1 and 1-2, we used Y-charts to illustrate the structural, functional and geometric domains for digital and analog electrical systems. We have also mentioned the need to model composite or coupled-energy systems from multiple energy domains, such as electromechanical, electro-optical and electro-fluidic systems. We use ordinary differential and algebraic equations as the modeling framework for these analog systems. We can classify sets of ordinary differential and algebraic equations as conservative or non-conservative. Conservative sets of equations represent systems in which energy is conserved, whereas non-conservative sets represent systems where energy is not conserved. Examples of conservative systems include the analog conditioning circuitry and the analog-to-digital converter circuitry described above that use Kirchoff’s current and voltage laws to describe the system functionality. Conservative electrical systems are typical of lumped systems with no electrical field effects. Conservative mechanical systems arise from systems in dynamic equilibrium. Non-conservative sets of equations can be used to model systems at abstract levels, to model systems in which the physical phenomena governing behavior are not precisely understood or to improve modeling productivity or simulation speed when approximations do not significantly degrade model fidelity. In the case of conservative systems, energy conservation laws result in additional implicit equations that can be used by an analog solver to represent the system behavior. In contrast, there are no implicit equations for non-conservative systems.

A common application for non-conservative sets of equations is abstract signal-flow models of system behavior. For example, we can describe the transfer functions of blocks in a control system using non-conservative equations without addressing the implementation details of each block. Subsequently, as we progress through the design process, we implement each of the blocks as a digital processing element or as a circuit described by a conservative set of equations.

Another example is a non-conservative set of equations representing Newton’s law of cooling. We use this law to model the time rate of heat dissipated from a body into a medium in which the body is immersed. The time rate of temperature change for the body can be represented using a simple ordinary differential equation as follows:

where A is the constant temperature of the medium, T(t) is the temperature of the body over time and k is a positive constant coefficient for thermal conductivity.

1.3 Modeling Languages

In the previous section, we saw that different kinds of models can be devised to represent the various levels of function, structure and physical arrangement of a system. There are also different ways of expressing these models, depending on the use made of the model.

As an example, consider the ways in which a structural model may be expressed. One common form is a circuit schematic. Graphical symbols are used to represent subsystems or sub-circuits, and instances of these are connected using lines that represent wires. This graphical form is generally the one preferred by designers. However, the same structural information can be represented textually in the form of a net list. For example, analog circuit designs created using a schematic capture tool are often extracted into an equivalent SPICE netlist.

When wemove into the functional domain, we usually see textual notations used for modeling. Some of these are intended for use as specification languages, to meet the need for describing the operation of a system without indicating how it might be implemented. For digital systems, these notations are usually based on formal mathematical methods, such as temporal logic or abstract state machines. For analog and mixed-signal systems, the notations may use equations or transfer functions. Other notations are intended for simulating the system for test and verification purposes and are typically based on conventional programming languages. Yet other notations are oriented toward hardware synthesis and usually have a more restricted set of modeling facilities, since some programming language constructs are difficult to translate into hardware.

The purpose of this book is to describe the modeling language VHDL-AMS. VHDL-AMS includes facilities for describing structure and function at a number of levels, from the most abstract down to the device level. It also provides an attribute mechanism that can be used to annotate a model with information in the geometric domain, a feature that can prove very useful for detailed device modeling. VHDL-AMS is intended, among other things, as a modeling language for specification and simulation. We can also use it for hardware synthesis if we restrict ourselves to a subset that can be automatically translated into hardware.

VHDL-AMS was developed to allow designers to represent both analog and digital functionality of a system in the same model. Existing hardware description languages, such as VHDL and Verilog, support digital systems modeling, while languages such as SPICE and its numerous variants support analog systems modeling. Integrating these two modeling domains is a significant new capability for designers.

As System-on-a-Chip (SoC) design becomes more prevalent, designers seek to integrate ever more functionality onto the same die. Analog and digital subsystems are being implemented together more often, requiring the mixed-signal modeling capabilities of VHDL-AMS to adequately describe such systems. As clock frequencies increase and feature sizes continue to shrink, the assumptions underlying digital design no longer hold, and analog models for digital components must be employed instead. In addition, the high-speed interconnects between the processor, memory and switches in a digital system such as the one described above may require more accurate analog transmission line models to adequately represent their function. VHDL-AMS can be used to express these analog models in SoC designs.

VHDL-AMS is an extension of VHDL, a modeling language for digital systems. Digital design with VHDL is mature and widespread in industry, which is why VHDL was used as the base language for the development of VHDL-AMS. Readers specifically interested in VHDL or the digital modeling portions of VHDL-AMS are encouraged to read The Designer’s Guide to VHDL 1.

1.4 VHDL-AMS Modeling Concepts

In Section 1.2, we looked at the three domains of modeling: function, structure and geometry. In this section, we look at the basic modeling concepts in each of these domains and introduce the corresponding VHDL-AMS elements for describing them. This will provide a feel for VHDL-AMS and a basis from which to work in later chapters. As an example, we look at ways of describing a 1-bit sampling analog-to-digital converter (ADC) with gain, shown in Figure 1-12.

FIGURE 1-12 A 1-bit sampling analog-to-digital converter (ADC) module. It is named adc and has two analog inputs gain and a, one digital input clk and one digital output d_out.

Using VHDL-AMS terminology, we call the module adc a design entity, and the inputs and outputs are ports. Figure 1-13 shows a VHDL-AMS description of the interface to this entity. This is an example of an entity declaration. The first two lines of the figure indicate that the entity involves aspects of analog electrical-energy systems. We will explain the precise meaning of these lines in due course, but for now we will treat them as VHDL-AMS magic to be included when we describe models in the electrical domain. The entity declaration introduces a name for the entity and lists the input and output ports. The port named gain is an analog quantity port, representing a voltage level that is a continuous function of time. The port named a is an analog terminal port of the electrical nature, representing a circuit node. The nature specifies that the terminal has voltage and current properties associated with it, and that rules governing conservation of energy apply at the terminal. The ports named clk and d are digital signal ports of type bit. They carry ‘0’ and ‘1’ values into and out of the entity. From this we see that an entity declaration describes the external view of the entity.