<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.cadence.com/Community/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" 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/"><channel><title>Manufacturability Signoff - All Comments</title><link>http://www.cadence.com/Community/blogs/mfg/default.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2007.1 (Build: 20917.1142)</generator><item><title>There is an Applicat ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2009/03/05/erc-in-assura.aspx#26891</link><pubDate>Fri, 12 Mar 2010 21:26:39 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:26891</guid><dc:creator>Anonymous</dc:creator><description>&lt;p&gt;There is an Application Note available on COS explaining Assura ERC flow. &lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=26891" width="1" height="1"&gt;</description></item><item><title>We have a linkedin g ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2009/08/07/tidbits-from-tsmc-q209-earnings-call-40nm-yield.aspx#21192</link><pubDate>Mon, 21 Sep 2009 19:50:29 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:21192</guid><dc:creator>Anonymous</dc:creator><description>&lt;p&gt;We have a linkedin group on semiconductor DFM, where you can find most of the industry leaders and university researchers. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;For those who would like to explore more please join at &lt;a href="http://www.linkedin.com/groups?gid=2257625&amp;amp;trk=hb_side_g" rel="nofollow" target="_new"&gt;www.linkedin.com/groups&lt;/a&gt;&lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=21192" width="1" height="1"&gt;</description></item><item><title>Thanks for pointing  ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2009/04/10/no-more-moore.aspx#19415</link><pubDate>Wed, 22 Jul 2009 03:57:44 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:19415</guid><dc:creator>skmurphy</dc:creator><description>&lt;p&gt;Thanks for pointing out &amp;quot;Alan Moore&amp;#39;s Law&amp;quot; it was very good. &amp;nbsp;There is in fact a relationship between the two laws (from Howard Landman and David Patterson)&lt;/p&gt;
&lt;p&gt;Productivity begets quality. Automated checking begets quality.&lt;/p&gt;
&lt;p&gt;Patterson&amp;rsquo;s Precept: Inexperience coupled with ambition leads to very large designs.&lt;/p&gt;
&lt;p&gt;Landman&amp;rsquo;s Law: In any sufficiently large design, if there is a type of error for which you have no automatic way of checking, then the final design will contain at least one error of that type.&lt;/p&gt;
&lt;p&gt;Landman&amp;rsquo;s Lemma: All designs are now sufficiently large. See Patterson&amp;rsquo;s Precept.&lt;/p&gt;
&lt;p&gt;Kevin Kelly recently wrote &amp;quot;Was Moore&amp;#39;s Law Inevitable?&amp;quot; ( &lt;a href="http://www.kk.org/thetechnium/archives/2009/07/was_moores_law.php" rel="nofollow" target="_new"&gt;www.kk.org/.../was_moores_law.php&lt;/a&gt; &amp;nbsp;) a long essay about Moore&amp;#39;s Law and a family of companion curves for magnetic medium, broadcast media bandwidth etc.. that &amp;quot;demonstrate the effects of scaling down, or working with the small. In this microcosmic realm energy is not very important. We don&amp;#39;t see exponential improvement in efforts to scale up.&amp;quot;&lt;/p&gt;
&lt;p&gt;I think you are missing out not at least reading the Watchmen graphic novel (all 12 issues of the comic book series gathered into a single volume). It&amp;#39;s very well done and extremely thought provoking, it&amp;#39;s not a traditional (superhero) comic at all. &lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=19415" width="1" height="1"&gt;</description></item><item><title>TSMC has a DDK (DFM  ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2008/07/13/dfm-in-disguise.aspx#19368</link><pubDate>Mon, 20 Jul 2009 17:28:30 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:19368</guid><dc:creator>wilbur</dc:creator><description>&lt;p&gt;TSMC has a DDK (DFM Data Kit) for each of their process nodes that their customers can download. &amp;nbsp;This kit includes models, etc... including what you asked about (defect densities that qualified CAA tools use to calculate random defect yield)&lt;/p&gt;
&lt;p&gt;So essentially, you need the kit + a qualified CAA analysis engine/tool + your layout... and you should be good to go. &amp;nbsp;Besides doing just the CAA analysis, note that some implementation tools (like Encounter) have a CAA engine available and can also read the TSMC DDK &lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=19368" width="1" height="1"&gt;</description></item><item><title>Does TSMC and/or oth ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2008/07/13/dfm-in-disguise.aspx#19351</link><pubDate>Mon, 20 Jul 2009 05:25:48 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:19351</guid><dc:creator>Anonymous</dc:creator><description>&lt;p&gt;Does TSMC and/or others produce failure rates (parts per billion) for their library models? In order to perform yield optimization (along with area, timing, and leakage) through the place and route flow?&lt;/p&gt;
&lt;p&gt;Im interested in proactive yield optimization rather than reactive (late flow) methods such as CAA.&lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=19351" width="1" height="1"&gt;</description></item><item><title>Please tell me what  ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2009/03/17/assura-on-steroids.aspx#17370</link><pubDate>Sun, 03 May 2009 21:43:00 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:17370</guid><dc:creator>Anonymous</dc:creator><description>&lt;p&gt;Please tell me what happened to PVS/&lt;/p&gt;
&lt;p&gt;Axel&lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=17370" width="1" height="1"&gt;</description></item><item><title>The other thing to c ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2009/01/09/getting-good-silicon-with-more-accurate-timing.aspx#16871</link><pubDate>Thu, 16 Apr 2009 17:54:25 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:16871</guid><dc:creator>wilbur</dc:creator><description>&lt;p&gt;The other thing to consider is separating random vs. systematic variation. If one can control systematic (through accurate modeling of the manufacturing process and application of the model to the simulation), and then add some margin for the random... that would reduce the over-margining.&lt;/p&gt;
&lt;p&gt;There have been a burst of papers at various conferences (like SPIE) addressing variability. Since it wouldn&amp;#39;t be proper to post the paper, drop me a note and I&amp;#39;ll point you to it. &amp;nbsp;One of the interesting findings is that at 65nm litho variation dominated and now at &amp;lt;=45nm context-dependent stress is dominating&lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=16871" width="1" height="1"&gt;</description></item><item><title>Yes, I am concerned. ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2009/01/09/getting-good-silicon-with-more-accurate-timing.aspx#16834</link><pubDate>Thu, 16 Apr 2009 02:09:47 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:16834</guid><dc:creator>kosimov</dc:creator><description>&lt;p&gt;Yes, I am concerned. &amp;nbsp;5% variation in the critical path is a target I could use, but of course would want to be able to go above and below that a reasonable amount, say, +- 5%, so, from zero to 10% for the total variation range, or, +-5% if considering direction of variations. (rough numbers; if there are reasons why similar numbers would be easier to implement, etc., of course that would be OK if in the ballpark...). &amp;nbsp;I have not had experience with variation aware methodologies yet but have &amp;quot;wished&amp;quot; for them for years, at least, for a technique which was common to all design tools (at the minimum, common to the tools in a manufacturer&amp;#39;s tool set(s)) and relatively simple and easy to use, and of course, any other blue sky spec I could think of! &amp;nbsp;Seriously, though, I hope it would be easier than running multiple monte carlo analyses on old spice versions!&lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=16834" width="1" height="1"&gt;</description></item><item><title>When you cannot get  ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2008/08/06/please-take-a-look-at-this.aspx#14233</link><pubDate>Thu, 29 Jan 2009 19:03:36 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:14233</guid><dc:creator>Anonymous</dc:creator><description>&lt;p&gt;When you cannot get closure between what you design and what you actually build with that design - sizing, placement, materials properties - you expect massive systematic failures. Design rule compliance can no longer be taken for granted. Our design and manufacture have gone beyond design verification infrastructure required for predictable execution. Yield learning is a terrible way to start learning DR violations. Extensive CD-SEM based metrology in layouts on production wafers is the right thing to do, as long as you get relevant and accurate data on DR compliance. Yet, I would think that much more is needed to regain closure. &amp;nbsp; &lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=14233" width="1" height="1"&gt;</description></item><item><title>Good points but the  ... </title><link>http://www.cadence.com/Community/blogs/mfg/archive/2008/10/21/diagnosis-of-compressed-test-patterns-what-is-best.aspx#12769</link><pubDate>Mon, 17 Nov 2008 22:57:04 GMT</pubDate><guid isPermaLink="false">75bcbcf9-38a3-4e2e-b84b-26c8c46a9500:12769</guid><dc:creator>Anonymous</dc:creator><description>&lt;p&gt;Good points but the data size of scan patterns is huge.&lt;/p&gt;
&lt;img src="http://www.cadence.com/Community/aggbug.aspx?PostID=12769" width="1" height="1"&gt;</description></item></channel></rss>
