16f883

[hatchethand1000]

I am using this line with the 16F883 with no other @ DEFINE lines or anything else, jus the one line.

@ __config _CONFIG1, _INTRC_OSC_NOCLKOUT & _WDT_ON & _MCLRE_ON & _LVP_OFF & _CP_ON & _CPD_ON

and I modified the file C:\PBP\16F883.INC

;****************************************************************
;*  16F883.INC                                                  *
;*                                                              *
;*  By        : Leonard Zerman, Jeff Schmoyer                   *
;*  Notice    : Copyright (c) 2009 microEngineering Labs, Inc.  *
;*              All Rights Reserved                             *
;*  Date      : 07/02/09                                        *
;*  Version   : 2.60                                            *
;*  Notes     :                                                 *
;****************************************************************
        NOLIST
    ifdef PM_USED
        LIST
        include 'M16F88x.INC'	; PM header
        device  pic16F883, intrc_osc_noclkout, wdt_on, mclr_on, lvp_off, protect_off
        XALL
        NOLIST
    else
        LIST
        LIST p = 16F883, r = dec, w = -302
        INCLUDE "P16F883.INC"	; MPASM  Header
;       __config _CONFIG1, _INTRC_OSC_NOCLKOUT & _WDT_ON & _MCLRE_ON & _LVP_OFF & _CP_OFF
        NOLIST
    endif
        LIST

Comment out the __config line and save the file.
This works good for me.
K

[Meriachee]

Absolutely, almost fabulous.

Everything works, up to the verify stage of the programmer without so much as a burp, but then:

Code verify error at 0000
3FFF should be 2828

and on and on it goes 3FFF at 0001, 3FFF at 0002 etc etc.
Erasing the target doesn't clear it.

[hatchethand1000]

Absolutely, almost fabulous.

Everything works, up to the verify stage of the programmer without so much as a burp, but then:

Code verify error at 0000
3FFF should be 2828

and on and on it goes 3FFF at 0001, 3FFF at 0002 etc etc.
Erasing the target doesn't clear it.

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

[Meriachee]

Reset it a couple of times, and same issue. I am going to contact MeLabs over this one....

[Meriachee]

Once again Charles comes through. It was the U2 programmer, indirectly. MeLabs updated the programmer code after the 883 chip was released. When the programmer was up-issued to 4.31 from 4.20 it worked exactly as it should. The firmware is current at #56.

Thanks all for the help!

Gary