editor's blog
Subscribe Now

Get Wreal

When analog design discussions turn to simulation, especially when they involve Cadence, one inevitably comes up against the unfortunately-named concept of the “wreal” type. I say “unfortunately” because, pronounced with standard English rules, it’s pronounced “real,” providing no audible distinction from the “real” type. So it’s typically pronounced “double-you-real.” (Or occasionally you’ll hear “wuh-real.”) Yeah, unfortunate.

It’s also difficult to find information on exactly what it is and the context driving its use. It’s easy to learn that it can make some simulation faster, but, somehow, from there you end up diving way down into the nitty gritty of differences between the Verilog-AMS version and Cadence’s version and specific problems being discussed in forums and… well… let’s just try to back up a bit. I was able to talk to Mladen Nizic, a Cadence engineering director, in an attempt to articulate a big-picture statement of the role of the wreal.

First some background. Analog and digital simulators fundamentally work differently. An analog simulator attempts to calculate the state or operating point of a complete circuit. It’s a static, holistic, matrix calculation that is then repeated over very small time increments in an attempt to model continuous time. At any given time, the voltage and current are known for any node.

By contrast, digital simulators model the flow of signals from stimulus to response, driven by events, and they assume the discrete time behavior afforded by a clock. There are no voltages or currents, only 1s and 0s. (And Xs.)

Wreal signals help to bridge the divide between pure analog simulation and full-chip analog/mixed-signal (AMS) simulation. This is necessary for two reasons: AMS simulation must account for the preponderance of digital content, and the size of these chips means that higher simulation performance is needed than would be remotely possible if you tried to simulate the entire chip at an analog level.

With a wreal signal, you can take a voltage or current (but not both) between modules of the full chip. It can operate in a signal-flow fashion, behaving more like a digital signal. This allows it to play nicely in the digital simulation paradigm.

Cadence has made some extensions to the standard wreal:

–          You can typecast signals to/from wreal

–          You can have arrays of wreals

–          You can have multiple drivers on a wreal signal (and the tool will resolve the correct voltage or current)

You still need to do your full analog simulation to make sure your analog module is working properly, but you can now integrate the analog block into your full-chip simulation to make sure that it plays nicely with everything else.

 

When discussions of analog simulation [B1] arise, especially when they involve Cadence, one inevitably comes up against the unfortunately-named concept of the “wreal” type. I say “unfortunately” because, pronounced with standard English rules, it’s pronounced “real,” providing no audible distinction from the “real” type. So it’s typically pronounced “double-you-real.” (Or occasionally you’ll hear “wuh-real.”) Yeah, unfortunate.

It’s also difficult to find information on exactly what it is and the context driving its use. It’s easy to learn that it can make some simulation faster, but, somehow, from there you end up diving way down into the nitty gritty of differences between the Verilog-AMS version and Cadence’s version and specific problems being discussed in forums and… well… let’s just try to back up a bit. I was able to talk to Mladen Nizic, a Cadence engineering director, in an attempt to articulate a big-picture statement of the role of the wreal.

First some background. Analog and digital simulators fundamentally work differently. An analog simulator attempts to calculate the state or operating point of a complete circuit. It’s a static, holistic, matrix calculation that is then repeated over very small time increments in an attempt to model continuous time. At any given time, the voltage and current are known for any node.

By contrast, digital simulators model the flow of signals from stimulus to response, driven by events, and they assume the discrete time behavior afforded by a clock. There are no voltages or currents, only 1s and 0s. (And Xs.)

Wreal signals help to bridge the divide between pure analog simulation and full-chip analog/mixed-signal (AMS) simulation. This is necessary for two reasons: AMS simulation must account for the preponderance of digital content, and the size of these chips means that higher simulation performance is needed than would be remotely possible if you tried to simulate the entire chip at an analog level.

With a wreal signal, you can take a voltage or current (but not both) between modules of the full chip. It can operate in a signal-flow fashion, behaving more like a digital signal. This allows it to play nicely in the digital simulation paradigm.

Cadence has made some extensions to the standard wreal:

          You can typecast signals to/from wreal

          You can have arrays of wreals

          You can have multiple drivers on a wreal signal (and the tool will resolve the correct voltage or current)

You still need to do your full analog simulation to make sure your analog module is working properly, but you can now integrate the analog block into your full-chip simulation to make sure that it plays nicely with everything else.


 [B1]Link to surrender article

Leave a Reply

featured blogs
Sep 25, 2018
Robots are a hot topic these days. From helping doctors in the operating room to helping survivors of a natural disaster, it'€™s clear that robots are poised to play an important role......
Sep 25, 2018
CDNLive India took place a few weeks ago and we are just trying to catch our breath! If you missed it, I'm going to be posting two cool videos before the weekend with the highlights. Here are two blogs by the veteran blogger Paul McLellan - one on Asynchronous Design and...
Sep 24, 2018
One of the biggest events in the FPGA/SoC ecosystem is the annual Xilinx Developers Forum (XDF). XDF connects software developers and system designers to the deep expertise of Xilinx engineers, partners, and industry leaders. XDF takes place in three locations this year.  Sa...
Sep 21, 2018
  FPGA luminary David Laws has just published a well-researched blog on the Computer History Museum'€™s Web site titled '€œWho invented the Microprocessor?'€ If you'€™re wildly waving your raised hand right now, going '€œOoo, Ooo, Ooo, Call on me!'€ to get ...