Presetting Configuration Fuses (PIC Defines) into your Program

[RUBiksCUbe]

Oh yeah! Got it working!! I needed to put in the PIC defines in the beginning. It was giving me those errors because I didn't need the line:

@ INCLUDE "P18F252.INC" ; MPASM Header

I'm not sure why I dont need it, but I think its because 18F252.INC has an identical line in it, so I was including it twice. Thanks soooo much!!!

[eoasap]

Hi, i'm using the 18F452 chip so required to use MPASM compiler through Picbasic.
if i try to set a fuse using ONLY (for example) the line below

@ __config _LVP_OFF

i get this error:
x.asm 112: symbol not previously defined (_LVP_OFF)
x.asm 112: argument out of range (not a valid config register address)



if i put the following code:
@ INCLUDE "P18F452.INC" ; MPASM Header
@ __config _LVP_OFF

i get errors like the following:
'1042: duplicate label ("DDRA" or redefining symbol that cannot be redefined)
1607: superseding current maximum RAM and RAM map
120: symbol not previously defined (_LVP_OFF)
etc..

i've been trying for a while now with no luck setting the fuses. any ideas what i'm doing wrong?

thanks!

[mister_e]

The 18F serie work different from the other. In the MPASM directory open the according .INC file. Look at the end you'll discover how to use the Config directive.

Free example here...

@ __CONFIG _CONFIG1H, _OSCS_OFF_1H & _HS_OSC_1H
    ' Oscillator switch OFF
    ' Use HS oscillator (20MHZ here)
    '
@ __CONFIG _CONFIG2L, _BOR_ON_2L & _PWRT_ON_2L & _BORV_45_2L
    ' Brown out reset ON @ 4.5Volts
    ' Power-up timer ON
    '
@ __CONFIG _CONFIG2H, _WDT_ON_2H 
    ' Watch dog timer ON
    '
@ __CONFIG _CONFIG4L, _STVR_ON_4L & _LVP_OFF_4L & _DEBUG_OFF_4L
    ' Stack over/underflow ON
    ' Low Voltage programming OFF
    ' Background debugger OFF

[eoasap]

Steve,

Once again you are my savior
Thanks alot for always helping me and guiding me in the right direction. your advice worked perfectly and i got the overwrite error which i see from your other post how to handle that.

Thanks so much

[mister_e]

If you are using any PIC18 serie, you will have this warning one day or another. Our friends from Microchip decide to change the way to define the config fuses when using the latest MPASM version 5.00.

The solution is still located at the same place... at the end of the 18XXXX.INC file located in the MPASM folder.

; IMPORTANT: For the PIC18 devices, the __CONFIG directive has been
; superseded by the CONFIG directive. The following settings
; are available for this device.
;
; Oscillator Selection:
; OSC = LP LP
; OSC = XT XT
; OSC = HS HS
; OSC = RC RC
; OSC = EC EC-OSC2 as Clock Out
; OSC = ECIO EC-OSC2 as RA6
; OSC = HSPLL HS-PLL Enabled
; OSC = RCIO RC-OSC2 as RA6

SO now the new method to set the config fuse on the PIC18 serie is...

@ CONFIG OSCS=OFF, OSC=HS
    ' Oscillator switch OFF
    ' Use HS oscillator (20MHZ here)
    '
@ CONFIG BOR=ON, PWRT=ON, BORV=45
    ' Brown out reset ON @ 4.5Volts
    ' Power-up timer ON
    '
@ CONFIG WDT=ON
    ' Watch dog timer ON
    '
@ CONFIG STVR=ON, LVP=OFF, DEBUG=OFF
    ' Stack over/underflow ON
    ' Low Voltage programming OFF
    ' Background debugger OFF

Or if you prefer...

ASM
    CONFIG OSCS=OFF  ; Oscillator switch OFF
    CONFIG OSC=HS    ; Use HS oscillator (20MHZ here)
    CONFIG BOR=ON    ; Brown out reset ON 
    CONFIG BORV=45   ; Brown out detect voltage=4.5 Volt
    CONFIG PWRT=ON   ; Power-up timer ON      
    CONFIG WDT=ON    ; Watch dog timer ON
    CONFIG STVR=ON   ; Stack over/underflow ON
    CONFIG LVP=OFF   ; Low Voltage programming OFF
    CONFIG DEBUG=OFF ; Background debugger OFF
    ENDASM

Don't forget to comment the default PBP config fuses...

[Tissy]

Nope can't get it going !!

I've used

@ CONFIG FOSC = HS

but it returns the error

__CONFIG directives cannot be used with CONFIG directives

I've even tried

@ CONFIG _CONFIG1H, _FOSC_HS_1H

which returns the same error as above and also,

@ __CONFIG _CONFIG1H, _FOSC_HS_1H

which returns two errors stating:
Overwriting previous address contents (0000)
Overwriting previous address contents (0001)

Any ideas?

[eoasap]

tissy, i just got the same thing you did. That's too bad because Steve's code looks so neat and orderly i personally would rather not use all the underscores and such.