From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25578 invoked by alias); 26 Jun 2003 22:47:00 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 25567 invoked from network); 26 Jun 2003 22:46:59 -0000 Received: from unknown (HELO web12904.mail.yahoo.com) (216.136.174.71) by sources.redhat.com with SMTP; 26 Jun 2003 22:46:59 -0000 Message-ID: <20030626224659.41279.qmail@web12904.mail.yahoo.com> Received: from [131.151.65.140] by web12904.mail.yahoo.com via HTTP; Thu, 26 Jun 2003 15:46:59 PDT Date: Thu, 26 Jun 2003 22:47:00 -0000 From: Partha Palit Subject: Re: how to generate external interrupts To: "Frank Ch. Eigler" Cc: sid@sources.redhat.com In-Reply-To: <20030624191120.GC1520@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-q2/txt/msg00057.txt.bz2 Hello, Thank you Frank for showing the direction to generating an external interrupt. Kindly advise if my approach is correct. I edited the sid.conf as follows- new sid-sched-sim sensor-sched //then I set the num clients to 5... //then connected the sched event to the intrctrl... connect-pin sensor-sched 1-event -> intrctrl source-16 //then I appropriately set the 'regular' and 'time' attributes. The problem is that I am unable to catch the interrupt.I am using eCos as the RTOS. In my program, I register an ISR at "vector 16". Is this correct ? I saw some memory mapping for the timers and UART in the SID config file. Do I have to do somehing like that? Also, when I checked the eCos header file (hal_intr.h), max interrupts were set to 8.If,possible could you kindly comment on this? P.S: my platform - ARM-PID. Thanks for your time. -Partha --- "Frank Ch. Eigler" wrote: > Hi - > > > >How would you prefer to cause interrupts? > > > > I want to simulate a periodic interrupt( > specifically, > > I want to be able to count the heart beats [...] > > OK. > > > Hence, I guess a script or a program would be > > a suitable way to do it. > > That's possible, but not necessary for this context. > > Probably the easiest thing to do is to use one of > the > sid scheduler objects to supply the periodic > interrupt. > You would have to decide whether you would like > these > interrupts based on the progression of host (real) > time, > versus target (simulated) time. Then, you'd pick a > suitable time interval, in milliseconds or clock > ticks > respectively. Then you'd arrange to get the chosen > scheduler to send out a ping at the chosen interval > to the appropriate interrupt input pin. This latter > bit is most easily done by emitting and editing the > sid configuration file that otherwise models your > desired system. > > > > Presently,I am reading through the SID user > manual. Is > > there any other documentation, which can be > helpful? > > The other two families of documentation that you may > find > helpful consist of a guide on developing sid > components and > the set of individual component reference pages. > These may > all be found on the sid project web page. > > > - FChE > > ATTACHMENT part 2 application/pgp-signature __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com