Getting Configs straight

[Bruce]

PBP has a device specific header file for each PIC it supports. This gets
included automatically each time you compile. In these header files are
generic "default" config fuse settings.

These are embedded in the .hex file. When you import a .hex file into
MPLAB these default config fuse settings are used, and should show up
in the config screen when viewed in MPLAB. You can either accept them,
or change them from within MPLAB.

I always include config fuse settings in my source. Changing them with your
programmers software, or from within MPLAB, can lead to confusion down
the road.

I.E. If you can't tell by looking at the source what they were set to when
you last programmed the target -- how will you know/remember the next
time what you manually set them to?

It's much easier to just drop them directly into your source code (or use the
generic defaults) than trying to remember what they were "manually" set to
previously.

[vacpress]

yeah. after once again and more carefully reading through the PBP manual, i have finally found the information about 'what all' files go into a typical pic basic compile... and i even now know what a .mac file is, finally!

i also answered another of my own questions... which was 'can i bury the configs in a seperate include?'

the answer seems to be 'yes'. although i am not certain to what extent, as it came out of some old forum post which suggests putting your config fuses in a configfuses.cfg...i do not know if this is a special or arbitrary file name... i will probably get around to trying this soon and may even remember to report back...

i am imagining .cfg files with names like... 18f45504musb.cfg which would setup a 4550 at 4mhz with the usb regulator turned on... possibly make a few as i really do work with just a few different chip types...

anyone tried anything like this?

it sure would be cool if microcode studio had an API so I could begin automating some of this stuff...

cheerio, robert