From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=BAYES_00,INVALID_MSGID, MSGID_RANDY autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a79e3b493c2ba811 X-Google-Attributes: gid103376,public From: Martin Gangkofer Subject: Re: Interrupt Handlers using GNAT-VxWorks? Date: 1999/10/15 Message-ID: <7u6hc1$v2e$1@nnrp1.deja.com>#1/1 X-Deja-AN: 536953367 References: <7u500m$e96@niven.ksc.nasa.gov> X-Http-Proxy: 1.0 www-proxy.frankfurt.de.uu.net:3128 (Squid/2.2.STABLE3), 1.0 x37.deja.com:80 (Squid/1.1.22) for client 195.124.164.3, 192.76.144.140 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Fri Oct 15 06:25:13 1999 GMT X-MyDeja-Info: XMYDJUIDmttg Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.06 [en] (WinNT; I ;Nav) Date: 1999-10-15T00:00:00+00:00 List-Id: In article <7u500m$e96@niven.ksc.nasa.gov>, "John Arnsparger" wrote: > I am trying to attach an interrupt handler (procedure) to Vector #29 > (decimal) on the mvme167 > board using Ada95 "protected" constructs. I have tried > Ada.Interrupts.Attach_Handler, > which results in "Program_Error: Trying to overwrite a static Interrupt > Handler" with a dynamic handler". > > I have also tried the "pragma Attach_Handler", which produces a run-time > error saying > "Unitialized Interrupt". > > Both of these were declared in package bodies. > > Does anyone have any helpful hints or examples of successfully doing this > with GNAT-Works m68K? Or pointers to better references than the LRM? :-) > > Thanks. > > John M. Arnsparger > Lockheed Martin Space Operations > e-mail john.arnsparger1@jsc.nasa.gov > Phone (281) 244 9693 > Fax (281) 244 9681 > > I actually have had the same problem using APEX/Tornado on top of VxWorks. As I remember there was a package named ada.interrupts.rational.handler.dependent.1.ada This package contains a handler table, which selects, which interrupts are legal interrupts and which are not. On illegal interrupts a Program_Error is raised. Unfortunately, after I made this change, the problem did relax (I think before I got a Program_Error on call to any routine in Ada.Interrupts), but there were still Program_Errors raised when I tried to attach an interrupt handler. RATIONAL support obviously was not not able to solve this problem, which was critical to the project I was working on, within half a year! So I was forced to do a bloody, unstable workaround using a C procedure and Vxworks interrupt service connect. This experience was one reason for us to select gnat for our next project starting end of the year. Therefore I would be happy if you could keep me informed via email or this newsgroup, whether or gnat support (ACT) could solve the problem. -- Martin Gangkofer, System Engineer ESG Elektroniksystem und -Logistik GmbH, Dept.EF-E eMail: mgangkof@esg-gmbh.de Tel: +49 89 9216 2176 Sent via Deja.com http://www.deja.com/ Before you buy.