<?xml version="1.0" ?>
<rss version="2.0">
<channel>
<title>Designer III Blog, avr eeprom</title>
<description>avr eeprom, Designer III Blog most recent posts</description>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
<link>http://blog.designer-iii.com/avr_eeprom</link>
<language>en</language>
<category></category>
<pubDate>Mon, 12 Jan 2009 01:08:02 GMT</pubDate>
<ttl>200</ttl>

<item>
<title>Why are some address of the AVR EEPROM corrupted Usually address zero. (avr eeprom)</title>
<description>Posted by Bob Paddock: (avr eeprom) Recent AVR-LibC FAQ submission of mine: Why are some address of the AVR EEPROM corrupted Usually address zero. The two most common reason for EEPROM corruption is either writing to the EEPROM beyond the datasheet endurance specification, or resetting the AVR while a EEPROM write is in progress. EEPROM writes can take up to tens of&lt;br&gt;Tags: &lt;b&gt;avr eeprom&lt;/b&gt;, &lt;b&gt;eeprom endurance&lt;/b&gt;. Comments: 0.</description>
<link>http://blog.designer-iii.com/avr_eeprom/20090111-20082-Why-are-some-address-of-the-AVR-EEPROM-corrupted--Usually-address-zero</link>
<guid isPermaLink="false">http://blog.designer-iii.com/avr_eeprom/20090111-20082-Why-are-some-address-of-the-AVR-EEPROM-corrupted--Usually-address-zero</guid>
</item>


</channel>
</rss>

