Configuration error

[mackrackit]

Below the message box when you reply there is a "manage attachment" button.

[Darrel Taylor]

Sounds like a programming cable problem.

If you have nothing connected to the programmer, and try to read back a 12F675, it'll show these configs.

Oscillator      LP
Watchdog timer  Disabled
Powerup timer   Enabled
MCLR Pin        Input Pin
Brown out       Disabled
Code protect    Protected
Data EEPROM     Protected

And it'll show all 0000's in the code window.

Check the connections again, especially at the 10-pin connector on the programmer.
Make sure the connector is alligned correctly.
<br>

[Russ Kincaid]

Thanks, Darryl but the connector has not been messed with and it worked OK before. The read does read the hex file that was loaded.

[Darrel Taylor]

OK, if it reads the memory then it wasn't the cable.

I am using melabs programmer version 4.01 ...

You might try the latest version of meProg which is up to version 4.31 now.

The beta can be downloaded here ...
http://www.melabs.com/support/progsoft.htm

hth,

[Russ Kincaid]

I did download the beta programmer and tried to program a 12F675 that had already been successfully programmed. First I read the memory; it was 3FFF in all locations. That was not correct but I tried to program it anyway. The process went smoothly and verified OK. I then read the memory; it was 3FFF all over. I clicked on the verify icon; it reports an error. Is this another IC for the dust bin?

[be80be]

I did download the beta programmer and tried to program a 12F675 that had already been successfully programmed. First I read the memory; it was 3FFF in all locations. That was not correct but I tried to program it anyway. The process went smoothly and verified OK. I then read the memory; it was 3FFF all over. I clicked on the verify icon; it reports an error. Is this another IC for the dust bin?

You can erase them don't throw them away all you have to do is open the pickit2 software and turn code protect off and then erase the chip.

The best way to do it is place the 12f675 in a solderless bread board fire up the pickit2 and reset code protect.

If it don't let you put a new chip in first let the pickit2 detect it then remove it and place you locked chip in then unlock and erase

You don't have microcode set for the right chip is why this is happen. What happen to me is that it set for default which is 16f628 and I changed it to the 12f675 before I compiled it still built for the 16f628
I then ended with a locked chip I then clean out the folder and started over saved the project as 12f675 from the start and it worked fine

[mackrackit]

be80be,
If the OP was using a PicKit2 ...
To bad he is not.

[Darrel Taylor]

... and tried to program a 12F675 that had already been successfully programmed. ...

Curious ...

Do you know if the program that was already loaded in it was using the Internal Oscillator with MCLR disabled?

I've had some difficult times trying to reprogram 675's and F88's after that scenario.
But I was able to get them back by turning on power to the chip at just the right time in the programming sequence. Took 10-15 or more tries each, but did get them all back.
<br>

[be80be]

Curious ...

Do you know if the program that was already loaded in it was using the Internal Oscillator with MCLR disabled?

I've had some difficult times trying to reprogram 675's and F88's after that scenario.
But I was able to get them back by turning on power to the chip at just the right time in the programming sequence. Took 10-15 or more tries each, but did get them all back.
<br>

The only chips i have had problems with has been 12f675 16f88 and 18f1320
what happens on the 16f88 and 18f1320 is you set the configure for ex-osc
and have none