New PBP and MCS -- a few errors

[HenrikOlsson]

No, you don't have to USE MPLAB X but you need to have it INSTALLED so that you have access to the assembler that comes with it. And, it doesn't HAVE to be the assembler from MPLAB X, it can be an older version from MPLAB 8 but then it won't be able to assemble programs for newer part.

So, if you haven't installed MPLAB X then do so. I Believe the plugin you mention is when you want to so the reverse, ie use PBP as the compiler from within MPLAB X.

/Henrik.

[Michael]

Thanks Henrik.

Yes, I have had MPLAB X installed (latest) and was just playing around and got a successful assembly. Was getting some errors and maybe you can help me confirm what I was doing wrong (using 16F1847).

I had -- (with the 16F88)

@ DEVICE pic16F88, INTRC_OSC_NOCLKOUT
''' System Clock Options
@ DEVICE pic16F88, WDT_ON
''' Watchdog Timer
ETC

but apparently the 1847 needs a hashtag like -- ?
#CONFIG ; F1847.
__config _CONFIG1, _FOSC_INTOSC & _WDTE_ON & _PWRTE_ON & _MCLRE_OFF & _CP_OFF & _BOREN_OFF
__config _CONFIG2, _PLLEN_OFF & _LVP_OFF
#ENDCONFIG

also -- found this,

@ ERRORLEVEL -306 ; turn off crossing page boundary message

which got rid of my boundry error. ?

does it FIX the boundry problem or just get rid of the message ? THANKS MUCH FOR HELP.


Think I have it working right now.

[HenrikOlsson]

Great, you're making progress!

That #CONFIG / #ENDCONFIG is "new" in PBP3 and it is what you should use for ALL devices.

In your PBP3 installation folder there's a sub folder called DEVICES_REFERENCE. If you look inside of that you'll find a file for each device the compiler supports and inside the file(s) you'll find all the available CONFIG bit options and what defaults PBP is using in case you DON'T include a #CONFIG / #ENDCONFIG block in your code. Also, make sure to read the manual as it explains it better than I can.

The "boundry error" is not an error - it's a message ment to make you aware of the fact that the code is crossing a page boundry. If you're NOT using any embedded assembly code in your programs you don't have to worry about it and can safely have the message disabled.

/Henrik.

[Michael]

Good deal.

I'll have to make note I can have all the config info handy -- always a hassle. Although I generally stick to one chip for what I do.

Not as dumb as I sound, just impatient. Honestly, the documentation on both MCS and PBP could be much clearer especially for installing and possible mishaps. thanks.

[Michael]

do you know how to open the .INFO file in device references?

do you just rename it text or something?

[HenrikOlsson]

Just open them with your favourite text editor or in MCS.