<?xml version="1.0" encoding="UTF-8"?><rss version="2.0">
    <channel>
        <title><![CDATA[TB-Blog - TechBites]]></title>
        <description><![CDATA[TechBites - The Science and Technology Collaborative Community]]></description>
        <link>http://www.techbites.com/</link>
		        	        	        <item>
                <guid isPermaLink="false">2010-488</guid>
	            <title><![CDATA[Synopsys and CoWare tie the knot. Virtual Prototyping on fire!!: How will all the pieces fit?]]></title>
	            <link>/201002082010/myblog/blog/z000d-synopsys-and-coware-tie-the-knot-virtual-prototyping-on-fire.html</link>
	            <description><![CDATA[
	            	            I just caught your tweet on this, thanks, Brian!  So after also taking VaST last week, SNPS has three pieces to put together in virtual prototyping ... the third being Innovator, a relatively new VP/hardware-software co-verification platform.

And thanks for the reminder in your piece about LTE work that CoWare is doing with Xilinx.  It's been a while since I've noted that CoWare has SPW (and BoNES), which was acquired by Cadence from Comdisco (a wide span holding company a la Tyco).  I can't recall if CoWare purchased rights to that product from Cadence or if CDNS subcontracted CoWare to take charge of it.  If CoWare owns it outright, I wonder if SPW and BoNES would be the first tools to hopscotch from one Big 3 EDA firm to another?  (Oh, what a great EDA pannel trivia question that would make, like the Political Junkie's weekly question on NPR's Talk Of The Nation!)  And if not, how quickly will Cadence pull it back?

And it now makes me wonder ... ARM's SoC Designer, formerly the Axys tool, has Carbon as its home.  Will Cadence or Mentor go after it, especially if ARM still owns the technology?  (Can tonight's '24' cliff-hanger top that?)
	            ]]></description>
                <category><![CDATA[TB-Blog]]></category>
                <pubDate>Tue, 09 Feb 2010 01:05:10 -0600</pubDate>
            </item>
	        		    </channel>
</rss>

