Programming Failed.

For questions and comments on programming in general. And for any items that don't fit into the forums below.

Moderators: Benj, Mods

Post Reply
KeithSloan
Posts: 114
Joined: Fri Jul 27, 2007 10:50 am
Been thanked: 1 time

Programming Failed.

Post by KeithSloan »

When trying to Program a 16F84A I get an error message

Programming Failed

Data memory check failed.

(Note if the PIC is memory protected this message will be displayed even if the program has been sent successfully.

Have I run out of memory ?

Is my PIC damaged ?

Thanks Keith

User avatar
Steve
Matrix Staff
Posts: 3433
Joined: Tue Jan 03, 2006 3:59 pm
Has thanked: 114 times
Been thanked: 422 times

Post by Steve »

Hello Keith,

It could be that you have the "code protect" option enabled in the configuration word. If your program seems to run fine, then I would suspect this.

Although it could be a broken chip. Do you get the same message when programming other chips (if you have any)?

KeithSloan
Posts: 114
Joined: Fri Jul 27, 2007 10:50 am
Been thanked: 1 time

Programmin Error

Post by KeithSloan »

The 16F84A programs fine with other programs.

I don't have another chip to try.

The program was written for a 16F84 and uses internal EEPROM could this be the problem.

I tried removing Config statement and just controlling by PPP but still the same problem with CONFIG is set to 0x3FF9 which also what PPP advises.

User avatar
Steve
Matrix Staff
Posts: 3433
Joined: Tue Jan 03, 2006 3:59 pm
Has thanked: 114 times
Been thanked: 422 times

Post by Steve »

Please send the program (HEX and source) to Ben (support@matrixmultimedia.co.uk) and he'll try it here.

KeithSloan
Posts: 114
Joined: Fri Jul 27, 2007 10:50 am
Been thanked: 1 time

Works okay with a 16F88

Post by KeithSloan »

Okay I tried it with a 16F88 that I have and it works fine. So I assume I must have a duff chip.

Gnu
Posts: 20
Joined: Mon Apr 16, 2007 6:59 pm
Location: UK
Contact:

Post by Gnu »

I've had the same error message when compiling a program to a PIC16F88 which had definitely not been code-protected. In spite of the warning, I found that the program had been correctly compiled into the chip. In the same program I was having problems with an LCD displaying random gibberish and so changed the clocking from internal 32KHz to crystal 20MHz. This cured the LCD problem and also, inexplicably, cleared the compiler error message.

Post Reply