16f946

[Darrel Taylor]

You should only use HIGH, LOW or TOGGLE on physical PINs.

Using HIGH on any other register will cause it to clear a bit in another register that you didn't specify. PBP thinks it's clearing a TRIS bit, but that's only the case if a PIN is used.

For instance, writing HIGH LCDDATA5.2 will also clear LCDDATA17.2

HIGH LCDDATA8.3 will clear LCDDATA20.3
... and even worse ...
HIGH LCDDATA12.0 will clear T1CON.0, which turns off Timer1 if running.
All kinds of strange things can happen.

LCDDATA12.0 = 1 would work much better.
<br>

[jderson]

Thank you, Darrel! You're GREAT, as usual.

[jderson]

Characters display perfectly now, thank you. Only one slight problem- when I compile with MPASM, I get the following warning: "Warning[219]c:\pbp\pbppic14.lib 905 : Invalid RAM location specified." Is this anything to be concerned with? I want to use MPASM so that I can use DT Instant Interrupts.

[Darrel Taylor]

Is this anything to be concerned with?

Yes it is.

The error is from a MOVE?CT macro. So one of the LCDDATAxx.x = 1 statements may have been edited wrong.

If you look in the .LST file, and search for "Warning", you should see which one caused it from the line following the warning message.
<br>

[jderson]

Fixed it, thank you!

[jderson]

I have been trying to make an "INCLUDE" file containing all the various LCDDATA subroutines, but the compiler doesn't like it because LCDDATA is processor-specific, apparently. How is this done?

[Darrel Taylor]

Not sure what you mean, but ...

The Main file that you are compiling determines the processor for all the include files too.

If you are trying to compile the include file by itself, you probably just need to change the chip in the drop-down box in MicroCode Studio.
<br>