This application is generally related to electronic design automation and, more specifically, to design aware adaptive mixed-signal simulation.
Designing and fabricating electronic systems typically involves many steps, known as a “design flow.” The particular steps of a design flow often are dependent upon the type of electronic system to be manufactured, its complexity, the design team, and the fabricator or foundry that will manufacture the electronic system from a design.
Initially, a specification for a new electronic system can be transformed into a logical design. When the electronic system includes a combination of digital circuitry and analog circuitry, such as with System-On-a-Chip (SOC) devices or the like, the logical design can be a mixed-signal design describing the electronic system in terms of both the exchange of analog and digital signals between circuit components and the operations that can be performed on those signals. These mixed-signal designs are typically written in one or more Hardware Design Languages (HDLs), such as System Verilog, Very high speed integrated circuit Hardware Design Language (VHDL), Verilog Analog Mixed Signal (Verilog-AMS), VHDL-AMS, System-C, Simulation Program with Integrated Circuit Emphasis (SPICE), Eldo-SPICE, Spectre, or the like.
After the logical design has been generated, verification tools can be utilized to verify a functionality of the logical design, for example, by running simulators and/or hardware emulators, or by utilizing formal techniques, allowing any errors in the design discovered during the verification process to be corrected. Simulators of mixed-signal designs can include both an analog simulator to simulate analog portions of the mixed-signal designs, for example, using a continuous time matrix-based differential equation solver, and a digital simulator to simulate the digital portions of the mixed-signal designs, for example, using an event-based discrete time events processor.
To perform mixed-signal simulation, the simulators partition the mixed-signal design into analog portions and digital portions, and then insert translator cells to enable the simulators to manage inter-solver dependencies between an analog simulation and a digital simulation. The performance and accuracy of mixed-signal simulation directly depends on the number of translator cells inserted by the simulators. Traditional approaches to mixed-signal design partitioning identify where to partition the mixed-signal design by processing signal connectivity in the mixed-signal design. While this partitioning approach allows the simulator a standard and predictable technique to partition the mixed-signal design, it often creates additional digital-analog crossings and thus an excessive number of translator cells that can hamper simulator performance.
This application discloses a computing system implementing a design verification system to classify a mixed-signal circuit design describing an electronic device having analog circuitry and digital circuitry based on a design topology of the mixed-signal circuit design. This classification of the mixed-signal circuit can be performed by identifying a top-level design block in a design hierarchy of the mixed-signal circuit design, traversing the design hierarchy of the mixed-signal circuit design to identify lower-level design blocks in the mixed-signal circuit design, and then classifying the mixed-signal circuit design based, at least in part, on at least one of a design type of the top-level design block, design types of the lower-level design blocks, or a connectivity of design blocks in the mixed-signal circuit design.
The design verification system can selectively partition the mixed-signal circuit design into an analog partition and a digital partition based, at least in part, on the classification of the mixed-signal circuit design. When the classification of the mixed-signal circuit design corresponds to an analog-on-top topology, a digital-on-top topology, or an analog mixed-signal topology, the design verification system can partition the mixed-signal circuit design at a design block level. When the classification of the mixed-signal circuit design corresponds to complex design topology, the design verification system can partition the mixed-signal circuit design by processing the signals in the mixed-signal circuit design.
The design verification system can locate transitions between types of design blocks in the mixed-signal circuit design and insert one or more boundary design blocks into the analog partition or the digital partition of the mixed-signal circuit design at the transitions between the types of the design blocks based, at least in part, on the classification of the topology of the mixed-signal circuit design. The design verification system also can insert translator cells into the mixed-signal circuit design between the analog partition and the digital partition.
The design verification system can elaborate the analog partition, the digital partition, and the translator cells, and then simulate the analog partition of the mixed-signal circuit design with an analog simulator and the digital partition of the mixed-signal circuit design with a digital simulator. The analog simulator and the digital simulator can communicate during their simulations via the translator cells. Embodiments of will be described below in greater detail.
Various examples may be implemented through the execution of software instructions by a computing device 101, such as a programmable computer. Accordingly,
The processor unit 105 and the system memory 107 are connected, either directly or indirectly, through a bus 113 or alternate communication structure, to one or more peripheral devices 115-123. For example, the processor unit 105 or the system memory 107 may be directly or indirectly connected to one or more additional memory storage devices, such as a hard disk drive 117, which can be magnetic and/or removable, a removable optical disk drive 119, and/or a flash memory card. The processor unit 105 and the system memory 107 also may be directly or indirectly connected to one or more input devices 121 and one or more output devices 123. The input devices 121 may include, for example, a keyboard, a pointing device (such as a mouse, touchpad, stylus, trackball, or joystick), a scanner, a camera, and a microphone. The output devices 123 may include, for example, a monitor display, a printer and speakers. With various examples of the computing device 101, one or more of the peripheral devices 115-123 may be internally housed with the computing unit 103. Alternately, one or more of the peripheral devices 115-123 may be external to the housing for the computing unit 103 and connected to the bus 113 through, for example, a Universal Serial Bus (USB) connection.
With some implementations, the computing unit 103 may be directly or indirectly connected to a network interface 115 for communicating with other devices making up a network. The network interface 115 can translate data and control signals from the computing unit 103 into network messages according to one or more communication protocols, such as the transmission control protocol (TCP) and the Internet protocol (IP). Also, the network interface 115 may employ any suitable connection agent (or combination of agents) for connecting to a network, including, for example, a wireless transceiver, a modem, or an Ethernet connection. Such network interfaces and protocols are well known in the art, and thus will not be discussed here in more detail.
It should be appreciated that the computing device 101 is illustrated as an example only, and it not intended to be limiting. Various embodiments may be implemented using one or more computing devices that include the components of the computing device 101 illustrated in
With some implementations, the processor unit 105 can have more than one processor core. Accordingly,
Each processor core 201A and 201B is connected to an interconnect 207. The particular construction of the interconnect 207 may vary depending upon the architecture of the processor unit 105. With some processor cores 201A and 201B, such as the Cell microprocessor created by Sony Corporation, Toshiba Corporation and IBM Corporation, the interconnect 207 may be implemented as an interconnect bus. With other processor units 201A and 201B, however, such as the Opteron™ and Athlon™ dual-core processors available from Advanced Micro Devices of Sunnyvale, California, the interconnect 207 may be implemented as a system request interface device. In any case, the processor cores 201A and 201B communicate through the interconnect 207 with an input/output interface 209 and a memory controller 210. The input/output interface 209 provides a communication interface to the bus 113. Similarly, the memory controller 210 controls the exchange of information to the system memory 107. With some implementations, the processor unit 105 may include additional components, such as a high-level cache memory accessible shared by the processor cores 201A and 201B. It also should be appreciated that the description of the computer network illustrated in
The design verification system 300, for example, implemented in the computing device 101 of
The design verification tool 300 can include an adaptive partitioning system 310 to partition the mixed-signal circuit design 301 into an analog partition and a digital partition based on design characteristics of the mixed-signal circuit design 301. By analyzing a block level design topology for the mixed-signal circuit design 301, rather than at the signal-level, the adaptive partitioning system 310 can selectively partition the mixed-signal circuit design 301 to preserve design blocks and reduce translation cell insertion.
The adaptive partitioning system 310 can include a design parser 312 that, in a block 401 of
The design parser 312 can traverse the design hierarchy of mixed-signal circuit design 301 to locate other design blocks and to determine their type, such as an analog design block, a digital design block, or an analog mixed-signal design block. For example, the design parser 312 can identify connections from the top-level design block to lower-level design blocks in the mixed-signal circuit design 301 and determine a design type for the lower-level design blocks, such as an analog design block, a digital design block, or an analog mixed-signal design block. The design parser 312 can then identify connections from the lower-level design blocks to even lower-level design blocks in the mixed-signal circuit design 301 and determine a design type for the even lower-level design blocks, such as an analog design block, a digital design block, or an analog mixed-signal design block.
In some embodiments, during the traversal, the design parser 312 can identify hierarchical connectivity in the mixed-signal circuit design 301. The hierarchical connectivity can correspond to one or more signal connections between an analog design block and a digital design block that are located in different levels and branches of the design hierarchy for the mixed-signal circuit design 301. For example, when a digital design block in a lower level of a design hierarchy connects with an analog design block in a different branch of the design hierarchy, the design parser 312 can categorize the connectivity between the digital design block and the analog design block as hierarchical connectivity.
The design parser 312 can classify the mixed-signal circuit design 301 based on the type of the top-level design block of the mixed-signal circuit design 301, the design blocks located at the boundaries between the digital portion and the analog portion of the mixed-signal circuit design 301, and a presence of any hierarchical connectivity. In some embodiments, the design parser 312 can classify the mixed-signal circuit design 301 as an analog-on-top design, a digital-on-top design, a mixed-signal design that includes a Verilog AMS (Analog Mixed Signal) design block, or complex design type, such as a mixed-signal design that includes a VHDL AMS design block, an analog block connected to a digital block through a hierarchical reference, analog and digital blocks intermixed in a complex fashion, or the like.
When, in a block 402 of
When, in the block 402 of
The adaptive partitioning system 310 can include a design conversion unit 314 that, in a block 404 of
During design aware partitioning of the mixed signal circuit design 500, a design verification system can determine that the mixed signal circuit design 500 has an analog on top design topology due to the presence of the analog block 501 located at the top of the design hierarchy and an absence of other complex design blocks, such as analog mixed signal design block describing both analog and digital circuitry, or complex connectivity, such as hierarchical connectivity between lower-level analog and digital blocks.
Referring to
During design aware partitioning of the mixed signal circuit design 600, a design verification system can determine that the mixed signal circuit design 600 has a digital on top design topology due to the presence of the digital block 601 located at the top of the design hierarchy and an absence of other complex design blocks, such as analog mixed signal design block describing both analog and digital circuitry, or complex connectivity, such as hierarchical connectivity between lower-level analog and digital blocks.
Referring to
During design aware partitioning of the mixed signal circuit design 700, a design verification system can determine that the mixed signal circuit design 700 has an analog mixed signal design topology due to the presence of the Verilog-AMS blocks 707 and 708 and an absence of other complex design blocks, such as VHDL analog mixed signal (VHDL-AMS) design block describing both analog and digital circuitry, or complex connectivity, such as hierarchical connectivity between lower-level analog and digital blocks.
Referring to
The digital partition 710 and the analog partition 720 can retain the same connectivity between the digital blocks 704-706 and the analog blocks 701-703, except the original connectivity between the analog block 701 and the digital block 704 can be routed through the analog proxy block 711. Since the Verilog-AMS blocks 707 and 708 in the mixed signal circuit design 700 were split into different analog and digital parts during the design aware partitioning, the digital partition 710 and the analog partition 720 can include new connectivity between the Verilog digital blocks 712 and 713 and the Verilog analog blocks 722 and 723.
Referring back to
The design verification tool 300 can include an elaboration system 320 to elaborate the translator cells, the analog partition, and the digital partition of the mixed-signal circuit design 301. The elaboration process can render the digital partition of the mixed-signal circuit design 301 possibly along with one or more of the translator cells into a format capable of being simulated by the digital simulator 332. The elaboration process also can render the analog partition possibly along with one or more of the translator cells into a format capable of being simulated by the analog simulator 334. The elaboration system 320 also can elaborate the test bench 302 into a format usable in the mixed-signal simulation environment.
The design verification tool 300 can include a functional verification unit 330 to implement a mixed-signal verification environment, which can simulate the mixed-signal circuit design 301 and the test bench 302. The functional verification unit 330 can perform analog simulation on the analog partition of the mixed-signal circuit design 301 with the analog simulator 334 and perform digital simulation on the digital partition of the mixed-signal circuit design 301 with the digital simulator 332. The digital simulator 332 can simulate the functional operations performed by the digital partition of the mixed-signal circuit design 301 in response to test stimulus generated by the test bench 302, for example, using an event-based discrete time events processor. The analog simulator 334 can simulate the functional operations performed by the analog partition of the mixed-signal circuit design 301 in response to the test stimulus generated by the test bench 302, for example, using a continuous time matrix-based differential equation solvers.
The functional verification unit 330 can generate verification results 303, for example, including waveform data corresponding to the functional operation of the mixed-signal circuit design 301 in the mixed-signal verification environment. The design verification system 300 (or a tool external to the design verification tool 300) can perform a functional verification of the mixed-signal circuit design 301, for example, by comparing the waveform data with an expected output from the mixed-signal circuit design 301 in response the test stimulus generated by the test bench 302.
The system and apparatus described above may use dedicated processor systems, micro controllers, programmable logic devices, microprocessors, or any combination thereof, to perform some or all of the operations described herein. Some of the operations described above may be implemented in software and other operations may be implemented in hardware. Any of the operations, processes, and/or methods described herein may be performed by an apparatus, a device, and/or a system substantially similar to those as described herein and with reference to the illustrated figures.
The processing device may execute instructions or “code” stored in memory. The memory may store data as well. The processing device may include, but may not be limited to, an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, a network processor, or the like. The processing device may be part of an integrated control system or system manager, or may be provided as a portable electronic device configured to interface with a networked system either locally or remotely via wireless transmission.
The processor memory may be integrated together with the processing device, for example RAM or FLASH memory disposed within an integrated circuit microprocessor or the like. In other examples, the memory may comprise an independent device, such as an external disk drive, a storage array, a portable FLASH key fob, or the like. The memory and processing device may be operatively coupled together, or in communication with each other, for example by an I/O port, a network connection, or the like, and the processing device may read a file stored on the memory. Associated memory may be “read only” by design (ROM) by virtue of permission settings, or not. Other examples of memory may include, but may not be limited to, WORM, EPROM, EEPROM, FLASH, or the like, which may be implemented in solid state semiconductor devices. Other memories may comprise moving parts, such as a known rotating disk drive. All such memories may be “machine-readable” and may be readable by a processing device.
Operating instructions or commands may be implemented or embodied in tangible forms of stored computer software (also known as “computer program” or “code”). Programs, or code, may be stored in a digital memory and may be read by the processing device. “Computer-readable storage medium” (or alternatively, “machine-readable storage medium”) may include all of the foregoing types of memory, as well as new technologies of the future, as long as the memory may be capable of storing digital information in the nature of a computer program or other data, at least temporarily, and as long at the stored information may be “read” by an appropriate processing device. The term “computer-readable” may not be limited to the historical usage of “computer” to imply a complete mainframe, mini-computer, desktop or even laptop computer. Rather, “computer-readable” may comprise storage medium that may be readable by a processor, a processing device, or any computing system. Such media may be any available media that may be locally and/or remotely accessible by a computer or a processor, and may include volatile and non-volatile media, and removable and non-removable media, or any combination thereof.
A program stored in a computer-readable storage medium may comprise a computer program product. For example, a storage medium may be used as a convenient means to store or transport a computer program. For the sake of convenience, the operations may be described as various interconnected or coupled functional blocks or diagrams. However, there may be cases where these functional blocks or diagrams may be equivalently aggregated into a single logic device, program or operation with unclear boundaries.
While the application describes specific examples of carrying out embodiments of the invention, those skilled in the art will appreciate that there are numerous variations and permutations of the above described systems and techniques that fall within the spirit and scope of the invention as set forth in the appended claims. For example, while specific terminology has been employed above to refer to design processes, it should be appreciated that various examples of the invention may be implemented using any desired combination of electronic design automation processes.
One of skill in the art will also recognize that the concepts taught herein can be tailored to a particular application in many other ways. In particular, those skilled in the art will recognize that the illustrated examples are but one of many alternative implementations that will become apparent upon reading this disclosure.
Although the specification may refer to “an”, “one”, “another”, or “some” example(s) in several locations, this does not necessarily mean that each such reference is to the same example(s), or that the feature only applies to a single example.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2020/047824 | 8/25/2020 | WO |