-
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?
-
Re: pbppi14e.lib problem
Posting your code might help.
Robert
-
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.
-
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!
-
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.