ccsload: code not protected problem.

[jai]

Hi all,

I am programming the 16F887 with the fuses

[PCM programmer]

Are you compiling in Debug mode or Release mode ? If you compile in
debug mode, the compiler will change several of the fuses. That's
because the ICD debuggers will not work with, or do not support certain
fuses.

Here is an example program. Notice that I have Watchdog, code protect,
and brownout enabled:

[jai]

Dear PCM programmer,

Thanks for the reply.

I am not on debug mode.

I also found that if i program without code protect and make a chip = file verify
there is a 100% match.

But when i set code protect with the fuses. When i do verification chip = file
I get a message
"
There are errors
Error patterns indicate code protection may be active.
"
The thing is the verification of code protection soon after programming always says "Code not protected" could this be a possible error in the programmer?

regards,
Jai.

[jai]

Hi all,

Yes i would like to confirm that there is a error in
CCSLOAD Programmer Control Software for Windows - 4.040 and 4.039

I tried v4.025 there is no error in that version.
It displays code protect verification message as it should.

I hope CCS will fix this.

Regards,
Jai.

[Ttelmah]

You should never be able to 'verify' a code protected chip. Depending on the chip, older chips when read with code protection enabled, will return a 'scrambled' version of the code, while later chips just read as blank if code protection is enabled. Verify can't then work.

The 'standard' sequence to program a code protected chip, is to program and verify with code protection off, _then_ enable just the code protection fuse.

On older chips what you could do, was to program and verify a chip, then enable it's code protect fuse, and read the scrambled contents back. Save this. Then write new chips with the protection enabled, and verify them against the scrambled file. The same 'code' would always give the same 'scrambled' result.

It sounds as if 4.025, is not setting the code protect bits, hence the chip verifies...
I'd say that the later version is doing what it should. Refusing to verify if code protection is enabled.
However then have to point out that all these versions are at best 'beta'; compiler versions. It is generally held that first 'reasonably working' V4 compilers, were around 4.068 and later....
4.040, has to be perhaps three years old.

Realise you are talking about CCSLoad, not CCSC. So version numbering is different, but comment still applies. I'd say the newer version is doing what it should, and is not able to verify a code protected chip.

Best Wishes

[jai]

Dear Ttelmah,

Thank you for the info.

I think i should clarify the problem.

I understand that if not protected the verification must be chip = file.
and if protected chip not equal to file.

But the problem here is that in CCS programmer CCSLOAD V4.040 in the
settings tab there is a VERIFY ROM PROTECT AFTER WRITE.
Which when programmed with PROTECT should come after programming and display CODE PROTECTED.
This never happens - it always says NOT PROTECTED with fuse protect or not.

But it works on CCSLOAD V4.025.

regards,
jai.