Exact match. Not showing close matches.
'[PIC] 16F88 Setting I/O - "Register in operand not'
I'm new (2 days now) to PICs and am working on a project that involves
reading weigand RFID signals, storing the ID numbers in memory then
transmitting them via RS232 to a computer in a big batch.
As a "build-up" to this, I'm trying to get an LED flasher to work, then an
RS232 broadcaster, then a weigand reader, then finally the weigand
I'm using a 16F88, as it seems to have more than enough capability and isn't
too expensive; programmed in assembly language in MPLAB. The code for the
LED flasher and RS232 are here:
The issue I have is with setting up the device I/O - this is the error I get
"Message C:\RFID\RS232.ASM 51 : Register in operand not in bank 0.
Ensure that bank bits are correct."
Page 15 of the datasheet says that TRISA, TRISB and ANSEL are in 'Bank 1'.
Page 11 describes the Settings for STATUA, RP0 and STATUS, RP1 needed for
I've played about with my code to no avail - I still get the error during
compile about the register not being in bank 0. (though it seems to simulate
Any chance somebody more experienced could take a quick peek at the code for
me please? (its lines 18 and 19 on the LED one, lines 51, 55 and 56 on the
RS232 one) Replies off-list would be great.
Marko (Mechanical Engineer/blacksmith trying his best at software)
PS - using the following exemple code from page 53 of the datasheet also
flags up the same compile errors:
BANKSEL PORTA ; select bank of PORTA
CLRF PORTA ; Initialize PORTA by
; clearing output
; data latches
BANKSEL ANSEL ; Select Bank of ANSEL
MOVLW 0x00 ; Configure all pins
MOVWF ANSEL ; as digital inputs
MOVLW 0xFF ; Value used to
; initialize data
MOVWF TRISA ; Set RA<7:0> as inputs
These are not errors, it is simply a message. Its a reminder, nothing more.
Don't worry about it.
> > "Message C:\RFID\RS232.ASM 51 : Register in operand
> > not in bank 0. Ensure that bank bits are correct."
Marko, as Bob said
> These are not errors, it is simply a message. Its a reminder, nothing
> Don't worry about it.
If this message becomes bothersome (for example there may be
so many you miss a real error message) you can turn it off
For more than one type eg
errorlevel -302, -305, -306
The responsibility then falls on you to know what's going on at
assembly time and that code has been written properly
There's more information in MPLAB, including
Help/Topics/MPASM Assembler/Errors, Assembler
Help/Topics/MPASM Assembler/Messages, Assembler
More... (looser matching)
- Last day of these posts
- In 2006
, 2007 only
- New search...