Programming verification error

[bill53]

Hi All, I'm writing code for the PIC12F1572.
I'm using PCWDH version 5.080.
Using the ICD-U64 Rev 3, Software 5.064, Firmware 3.45.

I've been writing and debugging code for the last couple of days making changes and writing new hex files to this PIC chip with no problem. Now however, I am unable to write any code to the PIC chip without getting a verification error. I've created a new project for the 12F1572 using the blink LED code which compiles without error however when I try to load this I get the verification error. I've tried a new PIC chip still with the same result.

I've tested MCLR, PGD, and PGC all are working as expected.
The U64 returns the correct target ID.
I've rebooted my PC and restarted PCWDH.

I'm stumped.

Cheers Bill

PS Wishing you all a merry Xmas and a safe new year.

[temtronic]

OK.....
1) can you load and run a previously WORKING program ??

2) did you 'update' ANYTHING ??

3) did anything 'update' itself without you knowing ??

4) is the new program compiled as 'release' and not 'debug' ?

I don't use the U64 but I use MPLAB to access the PICKit3 to program the PIC. By default, MPLAB was set to 'debug'.grr. has to be 'release' THEN compile THEN PIC actually gets programmed !

Since you can communicate to the U64, probably not Windoze.....

Can you read a PIC ??

[Ttelmah]

It could just simply be the chip has failed. They do have a limited life for
writing. It is only 10K cycles. So though it would take a long time normally
to get to this however, if you do anything like write to the program memory
in the code, you could use up the lives very quickly....

[newguy]

I've seen similar - a full erase of the target then a fresh write usually clears the error for me.

[Ttelmah]

Yes, there are a number of settings that can only be cleared by a full erase.
Sometimes the 'automatic erase' won't handle these, so manually doing a full
erase is well worthwhile.

[bill53]

Thanks everyone.

I was not able to successfully erase these chips using the CCSLoader tool?

I downloaded MPLAB to get access to the IPE. Using the Microchip IPE I was able to successfully load my hex files onto the PIC12F1572 chips I had been using. I used the Microchip IPE to erase all the chips and went back to the CCS IDE and was once again able to use the ICD-64U to write my hex file to these chips and use the monitor in a debugging cycle.

So problem avoided for now. But I do not think it is sorted? Thanks again.

Cheers Bill

[bill53]

PS I used the Microchip PICkit 3 to connect to the micro.

[Ttelmah]

There are a number of issues with the PK3 and this chip. It varies
according to the firmware version in the PK3.
Go back to MPLAB, and make it ask to upgrade the PK3 firmware
to the latest version.

[temtronic]

hmm..wonder if that's the one that you can't have 'NOMCLR' to free up a pin ? I 'know' there's one that doesn't 'play nice' with my PK3....

[bill53]

Sorry my last post may have been confusing.

I use the PICkit 3 with Microchips IPE to program the 12F1572 with success. I was able to program with the fuses NOMCLR and MCLR both seem to work as expected. I used the PICkit 3 with the IPE to successfully erase these chips and was then able to use the CCS ICD-U64 to program and use the ICD monitor.

When the problem as outlined in my first post occurred I had not changed anything except for the C code I am debugging. It just happened that I could no longer load code without getting a verification error. I changed to a new chip with the same result. I created another small project still with the same result. However, I was able to load the same unaltered hex file using the IPE and the PICkit 3.

It seems to me that the CCS ICD monitor process is a bit fragile. I have to kill the monitor process before attempting to load a new hex file otherwise it seems to hang the monitor. Is that common thing or is just my setup ? The problem is sorted for now. Cheers everyone.

[Ttelmah]

You do realise, that if you have this:

https://www.ccsinfo.com/downloads.php

Last item in the MPLAB plug ins.

It allows you to use the MicroChip programmer from the CCS IDE.

The same comment on firmware definitely applies to the ICD-U64, there
have been several firmware updates to this over the last few months,
and particular combinations of the software and firmware, do not work
correctly.

[bill53]

Hi Ttelmah, No I had not noted that plug-in I will give that a go. Thanks.

The CCSLoad reports that I have the latest firmware and software installed. Although, I note report of a new hardware mode for my U64.

Cheers Bill