Is it possible to deliberately define overlapping memory areas in
MPLAB? If so, can someone please point me towards some info on
overlaying RAM space in such a way that MPLINK will not fail on the
build?

I'm working on a 16C765 application that logs data in the field and
then downloads it via USB back at the office. The logging and USB
functions are mutually exclusive so I'm safe in sharing space between
my logged data and the USB variable space. (The buffer is written to
EEPROM for non-volatile storage.)

So far I've been unable to get my .lkr file configured to appease
MPLINK's insistence on non-overlapped RAM addresses. (I thought that
the SHAREBANK keyword might offer some hope but that doesn't seem to
be the case.)

I have been through the linker docs several times, googled 'til I'm
blue in the face, and prowled the piclist archive. If the info is out
there, I sure haven't been able to find it.=20

If I'm trying to do the impossible, I'd appreciate hearing that too.
(I know I can kludge a work-around; I just wanted to do it cleanly if
that's possible.)


Thanks, Bob

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu