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).
>From: spam_OUTpiclist-bouncesTakeThisOuTmit.edu [.....piclist-bouncesKILLspam@firstname.lastname@example.org]
>On Behalf Of William Bross
>Sent: 13 October 2004 15:38
>To: 'Microcontroller discussion list - Public.'
>Subject: RE: [PIC] ICD2 headers
>All the ICD-2 headers come with the appropriate -ICD chip
>installed. They are all about 25 - 35 USD from DigiKey so
>about 12 GBP sounds about right.
Sounds cheap to me if that is the case, we normaly pay pound for dollar!
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist
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>"
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
The MPLAB IDE docs on MPLINK aren't very useful at all here, I find.