Settings for internal oscillator

[peterdeco1]

Actually, on the 12F683 I use the following code and it defaults to 4MHZ

DEFINE OSCCON_1K 1
@ DEVICE MCLR_ON, INTRC_OSC_NOCLKOUT, WDT_ON, BOD_OFF, PWRT_ON, PROTECT_ON

On the 16F819 & 16F88 I use this, otherwise it defaults to the slowest speed (I think 32KHZ)
OSCCON = $60 'set int osc to 4mhz

[RussMartin]

DEFINE OSCCON_1K 1

This is a new one for me. Can you tell me more about it?--syntax and such--or direct me to more information?

And, yeah, I discovered the default-to-32 kHz thing the hard way.

Thanks!

[mister_e]

It's a new one for everyone I guess

You'll have more chance to find DEFINE OSCCAL_1K, and it's explained a litlle bit in the manual.

[RussMartin]

It's a new one for everyone I guess

You'll have more chance to find DEFINE OSCCAL_1K, and it's explained a litlle bit in the manual.

Yes, now that you mention it. I find it in my new manual on pp. 12 and 202.

(My old manual is the one with all the handwritten notes in it!)

But I find the explanation on p. 12 mysterious.

[peterdeco1]

 Originally Posted by mister_e  
It's a new one for everyone I guess 

You'll have more chance to find DEFINE OSCCAL_1K, and it's explained a litlle bit in the manual.

When I use DEFINE OSCCAL_1K, generates errors. "Error C:\PBP\PBPPIC14.LIB 7448:[225] Undefined Symbol 'OSCCAL'

The only way I don't get an error is:
DEFINE OSCCON_1K 1 ' Set OSCCON for 1K device

[mister_e]

peterdeco1,
if you have this error message it indeed mean that your particular PIC doesn't have the OSCCAL register.

12F683 have an OSCCON register indeed, and it's directly accessible through your code. Some also have OSCTUNE register, this one is to tweak the internal oscillator in case you need to do so. But still, this one is also directly accessible in code and no need for DEFINEs.

DEFINE can be everything, if it's not built-in in the compiler instruction set or the spelling (Case) is wrong, it will just do nothing, hence why we already discussed about their spelling.

DEFINE MarryHadAlittleBoy_HisNameIsJerry 1

will not return any error, and obviously it will not do anything unless you use it in ASM. This is handy when you want to customized your INCLUDE/Library or feature of your program. Check my Keypad routine for example.

[peterdeco1]

Yes Steve. I did see the Osctune in the datasheet, but haven't played with it yet. I'm using the HPWM in the 12F683 and it's dead-on accurate the way it is. I'm a great believer in "If it works, don't fix it." Besides, Osctune may make me pull more hair out! Thanks.