David Sprenkle wrote:


>Instead of beating my head against the wall on something really, really
>simple, I thought I would post my problem to the list.  What am I
>forgetting to do to Tris the a and b ports.  See code and error messages
>below.  This is on MPLAB 3.4.
> <snipped>
>Message[302] C:\DAVID\MPLAB\MOTORD~1\MOTOR.ASM 39 : Register in operand
>not in bank 0.  Ensure that bank bits are correct.
>Message[302] C:\DAVID\MPLAB\MOTORD~1\MOTOR.ASM 42 : Register in operand
>not in bank 0.  Ensure that bank bits are correct.


MPASM will warn about any access to other than bank 0. It does not have the
ability to track internally the RAM bank bits set at various points in the
program. This does get very irritating and I wrote a macro package which
fixes this, generating warnings only when there is a problem, including when
accessing bank 0 when another bank is selected. Microchip should have done
this from the start, but as it requires the programmer to tell the assembler
what to assume the bank registers are set to they probably figured they
would get complaints about it not generating warnings in when the programmer
misuses it.

Chip Weller