File registers.

Accessing registers in Bank1: You’ll have noticed in that some registers like option are in what they refer to as Bank1, as opposed to Bank 0. Others, like status are in both Banks. What this means in practical terms, is that these Bank 1 registers are not normally available, because our default sphere of operations is Bank 0. We use the status register to effect a switch between banks, with RP0 & RP1 (STATUS<5> & <6>) doing the trick. This simply means that we must set RP1 to go to Bank1 and clear it to return. For those registers which are in both banks, you can of course access them no matter where you are, but remember the register has 2 different addresses: status is known as h’03’ and h’83’.

From Programming the PIC16F84
http://www.piclist.com/techref/microchip/davidtait/picprog.html

There are 80 RAM locations in the 16F84. RAM is where you put your variables. The only way to change these RAM locations is through instructions. You don't load RAM from outside as in a 'regular' computer. The information in RAM disappears when power is removed. The first 12 RAM locations, ($00 - $0B), have internal registers mapped to them. Changing these locations with instructions changes the corresponding registers. Microchip calls RAM locations 'files' or 'registers' and uses the symbol 'f' when referring to them. The remaining 68 locations can be used for your variables. Microchip calls the first 12 locations special function registers and the remaining 68 general purpose registers.

Five special function registers are not among the first twelve addresses, not even among the 80 . Because of something called 'banking' you have to set a bit in the byte at RAM location 3 to reach them. This location is called STATUS and the bit, (bit 5), is called RP0. If RP0 is zero you are in bank 0, if it is 1 you are in bank 1. For your own variables it doesn't matter which bank is in use because they are mapped to both banks. For some of the first 12 locations it does matter. Seven of the 12 are mapped to both banks but five are not; so location 5 for example has two meanings depending on RP0. If RP0 is clear, ( bank 0 ), location 5 refers to the data on PORT A. IF RP0 is set, ( bank 1 ), location 5 refers to the direction register TRISA that tells which bits of PORTA are inputs and which are outputs.

Much of this complication can be avoided by using two instructions that Microchip indicates it might not support in future products. The TRIS instruction can be used to set the port direction registers and OPTION can be used to set the OPTION register which deals mainly with timer operations. If you port your code to future Microchip processors that don't support these instructions, you will probably want to rewrite the code for some other reason anyway.

Questions:

• solly-o at spamwebmail.co.za asks: " how does TMRO work if i have an incoming frequency." +
• /techref/microchip/mplab/msg302.htm Sometimes MPASM gives a Message [302] when you mess up the bank select ... but all to often MPASM gives no warning that I've selected the wrong bank.
  
  +

Comments:

• Paragraph 1: "we must set RP1 to go to Bank1 and clear it to return" is incorrect. To go to bank 1, RP1 must be clear and RP0 must be set.+
• /techref/microchip/fsr.htm Some people access file registers indirectly, through the FSR and its own special dedicated bank select bits.+
• /techref/microchip/pages.htm There's 3 different sets of memory select bits:
  use banksel to set the appropriate bank to access RAM and SFRs with most instructions
  use ???[FIXME:]??? to set the appropriate bank when accessing RAM with the FSR pointer.
  use pagesel to set the appropriate page for CALL and GOTO.
  +
• /techref/microchip/mpasm.htm has some code that warns me when I try to put too many variables in the same bank. (Move that code to *this* page).+
• /techref/microchip/12xfsr.htm describes bank select and pointer manipulation (FSR) for the PIC-12 -- anything useful for other chips ?+
• /techref/microchip/mplab/msg302.htm All too often I have the wrong bank selected.
  Sometimes MPASM warns me with
  Message [302]
  but all to often it compiles and runs with no error messages (it just doesn't work right).+

  .