<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>Ahmed Elzeftawi Blog</title><link>http://www.cadence.com/Community/search/SearchResults.aspx?&amp;u=266301&amp;un=AElzeftawi&amp;Scope=Blogs</link><description>Search results by user ID 266301</description><dc:language>en-US</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/cadence/community/blogs/266301" /><feedburner:info uri="cadence/community/blogs/266301" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item><title>Library &amp;quot;Safe Margins&amp;quot; -- Are They Really Saving Your Design?</title><link>http://feedproxy.google.com/~r/cadence/community/blogs/266301/~3/SWOIrWo-isw/library-safe-margins-are-these-really-saving-your-design.aspx</link><pubDate>Thu, 10 Jan 2013 19:15:00 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:1318576</guid><dc:creator>AElzeftawi</dc:creator><description>&lt;p&gt;Designers need to radically re-think their strategies for timing closure to get the most out of process technologies that are becoming readily available. The additional burdens of creating electrical cell views for timing, power and signal integrity, accounting for process variability, managing leakage power, and hitting a low power budget make obtaining market leading performance extremely difficult.&lt;/p&gt;&lt;p&gt;To overcome these increasing burdens, designers have to reduce margins that exist within timing models provided by a 3rd party IP provider or a central library group. This will require designers to control how standard cell library views are created to better tune their models. The best way to do so is to characterize/re-characterize the library for specific design goals.&lt;/p&gt;&lt;p&gt;Today, designers working on production designs for 40nm, 28-nm and 20nm processes are left with no window to work with - and the situation will only get worse as we head towards 16nm and 14nm. For example, timing signoff can be achieved at the worst case corner at high temperature but not at low temperature. The need for supporting a wide range of process, voltage and temperature corners (PVTs) is increasing due to shrinking device geometries. The impact of variation and temperature inversion is greater for lower voltages, yet these are now the norm due to the need to reduce power. &lt;/p&gt;&lt;p&gt;The sensitivity to process variation, the exponential growth of characterization runs, and the number of data points per each characterization run pose more challenges. The paradox is that the overlying process technology can often deliver on the design goals but the tools, process models and methodology get in the way. Every tool and each modeling level adds margin until all the guard bands eat up all the design space.&lt;/p&gt;&lt;p&gt;The following areas need careful consideration due to their impact on library accuracy and development schedules: &lt;/p&gt;&lt;p&gt;1. Standard cell library characterization solution must offer high productivity for large complex cells and complex I/Os&lt;/p&gt;&lt;p&gt;2. Solution must support libraries from multiple foundries and IP providers&lt;/p&gt;&lt;p&gt;3. Solution must be tightly integrated with a leading edge simulation solution for uncompromised accuracy and scalable performance&lt;/p&gt;&lt;p&gt;4. Solution must support a wide range of PVTs&lt;/p&gt;&lt;p&gt;5. Solution must support low-power, high speed standard cell library variants&lt;/p&gt;&lt;p&gt;6. Generated models must be of utmost precision and accuracy&lt;/p&gt;&lt;p&gt;7. Models must be consistent with other characterization components including large macros and memory blocks &lt;/p&gt;&lt;p&gt;8. Solution offers flexibility in setting measurements and thresholds for items such as: &lt;/p&gt;&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; a. Setup and hold for flip-flops, latches and clock gating cells &lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; b. Pin capacitance measurement&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; c. Type of pre-driver used&lt;/p&gt;&lt;p&gt;An integrated library characterization solution based on the Cadence Virtuoso platform is depicted below.&lt;/p&gt;&lt;p class="MsoNormal"&gt;&lt;span&gt;&lt;a href="http://www.cadence.com/Community/CSSharedFiles/blogs/cic/2012/ChzTools.jpg"&gt;&lt;img src="http://www.cadence.com/Community/CSSharedFiles/blogs/cic/2012/ChzTools.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;&lt;p&gt;By characterizing standard cell libraries, users can get a wide range of choices for how simulation data is captured and measured before it is encapsulated in Liberty format. For example, the value of pin capacitance varies by up to 50% depending on the measurement thresholds and this can have a major impact on hold time closure. For setup and hold values, typically there is additional margin added by the IP provider to avoid warnings further down in the tool flow. For example, some tools do not support negative setup or hold times so margin is added to the library to remove the negative constraints.&lt;/p&gt;&lt;p&gt;For designs that use multiple voltages or dynamic voltage scaling, the delay calculator will use interpolation if the library views do not explicitly cover the voltage being used, nearly always providing pessimistic results. Designers can overcome this by characterizing more voltage corners which reduces built-in margins thus achieving higher accuracy. Moreover, by the time the library is delivered the process models used to create it may have changed. Process models typically tighten their margins as they mature, but if the library isn&amp;#39;t up to date, the timing closure tools will not enjoy this benefit and will continue to be over-constrained. &lt;/p&gt;&lt;p&gt;For memory IP blocks, the timing and power models are created by a compiler without knowing the exact context of how the memory block will be used. The memory compiler creates the model for each instance from fitting data derived from the characterization of a small set of memory instances. A more accurate model can be achieved by characterizing the exact size for each instance of each memory block using precise loading, slew rates, voltage and temperature values for each design.&lt;/p&gt;&lt;p&gt;The investment required to do project or design family specific characterization is relatively small. A new library corner for a thousand cells can now be completed in half a day or less using a single eight core machine. Smart characterization tools exist that can automatically setup and optimize the characterization directly from analyzing the transistors and arcs inside the cell. Besides, this allows design teams to take control of the standard cell library delivery schedule so they do not need to rely on the over-burdened central group or to pay additional fees if a new corner or a different characterization setting is required.&lt;/p&gt;&lt;p&gt;Margins are necessary to help safe guard against inaccuracies inherent in abstracting silicon components to the higher models. However, over-margining is creating a huge barrier to the effective use of 45nm and below processes. Using statistical methods will greatly help by providing a more realistic timing answer, but also taking control of the margins inherent in off-the-shelf IP models can also alleviate many timing closure challenges. To accelerate their development schedules, designers should take control of their characterization tasks to create realistic library views instead of relying on over-margined standard cell libraries.&lt;/p&gt;&lt;p&gt;Ahmed Elzeftawi&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;/span&gt;</description><feedburner:origLink>http://www.cadence.com/Community/blogs/cic/archive/2013/01/10/library-safe-margins-are-these-really-saving-your-design.aspx</feedburner:origLink></item><item><title>CDNLive! -- Real Number Model Development and Application in Mixed-Signal SoC Verification</title><link>http://feedproxy.google.com/~r/cadence/community/blogs/266301/~3/cX81HWGzADw/cdnlive-real-number-model-development-and-application-in-mixed-signal-soc-verification.aspx</link><pubDate>Mon, 09 Apr 2012 13:00:00 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:1309657</guid><dc:creator>AElzeftawi</dc:creator><description>&lt;p&gt;With the escalating complexity of analog mixed-signal (AMS) chips, increasing digital content in response to new functionality demands, and steady growth of IP blocks into larger and larger SoCs, traditional AMS verification flows are becoming inefficient in handling full chip verification. High performance digital verification and high accuracy analog verification represented the foundation for traditional AMS verification, characterized by performance and accuracy tradeoffs -- thus making AMS verification the biggest challenge facing verification engineers today. &lt;/p&gt;&lt;p&gt;Lack of consistent handoff between analog and digital design boundaries and the inexistence of mature verification methodologies for mixed signal verification have been common reasons for chip re-spins.&amp;nbsp; As AMS verification matures, so do the methodologies that support AMS verification which now include low-power, behavioral modeling abstraction, assertions, and metric driven verification methodologies.&lt;/p&gt;&lt;p&gt;I had the pleasure of meeting lots of customers during &lt;a href="https://www.cadence.com:443/cdnlive/na/2012/pages/default.aspx"&gt;CDNLive! Silicon Valley 2012&lt;/a&gt; and learned firsthand about their verification challenges and the approaches they&amp;#39;re taking to address such challenges. Ken Luo from LSI Corporation delivered a presentation about real number model (RNM) development and application in mixed-signal SoC verification. Luo iterated that exploding operating modes, functionality demands for digital control, and calibration to mitigate against process variations are typical trends in modern SoC designs. &lt;/p&gt;&lt;p&gt;As such, analog simulation performance and convergence are bottlenecks for full chip verification. Luo discussed the benefits of adopting RNM, which include the continuous value and discrete time nature of real numbers that allow for pure digital solver simulation and high speed performance. Also, Luo highlighted other features like multiple drivers and resolution function support for RNM, discipline association, and ease of connecting real to electrical nets using R2E/E2R connect modules.&lt;/p&gt;&lt;p&gt;Luo also shared some guidelines for RNM modeling regarding signal flow modeling (voltage vs. current), sampling approaches (uniform vs. non-uniform sampling) which are required to balance performance and accuracy, and modeling data processing algebraic equations vs. nonlinear table models. One of the key takeaways of the presentation is to &amp;quot;model what you need and not what you can&amp;quot; to reflect the specified functionality and avoid unnecessary high order effects. Another takeaway is to align the model development plan with the design development plan, maintain consistent interfaces for model/design, and to use version control to keep the model/design in sync. &lt;/p&gt;&lt;p&gt;Also, Luo discussed that models should be classified according to the block characteristics and verification requirements. Communication I/Os that toggle frequently and have low accuracy requirements can be modeled using Verilog, while high accuracy and frequently toggling nodes like clocks, oscillators, and high bandwidth amplifiers or high accuracy, less frequently toggling nodes like reference voltage/current and, low speed high resolution ADC/DAC, should be modeled using Verilog-AMS/Wreal.&lt;/p&gt;&lt;p&gt;Luo introduced&amp;nbsp;an LSI application, which is a hard disk drive (HDD) PreAmplifier that performs small signal amplification (during READ operation) and voltage waveform shaping (during WRITE operation) interfaces to the HDD R/W heads. The PreAmp has been historically an analog ASIC, but today it has became a complex mixed-signal SoC due to &amp;gt; 4.0 Gbps high data rate requirements, multiple operation modes, programmability of bias/threshold control and calibration. The increased feature complexity poses a challenge to AMS verification due to extremely long simulation times, D/A interface coverage and lack of coverage measurement. &lt;/p&gt;&lt;p&gt;The LSI verification team used Cadence verification planning (vPlan) to collect and define model feature requirements and align verification milestones. Also, the team developed analog mixed-signal Universal Verification Components (UVC) and checkers for analog signals for amplitude, frequency, common mode voltage and sampling frequency. The team observed significant improvements (~600x) using the RNM models over&amp;nbsp;SPICE simulations, which suffered convergence issues and didn&amp;#39;t provide adequate coverage. The RNM models achieved 95% accuracy, enabled full coverage, and achieved first silicon success with zero functional bugs. &lt;/p&gt;&lt;p&gt;AMS verification engineers need access to a strong design environment that bridges the productivity gap between analog and digital verification flows. The Virtuoso environment empowered by AMS Designer verification technology&amp;nbsp;is well equipped to resolve the inconsistent handoff between analog and digital design boundaries. RNM makes it possible to apply advanced digital verification methodologies to mixed-signal SoCs and enhance traditional AMS verification. &lt;/p&gt;&lt;p&gt;If you need further information on the presentation, please do not hesitate to contact me at &lt;a href="mailto:ahmedelz@cadence.com"&gt;ahmedelz@cadence.com&lt;/a&gt;&lt;/p&gt;&lt;p&gt;Ahmed Elzeftawi&lt;/p&gt;</description><feedburner:origLink>http://www.cadence.com/Community/blogs/ms/archive/2012/04/09/cdnlive-real-number-model-development-and-application-in-mixed-signal-soc-verification.aspx</feedburner:origLink></item></channel></rss>
