public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Aaron Case" <aaron.case@dynazign.com>
To: "Gary Thomas" <gary@mlbassoc.com>
Cc: "Ecos-Discuss" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] EDB7312(ARM720T)  interrupts
Date: Mon, 17 Nov 2003 16:48:00 -0000	[thread overview]
Message-ID: <GBEOKKOEOGFDMKDFCHIMGENBCAAA.aaron.case@dynazign.com> (raw)
In-Reply-To: <1069084928.1961.10.camel@hermes>

inspection and a little pedantry

-----Original Message-----
From: Gary Thomas [mailto:gary@mlbassoc.com]
Sent: Monday, November 17, 2003 11:02 AM
To: Aaron Case
Cc: Andrew Lunn; Ecos-Discuss
Subject: RE: [ECOS] EDB7312(ARM720T) interrupts


On Mon, 2003-11-17 at 08:57, Aaron Case wrote:
> Hello,
>
> For purposes of updating the list I see now why it didnt work. I used the
> interrupt vector instead of the handle in the cyg_interrupt_attach() call.
> Refer to the bogus code I posted in the previous listing. Opps.
>

I'm curious how you found this?  by inspection?  did you try enabling
asserts?

> thanks,
> Aaron Case
>
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: Friday, November 14, 2003 5:13 PM
> To: Aaron Case
> Cc: Gary Thomas; Ecos-Discuss
> Subject: Re: [ECOS] EDB7312(ARM720T) interrupts
>
>
> On Fri, Nov 14, 2003 at 05:07:29PM -0500, Aaron Case wrote:
> > Gary,
> >
> > Many thanks, that cleared up my understanding of eCos interrupts a great
> > deal.  Although, I still cant seem to achieve software connectivity with
> the
> > eCos interrupt model.
> >
> > While testing my interrupt code I have observed that I can assert bits
in
> > the interrupt status register by sending characters to a UART. As well
as
> > enabling them with cyg_interrupt_unmask() call(see below).
> >
> > I, however, have not be able to get the ISR(and thus DSR) to execute(via
> > break points with my MAJIC ICE).
> >
> > In the case of the UART1 RX interrupt, I can send a character, verify
its
> > arrival at the buffer and FIFO, but no ISR or DSR is executed. Im
assuming
> > the problem is my software configuration(which is REALLY close to the
> Massa
> > text).  See code below.
>
> I don't see anywhere in your code where you program the serial chip to
> actually enable it to generate interrupts. Also, does eCos provide a
> serial driver for this chip? If so, that driver may already have the
> interrupt.
>
>         Andrew
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates



-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

      reply	other threads:[~2003-11-17 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-07 21:01 Aaron Case
2003-11-07 21:14 ` Gary Thomas
2003-11-07 22:05   ` Aaron Case
2003-11-07 23:00     ` Gary Thomas
2003-11-14 22:08       ` Aaron Case
2003-11-14 22:13         ` Andrew Lunn
2003-11-14 22:22           ` Aaron Case
2003-11-14 23:08             ` Gary Thomas
2003-11-17 15:57           ` Aaron Case
2003-11-17 16:02             ` Gary Thomas
2003-11-17 16:48               ` Aaron Case [this message]

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=GBEOKKOEOGFDMKDFCHIMGENBCAAA.aaron.case@dynazign.com \
    --to=aaron.case@dynazign.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gary@mlbassoc.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).