From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26488 invoked by alias); 9 Mar 2007 00:19:15 -0000 Received: (qmail 26480 invoked by uid 22791); 9 Mar 2007 00:19:14 -0000 X-Spam-Check-By: sourceware.org Received: from bay0-omc3-s1.bay0.hotmail.com (HELO bay0-omc3-s1.bay0.hotmail.com) (65.54.246.201) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 09 Mar 2007 00:19:08 +0000 Received: from hotmail.com ([64.4.48.102]) by bay0-omc3-s1.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2668); Thu, 8 Mar 2007 16:19:07 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 8 Mar 2007 16:19:07 -0800 Message-ID: Received: from 64.4.48.123 by by137fd.bay137.hotmail.msn.com with HTTP; Fri, 09 Mar 2007 00:19:05 GMT X-Sender: jetjiang@hotmail.com In-Reply-To: <9372163.post@talk.nabble.com> From: "jiang jet" To: neeraja.kothala@gmail.com Cc: ecos-discuss@ecos.sourceware.org Bcc: Date: Fri, 09 Mar 2007 00:19:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: RE: [ECOS] How to handle IRQ0 interrupt? X-SW-Source: 2007-03/txt/msg00076.txt.bz2 >From: Neeraja >To: ecos-discuss@ecos.sourceware.org >Subject: [ECOS] How to handle IRQ0 interrupt? >Date: Thu, 8 Mar 2007 02:34:26 -0800 (PST) > > >Hi, > I am working on at91rm9200 board. I want to catch the interrupt when the >button is pressed which is connected to IRQ0 line. > But what is happening is that when I run the application the interrupt isr >is being called always irrespective of the button press. > >Can anyone suggest me how to configure so that the interrupt comes only when >the button is pressed ? > I think it's hardware related..you have to assign interrupt number 0 to indicate the press of button >Here is the part of the code I am using > >interrupt = CYGNUM_HAL_INTERRUPT_IRQ0; >cyg_interrupt_create(interrupt, > 0, // Priority - what goes >here? > (cyg_addrword_t)0, // Data item passed to >interrupt handler > (cyg_ISR_t *)IRQ0_isr, > (cyg_DSR_t *)IRQ0_dsr, > &interrupt_handle, > &interrupt_object); > >cyg_interrupt_attach(interrupt_handle); >cyg_interrupt_acknowledge(interrupt); >cyg_interrupt_unmask(interrupt); > >Thanks, >Neeraja. > >-- >View this message in context: http://www.nabble.com/How-to-handle-IRQ0-interrupt--tf3368441.html#a9372163 >Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com. > > >-- >Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos >and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > _________________________________________________________________ ÏíÓÃÊÀ½çÉÏ×î´óµÄµç×ÓÓʼþϵͳ¡ª MSN Hotmail¡£ http://www.hotmail.com -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss