>Does the ICD execute extra cycles ONLY when processing
>a breakpoint or stepping etc, when the debugger has to
>communicate with the host or does it run a few cycles
>all the time in the background? (Sorry if this is in
>the doc's I'm not at home to look them up)

This should only be a problem while in the ICD code. Just remember that it
is a program in your programming space that has been enabled by a special
bit of hardware that has in effect caused a special interrupt.

>I'm trying to get a constant 10ms interrupt that will
>sample my ADC inputs and then spend the rest of the
>time processing the data and displaying on an LCD
>screen (which is slow!) Obviously I do not want this
>to vary as it's my main sampling rate.

Well I would say that to do this you are best to get the operations to a
point where they work correctly, i.e. the A/D operation, and the LCD
operation, and then dispense with the ICD and have printf(debug message)
messages going over a serial interface to a terminal when you let it rip so
you are not stopping your code.

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