<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>picmicrodevelopersforum at Yahoo! Groups</title>
    <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/</link>
    <description>PIC Micro Developers&#39; Forum - Microchip PIC Microcontrollers Discussion Forum</description>

    <item>
      <title>Re: EEPROM Update</title>
      <pubDate>Tue, 29 Dec 2009 13:38:33 GMT</pubDate>
      <dc:creator>Fournier, Pete</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1861</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1861</guid>
      <description>I once had (probably still have) an issue with a 16 bit write to an eeprom.  If the low byte/high byte crossed an 8 bit address location (ie one byte in 0xbf</description>
    </item>
    <item>
      <title>Re: EEPROM Update</title>
      <pubDate>Sun, 27 Dec 2009 12:46:45 GMT</pubDate>
      <dc:creator>Ian</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1860</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1860</guid>
      <description>Seems to me there is something in the state after the call that is causing the problem or conversely something you assume about the state at the beginning of</description>
    </item>
    <item>
      <title>Re: EEPROM Update</title>
      <pubDate>Sun, 27 Dec 2009 09:42:37 GMT</pubDate>
      <dc:creator>Kevin</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1859</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1859</guid>
      <description>Hi Mike, My &quot;2 pence&quot; (2 cents?) worth on the subject is .... whenever I&#39;ve had EEPROM problems it usually turned out to be BANK errors, e.g. I&#39;ve changed BANK</description>
    </item>
    <item>
      <title>EEPROM Update</title>
      <pubDate>Sat, 26 Dec 2009 20:32:58 GMT</pubDate>
      <dc:creator>Mike</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1858</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1858</guid>
      <description>I wanted to bring everyone up to date on my ongoing saga with EEPROM in a 16F627A. I thought I had it working, but quickly discovered that THE ORDER OF</description>
    </item>
    <item>
      <title>Re: Problem with EEPROM data not surviving power-cycle</title>
      <pubDate>Tue, 22 Dec 2009 17:42:05 GMT</pubDate>
      <dc:creator>Mike Dodd</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1857</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1857</guid>
      <description>Jonathan wrote:&gt; Mike, ... I got it working. I made a new source code file that does nothing but read the pushbutton and write/read the EEPROM. I did find the</description>
    </item>
    <item>
      <title>Re: Problem with EEPROM data not surviving power-cycle</title>
      <pubDate>Tue, 22 Dec 2009 16:17:09 GMT</pubDate>
      <dc:creator>Jonathan</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1856</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1856</guid>
      <description>Mike, I didn&#39;t see any problems in the EEPROM read and write routines, but I did spot a few things, below... Merry Christmas, Jonathan ... </description>
    </item>
    <item>
      <title>Re: Problem with EEPROM data not surviving power-cycle</title>
      <pubDate>Mon, 21 Dec 2009 21:24:19 GMT</pubDate>
      <dc:creator>Mike Dodd</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1855</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1855</guid>
      <description>... Thanks for the suggestion. I modified my code to write to two EEPROM locations. Now it appears that the EEPROM is not being written, and is returning</description>
    </item>
    <item>
      <title>Re: Problem with EEPROM data not surviving power-cycle</title>
      <pubDate>Mon, 21 Dec 2009 13:08:44 GMT</pubDate>
      <dc:creator>bergweed</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1854</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1854</guid>
      <description>My guess is the EEMEM isn&#39;t really being written to and you are just reading back the contents of the EEDATA register containing what was supposed to be</description>
    </item>
    <item>
      <title>Re: indetifying speed of a 16f688a</title>
      <pubDate>Sun, 20 Dec 2009 18:38:35 GMT</pubDate>
      <dc:creator>orwill@...</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1853</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1853</guid>
      <description>You can get the data sheet from the microchip website. The oscillator will operate up to 20 mhz. The instruction cycle is 1/4 of that so the instruction cycle</description>
    </item>
    <item>
      <title>indetifying speed of a 16f688a</title>
      <pubDate>Sun, 20 Dec 2009 18:03:35 GMT</pubDate>
      <dc:creator>Willem</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1852</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1852</guid>
      <description>Hello everybody, How can i find whit speed a 16F688 is i can&#39;t find anything on the PIC but like to know if it is a 4 or 20 MHz. thanks Willem</description>
    </item>
    <item>
      <title>Problem with EEPROM data not surviving power-cycle</title>
      <pubDate>Sun, 20 Dec 2009 03:35:05 GMT</pubDate>
      <dc:creator>Mike</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1851</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1851</guid>
      <description>I&#39;m having a major problem with 16F627A EEPROM. I can write data to a location in EEPROM, and read it back okay, but if I subsequently turn off the power</description>
    </item>
    <item>
      <title>Re: EEPROM question</title>
      <pubDate>Sat, 14 Nov 2009 02:31:40 GMT</pubDate>
      <dc:creator>bergweed</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1848</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1848</guid>
      <description>Mike, Here&#39;s my 16F627/8 asm sub to read and write the EEMEM. the address goes in variable ee_addr and the data comes/goes in ee_data. If you aren&#39;t using</description>
    </item>
    <item>
      <title>EEPROM question</title>
      <pubDate>Thu, 12 Nov 2009 21:19:32 GMT</pubDate>
      <dc:creator>jonw0224@...</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1847</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1847</guid>
      <description>Mike, Here is code I&#39;ve tested on a 16F84(A) and 16F877(A). variable CURRENTBANK CURRENTBANK set 0x0000 ;*Sets the STATUS bits RP0 and RP1 correctly depending</description>
    </item>
    <item>
      <title>Re: EEPROM question</title>
      <pubDate>Thu, 12 Nov 2009 19:41:11 GMT</pubDate>
      <dc:creator>Mike Dodd</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1846</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1846</guid>
      <description>... Thanks. The only significant difference between your routine and mine is that yours checks at the start for the previous write complete, and mine does this</description>
    </item>
    <item>
      <title>Re: EEPROM question</title>
      <pubDate>Thu, 12 Nov 2009 03:52:06 GMT</pubDate>
      <dc:creator>orwill@...</dc:creator>
      <link>http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1845</link>
      <guid isPermaLink="true">http://tech.groups.yahoo.com/group/picmicrodevelopersforum/message/1845</guid>
      <description>Hi Mike, This is one of my write subroutines for a PIC 18FXXX device. I think its similar maybe the movf instruction is different anyway this works perfectly</description>
    </item>

  </channel>
</rss>
<!-- wr2.grp.sp2.yahoo.com uncompressed/chunked Sun Feb 14 12:00:41 PST 2010 -->
