#fuses options definitions

[woz]

Are the definitions for each of the #fuses options defined anywhere? I realize that the allowable options are listed in each devices .h file, but how does one work out what each option sets?

Thank you,

Ed

[bluetooth]

1. Go to http://www.microchip.com

2. Look up the data sheet for the micro you're using

3. In the back of the data sheet you'll find a section (in pretty much all of them) called something like "Special Features of the CPU"

4. Your answer lies there!

[woz]

Thank you fo the reply!

I went to the section of the data sheet you suggested and I was able to find some of the terms like LP and XT, but I could not find INTRC mentioned anywhere. I even did a search over the entire data sheet for INTRC and nothing was found. The chip I am using is PIC12F629.

[bluetooth]

I'm guessing that the CCS INTRC corresponds to the 629's INTOSC bits...

INTRC should yield xxxxxxxxxx101 in config for I/O and CLKOUT, and INTRC_IO should yield xxxxxxxxxx100 in config for I/O on both oscillator pins.

You'll find the config value (fuses) at the end of the .LST file. Let us know how this turns out.

[Guest]

The CCS documentation regarding fuses really stinks. Many of the items in the header files for certain parts are undocumented.

[bluetooth]

The reason I am "guessing" is that I haven't built a project with the 629.
CCS can call the fuses anything they want, and I would think they used INTRC to maintain consistency with other processors (or because it was easy!).

So, do you need someone to check this out for you? All you need to do is report back what should ALREADY be in YOUR list file.

Good luck....

[Charlie U]

We don't know which version of the compiler you are using, so I'll give a reply that applies to PCW or PCWH.

The fuses for each device are described by looking under View>Valid Fuses in the main menu. Then selecting the device of interest.

Another way is to use the device selector which is accessed with Tools>Device Selector from the main menu. Then select the device of interest. The fuses appear in a box in the upper right corner. There is both the bit and the mask that CCS uses to set or clear the bit.

These two tools and the device data sheet should make the fuses fairly clear.

If you are using the command line version, I hope that someone familiar with its operation will answer for us.

[bluetooth]

[dyeatman]

This is getting crazy....here they are so we can move on...

12F629 Fuses

CPD Data EEPROM Code Protected
NOCPD No EE protection
PROTECT Code protected from reads
NOPROTECT Code not protected from reading
NOMCLR Master Clear pin used for I/O
MCLR Master Clear pin enabled
PUT Power Up Timer
NOPUT No Power Up Timer
INTRC_IO Internal RC Osc, no CLKOUT
INTRC Internal RC Osc
RC_IO Resistor/Capacitor Osc
RC Resistor/Capacitor Osc with CLKOUT
BROWNOUT Reset when brownout detected
NOBROWNOUT No brownout reset

[woz]

Thanks guys.

dyeatman's response should take care of it for me. Just for the record, I am using PCM inside of MPLAB IDE. In that configuration the VIEW menu does not have a selection for FUSE settings. There is a pull down menu that allows you to set the configuration bits, but what is set in this menu does not match what gets programmed into the device, so that function must be incompatable with the CCS software.

I took a look at the .lst file and I could not see any statement concerning the FUSE settings. The only way I have of determing what the FUSE settings are is to program a part and read it with the programming software that came with the PIKit evaluation board that I am using.

It appears that I have the low end version of CCs's software, but for the price that I paid and with the help I am getting here I am quite satified so far.

Thank you again for your help!

[Mark]