<?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">2998-643</guid>
	            <title><![CDATA[VDC says virtual prototypes may not be delivering: Did they measure any other benefits?]]></title>
	            <link>/201009072998/myblog/blog/z0019-vdc-says-virtual-prototypes-may-not-be-delivering.html</link>
	            <description><![CDATA[
	            	            The increase in usage (9% --> 15%) speaks volumes.  The tools are not hard to use (for the embedded developer handed a platform), so what holds up faster growth?  The availability of models!

I agree that virtual prototypes are helping us keep pace with increasing technology.  In addition I have the opinion that we do ourselves a disservice when we keep harping on the primary benefit of pre-silicon emulation and schedule saving without giving similar words to the quality improvements in the embedded system (warning messages), deterministic behavior, control-ability, fault injection, ability to pause/resume the stimuli and actuators, deep inspection of the system and regression capabilities.

Now for the shameful plug:

"How to make virtual prototyping better than designing with hardware" by Everett Lumpkin and Casey Alford

Part 1: http://www.embedded-systems.com/design/225701094
Part 2: http://www.embedded-systems.com/design/225701109	            ]]></description>
                <category><![CDATA[TB-Blog]]></category>
                <pubDate>Wed, 08 Sep 2010 01:09:53 -0500</pubDate>
            </item>
	        		    </channel>
</rss>

