Presetting Configuration Fuses (PIC Defines) into your Program

[mister_e]

OK, i also have the same problem here.. hum hum when i add some code line as you did.

SO it looks like PicBasic is not "New MPASM Compliant" for the config fuses. I'll contact Charles tomorrow.

For now, what you can do is to place your config fuses in the 18F2550.INC in the PBP folder. BUT if you do different project and you need different config fuse setting, You can add a device to the MCS list and create a new .INC and .BAS file for it. OR do an include file to be loaded in the 18F2550.INC file.

        NOLIST
    ifdef PM_USED
        LIST
        "Error: PM does not support this device.  Use MPASM."
        NOLIST
    else      
        LIST
        LIST p = 18F2550, r = dec, w = -311, f = inhx32
        INCLUDE "P18F2550.INC"	; MPASM  Header
        INCLUDE "C:\PBPProg\ConfigFuse.cfg" ; Your Config Fuses
        NOLIST
    endif
        LIST
EEPROM_START	EQU	0F00000h
BLOCK_SIZE	EQU	32

Just drop your config lines in the ConfigFuse.cfg file and it's work... this time. DOH sorry.

[Tissy]

Thanks for that. I thought i was going mad !! Theres nothing worse than people saying it should work when it doesn't. You have save my insanity.

I think the .CFG approach is a good solution.

Many thanks,

Steve

[pramodsinha]

Thanks for that. I thought i was going mad !! Theres nothing worse than people saying it should work when it doesn't. You have save my insanity.

I think the .CFG approach is a good solution.

Many thanks,

Steve

hi,
i also facing similar problem if i try to compile programe on 18f452 i get the similar message like:
Warning[230]c:\develo~1\susdco~1\rfusb~1.asm 67:__CONFIG has been deprecated for PIC18 devices. Use directive CONFIG.
i am using pbp2.44 with mpasm7.21.
I tried to rectify the problems with the above directives but fail should i go for the other version of mplab
pl. help
thanks

[Tissy]

Havin gtaken the .CFG route, Steve does yours come up with these errors?

Warning[205] c:\pbp\sdcconfigfuse.cfg 1 : Found directive in column 1. (CONFIG)
Warning[205] c:\pbp\sdcconfigfuse.cfg 2 : Found directive in column 1. (CONFIG)
Warning[205] c:\pbp\sdcconfigfuse.cfg 3 : Found directive in column 1. (CONFIG)
Warning[205] c:\pbp\sdcconfigfuse.cfg 4 : Found directive in column 1. (CONFIG)
Warning[205] c:\pbp\sdcconfigfuse.cfg 5 : Found directive in column 1. (CONFIG)

Could you post your .CFG file?

Cheers

[mister_e]

The CFG file is the one i post few post before. You just need to Indent your CONFIG lines as i did.

[Tissy]

Yup, got that now, thanks.

One fuse that doesn't work is

BOREN = SBORDIS

But the fuse settings in the .INC are

; Brown-out Reset:
; BOREN = OFF Disabled
; BOREN = ON SBOREN Enabled
; BOREN = NOSLP Enabled except Sleep, SBOREN Disabled
; BOREN = SBORDIS Enabled, SBOREN Disabled

So obvioulsy not all is compatible between, PBP and MPASM.

Out of interest can you try this fuse on your configuration.

Cheers.

[Darrel Taylor]

Well, I was finally forced to upgrade MPASM. And along with it came the dreaded __CONFIG has been deprecated warning. So I figured .. No problem, these guys have already figured it out.

But after trying everything out, and having to modify include files in the include files each time I compile a program that needs a different config, espescially when my programs already have all the config statements in them, just wasn't working out very well. And the thought of having to modify every program I've ever written, to use the new Config syntax, was leaving a bad taste in my mouth.

Fortunately, the old __CONFIG directives still work. The __CONFIG has been deprecated warning, is just that.   A warning.   And Warnings can be turned off.   So until Microchip decides to make it not work anymore, what I'm doing is to add this line to the .inc file for the chip it's being compiled for.

    errorlevel -230

Then everything works just like it always has.

[ScaleRobotics]

Ah, I see what you mean!

Define XTAL 48
OSCTUNE.6 =1
ASM
   CONFIG OSC=HSPLL

[SKOLS1]

I got this error: overwriting previous address contents (2007)
I write this line @ __CONFIG _INTRC_OSC_NOCLKOUT to turn on the internal oscilator of the PIC16F628A,
I fix any mistakes what I think I made them,but there are errors.I DEFINE OSC 4,it's not working.

[mackrackit]

You need to comment the *.inc file for the chip in the PBP directory.
http://www.picbasic.co.uk/forum/show...=6775#post6775

[SKOLS1]

I get: Unable to open INCLUDE file P16F628A.INC

[ScaleRobotics]

Thanks Bruce, that does the trick! Just did exactly as you said, and now it lets me compile inside my program code like this:

Define XTAL 48
OSCTUNE.6 =1
ASM
   CONFIG OSC=HSPLL 
   CONFIG CPUDIV=OSC1
   CONFIG PLLDIV=5
   CONFIG LPT1OSC=OFF 
   CONFIG CP0=OFF 
   CONFIG WDTEN=ON 
   CONFIG XINST=OFF 
   CONFIG IOL1WAY=OFF
   CONFIG STVREN=OFF 
   CONFIG T1DIG=ON 
   CONFIG FCMEN=OFF 
   CONFIG WDTPS=512
   CONFIG RTCOSC=T1OSCREF
ENDASM

And my LED is blinking at the right speed. Yes, I could just edit configs in the .inc file, but then you have to change it for each project. A pain if you want to jump around from unfinished project to unfinished project. Oh, that's just me....

[Bruce]

Cool. Maybe the fix is something as simple as melabs changing to something other than OSC?

Just bear-in-mind that your next PBP update will change everything, and any patch will fail since you've modified your library files...;o)