gnupic: Re: [gnupic] code directive question


Previous by date: 9 Sep 2005 18:34:56 +0100 Breadboard question (gpsim), wayne
Next by date: 9 Sep 2005 18:34:56 +0100 Re: [gnupic] code directive question, Ben Dugan
Previous in thread: 9 Sep 2005 18:34:56 +0100 Re: [gnupic] code directive question, Ben Dugan
Next in thread: 9 Sep 2005 18:34:56 +0100 Re: [gnupic] code directive question, Ben Dugan

Subject: Re: [gnupic] code directive question
From: Peter Onion ####@####.####
Date: 9 Sep 2005 18:34:56 +0100
Message-Id: <1126287268.5786.26.camel@HP.RoomLan>

On Fri, 2005-09-09 at 12:04 -0400, Ben Dugan wrote:
> > That's because interrupt vectors ARE NOT relocatable ;)
> > 
> > Try using relocation for some code that can be relocated and you'll
> > start to see the advantages.
> 
> 
> Yes, I understand that.  But I thought one advantage would be that I 
> could write the program in such a way that I could move it, say, from a 
> picdem board (with its linker script) to some other board or chip 
> architecture (with a different linker script) and just changing the 
> linker script would relocate things correctly.

It will do.  You'll have to name the segment you want to go in fixed
places and use the linker script to place it at the desired location for
the different targets.

I don't have the linker scripts to hand at the moment so I can't look
for an example but there are probably some segments already named for
the reset and interrupt vectors.

Peter 


Previous by date: 9 Sep 2005 18:34:56 +0100 Breadboard question (gpsim), wayne
Next by date: 9 Sep 2005 18:34:56 +0100 Re: [gnupic] code directive question, Ben Dugan
Previous in thread: 9 Sep 2005 18:34:56 +0100 Re: [gnupic] code directive question, Ben Dugan
Next in thread: 9 Sep 2005 18:34:56 +0100 Re: [gnupic] code directive question, Ben Dugan


Powered by ezmlm-browse 0.20.