>Why stop the timer, btw?  Reads do not (read: should) affect the count.
> Read the low byte into W, put it into another register, then get the
>high byte - the counter can't go fast enough to increment the high byte
>by the time it executes 3 instructions - and the interrupt latency could
>even be accounted for...

Oh yes it can !!

Consider what happens when you read the low byte, which happens to be FF

in the middle of the 3 instructions you talk about, an edge occurs that
causes the counter to increment.

What has happened to the total count as read in terms of what you think you
actually read? I think you will find a difference of 256 in there somewhere.

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads