Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

Using multiple capture pins

Using multiple capture pins

2004-05-06 by bobbruce000

On the LPC2114, multiple pins can be assigned to a single
capture port.  For instance, capture channel 0 of timer0
can be triggered by P0.2, P0.22 or P0.30.

According to the manual, these triggers should work in
parallel, so a capture interrupt will be triggered from
any of them.  But I can't get that to work.  I only
get interrupts from the lowest enabled trigger.  So
if I enable P0.30 as a capture trigger it works fine.
But when I enable P0.2, then I no longer get interrupts
when there is a trigger on P0.30.

Has anyone else seen similar behavior?

    -bob

Re: Using multiple capture pins

2004-05-07 by philips_apps

Hello Bob,

Thank you for your input. What you have reported here is 
a "documentation bug". While editing source documents, wrong text was 
entered.

The right wording in the LPC2114 User Manual (February 03, 2004 
revision), table 121 on page 162, "Capture Signals " section should 
be:

"
 Capture functionality can be selected from a number of pins. When 
more than one pin is selected for a Capture input on a single 
TIMER0/1 channel, the pin with the lowest Port number is used. If for 
example in case of LPC2114 pins 30 (P0.6) and 46 (P0.16) are selected 
for CAP0.2, only pin 30 will be used by TIMER0 to perform CAP0.2 
function."

It is the same case with the LPC2119 and other CAN based LPC200 parts.

Few days ago an updated revision of User Manuals for all 64 and 144 
pin LPC2000 parts have been submitted for publishing to Philips web 
team and these documents are unfortunately going to be released 
without the input on capture functionality. However, the revision 
that will follow later on will have this included.

Regards,

Philips Apps Team




--- In lpc2000@yahoogroups.com, "bobbruce000" <bobbruce000@y...> 
wrote:
Show quoted textHide quoted text
> On the LPC2114, multiple pins can be assigned to a single
> capture port.  For instance, capture channel 0 of timer0
> can be triggered by P0.2, P0.22 or P0.30.
> 
> According to the manual, these triggers should work in
> parallel, so a capture interrupt will be triggered from
> any of them.  But I can't get that to work.  I only
> get interrupts from the lowest enabled trigger.  So
> if I enable P0.30 as a capture trigger it works fine.
> But when I enable P0.2, then I no longer get interrupts
> when there is a trigger on P0.30.
> 
> Has anyone else seen similar behavior?
> 
>     -bob

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.