I have had the same type of problems with the MElabs U2 programmer. The only way I could fix it was to reload the defaults to the programmer.
meProg - Options - More Options - Set Options to Default
I have not had this problem with other chips but the 16F883 seems to do it late and night or early in the morning. I went so far as to think my programmer was either out of date or broken. I purchased a new one with updated code and it did the same thing. Restoring defaults does seem to fix the strange errors with the U2.
K
Bookmarks