<?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: The S4D Debug Conference</title>
	<atom:link href="http://jakob.engbloms.se/archives/942/feed" rel="self" type="application/rss+xml" />
	<link>http://jakob.engbloms.se/archives/942?&#038;owa_medium=feed&#038;owa_sid=</link>
	<description>Computer Technology: Simulation, Virtualization, Virtual Platforms, Embedded, Multicore and Multiprocessing (by Jakob Engblom)</description>
	<lastBuildDate>Thu, 12 Jan 2012 21:54:16 -0800</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jakob</title>
		<link>http://jakob.engbloms.se/archives/942/comment-page-1#comment-2555</link>
		<dc:creator>Jakob</dc:creator>
		<pubDate>Wed, 14 Oct 2009 04:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://jakob.engbloms.se/?p=942#comment-2555</guid>
		<description>You are right. You did talk about greater-than-SoC debug. The main issue with the hardware-synchronized approach is that you need a system small enough in physical size that you can keep it synchronized.  But in essence, you are chasing the right thing: debug across multiple SoC, using extended on-chip logic that lets you do synchronized commands across the entire set.</description>
		<content:encoded><![CDATA[<p>You are right. You did talk about greater-than-SoC debug. The main issue with the hardware-synchronized approach is that you need a system small enough in physical size that you can keep it synchronized.  But in essence, you are chasing the right thing: debug across multiple SoC, using extended on-chip logic that lets you do synchronized commands across the entire set.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roland Höller</title>
		<link>http://jakob.engbloms.se/archives/942/comment-page-1#comment-2554</link>
		<dc:creator>Roland Höller</dc:creator>
		<pubDate>Tue, 13 Oct 2009 14:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://jakob.engbloms.se/?p=942#comment-2554</guid>
		<description>Hi!

I just wanted to add a comment on your statemant that &quot;system-level debug was not in any talk&quot;. Unfortunately you seem to have missed my talk on the second day, where I presented our approach to coordinate debug and test activities of a multitude of nodes of a distributed system. The approach is based on precisely synchronized time-of-day clocks used to trigger debug and test action, operating with little hardware overhead in the CPU chips.

I add a link to one of our project websites in case a reader is interested in some more information: http://embsys.technikum-wien.at/projects/coordes/index.html

Best regards,

Roland Höller</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>I just wanted to add a comment on your statemant that &#8220;system-level debug was not in any talk&#8221;. Unfortunately you seem to have missed my talk on the second day, where I presented our approach to coordinate debug and test activities of a multitude of nodes of a distributed system. The approach is based on precisely synchronized time-of-day clocks used to trigger debug and test action, operating with little hardware overhead in the CPU chips.</p>
<p>I add a link to one of our project websites in case a reader is interested in some more information: <a href="http://embsys.technikum-wien.at/projects/coordes/index.html" rel="nofollow">http://embsys.technikum-wien.at/projects/coordes/index.html</a></p>
<p>Best regards,</p>
<p>Roland Höller</p>
]]></content:encoded>
	</item>
</channel>
</rss>

