Hi Joe,

Look in the compiler's "include" directory and find the .h file for the
chip group you are compiling. Near the end of the file are the
configuration fuses.

Beware, some chips have some of their config settings at a second
address and require a second config line in your code, like this:

__CONFIG (FOOBAR & FOOBAS)
__CONFIG (FOOBAT)

It's not always obvious in the include file which ones need to be on the
second line - consult the chip's data sheet for the addresses of the
configuration words to see which is which.

This may be fixed in the latest version of the HiTech compiler but I use
an ancient version that doesn't even have the 16F690 so that's why I am
being general in my explanation.

Cheerful regards,

Bob


Joseph Bento wrote:
> It can get frustrating trying to track down information when one is
> learning.  I'm perusing through the "Hi-Tech C 10/12/16" manual as well as
> the datasheet for the 16F690.  I'm trying a couple projects in C on the "Low
> Pin Count" Microchip board.
> 
> I'm trying to understand an example that flashes a couple LEDs on the board.
> I can follow the C source pretty well, I can edit the code and recompile to
> control different LEDs and so on.  It's the configuration bit setting that
> I'm trying to understand.
> 
> My program uses the following config setting:
> 
> __CONFIG (INTIO & WDTDIS & MCLRDIS & UNPROTECT);
> //Internal Clock, Watchdog off, MCLR off, Code Unprotect
> 
> Since it is commented, I can see what is happening.  It's the terminology
> itself that I haven't found a reference for.  I was playing around with the
> MCLR setting by temporarily deleting it from the code, and controlling MCLR
> via the buttons in MPLAB.  (I wanted to prove to myself that if MCLR is
> disabled as above, the buttons have no effect - they don't.)  
> 
> If I were writing this program from scratch, how would I know, and where
> would I find 'DIS' for 'MCLRDIS' ?  I searched on the web, and I see that If
> wanted MCLR enabled, the command is 'MCLREN'. No mention that I can see in
> the manual.
> 
> Since it's apparently related to the compiler, I don't expect to see the
> reference in the datasheet, but the compiler manual itself seems devoid of
> explanation.
> 
> Am I missing something in understanding where to find answers?
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist