comp.lang.ada
 help / color / mirror / Atom feed
From: Ted Dennison <dennison@telepath.com>
Subject: Re: Interrupt Handler Problems
Date: 1999/07/08
Date: 1999-07-08T00:00:00+00:00	[thread overview]
Message-ID: <7m2a6c$bif$1@nnrp1.deja.com> (raw)
In-Reply-To: 1999Jul7.160434.10447@nosc.mil

In article <1999Jul7.160434.10447@nosc.mil>,
  claveman@cod.nosc.mil (Charles H. Sampson) wrote:
>      I'm working on a project that uses a Motorola MVME2700 board
> (PowerPC CPU), VxWorks, the Green Hills Ada 95 compiler, and a lot of
> military boards in the rack (NTDS cards, GPS interfaces, etc.).  This
is
> a porting effort, of Ada 83 code that is currently using a different
CPU
> and a different operating system.
>
>      We're having a terrible time getting our code running in the new
> environment.  The killer problem of the moment is interrupt handlers.
> (We have a lot of them.)  Our handlers have been modified into
protected
> procedures, as required by Green Hills, but they don't seem to be
seeing
> the interrupts.  Green Hills assures us that interrupts are enabled
when
> the main program begins executing.  However, when we enable them our-
> selves in a little test program, its interrupt handler begins working.
> When we enable them in our "real" code, VxWorks blows up with a
> workQPanic.  The three vendors are now in a finger-pointing contest
(the
> Navy term is ruder), each claiming that it's not their fault, it must
be
> caused by one of the others.
>
>      This is clearly not a general Ada issue; discussing it in this
fo-
> rum appears inappropriate.  If there's anybody who has worked with the
> same or a similar environment and would be willing to exchange email
on
> lessons learned and suggestions, I'd be happy to hear from them.
Please
> note that my email address in this post has been anti-spammed.
>
> 			    Charlie
> --
> ******
>
>      For an email response, my user name is "sampson" and my host
> is "spawar.navy.mil".
>

(crosspoted to comp.os.vxworks since it is relevant there too)

Well, my suggestions would be to try to get one simple Ada interrupt
handler working. Then try to get a simple C interrupt handler for your
device working. Then try to get an Ada interrupt handler for your device
working.

I gather that you have done at least some of that. Right?

--
T.E.D.


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.




  parent reply	other threads:[~1999-07-08  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1999Jul7.160434.10447@nosc.mil>
1999-07-08  0:00 ` Interrupt Handler Problems Marin David Condic
1999-07-09  0:00   ` Charles H. Sampson
1999-07-08  0:00 ` Robert Dewar
     [not found] ` <7m1787$9k$1@nnrp1.deja.com>
1999-07-08  0:00   ` John Duncan
1999-07-08  0:00 ` Ted Dennison [this message]
1999-07-09  0:00   ` Charles H. Sampson
1999-07-12  0:00     ` Ted Dennison
     [not found] ` <7m177r$9e$1@nnrp1.deja.com>
1999-07-09  0:00   ` Charles H. Sampson
1999-07-09  0:00 ` Charles H. Sampson
1999-08-19  0:00   ` Charles H. Sampson
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox