----- Original Message ----- From: "Peter Onion" Subject: Re: [PIC] 16F873 Program Memory Paging > I would say Yes, especially if you intend to move to using relocatable > code later on. I've just done this and learnt this the hard way ! Well, I would move to relocatable code sooner. You can manage this pagesel business somewhat by thinking through your app. If you need more than 2K of program, then you have lots of code. Presumably you have broken it up, and presumably there is some logic to how you have organized it. It is the nature of code that related code tends to have a lot of calls amongst related routines and relatively few calls from the outside. By placing related code within commonly named sections, you can use short calls for the calls within the group, and long calls outside. Your linker script can now manage where you plunk these sections in memory to avoid having one section unnecessarily cross a page boundary. Now, if you're just hacking away at some non-relocatable code and it is growing without bounds or planning, then what I suggest will be hard. But if you have architected your solution, this sort of organization simply supports your architecture and makes life a lot easier. --McD -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist