Re: LPC2138 timers
- From: "Peter Dickerson" <first{dot}surname@xxxxxxxxx>
- Date: Thu, 29 Jun 2006 20:00:04 GMT
"Frank van Eijkelenburg" <someone@xxxxxxxxxxxxxxxx> wrote in message
news:44A3FC9B.5010001@xxxxxxxxxxxxxxxxxxx
Peter Dickerson wrote:[snip]
so
You shouldn't need to reset the timer at all. You want it to keep going
latencythat the results are entiely based on hardware timing without and
wouldissues (except to respond to the interrupt before the next capture is
expected).
Peter
Hi Peter,
thank you for the idea. If the timer was used only for measurement, it
work I guess. However, the timer is also used as timeout timer (if for along
period no edges are detected a timeout occures). I could manually detectif the
timeout period is elapsed, but this should be done outside the interruptservice
routine. Anyway, automatically reset the timer would be the best solution,but I
am afraid it isn't possible?!
So use two timers. Don't reset the input capture one but reset the timout
one. That way you'll get both the timeout and the timing to the nearest clk.
Peter
.
- Follow-Ups:
- Re: LPC2138 timers
- From: Peter Dickerson
- Re: LPC2138 timers
- References:
- LPC2138 timers
- From: Frank van Eijkelenburg
- Re: LPC2138 timers
- From: Peter Dickerson
- Re: LPC2138 timers
- From: Frank van Eijkelenburg
- LPC2138 timers
- Prev by Date: Re: LPC2138 timers
- Next by Date: Seeking for suggestions from embedded professionals
- Previous by thread: Re: LPC2138 timers
- Next by thread: Re: LPC2138 timers
- Index(es):