Searching \ for '[PIC]: MPLINK - Overlaying RAM space' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: 'MPLINK - Overlaying RAM space'.

Exact match. Not showing close matches.
PICList Thread
'[PIC]: MPLINK - Overlaying RAM space'
2002\08\29@011255 by Bob Barr

flavicon
face
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.
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
spam_OUTpiclist-unsubscribe-requestTakeThisOuTspammitvma.mit.edu


2002\08\29@080953 by Olin Lathrop

face picon face
First, please fix your mailer settings to not use quoted printable encoding.
Outlook Express displays your message fine, but won't put the "> " in front
of lines when I do a reply.  I would have responded in more detail, but that
would have been too much of a pain manually sticking the "> " in front of
each line.

> Is it possible to deliberately define overlapping memory areas in
> MPLAB?

Yes, see the assembler UDATA_OVR directive.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

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


2002\08\29@102637 by Simon Bryden

flavicon
face
On Thu, Aug 29, 2002 at 08:08:08AM -0400, Olin Lathrop wrote:
> First, please fix your mailer settings to not use quoted printable encoding.
> Outlook Express displays your message fine, but won't put the "> " in front
> of lines when I do a reply.  I would have responded in more detail, but that
> would have been too much of a pain manually sticking the "> " in front of
> each line.

The problem here is with the mail reader ;-)

You should try a decent client such as mutt which does not have this problem.

Simon.
---

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestspamKILLspammitvma.mit.edu


2002\08\29@112124 by Olin Lathrop

face picon face
> > First, please fix your mailer settings to not use quoted printable
encoding.
> > Outlook Express displays your message fine, but won't put the "> " in
front
> > of lines when I do a reply.  I would have responded in more detail, but
that
> > would have been too much of a pain manually sticking the "> " in front
of
> > each line.
>
> The problem here is with the mail reader ;-)

True, but MS Outlook Express is very widely used, so it makes sense to send
messages that work well with it, whether you like it or use it or not.
Besides that there is no excuse for sending message to this group in other
than PLAIN TEXT format, which works well with any mailer.

Also, he was asking me for a favor.  Remember the golden rule: He who has
the gold makes the rules.  In this case the "gold" is information.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

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


2002\08\29@132252 by Bob Barr

flavicon
face
On Thu, 29 Aug 2002 08:08:08 -0400, Olin Lathrop wrote:

>First, please fix your mailer settings to not use quoted printable encoding.
>Outlook Express displays your message fine, but won't put the "> " in front
>of lines when I do a reply.  I would have responded in more detail, but that
>would have been too much of a pain manually sticking the "> " in front of
>each line.

Sorry about that. I'll take a look at my Agent settings to see if I
have that option available. Thanks, you're the first person to mention
that my posts were inconvenient to reply to.

>
>> Is it possible to deliberately define overlapping memory areas in
>> MPLAB?
>
>Yes, see the assembler UDATA_OVR directive.
>

Thanks again. I'm away from my office at the moment but I'll download
another copy of the linker manual and do a search for that directive.


Regards, Bob

--
http://www.piclist.com hint: To leave the PICList
EraseMEpiclist-unsubscribe-requestspam_OUTspamTakeThisOuTmitvma.mit.edu


2002\08\29@142339 by Bob Barr

flavicon
face
On Thu, 29 Aug 2002 11:20:34 -0400, Olin Lathrop wrote:

>> > First, please fix your mailer settings to not use quoted printable
>encoding.
>> > Outlook Express displays your message fine, but won't put the "> " in
>front
>> > of lines when I do a reply.  I would have responded in more detail, but
>that
>> > would have been too much of a pain manually sticking the "> " in front
>of
>> > each line.
>>
>> The problem here is with the mail reader ;-)

Simon,
Nope, the problem is that I'm not sending messages the way I thought I
was.

>
>True, but MS Outlook Express is very widely used, so it makes sense to send
>messages that work well with it, whether you like it or use it or not.
>Besides that there is no excuse for sending message to this group in other
>than PLAIN TEXT format, which works well with any mailer.
>

