>-----Original Message-----
>From: Richard S [mailto:rschul@MYREALBOX.COM]

>Code now looks like this (the Jinx one) but I get basically
>the same error with my other version. what do these unfatal
>failures mean I can't seem to find a sourse of information so
>I can understand for myself.
>
>Build Log:
>Deleting intermediary files... done.
>Executing: "C:\Program Files\MPLAB
>IDE\MCHIP_Tools\mpasmwin.exe" /q /p16F876
>"Binarycounter_876_V2.asm" /l"Binarycounter_876_V2.lst"
>/e"Binarycounter_876_V2.err" /c- Message[302] C:\16F876
>PROJECTS\BINARYCOUNTER_876_V2.ASM 24 : Register in operand not
>in bank 0.  Ensure that bank bits are correct. Message[302]
>C:\16F876 PROJECTS\BINARYCOUNTER_876_V2.ASM 25 : Register in
>operand not in bank 0.  Ensure that bank bits are correct.
>Message[302] C:\16F876 PROJECTS\BINARYCOUNTER_876_V2.ASM 36 :
>Register in operand not in bank 0.  Ensure that bank bits are
>correct. Message[302] C:\16F876
>PROJECTS\BINARYCOUNTER_876_V2.ASM 42 : Register in operand not
>in bank 0.  Ensure that bank bits are correct. Message[305]
>C:\16F876 PROJECTS\BINARYCOUNTER_876_V2.ASM 49 : Using default
>destination of 1 (file). Message[305] C:\16F876
>PROJECTS\BINARYCOUNTER_876_V2.ASM 54 : Using default
>destination of 1 (file). Loaded C:\16f876
>Projects\Binarycounter_876_V2.COD BUILD SUCCEEDED: Tue Mar 09
>09:11:43 2004


The assembler does not have the intelligence to keep track of which RAM bank
is selected.  Whenever you access a register that is not in Bank 0, the
assembler automaticaly spits out a warning, tell you to make sure that the
bank has been selected correctly, because it dosen't know.

Many people find this very annoying, but it is easy to remove the warning by
a couple of methods.  One is to use the errorlevel command within you source
code as follows:

errorlevel -302

This stops the assembler spitting out message 302.  You can re-enable it by
using errorlevel +302.  The trouble with this is that it is possible to be
writing or reading to completely the wrong bank and the assembler won't say
a word about it.

Another method is shown at
http://www.piclist.com/techref/microchip/mplab/msg302.htm  This at least
gives you some protection against making a silly banking error (that can
take hours to track down).

Once you have found you feet with basic use of the assembler, you may want
to start writing relocatable code.  A previous piclister Olin Lathrop, has
written a usefull set of tools that includes some macro's that (mostly) keep
track of your bank selection automaticly.  You can find them at
http://www.embedinc.com/pic/

Regards





=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================
Any questions about Bookham's E-Mail service should be directed to
postmaster@bookham.com.

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.