Yahoo Groups archive

Lpc2000

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

Message

Re: [lpc2000] Polling for data reception

2006-03-04 by Richard Duits

I don't know anything about the USB controller, because I never used an 
LPC214x. All I know that you can poll if an interrupt routine would be 
called if you enabled the interrupt, by reading the VICRawIntr register.

Regards,
Richard.


Manisha wrote:
> Hi Richard,
>
> thanks a lot for the reply.
> i was going through this VICRawIntr register. but, somehow i got confused
> about the bits. the 22nd bit is for USB, but, for which interrupt, is it
> specific for data in endpointOUT or it can be any inetrrupt. i could not
> find any specific about this. it will be helpful for me if you share
> something more about this.
>
> again thanks a lot.
>
> regards
> Manisha Kalita
>
>
>
> -----Original Message-----
> From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
> Of Richard Duits
> Sent: Saturday, March 04, 2006 2:24 PM
> To: lpc2000@yahoogroups.com
> Subject: Re: [lpc2000] Polling for data reception
>
>
> You can always use the VICRawIntr register to poll the status of any
> interrupt, even those that are not enabled.
>
> Regards,
> Richard.
>
> Manisha wrote:
> > hi all,
> >
> > i am designing a USB driver code in LPC2148 board. whenever the USB port
> > receives any data, it generates an interrupt.
> >
> > However, i want to design my code by polling method, i dont want any 
> extra
> > running context i.e an extra ISR. but as i found in the manual the 
> bit in
> > the endpoint interrupt status register only indicates the reception. is
> > there any other bit or other CSR(Control status register) where i 
> can get
> > indication for data reception and use that bit for polling?
> >
> > Thanks for going through the problem.
> >
> > please help me if anyone has any idea.
> >
> > Regards
> >
> > Manisha
> >

Attachments

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.