Question: Anyone worked with a PIC12CE674 at low Xtal speed (32.768kHz--less current consumption) and tried to implement the onboard EEPROM? My part keeps resetting when the write_byte or read_byte is CALLed. I also #include and commented the #define FOURMHZ and #define TENMHZ. 32.768kHz is plenty slow for the EEPROM to work. Situation: I have developed a neat little circuit for the company I work for. I took a tip from one of the Stampers and used a BasicStamp BSII and external A/D (DS ADC0831) to verify the hardware. So I thinking, just bounce the code to a PIC and I'm done. Apparently, the on-chip I2C EEPROM function is not working. Two FAEs and Microchip's Technical Support cannot figure it out. I am working w/ very low current consumption restrictions (500uA or less). What I have done to conserve power is exploit some not-so-well know tricks w/ PIC. For example, the PIC12CE674 has WDT wakeup from SLEEP and WDT reset. So, you can use the WDT as a timer to wake up from SLEEP without resetting the part. So you can perform timing from 18mS up to 2300mS drawing only 5.5uA w/ WDT enabled! Then it executes the next instruction (PC+1=>PC). It works with everything I have done with this part. Well, to make a long story short, I have proven to the FAEs and Microchip's Technical Support that the WDT itself is not the problem, it is something to do w/ the EEPROM at low speed or the I2C Protocol in the EEPROM file you have to #include to your code to use the write_byte or read_byte functions. The WDT does reset the part AFTER the EEPROM fails to read/write in less than 18mS to 2300mS (depending on the postscaler value). -- Jason ======================================== E-Mail: milsumai@execpc.com ICQ # : 12978762 ======================================== .:::. ,,, _(- -)_ / ( ) \ \_/ : \_/ |_/ \_| | | | -TRY PRAYER-