Ok, about the device i am using itīs PIC16F628A.
And i DO am using the MCLR pin as input, might that be any reason?.
By the way Melanie, why would doing CRC help any good? i would still have to reconfigure the device and this is really BAD!!!
Now i donīt know if the discussion should be open here but.. this error seems to be of the device, else microchips. Does this happen to the uC`s of other companies like ATMEL or MOTO? You guys know that none cares if itīs the device, ultimately it`s the designers fault!. If this keeps happening to me i would have to change to other brands to avoid such bothers! Wouldnīt you? We need faultyless bases to develop our devices donīt we?
I still hope this can be fixed, could some other configuration help me avoid the problem? i don`t have any extra memory outside the device and if for some reason is a stack problem i am not using any gosub... just GOTO sentences in my program.
What could be worst is that the number donīt just gets erased to FF or 00 but takes any random number wich means a different configuration for the firmware.
Could a Voltage peak at startup be the reason? i donīt get how programming works or even how LVP works (628 doesnīt have this does it?)
I will try this, maybe store the same data (itīs just one byte) in two or three different places of the memory and handle differently if they donīt match.
Thanks for your replies.
DJC
Bookmarks