Hi jessey,
Sorry. P18F452.INC is the "Microchip" include file. Open the 18F452.INC file "in your PBP directory". Make the change to this one. Not the one located in your MPLAB directory.
PBP has a device specific header file for each PIC it supports. These header files contain default config fuse settings for each device.
This is the file you edit. Not the Microchip header file.
Yes. You can make changes to over-ride config fuse settings embedded in the final .hex file with your EPIC software, however, it may not always work like you might expect.
Example. You compile your code using the default config fuse settings in the "18F452.INC" file in your "PBP" directory. You launch the EPIC software from within MCS, and you make changes to the config fuse settings with your EPIC software.
Now you click program, and it stil uses the default settings from the .hex file.
What happened? If you have the "Reread file before programming", and "Update Configuration From File" options selected, it just reloads the .hex file "from disc" into memory, and dumps the default settings in.
What most folks forget is to click the "Save" button after making changes to the config fuse settings to save them back to the .hex file on disc.
MPASM does not like it when you have config fuse settings in your code & in the PBP 18F452.INC file. You can only have them in "1" location or it returns this error message.
If you place the config fuse directive in your code, then you need to comment them all out in the PBP 18F452.INC header file.
Change your Microchip P18F452.INC file back to its original state.
Look in your "PBP" directory for 18F452.INC. Make only the change I mentioned previously, and see what you get.
Bookmarks