Originally Posted by
prstein
Right now it parses the .inc files for the selected PIC (if they're not in the default locations on you computer you have to set the paths). From the MPASM files it parses out all of the provided configuration settings, and from the PBP folder it parses out the current default configuration settings.
That sounds great!
I can get it to compile using something like this at the front of a large program, even with some includes thrown in for the PIC18F67J50. And I see the change in my PicKit2 programmer. (Doing so with PBP inc files configs remmed out).
Code:
asm
CONFIG XINST = OFF
CONFIG PLLDIV = 5
CONFIG WDTPS = 512
CONFIG CPUDIV = OSC1
CONFIG FOSC = HSPLL
endasm
or:
@ CONFIG XINST = OFF, PLLDIV = 5, WDTPS = 512, CPUDIV = OSC1, FOSC = HSPLL
See Bruce's post here: http://www.picbasic.co.uk/forum/show...3087#post13087
There are some issues with other newer chips though. For instance the PIC26J50 uses OSC instead of FOSC, which really throws a wrench in the works. (See semi work around here: http://www.picbasic.co.uk/forum/show...0854#post90854 ) If anyone wanted to get fancy: If it was one of the chips that required a change to the pbp .inc file .... It could ask you "would you like me to edit your 18F26j50.inc file?" That would be so much nicer than looking through the list of chips, finding it, commenting other stuff out, and entering new settings, then hitting save. Don't know how many other chips we are talking about here though.
I am not sure if it helps, but here is a PDF with a lot of chip's configs:
http://ww1.microchip.com/downloads/e...ngs_51537f.pdf
Bookmarks