The processor is stated in the ASM code generated by PBP that is then turned to hex.
If you are using MCS or MPLAB the chip selected is the one used when the code is compiled.
The processor is stated in the ASM code generated by PBP that is then turned to hex.
If you are using MCS or MPLAB the chip selected is the one used when the code is compiled.
Dave
Always wear safety glasses while programming.
I am using MCS and PBP
I see that, I forgot about that, I was thinking about the epic definitions.
So, one question down, I see the definition for the processor. So why does
@ DEVICE PIC16F88 __config _CONFIG1, _INTRC_IO
or
@ __config _CONFIG1, _INTRC_IO
give me error[118]?
If you are going to set configs in your code, you need to comment out the default configs in c:/pbp/picxxx.inc file like this (see bottom "do not forget" paragraph) http://www.picbasic.co.uk/forum/cont...o-your-Program
http://www.scalerobotics.com
And I will add..
Do not use PM
@ DEVICE PIC16F88 __config _CONFIG1, _INTRC_IO
Move up to MPASM
@ __config _CONFIG1, _INTRC_IO
It will save you problems in the future.
Dave
Always wear safety glasses while programming.
Now that I see Melanie's write up I get it.
I'm surprised I didn't find this in a search? I looked in FAQ, but that is for the forum only.
Thank you for the pointing.
So, I'm assuming PM has "features" MPASM doesn't?
The write up from Mel is in the FAQ forum.
You have it backwards, MPASM has more than PM.
Dave
Always wear safety glasses while programming.
Well, technically it is in the "How To" section. http://www.picbasic.co.uk/forum/content.php?r=57 Maybe I will try moving some things to the FAQ to try to make things a little easier to find.
http://www.scalerobotics.com
Bookmarks