New PBP and MCS -- a few errors


Closed Thread
Results 1 to 11 of 11

Hybrid View

  1. #1


    Did you find this post helpful? Yes | No

    Default Re: New PBP and MCS -- a few errors

    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.

  2. #2
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,622


    Did you find this post helpful? Yes | No

    Default Re: New PBP and MCS -- a few errors

    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.

  3. #3


    Did you find this post helpful? Yes | No

    Default Re: New PBP and MCS -- a few errors

    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.

  4. #4


    Did you find this post helpful? Yes | No

    Default Re: New PBP and MCS -- a few errors

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

    do you just rename it text or something?

  5. #5
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,622


    Did you find this post helpful? Yes | No

    Default Re: New PBP and MCS -- a few errors

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

Similar Threads

  1. Replies: 1
    Last Post: - 4th April 2013, 02:31
  2. ELSEIF Command, PBP 2.60, and MCS
    By rsocor01 in forum mel PIC BASIC Pro
    Replies: 1
    Last Post: - 6th December 2011, 07:16
  3. MCS+ with PBP 2.50
    By BrianT in forum mel PIC BASIC Pro
    Replies: 4
    Last Post: - 21st September 2007, 06:52
  4. Are these errors in the PBP manual?
    By websmith in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 30th November 2006, 09:22
  5. PBP+MCS+PICKit1
    By sincity337 in forum mel PIC BASIC Pro
    Replies: 2
    Last Post: - 21st December 2005, 03:12

Members who have read this thread : 1

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts