<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Experts At The Table: The Mixed Signal Challenge</title>
	<atom:link href="http://chipdesignmag.com/sld/blog/2009/01/02/experts-at-the-table-the-mixed-signal-challenge/feed/" rel="self" type="application/rss+xml" />
	<link>http://chipdesignmag.com/sld/blog/2009/01/02/experts-at-the-table-the-mixed-signal-challenge/</link>
	<description>Deep Insights for Chip Architects and Engineers</description>
	<lastBuildDate>Wed, 15 Jun 2011 14:29:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Kevin Cameron</title>
		<link>http://chipdesignmag.com/sld/blog/2009/01/02/experts-at-the-table-the-mixed-signal-challenge/comment-page-1/#comment-6514</link>
		<dc:creator>Kevin Cameron</dc:creator>
		<pubDate>Sat, 11 Jul 2009 18:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://chipdesignmag.com/sld/?p=1292#comment-6514</guid>
		<description>It would help a lot if the people with the problems would actually turn up at the committees and drive the process. The Verilog-AMS language has been stuck at Accellera for a decade when it should have been rolled into the IEEE Verilog efforts, in which case we would have a SystemVerilog-AMS language by now. As it is, a unified AMS flow is probably still some years off.

A top-down/bottom-up AMS design flow with IP reuse requires that things like back-annotation work correctly for behavioral descriptions, and as far as I can tell nobody is working on that problem for AMS. A related issue is how you handle power distribution/management, and that doesn&#039;t seem to be making a lot of progress either in the HDLs, so people are resorting to defining external standards (LPF etc.). This has also led to people trying to add AMS assertions to SystemVerilog, while there is still no support for analog design in SystemVerilog! 

So I would say &quot;yes we can&quot; automate mixed-signal design, but it&#039;s going to require a lot of work on the low level tools and standards first.</description>
		<content:encoded><![CDATA[<p>It would help a lot if the people with the problems would actually turn up at the committees and drive the process. The Verilog-AMS language has been stuck at Accellera for a decade when it should have been rolled into the IEEE Verilog efforts, in which case we would have a SystemVerilog-AMS language by now. As it is, a unified AMS flow is probably still some years off.</p>
<p>A top-down/bottom-up AMS design flow with IP reuse requires that things like back-annotation work correctly for behavioral descriptions, and as far as I can tell nobody is working on that problem for AMS. A related issue is how you handle power distribution/management, and that doesn&#8217;t seem to be making a lot of progress either in the HDLs, so people are resorting to defining external standards (LPF etc.). This has also led to people trying to add AMS assertions to SystemVerilog, while there is still no support for analog design in SystemVerilog! </p>
<p>So I would say &#8220;yes we can&#8221; automate mixed-signal design, but it&#8217;s going to require a lot of work on the low level tools and standards first.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

