<?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: Parts: SPI EEPROM (25AA/25LC)</title>
	<atom:link href="http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/</link>
	<description>Fresh hacks every day</description>
	<lastBuildDate>Fri, 10 Feb 2012 18:02:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ian Lesnet</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-80099</link>
		<dc:creator><![CDATA[Ian Lesnet]]></dc:creator>
		<pubDate>Thu, 02 Jul 2009 18:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-80099</guid>
		<description><![CDATA[We used XON/XOFF software flow control with a &#039;dribble&#039; buffer in the &lt;a href=&quot;http://code.google.com/p/the-bus-pirate/source/browse/v0g/source/jtag/ports.c#76&quot; rel=&quot;nofollow&quot;&gt;JTAG programmer code&lt;/a&gt;.]]></description>
		<content:encoded><![CDATA[<p>We used XON/XOFF software flow control with a &#8216;dribble&#8217; buffer in the <a href="http://code.google.com/p/the-bus-pirate/source/browse/v0g/source/jtag/ports.c#76" rel="nofollow">JTAG programmer code</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-80096</link>
		<dc:creator><![CDATA[Todd]]></dc:creator>
		<pubDate>Thu, 02 Jul 2009 17:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-80096</guid>
		<description><![CDATA[@killerspud - You would need to stream the file to your microcontroller, using a receive buffer to hold the incoming data while you write it to the eeprom.  

Think of it like a sink.  The faucet is the PC sending the file to the microcontroller.  The basin is the buffer. The drain would then be the eeprom.  If the faucet/PC pours water/data in to the basin/buffer faster than the drain/eeprom takes it out, the basin/buffer will over flow, and some of the water/data wont make it to the drain/eeprom.

Just make the PC send the data slower than the micro can write to the eeprom.]]></description>
		<content:encoded><![CDATA[<p>@killerspud &#8211; You would need to stream the file to your microcontroller, using a receive buffer to hold the incoming data while you write it to the eeprom.  </p>
<p>Think of it like a sink.  The faucet is the PC sending the file to the microcontroller.  The basin is the buffer. The drain would then be the eeprom.  If the faucet/PC pours water/data in to the basin/buffer faster than the drain/eeprom takes it out, the basin/buffer will over flow, and some of the water/data wont make it to the drain/eeprom.</p>
<p>Just make the PC send the data slower than the micro can write to the eeprom.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Lesnet</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-79901</link>
		<dc:creator><![CDATA[Ian Lesnet]]></dc:creator>
		<pubDate>Wed, 01 Jul 2009 06:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-79901</guid>
		<description><![CDATA[@matt - Fantastic idea, we&#039;ll find some BIOS chips to play with.

@gcl - Yup, Maxim makes an I2C-&gt;1-wire converter chip, and other adapters. 1-wire, I2C, and other buses are common inside a PC. 1-wire parts are often used for their unique 64bit serial number. 

I&#039;m not sure of many places where you can get those signals outside of the PC without some sort of external bus adapter. I know there&#039;s an I2C connection for DDC in DVI connectors and some VGA cards.

@killerspud - EEPROM programming from a file is on our development roadmap. It&#039;s a needed feature. We&#039;ll just recycle the code we used for the JTAG XSVF uploader.]]></description>
		<content:encoded><![CDATA[<p>@matt &#8211; Fantastic idea, we&#8217;ll find some BIOS chips to play with.</p>
<p>@gcl &#8211; Yup, Maxim makes an I2C-&gt;1-wire converter chip, and other adapters. 1-wire, I2C, and other buses are common inside a PC. 1-wire parts are often used for their unique 64bit serial number. </p>
<p>I&#8217;m not sure of many places where you can get those signals outside of the PC without some sort of external bus adapter. I know there&#8217;s an I2C connection for DDC in DVI connectors and some VGA cards.</p>
<p>@killerspud &#8211; EEPROM programming from a file is on our development roadmap. It&#8217;s a needed feature. We&#8217;ll just recycle the code we used for the JTAG XSVF uploader.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KillerSpud</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-79895</link>
		<dc:creator><![CDATA[KillerSpud]]></dc:creator>
		<pubDate>Wed, 01 Jul 2009 04:32:07 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-79895</guid>
		<description><![CDATA[Are there any provisions for uploading files to EEPROMs?  A common reason to use these memory chips is when your uC&#039;s onboard memory can&#039;t handle what you want it to do (I.E. sound or picture files).  But then you run into the problem of how to get your files onto that chip, so you have to invest either time or money in a separate device just to burn your memory.

I personally don&#039;t know a thing about common file transfer protocols (xmodem, kermit, etc.) so I don&#039;t know what to do (and I&#039;ve got a pile of other projects to work on).]]></description>
		<content:encoded><![CDATA[<p>Are there any provisions for uploading files to EEPROMs?  A common reason to use these memory chips is when your uC&#8217;s onboard memory can&#8217;t handle what you want it to do (I.E. sound or picture files).  But then you run into the problem of how to get your files onto that chip, so you have to invest either time or money in a separate device just to burn your memory.</p>
<p>I personally don&#8217;t know a thing about common file transfer protocols (xmodem, kermit, etc.) so I don&#8217;t know what to do (and I&#8217;ve got a pile of other projects to work on).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gcl</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-79872</link>
		<dc:creator><![CDATA[gcl]]></dc:creator>
		<pubDate>Wed, 01 Jul 2009 00:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-79872</guid>
		<description><![CDATA[Okay, I believe Maxim makes hardware that translates from one protocol to the other.

Incidentally the One-Wire one is actively developed for by Linux users, including myself.]]></description>
		<content:encoded><![CDATA[<p>Okay, I believe Maxim makes hardware that translates from one protocol to the other.</p>
<p>Incidentally the One-Wire one is actively developed for by Linux users, including myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-79859</link>
		<dc:creator><![CDATA[Matt]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 22:27:29 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-79859</guid>
		<description><![CDATA[What about using this with the SPI parts used for BIOS? It could be useful in un-bricking mainboards with a bad flash.]]></description>
		<content:encoded><![CDATA[<p>What about using this with the SPI parts used for BIOS? It could be useful in un-bricking mainboards with a bad flash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Lesnet</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-79846</link>
		<dc:creator><![CDATA[Ian Lesnet]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 20:48:58 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-79846</guid>
		<description><![CDATA[The &#039;3EEPROM&#039; test board in the picture has a 1-wire EEPROM, I2C EEPROM, and SPI EEPROM. We use it to test these protocol libraries before releasing new firmware.]]></description>
		<content:encoded><![CDATA[<p>The &#8217;3EEPROM&#8217; test board in the picture has a 1-wire EEPROM, I2C EEPROM, and SPI EEPROM. We use it to test these protocol libraries before releasing new firmware.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: luke</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-79835</link>
		<dc:creator><![CDATA[luke]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 19:33:24 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-79835</guid>
		<description><![CDATA[Is there a good site or book out there that can help me start to understand electronics? I have played with them ever since I was a kid and I would like to know more. Where do I begin?]]></description>
		<content:encoded><![CDATA[<p>Is there a good site or book out there that can help me start to understand electronics? I have played with them ever since I was a kid and I would like to know more. Where do I begin?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark barnes</title>
		<link>http://hackaday.com/2009/06/30/parts-spi-eeprom-25aa25lc/comment-page-1/#comment-79830</link>
		<dc:creator><![CDATA[Mark barnes]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 19:10:12 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=10553#comment-79830</guid>
		<description><![CDATA[hackaday have bus pirates on the brain??]]></description>
		<content:encoded><![CDATA[<p>hackaday have bus pirates on the brain??</p>
]]></content:encoded>
	</item>
</channel>
</rss>

