Neil narwani.org> writes: >=20 > Bump. >=20 > On 8/10/2014 5:12 PM, Neil wrote: > > Hi all, > > > > Getting back into PIC dev recently, and I've run into a > > somewhat-familiar EEPROM issue. I'm preloading a PIC18F46K22 with 400+ > > bytes of data and it works fine initially, but after some time (with no > > EEPROM writes from the code) the data is getting corrupted. Swapped th= e > > chip and same issue. Without any writes, it seems it's not the old > > wear-leveling issue with writing to some cells possibly degrading or > > corrupting other cells. The only thing that happened from working to > > non-working is that power was cycled several times. > > > > I do have brown-out reset enabled (at 2.85V), so I don't think it's tha= t. Do you have the BOREN config bits set so that the BOR can't be over-ridden by software? Do you also have the power-up timer enabled? =20 Since you aren't writing anything, do you keep the WREN bit clear at all ti= mes? Some of the older AVR devices were a prone to EEPROM corruption during powe= r cycles. On a project I worked on some years ago I reserved EEPROM address 0x0000 and made sure the address registers were always set back to 0x0000 after any access which seemed to greatly reduce the chance of corruption occurring. Mike --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .