.For the few cases I checked, it seems that in new mlk files the old 'Config Register Write Protection' was replaced with 'Configuration Register Write Protection' and this causes conflict.
v5.60 configuration files
v5.60 configuration files
Configuration files shipped with newest version cannot be opened ('Scheme file description(s) do not match' error) .
For the few cases I checked, it seems that in new mlk files the old 'Config Register Write Protection' was replaced with 'Configuration Register Write Protection' and this causes conflict.
.For the few cases I checked, it seems that in new mlk files the old 'Config Register Write Protection' was replaced with 'Configuration Register Write Protection' and this causes conflict.
Re: v5.60 configuration files
Hi,
I tried few schemes as well, but they did not fail. Do you have exact names so we can check?
Thanks.
I tried few schemes as well, but they did not fail. Do you have exact names so we can check?
Thanks.
Re: v5.60 configuration files
For example, P18F2620, P18F4520, P18F8722, etc.
BTW, all scheme files are dated on 2011-09-16.
BTW, all scheme files are dated on 2011-09-16.
Re: v5.60 configuration files
True. 
Thanks for reporting the issue.
Thanks for reporting the issue.
Re: v5.60 configuration files
Unfortunately, the same concerns new versions of mB and mC for PIC .
Naturally, if one saved own configuration under previous compiler version, such scheme also may not be read with new version, so here's a way to fix older cfgsch files:
- open the scheme file with text editor,
- find '<NAME>Config Register Write Protection</NAME>' field,
- change it to '<NAME>Configuration Register Write Protection</NAME>'.
For processors with oscillator switchover option it may be necessary to change also
<NAME>Int/Ext Oscillator Switchover</NAME>
to
<NAME>Internal/External Oscillator Switchover</NAME>
Another difference I've found (there may be more for specific processors):
'Write/Erase Protect Page Start/End' needs to be replaced with 'Write/Erase Protect Page Start/End Location'.
.Naturally, if one saved own configuration under previous compiler version, such scheme also may not be read with new version, so here's a way to fix older cfgsch files:
- open the scheme file with text editor,
- find '<NAME>Config Register Write Protection</NAME>' field,
- change it to '<NAME>Configuration Register Write Protection</NAME>'.
For processors with oscillator switchover option it may be necessary to change also
<NAME>Int/Ext Oscillator Switchover</NAME>
to
<NAME>Internal/External Oscillator Switchover</NAME>
Another difference I've found (there may be more for specific processors):
'Write/Erase Protect Page Start/End' needs to be replaced with 'Write/Erase Protect Page Start/End Location'.
