Read the newbee threads, 16F877A no go.

[BobbyA]

I still stand by the comment that 8 variations of:

Error c:\pbp\pbppic14.lib 2827 : [225] Undefined Symbol 'PAUSEUS'

Is just a goofy error msg for having selected an illegal clock speed.

Bobby

[mister_e]

I can agree. It should be something like illegal crystal speed definition but, once you know the problem source... it will never happen again. Well i guess.

[BobbyA]

I can agree. It should be something like illegal crystal speed definition but, once you know the problem source... it will never happen again. Well i guess.

Hi Steve,

I'd be willing to make a small wager, perhaps a drink, that if another assembler were selected the same mistake would produce a different error.
Call me a cynic but I'll go double or nothing that it's equally obsure...

BR,
Bobby

[mister_e]

you know, in ALL programming language, error message are often helpfull but often they wouldn't point you the exact line or part of code where the error is. It's amazing what a missplaced or missing ENDIF, WEND, Variable declaration could do also

here's a reaally short example

b1 var byte

I2cread PORTB.0,PORTB.1,0,0,[b1]

try this as is. Without anything else It compile O.K right ???

Now remove the first line and compile the code and see what's happen

ERROR Line 3: Expected '['. (a.bas)

[NavMicroSystems]

I'd be willing to make a small wager, perhaps a drink, that if another assembler were selected the same mistake would produce a different error.

For sure, different systems produce different (nonsense) Error Messages.

The best one I have ever seen was:

A Nonexistent error has occured in Module xxxxx at Address yyyy

(Guess what: It was Intel Hardware running a Microsoft OS . . .)

[BobbyA]

Hi Ralph, I sit corrected, it does say somewhere the "acceptable clocks speeds are". Although in my defense you didn't find it first time either.

Steve, My favorite error occurs on a PC running MS too. If you remove the keyboard the error on POST is: Keyboard bad or missing, press F1 to continue.

By the way adding the other configuration switches to the .inc file didn't resolve the need to press reset to get the program to run. Still learning.

BR,
Bobby

[Melanie]

> For the 16F877A, the datasheet calls out many configuration bit switches that are not addressed in the c:\pbp\16F877A.INC file, when using PM.

Many? Name just one. Every item in the Configuration Word Address (Datasheet Register 14-1) is replicated in the PICBasic INC file. Try looking in \pbp\inc\M16f87XA.INC.

If you correctly read the FAQ, I wrote...

3.a. When using MeLabs default (PM) Assembler

Open up the PBP directory, and in it you will find an INC subdirectory. Opening that up and you'll see a heap of files. Find the Mxxxx.INC file for the PIC you're interested in... (example M12F675.INC). If you can’t locate your exact PIC, it might be listed under a family of PICs that share the same settings (example chose M16F62X.INC if you need the settings for a 16F628).

[BobbyA]

Hi Melanie,

As I said I'm a newbee to PBP, and it's still not clear to me the purpose of the c:\PBP\INC\M16F87xA.INC vs. the C:\PBP\16F877A.INC file.

I do know the suggested fix was to edit the xt_osc to be hs_osc in light of the clock speed used, and to check the Special Features section of the datasheet. While in the PIC datasheet I noticed there were other configuration bit options that didn't have entries in that file.
So I stand by the statement, "the datasheet calls out many configuration bit switches that are not addressed in the c:\pbp\16F877A.INC file, when using PM."

Maybe they don't need to be there, I'm not well versed yet on the effect each configuration bit has on PIC performance. I have to assume if they were not included in this file they are not critical for simple functioning, same with an initial set or cleared condition. This may yet lead me to grief.

BR,
Bobby