<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Tama-Town Tamago Teardown</title>
	<atom:link href="http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/</link>
	<description>Home of Kwartzlab Makerspace in Kitchener/Waterloo, Ontario</description>
	<lastBuildDate>Tue, 21 May 2013 22:45:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: natalies</title>
		<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/comment-page-1/#comment-239</link>
		<dc:creator>natalies</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-239</guid>
		<description><![CDATA[Yeah, another concern is that instruction memory might be ROM under the blob, in which case there&#039;s no wire to tap into. If it&#039;s in the SRAM, then I might be able to lift and dump it or tap the wires.]]></description>
		<content:encoded><![CDATA[<p>Yeah, another concern is that instruction memory might be ROM under the blob, in which case there&#8217;s no wire to tap into. If it&#8217;s in the SRAM, then I might be able to lift and dump it or tap the wires.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jlamothe</title>
		<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/comment-page-1/#comment-240</link>
		<dc:creator>jlamothe</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-240</guid>
		<description><![CDATA[Generally, embedded code tends to go into flash memory as opposed to straight-out ROM.  People who make embedded products like to have a way to reprogram in the event of a problem rather than having to outright replace the chip.

Even if they have no intention of reprogramming after the product is shipped, it&#039;s generally nice to have comparable (if not identical) hardware in the prototype as in the finished product.  Makes the testing process much easier.]]></description>
		<content:encoded><![CDATA[<p>Generally, embedded code tends to go into flash memory as opposed to straight-out ROM.  People who make embedded products like to have a way to reprogram in the event of a problem rather than having to outright replace the chip.</p>
<p>Even if they have no intention of reprogramming after the product is shipped, it&#8217;s generally nice to have comparable (if not identical) hardware in the prototype as in the finished product.  Makes the testing process much easier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeff-o</title>
		<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/comment-page-1/#comment-327</link>
		<dc:creator>jeff-o</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-327</guid>
		<description><![CDATA[Hmmm, time to build one of those open source logic analyzers, I think!]]></description>
		<content:encoded><![CDATA[<p>Hmmm, time to build one of those open source logic analyzers, I think!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/comment-page-1/#comment-330</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-330</guid>
		<description><![CDATA[There are two types of character figures. Type 1: those that are bundled with the Tama-Go, and Type 2: those that are purchased separately. Type 1 does not contain a ROM. The content that&#039;s unlocked by attaching them is actually already in the Tama-Go&#039;s ROM. A Type 1 PCB contains only a few jumpers to inform the Tama-Go which content to unlock.  Type 2 contain a ROM and a few jumpers. Each type 2 ROM contains 3 data areas which allows it to be shared across three Type 2 character figures. Some jumpers on the Type 2 PCB inform the Tama-Go which data area to read from.]]></description>
		<content:encoded><![CDATA[<p>There are two types of character figures. Type 1: those that are bundled with the Tama-Go, and Type 2: those that are purchased separately. Type 1 does not contain a ROM. The content that&#8217;s unlocked by attaching them is actually already in the Tama-Go&#8217;s ROM. A Type 1 PCB contains only a few jumpers to inform the Tama-Go which content to unlock.  Type 2 contain a ROM and a few jumpers. Each type 2 ROM contains 3 data areas which allows it to be shared across three Type 2 character figures. Some jumpers on the Type 2 PCB inform the Tama-Go which data area to read from.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jeff-o</title>
		<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/comment-page-1/#comment-392</link>
		<dc:creator>jeff-o</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-392</guid>
		<description><![CDATA[There&#039;s really no point in removing the epoxy.  Underneath is actually the bare semiconductor die, wire-bonded to the PCB.  There will be no markings or evidence of what chip is actually in there.  The only thing you&#039;ll accomplish is the complete destruction of the brains of the device.]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s really no point in removing the epoxy.  Underneath is actually the bare semiconductor die, wire-bonded to the PCB.  There will be no markings or evidence of what chip is actually in there.  The only thing you&#8217;ll accomplish is the complete destruction of the brains of the device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jlamothe</title>
		<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/comment-page-1/#comment-393</link>
		<dc:creator>jlamothe</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-393</guid>
		<description><![CDATA[I guess the best bet would be to hook some sort of logic analyzer up to the pins on the sides of the board (they look like the means by which the chip is programmed).

Ordinarily, I&#039;d think it&#039;d be near impossible to make any sense of any signals being read from them, but I would have thought the same about reverse-engineering the IR protocol on the previous generation.  I was proven wrong.  :P

The trouble is going to be: unlike the IR protocol, I don&#039;t believe Natalie has the device to which these pins connect.  It&#039;s really hard to reverse-engineer a protocol when you can&#039;t receive input from both ends of the connection.]]></description>
		<content:encoded><![CDATA[<p>I guess the best bet would be to hook some sort of logic analyzer up to the pins on the sides of the board (they look like the means by which the chip is programmed).</p>
<p>Ordinarily, I&#8217;d think it&#8217;d be near impossible to make any sense of any signals being read from them, but I would have thought the same about reverse-engineering the IR protocol on the previous generation.  I was proven wrong.  <img src='http://www.kwartzlab.ca/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>The trouble is going to be: unlike the IR protocol, I don&#8217;t believe Natalie has the device to which these pins connect.  It&#8217;s really hard to reverse-engineer a protocol when you can&#8217;t receive input from both ends of the connection.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jlamothe</title>
		<link>http://www.kwartzlab.ca/2010/11/tama-town-tamago-teardown/comment-page-1/#comment-394</link>
		<dc:creator>jlamothe</dc:creator>
		<pubDate>Wed, 30 Nov -0001 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-394</guid>
		<description><![CDATA[Just to clarify:

I&#039;m talking about the pins on the blue board, not the red one.]]></description>
		<content:encoded><![CDATA[<p>Just to clarify:</p>
<p>I&#8217;m talking about the pins on the blue board, not the red one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
