What am I doing wrong ?

[malc-c]

In your code, put a space between '@' and "DEVICE"


--------------

Yup, have done (I copied and pasted the line in your post) and still fails to compile.

Malc

[mister_e]

if you use MPASM, DEVICE is not the right command, the the FAQ thread about the config fuse.

    @ __CONFIG _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_ON & _MCLRE_OFF & _BODEN_ON
         ' Internal Oscillator
         ' Enable watch dog timer
         ' Enable power up timer
         ' Disable MCLR pin
         ' Enable brown out detect

Or you may set them manually in your device programmer software.

HTH

[malc-c]

Steve,

Looks like I might have to set them manually or use the 16F628 as I still get an error when I copy and past the line of code from your mail.

This time I get:

Error 118: overwriting previous address contents 2007

What the hell that means I have no idea ?

I think I need to go back to basics and get a LED flashing on a PIN and then impliment my code for the PWM

Thanks guys for your continuing help, its this support that makes PBP my preferred programming language

Malc

[mister_e]

so it seems you didn't read the FAQ
pay attention to post #5 of the link bellow
http://www.picbasic.co.uk/forum/showthread.php?t=543

[Acetronics2]

Hi, Steve

somewhat tired in the end of that week ...

Alain

[mister_e]

Alain, try it and uncomment the default config fuses.. what do you get?

Maudit francais

Steve who laught a big time right now!

[malc-c]

so it seems you didn't read the FAQ
pay attention to post #5 of the link bellow
http://www.picbasic.co.uk/forum/showthread.php?t=543

Thanks for the link, and whist I did look at the FAQ's.. I must admit that I didn't scroll down much further than the original post - Sorry !

However the good news is that the LED is now pulsing away on GPIO 0

However I really want to learn from this and I'm a tad confused (easy to do). Whats the difference between having the line in the program code and the INC file. ?

I found that if I removed the line

@ __CONFIG _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_ON & _MCLRE_OFF & _BODEN_ON

from the programing code and left the INC file intact the program compiled but the LED did nothing. - Reming out the line in the INC file and adding it to the code file, resulted in the code compiling without errors and the LED is pulsing away fine !

Should (or is that could) I use the INC file and have some statement in the programming code to call this file (something like include 12F675.inc)

Also, will I have to modify every INC file for every PIC that I use so i don't get this problem again ?

Cheers

Malc

[paul borgmeier]

Although technically correct, after some sleep and a few cups of coffee I can see that my suggestions would not have helped you. (#5 in this thread)

good luck,

Paul

[mister_e]

Yeah it's pain dude, you'll have to modify all .INC for all PIC you have in stock. The MPAM 'errorlevel -' stuff can't work on that... it would be just too much convenient.

I already think of doing an automatic application to comment out every .inc file... maybe i'll do it one day... maybe

But i think that even if you get this Error message, your config fuse will be set as per your code. It will just be an error message like the one for Page Boundary, or Find directive in column x, or... ,.. wich can be ignored. It's just unplesant to see it in your face