Thanks for the suggestion, but I now get a warning when I try to compile (using MPSAM) - it states "Found lable [DEVICE]" and "Illegal Opcode [12F675]"Originally Posted by sayzer
Thanks for the suggestion, but I now get a warning when I try to compile (using MPSAM) - it states "Found lable [DEVICE]" and "Illegal Opcode [12F675]"Originally Posted by sayzer
Originally Posted by malc-c
In your code, put a space between '@' and "DEVICE"
--------------
"If the Earth were a single state, Istanbul would be its capital." Napoleon Bonaparte
Yup, have done (I copied and pasted the line in your post) and still fails to compile.Originally Posted by sayzer
Malc
if you use MPASM, DEVICE is not the right command, the the FAQ thread about the config fuse.
Or you may set them manually in your device programmer software.Code:@ __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
HTH
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
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
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
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Hi, Steve
somewhat tired in the end of that week ...
Alain
Last edited by Acetronics2; - 9th June 2006 at 19:08.
************************************************** ***********************
Why insist on using 32 Bits when you're not even able to deal with the first 8 ones ??? ehhhhhh ...
************************************************** ***********************
IF there is the word "Problem" in your question ...
certainly the answer is " RTFM " or " RTFDataSheet " !!!
*****************************************
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 !Originally Posted by mister_e
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
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 !Code:@ __CONFIG _INTRC_OSC_NOCLKOUT & _WDT_ON & _PWRTE_ON & _MCLRE_OFF & _BODEN_ON
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
Bookmarks