Change to Fuses in device file for PIC16LF18856

blowtorch · Joined: 11 Jun 2013 Posts: 35 Location: Cape Town

So, recently installed PCM 5.083. Today I tried to compile some production code for a PIC16LF18856 using the new version, got a compiler error:

PCM programmer · Joined: 06 Sep 2003 Posts: 21708

It's clearly a bug, because the 16LF18856 data sheet shows the CP and CPD
fuses in Config Word 5. Report it to CCS.

If you have the full IDE, you could edit the device file.

blowtorch · Joined: 11 Jun 2013 Posts: 35 Location: Cape Town

Thanks PCM. I do have the full IDE, will give it a go (and report it).

Recently upgraded to cover the 16 bit PICs too, very excited to give them a go.

Ttelmah · Joined: 11 Mar 2010 Posts: 19496

As a comment, you can also do it without having to edit the file.
#FUSES will also accept an address and a hex value, so you can
just explicitly set the required pattern.
So for instance:

#FUSES 1=0xFFFF

Will set word one of the fuses to 0xFFFF.

So look at the .lst from one of your old compiles, and set the right
byte pattern into the location that controls the protection.

blowtorch · Joined: 11 Jun 2013 Posts: 35 Location: Cape Town

Thanks Ttelmah. Nice tip!

I have logged it BTW.

Ttelmah · Joined: 11 Mar 2010 Posts: 19496

It's interesting. If you read the 'readme' for this compiler, they have been
playing with the meaning of 'PROTECT'. Making it now protect the whole
of memory, where it previously omitted the bootblock. You now have to
explicitly exclude the bootblock if you want the old behaviour. Suggest in
that doing this change, they have managed to make it not work on some
chips....

blowtorch · Joined: 11 Jun 2013 Posts: 35 Location: Cape Town

Yes. Afraid I am guilty of omitting a thorough read of the readme.

CCS support emailed me a new devices file, problem fixed.

I need to install updates to separate folders I think. Choosing to keep previous versions means the DLL folder per version is retained, but that is only part of the story. The readme also states "The command line compiler has a new command line option to set the compiler version. For example: CCSC +FH VERSION=5.006 test.c"
Thats all very well, but I use MPLABX as IDE, which supports multiple configurations, but it would seem to me they would need to be installed to different folders in it's entirety.

Ttelmah · Joined: 11 Mar 2010 Posts: 19496

Yes. I always install into different directories. So PICC5083 for the latest
compiler.
However there is an issue that MPLAB, insists on finding all the compilers.
Trying to disable this with the exclusion syntax doesn't seem to be reliable.
Currently the nicest way, is to keep a separate virtual machine for each
compiler I want to use. Makes it really tidy, and ensures there is no
interference between the versions....