Publishing Positron Studio 2.0.2.8

[JohnB]

I have updated Positron Studio.  Main change: if you keep copies of previous versions of the compiler you can save these links and switch quickly between compiler versions from the Tools/options menu.

[JonW]

Really nice IDE John. 

Jon

[JonW]

John

Noticed that the fuse configurator for the 12F1822 is not correct for the Brown out and causes and error with the compiler. 

Cheers

Jon

[JohnB]

OK, I'll take a look but I haven't changed Fuse Config for some time. Suspect its an old issue.

Just checked the ppi files are expecting BORV_25 or BORV_19

After that it compiles.  I get this info from the 8bit_device.info file which appears to differ from the ppi files.  Not sure  if Les has changed anything around here or whether the 8bit_device.info needs to be updated.  either way, that is the cause of the problem.  Maybe Les can throw some light on this.

[Stephen Moss]

OK, I'll take a look but I haven't changed Fuse Config for some time. Suspect its an old issue.

Just checked the ppi files are expecting BORV_25 or BORV_19

After that it compiles.  I get this info from the 8bit_device.info file which appears to differ from the ppi files.  Not sure  if Les has changed anything around here or whether the 8bit_device.info needs to be updated.  either way, that is the cause of the problem.  Maybe Les can throw some light on this.

Is that not the age old issue where Microchip retrospectively renamed some configuration fuses after the PPI files were created thus creating a mismatch between the fuse names the configurator uses and those the compiler expects which then generates an error.

My usual solution is to change the fuse configurator to output the configuration fuse setting as ASM because either compiler does (or previously did) not check any Assembler code for errors and/or the fuse registers are written to as a number, I cannot recall which but either way the fuse are correctly set without the fuse name mismatch occurring and being flagged as an error.
I find that quicker than trawling through the PPI files to find the equivalent fuse name the compiler expects and then manually correcting in my config settings.

[JohnB]

Stephen, you are right, its so long that I have been actually coding in Positron or used the fuse config in earnest that I had forgotten this issue and its resolution although I wrote the fuse config.  Sad sign of getting past my best by vintage!