how to protect oscillator calibration value

[sadman]

is there any command in Mikro c compiler to protect oscillator calibration being changed during programing

sadman

[Gallymimu]

what oscillator calibration are you talking about.  Are you talking about the OSCTUN bits in PIC processors?

[piccolo]

is there any command in Mikro c compiler to protect oscillator calibration being changed during programing

sadman

If you use mikroProg suite for PIC, click on the button "config" and select the box "OSCCAL Values Protect."

If you use another programmer, looks for a similar menu item.

There is no way through mikroC compiler.

[sadman]

what oscillator calibration are you talking about.  Are you talking about the OSCTUN bits in PIC processors?

yes osctun or osccal bit, yes i know it can be done in Mikroprog but if i have used different programmer then it can be configure in code to protect it,

it can easily done in proton plus compiler

sadam

[piccolo]

yes osctun or osccal bit, yes i know it can be done in Mikroprog but if i have used different programmer then it can be configure in code to protect it,
it can easily done in proton plus compiler

sadam

Yes, however you must read the value of osccal before writing it.
Every single chip has its value of osccal.
For example, in the pic16F675, the value of osccal is situated in the last location of memory program.
I don't use proton and I don't know how it inserts the value of osccal, but you can try to read the value of osccal before programming the chip and then insert it in your mikroC program to be rewritten in his own location of memory program.
I have never tried but, maybe it works.
For info, you can see the document "memory programming specification" for your device, from the Microchip site.

[Gallymimu]

I could be wrong but I THOUGHT, that typically programmers didn't overwrite those factory oscillator calibrations unless told to do so.  I don't often use other tools besides microchip's though.

[piccolo]

I could be wrong but I THOUGHT, that typically programmers didn't overwrite those factory oscillator calibrations unless told to do so.  I don't often use other tools besides microchip's though.

If you totally erase the device, the value of osccal is also erased.
Then it will need to write it again, but it needs to write the correct value.

[ron]

Posted this question before but cant find the post right now.
If I am using an external crystal oscillator does the OSCCAL value really matter.
My understanding is that its only important if your using the internal oscillator.

[Sideshow Bob]

Posted this question before but cant find the post right now.
If I am using an external crystal oscillator does the OSCCAL value really matter.
My understanding is that its only important if your using the internal oscillator.

That is also my impression. The internal oscillator is a RC oscillator. And hence it is not as accurate as a crystal oscillator. But it will be repetitive "wrong" so it can be tuned. If you use a crystal the accuracy will be determined by the crystal. So the OSCCAL value will not be used at at all. If your goal is accuracy do not use the internal oscillator. But for most hobbyist application it will work just fine if tuned. And I also believe they are tuned from factory.
So to sum it up For internal oscillator use OSCCAL value will be used. Any other clock source it will NOT be used