public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Ivan Griffin" <ivan.griffin@parthus.com>
To: "Gary Thomas" <gthomas@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] cyg_interrupt_set_vsr and ARM AEB-1
Date: Tue, 30 May 2000 13:55:00 -0000	[thread overview]
Message-ID: <001801bfca79$78fd8f40$ef0fa8c0@sslinc.com> (raw)
In-Reply-To: <XFMail.000530143457.gthomas@redhat.com>

woops, perhaps I should have been a bit more descriptive the first time
around.

The IRQ Handler should flash the LEDs on the AEB every 800 interrupts
 - each
interrupt comes from an external hardware source about every
milli-second]
This does not happen.

However, the code is verified using the ARM compiler (minus eCos, using
a simple scheduler).

I'm using a stripped binary, downloaded via the ARM Multi-ICE and ADW
for Windows
(a real pain to debug -- using the symbols !) -- so I can see that the
non-interrupt related
portion of the software is running correctly.

Is there some reason these interrupts would still be hooked by eCos for
some purpose?
Or is it possible that output port C of the PPI on the AEB is being
setup not to drive
the LEDs?

Regards,
Ivan.

----- Original Message -----
From: Gary Thomas <gthomas@redhat.com>
To: Ivan Griffin <ivan.griffin@parthus.com>
Cc: <ecos-discuss@sourceware.cygnus.com>
Sent: Tuesday, May 30, 2000 9:34 PM
Subject: RE: [ECOS] cyg_interrupt_set_vsr and ARM AEB-1


>
> On 30-May-00 Ivan Griffin wrote:
> > I'm trying to do the following in cyg_prestart() to hook the IRQ and
FIQ
> > interrupts on the ARM AEB-7.  Can anyone tell me why the following
code
> > doesn't appear to work?
> >
> >#define ARM_IRQ_INTR 0x18
> >#define ARM_FIQ_INTR 0x1c
> >
> > extern void IRQ_Veneer(void);
> > extern void FIQ_Handler(void);
> >
> > void cyg_prestart(void)
> > {
> >     cyg_interrupt_disable();
> >     cyg_interrupt_set_vsr(ARM_IRQ_INTR, (cyg_VSR_t*)IRQ_Veneer);
> >     cyg_interrupt_set_vsr(ARM_FIQ_INTR, (cyg_VSR_t*)FIQ_Handler);
> >     cyg_interrupt_enable();
> > }
> >
>
> What does it appear to do [if not work]?
>

  reply	other threads:[~2000-05-30 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-30 13:27 Ivan Griffin
2000-05-30 13:35 ` Gary Thomas
2000-05-30 13:55   ` Ivan Griffin [this message]
2000-05-31  6:00 ` Hugo Tyson
2001-09-05  0:10   ` Hugo Tyson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001801bfca79$78fd8f40$ef0fa8c0@sslinc.com' \
    --to=ivan.griffin@parthus.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).