Configuration fuses in source file for 18f252

[mackrackit]

Can we see your code?

You do not copy the whole file, just the config lines.
Might be better at this point to not set the fuses in code. Just modify the PBP inc file.

[PickyBiker]

' using 20 MHz Resonator Pause 1 = 200 usec, 10 = 2 msec

__CONFIG _CONFIG1H, _HS_OSC_1H

symbol LED = 0 'Rename pin 0 of portb (PIC 16F84 pin 6) to LED

trisb = %00000001 'Setup port b as RB7-RB1 inputs, RB0 as output

main: 'Label for beginning of main loop
High LED 'Set pin 0 of portb high (5 volts) which turns the LED on
pause 10 'Pause 2 milliseconds with LED on
Low LED 'Set pin 0 of portb low (0 volts) which turns the LED off
pause 90 'Pause for 18 milliseconds with LED off
goto main 'Jump to the main label and do it all again and again

[mackrackit]

@ __CONFIG _CONFIG1H, _HS_OSC_1H

try that

[mackrackit]

And if you add
DEFINE OSC 20
near the beginning of your code you will not have to recalc the pauses

PAUSE 1000
will be 1 second

[PickyBiker]

Now that is progress.

DEFINE OSC 20, is a very nice little bit of info.

and

@ __CONFIG _CONFIG1H, _OSCS_OFF_1H & _HS_OSC_1H

Did the trick.

I noticed that I can comment out the config lines in the 18f252.inc file in the c:\pbp folder and put them directly in the source, or make the changes in the .inc file directly.

I woud rather make a copy of the .inc file and put it in the project folder to make the changes there, but when I did that, it took the values from the original .inc file in the c:\pbp.

How can I tell it to use the modified copy in the project folder?

Thanks,

Mike

[mackrackit]

The compiler will read the inc file, will always read the inc file. That is why you have to comment the things in the inc that you do not want read.

I know what you are after by making a copy of the inc for the project directory. But that would take some messing with the heart of PBP.. So that is why we have the way of putting the config settings in the code.

I guess you code write an include file for the configs... but then you would have the include statement in your code... Just stick with the configs in code space. It works..

[PickyBiker]

Okay... I can live with that.

I'll work with direct ,inc changes and putting the changes in the code and see which way works best for me.

Thank you al for the excellent help.

I will create a new post with my accomplishments so far, thanks to your help.