> -----Original Message-----
> From: spam_OUTpiclist-bouncesTakeThisOuTmit.edu
> [.....piclist-bouncesKILLspam@spam@mit.edu]On Behalf
> Of Mcgee, Mark
> Sent: 13 October 2004 16:24
> To: 'Microcontroller discussion list - Public.'
> Subject: RE: [PIC] ICD2 headers
>
>
> I've managed to get my project working with relocatable code
> now - it's not
> too bad really.
>
> Here's some things to consider that I've realised with help
> from this list:-
> i) You need to add the lnk script for your PIC to the linker
> ii) Don't use org, use code instead
> iii) Don't use cblock or equ, use udata instead
> iv) whenever you need to access something living/defined in
> another file use
> extern <label> in your file, and use global <label> to export
> the label from
> the owning file
> v) make include files for common constants and "include
> <myincludefile.inc>"
> where necessary.
>
> One thing I'm still not really sure about is the label/name
> given to a code
> section.  I see these appearing in the .map file (after
> enabling it in the
> build settings) with the name I've given each distinct code
> block, but how do
> I get the interrupt vector set up without doing this for 16F628A?
> "SomeIsrName code 0x004" - that still looks like an absolute
> declaration to
> me.  Or is there a standard name I should give like this;
> "isr_code code
> followed by goto real_isr_code", that'll ensure that the
> correct code gets
> placed at the interrupt vector?  Say I compile for another
> PIC model, will it
> adapt automatically?
>
> The MPLAB IDE docs on MPLINK aren't very useful at all here, I find.
>
> Regards,
> Mark
>
>
> > -----Original Message-----
> > From: piclist-bouncesKILLspammit.edu
> > [.....piclist-bouncesKILLspam.....mit.edu]On Behalf
> > Of Alan B. Pearce
> > Sent: 13 October 2004 14:09
> > To: PicList
> > Subject: [PIC] ICD2 headers
> >
> >
> > The headers available for using the ICD2 with -ICD versions
> > of the smaller
> > chips - do they come with an appropriate chip? The
> > instruction sheet on the
> > Microchip web site seems to imply that the chip is supplied
> > separately, but
> > I don't seem to be able to find the chips listed. However the
> > price of the
> > 12f675 version of the header seems to be enough (here in the
> > UK anyway) to
> > include the chip (I'm looking at GBP11.82 for the header after a 14%
> > discount, from Farnell Onecall).
> >
> > _______________________________________________
> > http://www.piclist.com
> > View/change your membership options at
> > mailman.mit.edu/mailman/listinfo/piclist
> >
>
> ==============================================================
> ================
> This message is for the sole use of the intended recipient.
> If you received
> this message in error please delete it and notify us. If this
> message was
> misdirected, CSFB does not waive any confidentiality or
> privilege. CSFB
> retains and monitors electronic communications sent through
> its network.
> Instructions transmitted over this system are not binding on
> CSFB until they
> are confirmed by us. Message transmission is not guaranteed
> to be secure.
> ==============================================================
> ================
>
> _______________________________________________
> http://www.piclist.com
> View/change your membership options at
> mailman.mit.edu/mailman/listinfo/piclist
>

> -----Original Message-----
> From: EraseMEpiclist-bouncesspam_OUTTakeThisOuTmit.edu
> [piclist-bouncesspam_OUTmit.edu] On Behalf Of Mcgee, Mark
> Sent: Wednesday, October 13, 2004 11:48 AM
> To: 'Microcontroller discussion list - Public.'
> Subject: RE: [PIC] oops - splitting in to multiple files
>
>
> My apologies, must've replied to the wrong thread.
>
> Mark
>
> > -----Original Message-----
> > From: @spam@piclist-bouncesKILLspammit.edu
> > [KILLspampiclist-bouncesKILLspammit.edu]On Behalf
> > Of Mcgee, Mark
> > Sent: 13 October 2004 16:24
> > To: 'Microcontroller discussion list - Public.'
> > Subject: RE: [PIC] ICD2 headers
> >
> >
> > I've managed to get my project working with relocatable code
> > now - it's not
> > too bad really.
> >
> > Here's some things to consider that I've realised with help
> > from this list:-
> > i) You need to add the lnk script for your PIC to the linker
> > ii) Don't use org, use code instead
> > iii) Don't use cblock or equ, use udata instead
> > iv) whenever you need to access something living/defined in
> > another file use
> > extern <label> in your file, and use global <label> to export
> > the label from
> > the owning file
> > v) make include files for common constants and "include
> > <myincludefile.inc>"
> > where necessary.
> >
> > One thing I'm still not really sure about is the label/name
> > given to a code
> > section.  I see these appearing in the .map file (after
> > enabling it in the
> > build settings) with the name I've given each distinct code
> > block, but how do
> > I get the interrupt vector set up without doing this for 16F628A?
> > "SomeIsrName code 0x004" - that still looks like an absolute
> > declaration to
> > me.  Or is there a standard name I should give like this;
> > "isr_code code
> > followed by goto real_isr_code", that'll ensure that the
> > correct code gets
> > placed at the interrupt vector?  Say I compile for another
> > PIC model, will it
> > adapt automatically?
> >
> > The MPLAB IDE docs on MPLINK aren't very useful at all here, I find.
> >
> > Regards,
> > Mark
> >