pbppi14e.lib problem


Closed Thread
Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2010
    Posts
    409

    Default pbppi14e.lib problem

    So my program is running happily on a 16F1828. I've been coding with the 16 MHz internal clock, but eventually need to use a 25 MHz external clock. The clock devices came in, I'm trying to switch over, and PBP is throwing errors during compile. Here's what I get:

    Error [101] c:\pbp\pbppi14e.lib 104: ERROR: (invalid OSC Define.)
    Error [113] c:\pbp\pbppi14e.lib 4992 : symbol not previously defined (PAUSEUSL)
    Error [113] c:\pbp\pbppi14e.lib 6192 : symbol not previously defined (PAUSEUSL)
    Error [113] c:\pbp\pbppi14e.lib 5604 : symbol not previously defined (PAUSEUSL)

    The manual says a 25 MHz clock is fine, and the devices say a 25 MHz clock is fine.... What now?

    PBP 2.60C

    I stress again, the code works fine on the 16 MHz internal clock.

    Any ideas?

  2. #2
    Join Date
    Jan 2005
    Location
    Montreal, Quebec, Canada
    Posts
    2,597


    Did you find this post helpful? Yes | No

    Default Re: pbppi14e.lib problem

    Posting your code might help.

    Robert

  3. #3
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959


    Did you find this post helpful? Yes | No

    Default Re: pbppi14e.lib problem

    25Mhz is valid on 18F parts, but not on the "Enhanced Core" devices (12F1,16F1).

    For the enhanced core devices ... 3.58(3),4,8,10,12,16,20,24 and 32Mhz are supported.
    DT

  4. #4
    Join Date
    Dec 2010
    Posts
    409


    Did you find this post helpful? Yes | No

    Default Re: pbppi14e.lib problem

    Thanks, Darrel.

    Bummer.
    Well, I don't have any timing critical operations once I'm finished debugging, so perhaps I'll lie to PBP - tell it it's running 24 MHZ but really run it on 25 MHz. As long as I manage my timings outside PBP, all should be fine.

    Another adventure!

  5. #5
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959


    Did you find this post helpful? Yes | No

    Default Re: pbppi14e.lib problem

    If nothing has critical timing ... you could run it at 32Mhz from the internal oscillator and dump the crystal and caps.
    Which also frees up 2 I/O pins.

    Contrary to popular belief, the internal oscillators are pretty accurate these days.
    You can even debug through a serial port that way.
    DT

Similar Threads

  1. Code in PBPPI18L.LIB, can I ?
    By amgen in forum PBP Extensions
    Replies: 8
    Last Post: - 13th June 2014, 13:54
  2. Replies: 0
    Last Post: - 21st October 2011, 01:33
  3. WRITE error in 18l.lib
    By Rogerio in forum mel PIC BASIC Pro
    Replies: 6
    Last Post: - 18th March 2010, 00:00
  4. error in pbppic14.lib after re-installing xp
    By comwarrior in forum mel PIC BASIC Pro
    Replies: 1
    Last Post: - 27th November 2009, 01:13
  5. Erron in PBPPIC14.LIB
    By ruijc in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 21st January 2008, 16:14

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