Anyway, the MAP files should tell you what realy is
allocated and where.



Carl Denk wrote:
> I have the optimization turned off, so when the active time on the free 
> period is past, it still will compile. Code size isn't an issue, there 
> is plenty of code memory available. There are only 4 or 5 arrays, and 
> most are only 10, and one is 25 int's. Other variables I declare are 
> maybe 20, with only one long. The PIC watches 3 ADC's, scales the 
> values, and puts them out fiber optic to RS-485. The unit is slave on 
> the RS-485, checks 3 lead-in characters for identifying it's commands.
> 
> Olin Lathrop wrote:
>> Jan-Erik Soderholm wrote:
>>   
>>> In *this* particular case (18F1320) with only *one* RAM bank (half
>>> accessed via access-bank and half via BANK0), one can (as far as
>>> I understand) put the variables wherever one likes, then setup
>>> the BANK bits to point to BANK0.
>>>     
>> True if using MPASM where you know exactly what may be messing with the bank
>> register.  I don't know whether his compiler has a optimization for when
>> there is only a single bank to set the bank once and then assume the bank
>> register is always set to this single bank.
>>
>>
>> ********************************************************************
>> Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
>> (978) 742-9014.  Gold level PIC consultants since 2000.
>>   
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist