<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Dual core&#8230; Arduino?</title>
	<atom:link href="http://hackaday.com/2008/04/11/dual-core-arduino/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackaday.com/2008/04/11/dual-core-arduino/</link>
	<description>Fresh hacks every day</description>
	<lastBuildDate>Tue, 24 Nov 2009 12:42:43 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dro kulix</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32924</link>
		<dc:creator>dro kulix</dc:creator>
		<pubDate>Mon, 14 Apr 2008 17:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32924</guid>
		<description>Isn&#039;t a 74HC595 shift register, like, a quarter?&lt;br&gt;&lt;br&gt;Concurrent firmware (on something other than the Propeller) would be interesting, though. :-)</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t a 74HC595 shift register, like, a quarter?</p>
<p>Concurrent firmware (on something other than the Propeller) would be interesting, though. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ric Johnson</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32923</link>
		<dc:creator>Ric Johnson</dc:creator>
		<pubDate>Mon, 14 Apr 2008 16:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32923</guid>
		<description>What about an 8-to-1 multiplexer chip? $1?</description>
		<content:encoded><![CDATA[<p>What about an 8-to-1 multiplexer chip? $1?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mem</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32922</link>
		<dc:creator>mem</dc:creator>
		<pubDate>Sun, 13 Apr 2008 11:10:16 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32922</guid>
		<description>the only real hack in this is the semi clever name.</description>
		<content:encoded><![CDATA[<p>the only real hack in this is the semi clever name.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Takato</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32921</link>
		<dc:creator>Takato</dc:creator>
		<pubDate>Sun, 13 Apr 2008 07:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32921</guid>
		<description>He needs to get a truckload of arduinos (1024 maybe?) and build the computer with the most processers that can still fit in a small bathroom.</description>
		<content:encoded><![CDATA[<p>He needs to get a truckload of arduinos (1024 maybe?) and build the computer with the most processers that can still fit in a small bathroom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DarkLightConnection</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32920</link>
		<dc:creator>DarkLightConnection</dc:creator>
		<pubDate>Sun, 13 Apr 2008 03:13:17 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32920</guid>
		<description>Useful or not, &quot;dual-core arduino&quot; sounds very macho</description>
		<content:encoded><![CDATA[<p>Useful or not, &#8220;dual-core arduino&#8221; sounds very macho</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chupa</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32919</link>
		<dc:creator>chupa</dc:creator>
		<pubDate>Sun, 13 Apr 2008 01:15:15 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32919</guid>
		<description>why?</description>
		<content:encoded><![CDATA[<p>why?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lupin</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32918</link>
		<dc:creator>Lupin</dc:creator>
		<pubDate>Sun, 13 Apr 2008 00:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32918</guid>
		<description>I am surprised this is considered a hack...&lt;br&gt;&lt;br&gt;This is like connecting two lamps in parallel and being surprised that both glow.</description>
		<content:encoded><![CDATA[<p>I am surprised this is considered a hack&#8230;</p>
<p>This is like connecting two lamps in parallel and being surprised that both glow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pc486</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32917</link>
		<dc:creator>pc486</dc:creator>
		<pubDate>Sat, 12 Apr 2008 09:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32917</guid>
		<description>There are plenty of i2c I/O expanders out there that are much cheaper than a full ATMega168. Not nearly as cool though :p.</description>
		<content:encoded><![CDATA[<p>There are plenty of i2c I/O expanders out there that are much cheaper than a full ATMega168. Not nearly as cool though :p.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: morcheeba</title>
		<link>http://hackaday.com/2008/04/11/dual-core-arduino/comment-page-1/#comment-32916</link>
		<dc:creator>morcheeba</dc:creator>
		<pubDate>Sat, 12 Apr 2008 08:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.iheartcashews.com:8181/2008/04/11/dual-core-arduino/#comment-32916</guid>
		<description>He wired the chips in parallel - this doesn&#039;t seem to be a good idea.  Resonators are usually driven by a not gate - one pin is an input, the other is an output. It&#039;s wired so that the two outputs are driving each other -- bad practice!  This will waste energy and stress the parts.  It&#039;ll also create a lot of electrical noise as the power supply is repeatedly asked to supply the short circuit current every oscillation.&lt;br&gt;&lt;br&gt;The better solution is a master/slave setup.  One device will control the oscillator (connect XTAL1 and XTAL2 as usual) - this is the master. The other device is set up in &quot;external oscillator&quot; mode, with its input driven from the first.  I looked at the spec sheet quickly, and it looks like XTAL2 is the output and XTAL1 is the input - this means you should connect XTAL2 of the master to XTAL1 of the slave. (you can verify this with an oscilliscope - the output waveform should be the squarer one)&lt;br&gt;---&lt;br&gt;On another note, I&#039;ve thought it would be fun to take a 10 x 10 array of these tiny 100 MHz processors and make a 10GHz-equivalent computer on a 4x4&quot; pc board:&lt;br&gt;&lt;br&gt;&lt;a href=&quot;http://www.silabs.com/public/documents/tpub_doc/dshort/microcontrollers/small_form_factor/en/c8051f365_short.pdf&quot; rel=&quot;nofollow&quot;&gt;http://www.silabs.com/public/documents/tpub_doc/dshort/microcontrollers/small_form_factor/en/c8051f365_short.pdf&lt;/a&gt;&lt;br&gt;&lt;br&gt;but, with limited communication, it could only run certain apps well.</description>
		<content:encoded><![CDATA[<p>He wired the chips in parallel &#8211; this doesn&#8217;t seem to be a good idea.  Resonators are usually driven by a not gate &#8211; one pin is an input, the other is an output. It&#8217;s wired so that the two outputs are driving each other &#8212; bad practice!  This will waste energy and stress the parts.  It&#8217;ll also create a lot of electrical noise as the power supply is repeatedly asked to supply the short circuit current every oscillation.</p>
<p>The better solution is a master/slave setup.  One device will control the oscillator (connect XTAL1 and XTAL2 as usual) &#8211; this is the master. The other device is set up in &#8220;external oscillator&#8221; mode, with its input driven from the first.  I looked at the spec sheet quickly, and it looks like XTAL2 is the output and XTAL1 is the input &#8211; this means you should connect XTAL2 of the master to XTAL1 of the slave. (you can verify this with an oscilliscope &#8211; the output waveform should be the squarer one)<br />&#8212;<br />On another note, I&#8217;ve thought it would be fun to take a 10 x 10 array of these tiny 100 MHz processors and make a 10GHz-equivalent computer on a 4&#215;4&#8243; pc board:</p>
<p><a href="http://www.silabs.com/public/documents/tpub_doc/dshort/microcontrollers/small_form_factor/en/c8051f365_short.pdf" rel="nofollow">http://www.silabs.com/public/documents/tpub_doc/dshort/microcontrollers/small_form_factor/en/c8051f365_short.pdf</a></p>
<p>but, with limited communication, it could only run certain apps well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