Olin,
Agreed 100%. I had no idea that I *wasn't* sending plain text until
you pointed it out to me. (And I'm still not, unfortunately.) I
haven't been able to find an option setting to send plain text so I've
sent off a query to Forte tech-support to see what recommendations
they might have. I'd certainly prefer that my posts be as convenient
as possible for as many people on the list as I can. Plain text just
makes common sense to use.


>Also, he was asking me for a favor.  Remember the golden rule: He who has
>the gold makes the rules.  In this case the "gold" is information.

Yep, I was and it certainly is. Thanks again.


Regards, Bob
>
>
>*****************************************************************
>Embed Inc, embedded system specialists in Littleton Massachusetts
>(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: To leave the PICList
piclist-unsubscribe-requestspamspam_OUTmitvma.mit.edu


2002\08\29@151133 by Simon Bryden

flavicon
face
On Thu, Aug 29, 2002 at 11:08:30AM -0700, Bob Barr wrote:
> Simon,
> Nope, the problem is that I'm not sending messages the way I thought I
> was.
>
That may be so, but quoted-printable is a very commonly used encoding,
especially in countries which use characters which don't appear in the ascii
table and I don't think that having people reconfigure their clients to send
to the piclist is very scalable.
>
> Olin,
> Agreed 100%. I had no idea that I *wasn't* sending plain text until
> you pointed it out to me. (And I'm still not, unfortunately.) I
> haven't been able to find an option setting to send plain text so I've
> sent off a query to Forte tech-support to see what recommendations
> they might have. I'd certainly prefer that my posts be as convenient
> as possible for as many people on the list as I can. Plain text just
> makes common sense to use.
>
Agreed, but your post *was* plain text - it did not include any QP-style
encodings, as indeed it shouldn't if you send plain ascii messages. That's why
I have a problem with Microsoft making life difficult when there really
shouldn't be a problem.

>
> >Also, he was asking me for a favor.  Remember the golden rule: He who has
> >the gold makes the rules.  In this case the "gold" is information.
>
> Yep, I was and it certainly is. Thanks again.
>
Ok, but expect quoted-printable or 8-bit encoded messages from Europeans who
tend to use it more than Americans because of their alphabets. And remember,
they may hold the gold next time.

Simon.
---

--
http://www.piclist.com hint: To leave the PICList
@spam@piclist-unsubscribe-requestKILLspamspammitvma.mit.edu


2002\08\29@160130 by Olin Lathrop

face picon face
> Agreed 100%. I had no idea that I *wasn't* sending plain text until
> you pointed it out to me. (And I'm still not, unfortunately.)

Here are the relevant lines from the header of your earlier message:

> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: quoted-printable

This last line is the problem.  Just deleting it fixes it.  I deleted it
then re-imported the message into Outlook Express and it put the "> " in
front of every line when I replied to the message.  I agree this is really a
problem in OE's handling of the message, but nonetheless the problem is
there.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: To leave the PICList
KILLspampiclist-unsubscribe-requestKILLspamspammitvma.mit.edu


2002\08\29@162218 by Peter L. Peres

picon face
On Thu, 29 Aug 2002, Olin Lathrop wrote:

>> Agreed 100%. I had no idea that I *wasn't* sending plain text until
>> you pointed it out to me. (And I'm still not, unfortunately.)
>
>Here are the relevant lines from the header of your earlier message:
>
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=us-ascii
>> Content-Transfer-Encoding: quoted-printable
>
>This last line is the problem.  Just deleting it fixes it.  I deleted it
>then re-imported the message into Outlook Express and it put the "> " in
>front of every line when I replied to the message.  I agree this is really a
>problem in OE's handling of the message, but nonetheless the problem is
>there.

The quoted-printable conversion is applied by servers whenever there is
even a single non-ASCII character in a message sent with 7-bit encoding.
Setting 8-bit encoding by the sender fixes this. The sender should set
his/her charset to iso8859-1 (US english), or iso8859-2 (Latin 2) which
covers most corners (including foreign language characters that are often
used in names etc), send plain text, and 8 bits (not 7) if available.

Peter

--
http://www.piclist.com hint: To leave the PICList
RemoveMEpiclist-unsubscribe-requestTakeThisOuTspammitvma.mit.edu


More... (looser matching)
- Last day of these posts
- In 2002 , 2003 only
- Today
- New search...