gnupic@linuxhacker.org

MPASM (the windows assembler from Microchip that comes with MPLAB) has
always generated that message.  While you may have the code to set the
page bits right above, who says you didn't jump to that address
indirectly (by adding to the PCL register)?  The assembler does not want
(and should not have to) keep track of those sorts of things, so anytime
you access an item in a bank other than bank 0, that message will be
generated.

I believe gpasm has been working toward giving the exact same
errors/warnings/messages as MPASM, which might explain why you see these
warnings now and not in an earlier version of gpasm.

I usually leave the messages, because there have been a few times where
I did indeed forget to set the page bits.  If they annoy you too much,
you can turn them off by number, eg. to turn off warning 302, you might
add to your .asm file:

	errorlevel 1
or
	errorlevel -302

The errorlevel 1 seeting only prints warnings and errors (but not
messages).  The -302 specifically turns off message #302.

Because gpasm follows MPASM quite closely, I often refer to Microchip's
MPASM User Guide (downloadable from their site).  It does, for example,
explain what message 302 is all about.

-SamCo

On Fri, 2003-06-13 at 22:40, Tom Jennings wrote:
> I upgraded to 0.11.0 gpasm, and now have a problem I'm sure is an I/O
> problem (Idiot Operator):
> 
> 
> The sequence:
> 
> 
> 	bcf STATUS, RP1
> 	bsf STATUS, RP0
> 	movlw 0
> 	movwf TRISB
> 
> generates the error/warning:
> 
> Message [302]: Register in operand not in bank 0. Ensure bank bits are
> correct.
> 
> The PDF makes no mention of message 302. If gpasm is going to second
> guess me, shouldn't it notice I set RP0 and RP1 correctly to get at
> TRISB? Or is there a magic Simon Says order (instruction) required?
> 
> 0.0.99 didn't exhibit this. The program runs fine.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gnupic-unsubscribe@linuxhacker.org
> For additional commands, e-mail: gnupic-help@linuxhacker.org
>