Hi Neil
Sorry if I'm being so dense (it would not be the first time)
I'm using an ICD2.
I did not understand the "Running att all through an ICD2"   (is this a
typo?)
What does the "Running att all" mean in regards to an ICD2?

I do the pulsing a bit high trick often to check the timing interval[s] of
my counters or to trigger the oscope when I enter a function so I can watch
for edges and levels at the moment of interest.
I did it also when I was working out the timing on the LCD.
 
Thanks much
 
Phillip
Things should be as simple as possible but no simpler
 
 
 
Phillip Coiner
CTO, GPS Source, Inc.
 
 
Your source for quality GNSS Networking Solutions and Design Services, Now!

-----Original Message-----
From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of
Neil Baylis
Sent: Wednesday, September 20, 2006 7:48 AM
To: Microcontroller discussion list - Public.
Subject: Re: Re: RE: RE: RE: FW: [PIC] Trouble getting my ISR high

'sceop' == scope, sorry.


On 9/20/06, Neil Baylis <neil.baylis@gmail.com> wrote:
> Phillip,
>
> ICD = In Circuit Debugger.
>
> If you don't have one, here's another thing you can try.
>
> You need an oscilloscope or logic probe:
>
> write a little assembler macro or function that pulses a spare output
> pin high then low. Call that macro at strategic spots in your code.
> Watch the sceop to see when it triggers.
> I use one that pulses a pin if the W register contains zero. Then,
> call the macro from places in my code where I'm not sure what's
> happening.
>
> Neil
>
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist