For many 18F projects one can mainly ignore data banking, if you use a certain memory allocation scheme: 1: Use the 'access' page to get access to low memory and SFR's 2: Set the BSR to point to a bank (say bank 1) and leave it there. 3: Use the remaining banks to store larger buffers, arrays, and perhaps a data stack accessed via the FSR's. Now you have immediate access to about 384 bytes of directly accessible variables and simple access to the larger buffers via FSR. Very simple to do. Bob Ammerman RAm Systems ----- Original Message ----- From: "Brendan Moran" To: Sent: Monday, August 19, 2002 4:02 PM Subject: Re: [PIC]: First pic project > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > Because the 18F series solves alot of the > > > "interesting" issues you would > > > have to learn about with the 16F's (and earlier). A very short > > > list: banking, the read write thing, and others. Also the 18F is > > > > --^^^^^^^ misconception error > > > > 18f *does* use (register) banking. but it uses no (code) paging, > > just limited-range braching. > > Thanks for pointing that out, Wouter. I got a little burned by that > in a post last week. (: > > The more often misconceptions are dispelled, the less often they > cause problems. > > - --Brendan > > -----BEGIN PGP SIGNATURE----- > Version: PGPfreeware 6.5.8 for non-commercial use > > iQA/AwUBPWFO7AVk8xtQuK+BEQLXpQCfW+gRHPThzN0NnCCbTEN4IcRF+BcAoIwB > NHCNJetk0z04Bsi02NcE8vtI > =LY2e > -----END PGP SIGNATURE----- > > -- > http://www.piclist.com hint: To leave the PICList > mailto:piclist-unsubscribe-request@mitvma.mit.edu > > -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu