thanks henrik , I knew somebody would know where to find the info.
its worth persisting on getting the config syntax right because editing the inc files will get very messy
thanks henrik , I knew somebody would know where to find the info.
its worth persisting on getting the config syntax right because editing the inc files will get very messy
Thank you Henrik, I have now removed the config statements from the PBP 2.6 18F1220.inc file
and inserted the required config statements into my program. Works like a dream and no more
interfering with the .inc file.
I realise now that my problem was caused by the inclusion of the following lines in the PBP 2.6
18F1220.inc file:
"
__CONFIG _CONFIG1H, _XT_OSC_1H
__CONFIG _CONFIG2H, _WDT_ON_2H & _WDTPS_512_2H
__CONFIG _CONFIG4L, _LVP_OFF_4L
"
I can't believe that this took thirty hours to resolve. I would most probably
have abandoned this project if I hadn't received such patient and speedy assistance from
you and Richard. And an added bonus - I don't have to go to the pains of buying new
software tools and dealing with their idiosyncrasies.
Hebe
Hi,
Yes, dealing with the CONFIG bits has got to be THE single most discussed issue on this very forum and, I'm guessing, on the various support channels to MELABS - which is probably why they changed it - for the better - when releasing PBP3. That change alone is IMHO worth the cost of an upgrade, not to mention the conditional compile feature but of course YMMV.
Now that you've commented the CONFIG out of the .inc file you must remember to always include them in your source file when compiling for that particular device. If you don't they will default to their erased state.
/Henrik.
Bookmarks